ISO/IEC 21617-1:2026 – Information technology - JPEG Trust - Part 1: Core foundation

ISO/IEC 21617-1:2026 defines a core foundation for establishing trust in media assets. Published in August 2026 by the joint technical committee responsible for audio, image, multimedia and hypermedia information coding, it addresses authenticity, provenance, attribution, intellectual property rights and integrity. This page gives testing engineers, procurement specialists and quality managers an interpretive overview of the standard, its scope and the practical considerations that follow from it.

Standard Information

Trust in digital media has become a procurement and quality concern as well as a technical one. ISO/IEC 21617-1:2026 responds to this by specifying a framework in which media assets carry secure and reliable annotations across their entire life cycle. The document is the core foundation part of the JPEG Trust work within ISO/IEC JTC 1/SC 29, the committee that develops coding standards for still images, audio and multimedia content. Its classification under information technology character sets and coding techniques places it in the family of standards dealing with how information is represented and protected. - Designation: ISO/IEC 21617-1:2026
- Full title: Information technology - JPEG Trust - Part 1: Core foundation
- Status: Current
- Publication date: 2026-08-26
- ICS classification: 35, 35.040, 35.040.30
- Technical committee: ISO/IEC JTC 1/SC 29

Scope and Application

The document specifies a framework for establishing trust in media. Within that framework, five aspects are addressed: authenticity, provenance, attribution, intellectual property rights and integrity. The mechanism is annotation of media assets in a secure and reliable manner, applied as those assets move through their life cycle rather than at a single fixed point. Because the framework follows media from creation onward, it applies wherever digital media is produced, exchanged, stored or consumed. Parties that capture images and video, platforms that redistribute them, archives that preserve them and enterprises that rely on them for records or commerce can all reference the same annotation-based foundation. The framework does not describe one specific product; it defines the structure that different implementations use to express trust-related information about a media asset. For quality managers, the practical consequence is that conformity discussions centre on whether a system attaches and maintains the annotations correctly. For testing engineers, the relevant questions concern how those annotations are structured, secured and verified, since the framework treats the annotation as the carrier of authenticity, provenance, attribution, rights and integrity information.

Products and Materials Covered

The standard is a framework document rather than a specification for a physical product. The objects it covers are media assets — digital content such as images and other media handled by JPEG-family technologies — together with the annotation constructs attached to them. No material, component or equipment family falls within its scope in the way that hardware standards cover cables, connectors or tools. The ICS classification confirms this orientation. Class 35 covers information technology as a whole, while 35.040 concerns character sets and information coding, and 35.040.30 addresses coding of graphical and geographical information more specifically. Systems, software tools and services that create, process or consume annotated media therefore form the practical product landscape around this standard, even though the document itself specifies the framework rather than any single implementation.

Testing and Compliance Considerations

Conformity work with a framework standard of this kind differs from pass-fail product testing. An accredited laboratory or assessment body typically begins by reviewing the implementation against the framework's structural requirements: which trust aspects are represented, how annotations are attached and how they are protected against modification. Documentation review therefore carries substantial weight alongside functional verification. For type testing or acceptance verification, engineers establish traceability between the claimed trust properties and the annotations actually present on sample media assets. Test documentation should record the asset set examined, the annotation structures observed and the verification steps performed. Where an implementation is updated in ways that affect annotation handling, retesting is triggered for the affected aspects rather than for the whole system. Cost drivers for assessment include the number of media asset types in scope, the number of trust aspects claimed and the depth of life-cycle coverage to be verified. When results are disputed, the usual course is a documented review of the test evidence, followed by retest of the specific annotation properties in question using agreed samples. Clear sampling agreements and written acceptance criteria, agreed befOre testing starts, reduce the risk of such disputes.

Related Standards and Series Context

The designation itself carries structural information. The number 21617 with the suffix -1 identifies the document as Part 1 of a multi-part series, and the title confirms that this part states the core foundation on which further parts of the JPEG Trust work are built. Later part numbers, where the series develops them, would address additional layers without redefining the foundation given here. The year 2026 in the designation marks this published edition. Under ISO/IEC designation practice, an edition year distinguishes the published version from any other, and readers citing the document should include it. The joint ISO/IEC prefix shows that the standard was developed through the combined technical programme of both organizations, within subcommittee SC 29 of joint technical committee JTC 1. Readers who need the authoritative text should obtain it through official ISO or IEC sales channels; this page is an interpretive overview only.