SIST EN 319 142-1 V1.3.1:2027
(Main)Electronic Signatures and Trust Infrastructures (ESI) - PAdES digital signatures - Part 1: Building blocks and PAdES baseline signatures
- Abstract
The present document specifies PAdES digital signatures. PAdES signatures build on PDF signature mechanisms defined in the ISO 32000 series. For documents conforming to ISO 32000-1 [1] PAdES utilizes an extended, alternative signature encoding. For documents conforming to ISO 32000-2 [9], these signature structures are incorporated natively by default within the core standard. Both approaches support digital signature formats equivalent to the signature format CAdES as specified in ETSI EN 319 122-1 [2], by incorporation of signed and unsigned attributes, which fulfil certain common requirements (such as the long term validity of digital signatures) in a number of use cases. The present document specifies formats for PAdES baseline signatures, which provide the basic features necessary for a wide range of business and governmental use cases for electronic procedures and communications to be applicable to a wide range of communities when there is a clear need for interoperability of digital signatures used in electronic documents. The present document defines four levels of PAdES baseline signatures addressing incremental requirements to maintain the validity of the signatures over the long term, in a way that a certain level always addresses all the requirements addressed at levels that are below it. Each level requires the presence of certain PAdES attributes, suitably profiled for reducing the optionality as much as possible. Procedures for creation, augmentation, and validation of PAdES digital signatures are out of scope and specified in ETSI EN 319 102-1 [10]. Guidance on creation, augmentation and validation of PAdES digital signatures including the usage of the different attributes defined in the present document is provided in ETSI TR 119 100 [i.4]. The present document aims at supporting electronic signatures in different regulatory frameworks. NOTE: Specifically but not exclusively, PAdES digital signatures specified in the present document aim at supporting electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.2].
- Status
- Published
- Public Enquiry End Date
- 31-Oct-2026
- Publication Date
- 17-Nov-2026
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 16-Nov-2026
- Due Date
- 21-Jan-2027
- Completion Date
- 18-Nov-2026
Buy Documents
ETSI EN 319 142-1 V1.3.0 (2026-08) - Electronic Signatures and Trust Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures
ETSI EN 319 142-1 V1.3.1 (2026-11) - Electronic Signatures and Trust Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures
ETSI EN 319 142-1 specifies PAdES digital signatures for PDF documents, with a focus on building blocks and the baseline signature profiles. It is written for interoperable electronic signatures in business and government use cases, including electronic procedures and communications. The document defines how these signatures are encoded, what attributes and PDF fields they use, and how they support long-term validation.
What does SIST EN 319 142-1 V1.3.1:2027 specify?
SIST EN 319 142-1 V1.3.1:2027 specifies PAdES digital signatures built on the PDF signature mechanisms in the ISO 32000 series. It covers the baseline signature formats and the supporting attributes and PDF structures needed for interoperable use in electronic documents.
The scope includes both PDF 1.7 documents based on ISO 32000-1 and PDF 2.0 documents based on ISO 32000-2. For PDF 1.7, PAdES uses an extended alternative signature encoding; for PDF 2.0, the structures are native in the core PDF standard.
The document is organized into:
- Clause 1 Scope
- Clause 2 References
- Clause 3 Terms, symbols and abbreviations
- Clause 4 General syntax
- Clause 5 Attributes syntax and semantics
- Clause 6 PAdES baseline signatures
- Annex A, which is informative and gives the change history
Procedures for creation, augmentation, and validation are outside the scope and are handled in ETSI EN 319 102-1. The document also points to ETSI TR 119 100 for guidance on using the signature attributes in practice.
What are the key requirements of SIST EN 319 142-1 V1.3.1:2027?
SIST EN 319 142-1 V1.3.1:2027 sets the technical rules for how a PAdES signature is encoded, which attributes are used, and how long-term validation data is stored. The most practical point is that a conforming signature is not just a cryptographic blob - it must fit the PDF structure, the selected PDF version, and the PAdES profile level.
Signature encoding and PDF structure
Clause 4 requires the signature to be a DER-encoded SignedData object placed in the PDF Signature Dictionary Contents entry. The document also requires a single signer and a ByteRange that covers the whole PDF revision except the Contents space. In practice, this means the signed bytes must be complete and contiguous, with no unmapped gaps.
For ISO 32000-2 based signatures, cryptographically secure digest algorithms are required and MD5 and SHA-1 are not allowed for new signature creation. For ISO 32000-1 based signatures, SHA-256 or stronger is strongly recommended for new signatures, while SHA-1 and MD5 are only for legacy verification.
Attribute handling and field consistency
Clause 5 defines CMS, CAdES, ISO 32000, validation data, and archive validation data attributes. The document identifies the key signing attributes such as content-type, message-digest, signing certificate reference attributes, commitment-type-indication, signer-attributes-v2, content-time-stamp, signature-policy-identifier, and signature-time-stamp.
Where a PDF dictionary key and a CMS/CAdES attribute mean the same thing, only one should be used according to the rules in Table 1. This matters because duplicate or conflicting information can cause validation problems later.
Validation data, DSS, and VRI
Clause 5.4 introduces the Document Security Store (DSS), which collects validation material such as certificates, OCSP responses, and CRLs. For PDF 1.7, DSS is an extension; for PDF 2.0, it is native. The related Validation Related Information (VRI) can tie validation material to a specific signature.
For long-term validation, the DSS can be updated in incremental revisions, and the document explains how previous validation data should be carried forward. In practice, this is what allows a verifier to check signatures after certificate expiry or revocation information changes.
Document Time-stamp
Clause 5.4.3 defines the Document Time-stamp dictionary. It uses SubFilter ETSI.RFC3161 and a TimeStampToken in Contents, and the ByteRange covers the whole document except the token itself. This is the mechanism that extends protection over time for PDF 1.7 documents, and it is native in PDF 2.0.
The document also states which keys should not be present in a Document Time-stamp dictionary. That helps keep the time-stamp structure clean and avoids duplication with the token itself.
Baseline levels
Clause 6 defines four baseline levels:
- B-B for the basic signed attributes
- B-T for a trusted time proving that the signature existed at a given time
- B-LT for embedding the validation material needed to validate the signature later
- B-LTA for adding document time-stamps to preserve validation over the long term
The levels are cumulative: each higher level includes the requirements of the lower levels. In practice, this lets an organization choose the least complex profile that still matches its retention and validation needs.
Encryption and version conformance
Clause 5.5 states that if encryption and signatures are combined, encryption is applied before the signature is incorporated. The document also limits which encrypted elements are exempt from encryption, including the signature Contents value.
Clause 5.6 handles PAdES extensions in PDF 1.7 and PDF 2.0 and says that version-dependent requirements apply to the revision in which a signature or validation structure was created. This matters when a single PDF file evolves across revisions.
What terms does SIST EN 319 142-1 V1.3.1:2027 define?
- PAdES signature - A digital signature that satisfies this document or ETSI EN 319 142-2.
- generator - The party that creates or augments a digital signature, including the signer or a later maintainer.
- signature handler - Software that performs signing or validation in conformance with ISO 32000 and the relevant profile.
- validation data - Data used to validate a digital signature, such as certificates or revocation information.
- Document Security Store (DSS) - The PDF structure that stores document-wide security-related validation material.
- Validation Related Information (VRI) - Information that links validation material to a specific signature.
- Document Time-stamp - An electronic time-stamp applied at document level to support long-term protection.
- trust service provider - A person or legal entity that provides one or more trust services.
Who uses SIST EN 319 142-1 V1.3.1:2027?
SIST EN 319 142-1 V1.3.1:2027 is used by organizations that create, verify, store, or preserve signed PDF documents. That includes electronic signature providers, software vendors building PDF signing or validation functions, trust service providers, and teams responsible for compliance or long-term preservation.
It is relevant to business and government workflows where interoperable signed documents are exchanged between individuals, companies, and public bodies. It also matters for anyone implementing a signature handler for PDF readers, signing services, archival systems, or validation services.
What changed in SIST EN 319 142-1 V1.3.1:2027 from the previous edition?
Annex A gives the change history. The listed changes include clarification of the OCSPResponse ASN.1 type in the DSS dictionary, an updated ISO 32000-1 reference, and dual support for ISO 32000-1 (PDF 1.7) and ISO 32000-2 (PDF 2.0) with enhanced cryptographic requirements.
Which standards are used with SIST EN 319 142-1 V1.3.1:2027?
The document depends on several standards for the PDF, cryptographic, and validation building blocks:
- ISO 32000-1 - PDF 1.7 structure and signature dictionary rules
- ISO 32000-2 - PDF 2.0 structure and native support for the relevant PAdES mechanisms
- ETSI EN 319 122-1 - CAdES building blocks and baseline signatures used for the CMS/CAdES attributes
- ETSI EN 319 102-1 - creation and validation procedures for AdES digital signatures
- RFC 5652 - CMS syntax for the SignedData object
- RFC 5280 - X.509 certificates and CRLs
- RFC 6960 - OCSP responses
- RFC 3161 and RFC 5816 - time-stamp tokens and updates
- W3C Canonical XML Version 1.1 - canonicalization for XAdES-related digesting in VRI
- ETSI TS 119 312 - cryptographic suite guidance
- ETSI TR 119 100 - guidance on using the standard in practice
Companion parts named in the document are ETSI EN 319 142-2 for additional PAdES signature profiles and ETSI TS 119 142-3 for PAdES Document Time-stamp digital signatures.
What does the SIST EN 319 142-1 V1.3.1:2027 document contain?
The document contains the syntax and semantics of the PAdES signing attributes, the PDF Signature Dictionary requirements, and the rules for the DSS, VRI, and Document Time-stamp structures. It also contains a requirements matrix that maps the four baseline levels to the required, optional, or forbidden attributes and fields.
It includes explanatory material on how CMS and CAdES attributes relate to PDF fields, how validation material is packaged, and how incremental updates are handled. The figures illustrate the DSS and VRI structure, the long-term validation arrangement, and repeated LTV data across revisions.
The document also includes the baseline level definitions, the algorithm and encryption rules, and the conformance rules for PDF 1.7 and PDF 2.0 revisions. Annex A provides the publication change history.
Buy Documents
ETSI EN 319 142-1 V1.3.0 (2026-08) - Electronic Signatures and Trust Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures
ETSI EN 319 142-1 V1.3.1 (2026-11) - Electronic Signatures and Trust Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures
Get Certified
Connect with accredited certification bodies for this standard

BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.

NYCE
Mexican standards and certification body.
Sponsored listings
Frequently Asked Questions
SIST EN 319 142-1 V1.3.1:2027 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Electronic Signatures and Trust Infrastructures (ESI) - PAdES digital signatures - Part 1: Building blocks and PAdES baseline signatures". This standard covers: The present document specifies PAdES digital signatures. PAdES signatures build on PDF signature mechanisms defined in the ISO 32000 series. For documents conforming to ISO 32000-1 [1] PAdES utilizes an extended, alternative signature encoding. For documents conforming to ISO 32000-2 [9], these signature structures are incorporated natively by default within the core standard. Both approaches support digital signature formats equivalent to the signature format CAdES as specified in ETSI EN 319 122-1 [2], by incorporation of signed and unsigned attributes, which fulfil certain common requirements (such as the long term validity of digital signatures) in a number of use cases. The present document specifies formats for PAdES baseline signatures, which provide the basic features necessary for a wide range of business and governmental use cases for electronic procedures and communications to be applicable to a wide range of communities when there is a clear need for interoperability of digital signatures used in electronic documents. The present document defines four levels of PAdES baseline signatures addressing incremental requirements to maintain the validity of the signatures over the long term, in a way that a certain level always addresses all the requirements addressed at levels that are below it. Each level requires the presence of certain PAdES attributes, suitably profiled for reducing the optionality as much as possible. Procedures for creation, augmentation, and validation of PAdES digital signatures are out of scope and specified in ETSI EN 319 102-1 [10]. Guidance on creation, augmentation and validation of PAdES digital signatures including the usage of the different attributes defined in the present document is provided in ETSI TR 119 100 [i.4]. The present document aims at supporting electronic signatures in different regulatory frameworks. NOTE: Specifically but not exclusively, PAdES digital signatures specified in the present document aim at supporting electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.2].
The present document specifies PAdES digital signatures. PAdES signatures build on PDF signature mechanisms defined in the ISO 32000 series. For documents conforming to ISO 32000-1 [1] PAdES utilizes an extended, alternative signature encoding. For documents conforming to ISO 32000-2 [9], these signature structures are incorporated natively by default within the core standard. Both approaches support digital signature formats equivalent to the signature format CAdES as specified in ETSI EN 319 122-1 [2], by incorporation of signed and unsigned attributes, which fulfil certain common requirements (such as the long term validity of digital signatures) in a number of use cases. The present document specifies formats for PAdES baseline signatures, which provide the basic features necessary for a wide range of business and governmental use cases for electronic procedures and communications to be applicable to a wide range of communities when there is a clear need for interoperability of digital signatures used in electronic documents. The present document defines four levels of PAdES baseline signatures addressing incremental requirements to maintain the validity of the signatures over the long term, in a way that a certain level always addresses all the requirements addressed at levels that are below it. Each level requires the presence of certain PAdES attributes, suitably profiled for reducing the optionality as much as possible. Procedures for creation, augmentation, and validation of PAdES digital signatures are out of scope and specified in ETSI EN 319 102-1 [10]. Guidance on creation, augmentation and validation of PAdES digital signatures including the usage of the different attributes defined in the present document is provided in ETSI TR 119 100 [i.4]. The present document aims at supporting electronic signatures in different regulatory frameworks. NOTE: Specifically but not exclusively, PAdES digital signatures specified in the present document aim at supporting electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.2].
SIST EN 319 142-1 V1.3.1:2027 is classified under the following ICS (International Classification for Standards) categories: 35.040.01 - Information coding in general. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 319 142-1 V1.3.1:2027 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
EUROPEAN STANDARD
Electronic Signatures and Trust Infrastructures (ESI);
PAdES digital signatures;
Part 1: Building blocks and PAdES baseline signatures
2 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
Reference
REN/ESI-0019142-1v131
Keywords
electronic signature, PAdES, profile, security
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part of this document may be reproduced in any form, by any means and in any media, without the prior written
authorization of ETSI and except as expressly permitted below.
By way of exception and when the document is a normative deliverable (European Standard (EN),
Technical Specification (TS), Group Specification (GS) or ETSI Standard (ES)), ETSI authorizes to reproduce
and incorporate into products, services and technical documentation only those extracts (e.g. templates) that are strictly
necessary for the technical implementation of the normative deliverable, to ensure compliance with the latter.
Nothing in this notice shall be construed as limiting any mandatory exceptions to copyright provided by applicable law.
© ETSI 2026.
All rights reserved.
ETSI
3 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 General syntax . 9
4.1 General requirements for PAdES signatures based on PDF signatures . 9
5 Attributes syntax and semantics . 9
5.1 Introduction . 9
5.2 CMS and CAdES defined attributes . 10
5.3 ISO 32000 defined attributes . 10
5.4 Validation data and archive validation data attributes . 11
5.4.1 Overview . 11
5.4.2 Document Security Store . 13
5.4.2.1 Catalog . 13
5.4.2.2 DSS Dictionary . 13
5.4.2.3 Signature VRI Dictionary . 15
5.4.3 Document Time-stamp . 16
5.4.4 Validation of PAdES signatures . 16
5.5 Requirements on encryption . 17
5.6 Extensions dictionary and PDF 2.0 conformance . 17
5.6.1 ISO 32000-1 (PDF 1.7) Compliant Documents . 17
5.6.2 ISO 32000-2 (PDF 2.0) Compliant Documents . 18
5.6.3 Version conformance across document revisions . 18
6 PAdES baseline signatures . 18
6.1 Signature levels . 18
6.2 General requirements for PAdES baseline signatures . 19
6.2.1 Algorithm requirements . 19
6.2.2 Notation for requirements . 19
6.3 PAdES baseline signatures . 21
6.4 Legacy PAdES baseline signatures . 26
Annex A (informative): Change history . 27
History . 28
ETSI
4 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables (European Standard (EN), Technical Specification (TS),
Group Specification (GS) or ETSI Standard (ES)) may have been declared to ETSI. The declarations pertaining to these
essential IPRs, if any, are publicly available for ETSI members and non-members, and can be found in
ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This draft European Standard (EN) has been produced by ETSI Technical Committee Electronic Signatures and Trust
Infrastructures (ESI), and is now submitted for the combined Public Enquiry and Vote of the ETSI EN Approval
Procedure (ENAP).
The present document is part 1 of a multi-part deliverable covering the PDF digital signatures (PAdES), as identified
below:
ETSI EN 319 142-1: "Building blocks and PAdES baseline signatures";
ETSI EN 319 142-2: "Additional PAdES signatures profiles";
ETSI TS 119 142-3: "PAdES Document Time-stamp digital signatures (PAdES-DTS)".
Proposed national transposition dates
Date of latest announcement of this EN (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 6 months after doa
ETSI
5 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
Electronic commerce has emerged as a frequent way of doing business between companies across local, wide area and
global networks. Trust in this way of doing business is essential for the success and continued development of
electronic commerce. It is therefore important that companies using this electronic means of doing business have
suitable security controls and mechanisms in place to protect their transactions and to ensure trust and confidence with
their business partners. In this respect digital signatures are an important security component that can be used to protect
information and provide trust in electronic business.
The present document is intended to cover digital signatures supported by PKI and public key certificates, and aims to
meet the general requirements of the international community to provide trust and confidence in electronic transactions,
including, amongst other, applicable requirements from Regulation (EU) No 910/2014 [i.2].
The present document can be used for any transaction between an individual and a company, between two companies,
between an individual and a governmental body, etc. The present document is independent of any environment. It can
be applied to any environment e.g. smart cards, SIM cards, special programs for electronic signatures, etc.
The present document is part of a rationalized framework of standards (see ETSI TR 119 000 [i.3]).
ETSI TR 119 100 [i.4] provides guidance on how to use the present document within the aforementioned framework.
ETSI
6 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
1 Scope
The present document specifies PAdES digital signatures. PAdES signatures build on PDF signature mechanisms
defined in the ISO 32000 series. For documents conforming to ISO 32000-1 [1] PAdES utilizes an extended, alternative
signature encoding. For documents conforming to ISO 32000-2 [9], these signature structures are incorporated natively
by default within the core standard. Both approaches support digital signature formats equivalent to the signature format
CAdES as specified in ETSI EN 319 122-1 [2], by incorporation of signed and unsigned attributes, which fulfil certain
common requirements (such as the long term validity of digital signatures) in a number of use cases.
The present document specifies formats for PAdES baseline signatures, which provide the basic features necessary for a
wide range of business and governmental use cases for electronic procedures and communications to be applicable to a
wide range of communities when there is a clear need for interoperability of digital signatures used in electronic
documents.
The present document defines four levels of PAdES baseline signatures addressing incremental requirements to
maintain the validity of the signatures over the long term, in a way that a certain level always addresses all the
requirements addressed at levels that are below it. Each level requires the presence of certain PAdES attributes, suitably
profiled for reducing the optionality as much as possible.
Procedures for creation, augmentation, and validation of PAdES digital signatures are out of scope and specified in
ETSI EN 319 102-1 [10]. Guidance on creation, augmentation and validation of PAdES digital signatures including the
usage of the different attributes defined in the present document is provided in ETSI TR 119 100 [i.4]. The present
document aims at supporting electronic signatures in different regulatory frameworks.
NOTE: Specifically but not exclusively, PAdES digital signatures specified in the present document aim at
supporting electronic signatures, advanced electronic signatures, qualified electronic signatures,
electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU)
No 910/2014 [i.2].
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found in the
ETSI docbox.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are necessary for the application of the present document.
[1] ISO 32000-1: "Document management — Portable document format — Part 1: PDF 1.7".
[2] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures;
Part 1: Building blocks and CAdES baseline signatures".
[3] IETF RFC 5652 (2009): "Cryptographic Message Syntax (CMS)".
[4] IETF RFC 5280 (2008): "Internet X.509 Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile".
[5] IETF RFC 6960 (2013): "X.509 Internet Public Key Infrastructure Online Certificate Status
Protocol - OCSP".
[6] IETF RFC 3161 (2001): "Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)". ®
[7] W3C Recommendation (2 May 2008): "Canonical XML Version 1.1".
ETSI
7 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
[8] IETF RFC 5816 (2010): "ESSCertIDv2 Update for RFC 3161".
[9] ISO 32000-2: "Document management — Portable document format —Part 2: PDF 2.0".
[10] ETSI EN 319 102-1: "Electronic Signatures and Trust Infrastructures (ESI); Procedures for
Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document.
[i.1] Void.
[i.2] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on
electronic identification and trust services for electronic transactions in the internal market and
repealing Directive 1999/93/EC.
[i.3] ETSI TR 119 000: "Electronic Signatures and Infrastructures (ESI); The framework for
standardization of digital signatures and trust services; Overview".
[i.4] ETSI TR 119 100: "Electronic Signatures and Infrastructures (ESI); Guidance on the use of
standards for signature creation and validation".
[i.5] Void.
[i.6] ETSI TS 119 312: "Electronic Signatures and Trust Infrastructures (ESI); Cryptographic Suites". ®
[i.7] Adobe XFA: "XML Forms Architecture (XFA) Specification" version 2.5, (June 2007), Adobe
Systems Incorporated".
[i.8] ETSI TS 103 172: "Electronic Signatures and Infrastructures (ESI); PAdES Baseline Profile".
[i.9] IETF RFC 2315 (1998): "PKCS #7: Cryptographic Message Syntax Version 1.5".
[i.10] ETSI TS 119 612: "Electronic Signatures and Trust Infrastructures (ESI); Trusted Lists".
[i.11] ETSI EN 319 142-2: "Electronic Signatures and Trust Infrastructures (ESI); PAdES digital
signatures; Part 2: Additional PAdES signatures profiles".
[i.12] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for
standardization of signatures; Definitions and abbreviations".
[i.13] ETSI TS 119 511: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security
requirements for trust service providers providing long-term preservation of digital signatures or
general data using digital signature techniques".
ETSI
8 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ISO 32000-1 [1], ISO 32000-2 [9], ETSI
TR 119 001 [i.12] and the following apply:
digital signature: data appended to, or a cryptographic transformation of a data unit that allows a recipient of the data
unit to prove the source and integrity of the data unit and protect against forgery, e.g. by the recipient
digital signature value: result of the cryptographic transformation of a data unit that allows a recipient of the data unit
to prove the source and integrity of the data unit and protect against forgery, e.g. by the recipient
electronic time-stamp: data in electronic form which binds other electronic data to a particular time establishing
evidence that these data existed at that time
generator: any party which creates, or augments a digital signature
NOTE: This can be the signer or any party that initially validates or further maintains the signature.
legacy PAdES baseline signature: digital signature generated according to ETSI TS 103 172 [i.8]
PAdES signature: digital signature that satisfies the requirements specified within the present document or ETSI
EN 319 142-2 [i.11]
proof of existence: evidence that proves that an object existed at a specific date/time
signature augmentation policy: set of rules, applicable to one or more digital signatures, that defines the technical and
procedural requirements for their augmentation, in order to meet a particular business need, and under which the digital
signature(s) can be determined to be conformant
signature creation policy: set of rules, applicable to one or more digital signatures, that defines the technical and
procedural requirements for their creation, in order to meet a particular business need, and under which the digital
signature(s) can be determined to be conformant
signature handler: software application, or part of a software application, that knows how to perform digital signature
operations (e.g. signing and/or validating) in conformance with ISO 32000-1 [1] or ISO 32000-2 [9] and the
requirements of the appropriate profile
signature policy: signature creation policy, signature augmentation policy, signature validation policy or any
combination thereof, applicable to the same signature or set of signatures
signature validation policy: set of rules, applicable to one or more digital signatures, that defines the technical and
procedural requirements for their validation, in order to meet a particular business need, and under which the digital
signature(s) can be determined to be valid
trust service provider: natural or legal person who provides one or more trust services
validation data: data that is used to validate a digital signature
verifier: entity that wants to validate or verify a digital signature
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.12] and the following apply:
DSS Document Security Store
ETSI
9 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
4 General syntax
4.1 General requirements for PAdES signatures based on PDF
signatures
PAdES signatures profiled in the present document build on PDF signatures specified in either ISO 32000-1 [1] or
ISO 32000-2 [9] with an alternative signature encoding to support digital signature formats equivalent to the signature
format CAdES as specified in ETSI EN 319 122-1 [2], by incorporation of signed and unsigned attributes described in
clause 5.
The following requirements apply:
a) A DER-encoded SignedData object as specified in ETSI EN 319 122-1 [2] shall be included as the PDF
signature in the entry with the key Contents of the Signature Dictionary as described in ISO 32000-1 [1],
clause 12.8.1 or ISO 32000-2 [9], clause 12.8.1. There shall only be a single signer (i.e. one single component
of SignerInfo type within signerInfos element) in any PDF Signature. Regardless of the PDF version
used, the byte-range covered by the signature shall comprise exactly the entire PDF revision being signed
except for the Contents space itself, leaving no unmapped bytes outside the ByteRange definition.
b) Requirements for handling PDF Signatures specified in ISO 32000-1 [1], clause 12.8 or ISO 32000-2 [9],
clause 12.8 shall apply except where overridden by the present document.
When signatures are generated based on ISO 32000-2 [9], cryptographically secure digest algorithms (defined
in ETSI TS 119 312 [i.6]) shall be used, and legacy algorithms (MD5 and SHA-1) shall not be used for new
signature creation. For signatures based on ISO 32000-1 [1], the use of SHA-256 or stronger algorithms is
highly recommended for signature creation, while SHA-1 and MD5 may be supported solely for verification
purposes of legacy documents.
NOTE 1: Given that PAdES signatures are enveloped inside a PDF document and are detached in the sense of a
CMS signature, the signature placement is implied by ISO 32000-1 [1] or ISO 32000-2 [9].
In ISO 32000-1 [1], clause 12.8.3.3.1 reads "No data shall be encapsulated in the PKCS#7 SignedData
field" whereas in ISO 32000-2 [9], the corresponding clause refers to the field as the CMS SignedData
field.
NOTE 2: ISO 32000-2 [9] deprecates legacy SubFilter values like adbe.pkcs7.sha1. For maximum interoperability
across PDF versions, the SubFilter value ETSI.CAdES.detached should be used, as it is natively
supported by ISO 32000-2 [9] (Table 252) and widely implemented as an extension in ISO 32000-1 [1]
compliant software.
c) Some signature attributes found in ETSI EN 319 122-1 [2] have the same or similar meaning as keys in the
Signature Dictionary described in ISO 32000-1 [1] or ISO 32000-2 [9]. For signature attributes and keys that
have the same or similar meaning only one of them should be used according to the requirements set in
Table 1.
5 Attributes syntax and semantics
5.1 Introduction
This clause provides details on attributes specified within ISO 32000-1 [1], ISO 32000-2 [9], and ETSI
EN 319 122-1 [2] and defines new attributes for building PAdES signatures.
The clause distinguishes between the following types of attributes: CMS and CAdES defined attributes,
ISO 32000-1 [1] or ISO 32000-2 [9] defined attributes, validation data and archive validation data attributes.
• The first ones are the attributes that build the DER-encoded SignedData object included as the PDF signature
in the entry with the key Contents of the Signature Dictionary as described in ISO 32000-1 [1], clause 12.8.1
or ISO 32000-2 [9], clause 12.8.1. Depending on the underlying PDF specification version, this object
conforms either to the PKCS#7 format or the CMS (Cryptographic Message Syntax) format, respectively.
ETSI
10 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
• The second ones are the attributes that build the Signature Dictionary as described in ISO 32000-1 [1] or
ISO 32000-2 [9].
• The other ones are the attributes where to include validation data and archive validation data that can guarantee
long term validity of digital signatures.
Clause 6.3 provides the requirements concerning how to use the attributes described above.
5.2 CMS and CAdES defined attributes
The attributes included in the following list may be used to generate the DER-encoded SignedData object included as
the PDF signature in the entry with the key Contents of the Signature Dictionary as described in ISO 32000-1 [1],
clause 12.8.1 or ISO 32000-2 [9], clause 12.8.1. Their syntax shall be as defined in ETSI EN 319 122-1 [2], clause 5.
• content-type
• message-digest
• Signing certificate reference attributes
- ESS signing-certificate
May be used for legacy compliance in ISO 32000-1 [1] signatures; shall not be used in ISO 32000-2 [9]
signatures.
- ESS signing-certificate-v2
Shall be used for ISO 32000-2 [9] signatures and is strongly recommended for ISO 32000-1 [1]
signatures using SHA-2 or stronger digest algorithms.
• commitment-type-indication
• signer-attributes-v2
• content-time-stamp
• signature-policy-identifier
• signature-time-stamp
5.3 ISO 32000 defined attributes
The entries of the Signature Dictionary shall be as defined in ISO 32000-1 [1], clause 12.8.1 (Table 252) or
ISO 32000-2 [9], clause 12.8.1 (Table 254).
For the following signature dictionary entries, these additional requirements apply:
• SubFilter
For signatures conforming to ISO 32000-2 [9], this shall be set to ETSI.CAdES.detached. For legacy
compliance with ISO 32000-1 [1], adbe.pkcs7.detached may be supported for verification, but
ETSI.CAdES.detached is preferred for new signature generation.
• Contents
Shall contain the DER-encoded SignedData object as specified in clause 4.1.a).
• ByteRange
Shall be used to identify the bytes of the document covered by the signature, conforming to the gapless
requirement specified in clause 4.1.a).
ETSI
11 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
• M
The time of signing. The syntax shall conform to the Date format specified in ISO 32000-1 [1] or
ISO 32000-2 [9]).
• Name (Optional)
The name of the person or authority signing the document. This value should be used only when it is not
possible to extract the name from the signature.
• Location (Optional)
To prevent data redundancy and synchronization conflicts during validation, this key shall not be used if
equivalent information is present within the CMS signed attributes of the signature: signer-location.
• Reason (Optional)
To prevent data redundancy and synchronization conflicts during validation, this key shall not be used if
equivalent information is present within the CMS signed attributes of the signature: commitment-type-
indication.
• ContactInfo (Optional)
• Prop_Build (Optional in ISO 32000-1 [1], strongly recommended in ISO 32000-2 [9])
In ISO 32000-2 [9] strongly recommended to build an internal dictionary containing the software application
name, version, and operating system used to create the signature.
5.4 Validation data and archive validation data attributes
5.4.1 Overview
Validation of a digital signature requires data to validate the signature such as CA certificates, Certificate Revocation
List (CRL) or Online Certificate Status Protocol (OCSP) commonly provided by online services (referred to in the
present document as validation data).
This clause describes the mechanism to carry such validation data as necessary to validate a signature, optionally with
Validation Related Information (VRI) which relates the validation data to a specific signature (see clause 5.4.2).
For signatures based on ISO 32000-1 [1], this mechanism is implemented via the Document Security Store (DSS)
extension. For signatures based on ISO 32000-2 [9], this mechanism relies on the native Document Security Store
(DSS) as formally standardized in ISO 32000-2 [9], clause 12.8.4.
The structure of DSS and VRI is illustrated in Figure 1.
ETSI
12 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
DSS dict
VRI
Indirect references to all Certs
Indirect references to all OCSPs
Indirect references to all CRLs
VRI of a specific signature
Indirect references to required Certs
Indirect references to required OCSPs
Indirect references to required CRLs
Cert1 (value)
Cert2 (value)
OCSP1 (response value)
CRL1 (value)
Certn (value)
OCSPn (value)
CRLn (value)
Figure 1: Illustration of DSS and VRI structures
For PDF documents based on ISO 32000-1 [1], this clause also defines an extension called Document Time-stamp (see
clause 5.4.3) to extend the life-time of protection to the document.
NOTE 1: ISO 32000-2 [9] includes this feature natively.
These extensions support Long Term Validation (LTV) of PDF Signatures. The structure of a PDF document with LTV
data is illustrated in Figure 2.
Document
Security Store
Document
Time-stamp
Figure 2: Illustration of PDF document with extended life-time protection
The life-time of the protection can be further extended beyond the life-time of the last Document Time-stamp applied
by adding further DSS information to validate the previous last Document Time-stamp along with a new Document
Time-stamp. Every time a DSS Dictionary is updated during incremental update, it should contain the values from the
previous DSS Dictionary.
NOTE 2: In general the DSS Dictionary will contain validation data from previous revisions plus validation data
added for the current revision. If entries are removed from a DSS Dictionary during an incremental
update the set of validation data might not be complete for validation of the signatures, but replacement of
validation data - e.g. more up-to-date certificate status information - might be performed for optimization
reasons.
ETSI
13 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
This is illustrated in Figure 3.
Figure 3: Illustration of PDF Document with repeated LTV data
5.4.2 Document Security Store
5.4.2.1 Catalog
For documents conforming to ISO 32000-1 [1], the DSS entry is added to Table 28 ("Entries in catalogue dictionary").
Added to ISO 32000-1 [1], Table 28 "Entries in catalogue dictionary"
KEY TYPE VALUE
DSS Dictionary (Optional) Document-wide security-related information.
For documents conforming to ISO 32000-2 [9], the DSS entry shall be populated in accordance with Table 31 ("Entries
in the document catalog dictionary") of the PDF 2.0 specification.
5.4.2.2 DSS Dictionary
The Document Security Store (DSS) shall be a dictionary that shall have the value DSS as key in the document catalog
dictionary. This dictionary is used to provide a single place where all of the VRI for some or all signatures in the
document should be placed.
The DSS dictionary, if present, shall contain VRI only for document and time-stamps signatures represented in PKCS#7
and CMS (and its derivatives) format or for XAdES signatures of forms signing dynamic XFA [i.7].
NOTE 1: See ETSI EN 319 142-2 [i.11] for specification of XAdES signatures of forms signing dynamic XFA.
ETSI
14 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
Entries in a DSS Dictionary (Conforming to ISO 32000-1 [1] extensions or natively to ISO 32000-2 [9], Table 256):
Entries in a DSS Dictionary
KEY TYPE VALUE
Type Name (Optional) It shall be DSS for a document security store
dictionary.
VRI
Dictionary (Optional) This dictionary contains Signature VRI dictionaries in
the document. For ISO 32000-1 [1] documents the key of each
entry in this dictionary is the base-16-encoded (uppercase)
SHA1 digest of the signature to which it applies and the value
is the Signature VRI dictionary which contains the VRI for that
signature.
See additional requirements a), b), c) and d).
Certs Array (Optional) An array of indirect references to streams, each
containing one DER-encoded X.509 certificate (that shall be as
defined in IETF RFC 5280 [4]). This array contains certificates
that can be used in the validation of any signatures in the
document.
OCSPs Array (Optional) An array of indirect references to streams, each
containing a DER-encoded Online Certificate Status
Protocol (OCSP) response, which can be used in the validation
of any signature in the document. The OCSP response shall be
encoded by using the encoding of the OCSPResponse type as
defined in IETF RFC 6960 [5] (see note 2).
CRLs Array (Optional) An array of indirect references to streams, each
containing a DER-encoded Certificate Revocation List (CRL)
(that shall be as defined in IETF RFC 5280 [4]). This array
contains CRLs that can be used in the validation of any
signatures in the document.
Additional requirements for VRI keys:
a) For document signatures or Document Time-stamp signatures the bytes that are hashed shall be those of the
complete hexadecimal string in the entry with the key Contents of the associated Signature Dictionary
containing the signature's DER-encoded binary data object (e.g. PKCS#7, CMS or CAdES objects).
b) For the signatures of CRLs and OCSP responses, the bytes that are hashed shall be the respective signature
objects represented as a BER-encoded OCTET STRING encoded with primitive encoding.
c) When computing the digest of a XAdES signature found in dynamic XFA [i.7], the contents of the ds:Signature
shall be canonicalized using exclusive canonicalization (http://www.w3.org/2001/10/xml-exc-c14n#) as
specified in [7] and then hashed.
Any VRI dictionaries shall be located in document incremental update sections. If the Signature Dictionary to which a
VRI dictionary applies is itself in an incremental update section (see clause 7.5.6 of ISO 32000-1 [1] or clause 7.5.6 of
ISO 32000-2 [9]), the VRI update shall be done later than the signature update.
NOTE 2: To facilitate the verification of signatures created according to previous versions of the signature format
specifications, a verifier can also accept OCSP responses encoded by using the encoding of the
BasicOCSPResponse type as defined in IETF RFC 6960 [5].
ETSI
15 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
5.4.2.3 Signature VRI Dictionary
The signature VRI dictionary shall contain Validation Related Information (VRI) for a specific signature in the
document to which the validation information applies.
Entries in a Signature VRI Dictionary (Conforming to ISO 32000-1 [1] extensions or natively to ISO 32000-2 [9],
Table 257):
Entries in a Signature VRI Dictionary
KEY TYPE VALUE
Type (Optional),if present, it shall be VRI for a VRI dictionary.
Name
Cert (Optional, if present, it shall not be an empty array) An array of
Array
indirect references to streams, each containing one DER-encoded
X.509 certificate (that shall be as defined in IETF RFC 5280 [4]). This
array should contain all certificates that were used in the validation of
this signature.
CRL Array (Optional, if present, it shall not be an empty array) An array of
indirect references to streams that are all CRLs used to determine the
validity of the certificates in the chains related to this signature. Each
stream shall reference a CRL that is an entry in the CRLs array in the
DSS dictionary.
OCSP (Optional, if present shall not be an empty array) An array of indirect
Array
references to streams that are all OCSP responses used to determine
the validity of the certificates in the chains related to this signature.
Each stream shall reference an OCSP response that is an entry in the
OCSPs array in the DSS dictionary.
TU Date (Optional), the date/time at which this signature VRI dictionary was
created. A signature handler may ignore this entry and use a different
time for the signature validation. This entry shall be absent when the
TS entry is present. Date shall be a date string as defined in
ISO 32000-1 [1], clause 7.9.4 or ISO 32000-2 [9], clause 7.9.4. See
additional requirement a).
TS Stream (Optional), a stream containing the DER-encoded time-stamp token
(that shall be as defined in IETF RFC 3161 [6] updated by IETF
RFC 5816 [8] and which represents the secure time at which this
signature VRI dictionary was created. This entry shall be absent when
a TU entry is present. See note 1 and additional requirement b).
Additional requirements:
a) The TU key should not be used.
b) The TS key should not be used.
c) Exactly one of the following methods to provide a VRI generation claimed time shall be used: the TU entry, the
TS entry or a subsequent Document Time-stamp.
NOTE 1: For PKCS#7 signatures conforming to ISO 32000-1 [1] the datum that is hashed and included in the
messageImprint field of the DER-encoded time stamp stored in TS entry (see IETF RFC 3161 [6] updated
by IETF RFC 5816 [8]) is the encryptedDigest field in the signature's PKCS#7 object (as defined in IETF
RFC 2315 [i.9]). For CMS signatures conforming to ISO 32000-2 [9], the corresponding signature value field
within the SignerInfo structure shall be used.
NOTE 2: The VRI dictionary is optional, since all necessary data to validate the signature can be available from other
sources like the DSS dictionary itself. The VRI dictionary offers possibilities for optimization of the validation
process, since it relates the data to one specific signature.
NOTE 3: The value of TS can be used as a proof of existence for the signature value itself.
Any values in the Cert, CRL and OCSP arrays of a Signature VRI dictionary shall also be present in the DSS dictionary
applicable to the signature for which this Signature VRI dictionary is associated. If this signature (e.g. PKCS#7, CMS
or CAdES object) does not have any associated Certs, CRLs or OCSPs, then the corresponding key shall not be present
in the VRI dictionary.
A Signature VRI dictionary shall not be used to record the information used in an unsuccessful validation attempt.
MDP restrictions (see ISO 32000-1 [1], clause 12.8.2.2 or ISO 32000-2 [9], clauses 12.8.2.2 and 12.7.5.5) shall not
apply to incremental updates to a PDF document containing a DSS dictionary and associated VRI, Certs, CRLs and
OCSPs.
ETSI
16 Draft ETSI EN 319 142-1 V1.3.0 (2026-08)
NOTE: ISO 32000-1 [1], clause 12.8.2.2 and ISO 32000-2 [9], clauses 12.8.2.2 and 12.7.5.5, address the MDP
(Modification, Detection and Prevention) feature whereby a set of permissions can be associated with a
PDF in conjunction with a certification signature. The permissions of MDP are present in the entry with
the P key of the DocMDP transform parameters dictionary and of the signature field lock dictionary, as an
integer in the range 1 through 3. Values of 2 and 3 allow for additional signatures to be included after the
certification but a value of 1 does not allow any change but allows Document Time-stamps.
5.4.3 Document Time-stamp
A Document Time-stamp dictionary shall be a standard Signature Dictionary (as defined in ISO 32000-1 [1],
clause 12.8.1, Table 252) with the following changes.
Modifications to the standard Signature Dictionary for a Document Time-stamp Dictionary:
Modifications to Table 252 for a Document Time-stamp Dictionary of ISO 32000-1 [1]
KEY TYPE VALUE
Type Name (Required) It shall be DocTimeStamp.
SubFilter Name (Required) The value of SubFilter identifies the format of the data contained in
the stream. A conforming reader may use any signature handler that supports the
specified format.
The value of SubFilter should be ETSI.RFC3161.
Other values may be defined by developers, and when used, shall be prefixed
with the registered developer identification as described in ISO 32000-1 [1],
annex E.
Contents
Byte string (Required) When the value of SubFilter is ETSI.RFC3161, the value of
Contents shall be the hexadecimal string (as defined in clause 7.3.4.3 in
ISO 32000-1 [1]) representing the value of TimeStampToken as specified in IETF
RFC 3161 [6] updated by IETF RFC 5816 [8]. The value of the
messageImprint field within the TimeStampToken
...
EUROPEAN STANDARD
Electronic Signatures and Trust Infrastructures (ESI);
PAdES digital signatures;
Part 1: Building blocks and PAdES baseline signatures
2 ETSI EN 319 142-1 V1.3.1 (2026-11)
Reference
REN/ESI-0019142-1v131
Keywords
electronic signature, PAdES, profile, security
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part of this document may be reproduced in any form, by any means and in any media, without the prior written
authorization of ETSI and except as expressly permitted below.
By way of exception and when the document is a normative deliverable (European Standard (EN),
Technical Specification (TS), Group Specification (GS) or ETSI Standard (ES)), ETSI authorizes to reproduce
and incorporate into products, services and technical documentation only those extracts (e.g. templates) that are strictly
necessary for the technical implementation of the normative deliverable, to ensure compliance with the latter.
Nothing in this notice shall be construed as limiting any mandatory exceptions to copyright provided by applicable law.
© ETSI 2026.
All rights reserved.
ETSI
3 ETSI EN 319 142-1 V1.3.1 (2026-11)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 General syntax . 9
4.1 General requirements for PAdES signatures based on PDF signatures . 9
5 Attributes syntax and semantics . 9
5.1 Introduction . 9
5.2 CMS and CAdES defined attributes . 10
5.3 ISO 32000 defined attributes . 10
5.4 Validation data and archive validation data attributes . 11
5.4.1 Overview . 11
5.4.2 Document Security Store . 13
5.4.2.1 Catalog . 13
5.4.2.2 DSS Dictionary . 13
5.4.2.3 Signature VRI Dictionary . 15
5.4.3 Document Time-stamp . 16
5.4.4 Validation of PAdES signatures . 16
5.5 Requirements on encryption . 17
5.6 Extensions dictionary and PDF 2.0 conformance . 17
5.6.1 ISO 32000-1 (PDF 1.7) Compliant Documents . 17
5.6.2 ISO 32000-2 (PDF 2.0) Compliant Documents . 18
5.6.3 Version conformance across document revisions . 18
6 PAdES baseline signatures . 18
6.1 Signature levels . 18
6.2 General requirements for PAdES baseline signatures . 19
6.2.1 Algorithm requirements . 19
6.2.2 Notation for requirements . 19
6.3 PAdES baseline signatures . 21
6.4 Legacy PAdES baseline signatures . 27
Annex A (informative): Change history . 28
History . 29
ETSI
4 ETSI EN 319 142-1 V1.3.1 (2026-11)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables (European Standard (EN), Technical Specification (TS),
Group Specification (GS) or ETSI Standard (ES)) may have been declared to ETSI. The declarations pertaining to these
essential IPRs, if any, are publicly available for ETSI members and non-members, and can be found in
ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This European Standard (EN) has been produced by ETSI Technical Committee Electronic Signatures and Trust
Infrastructures (ESI).
The present document is part 1 of a multi-part deliverable covering the PDF digital signatures (PAdES), as identified
below:
ETSI EN 319 142-1: "Building blocks and PAdES baseline signatures";
ETSI EN 319 142-2: "Additional PAdES signatures profiles";
ETSI TS 119 142-3: "PAdES Document Time-stamp digital signatures (PAdES-DTS)".
National transposition dates
Date of adoption of this EN: 9 November 2026
Date of latest announcement of this EN (doa): 28 February 2027
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 August 2027
Date of withdrawal of any conflicting National Standard (dow): 31 August 2027
ETSI
5 ETSI EN 319 142-1 V1.3.1 (2026-11)
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
Electronic commerce has emerged as a frequent way of doing business between companies across local, wide area and
global networks. Trust in this way of doing business is essential for the success and continued development of
electronic commerce. It is therefore important that companies using this electronic means of doing business have
suitable security controls and mechanisms in place to protect their transactions and to ensure trust and confidence with
their business partners. In this respect digital signatures are an important security component that can be used to protect
information and provide trust in electronic business.
The present document is intended to cover digital signatures supported by PKI and public key certificates, and aims to
meet the general requirements of the international community to provide trust and confidence in electronic transactions,
including, amongst other, applicable requirements from Regulation (EU) No 910/2014 [i.2].
The present document can be used for any transaction between an individual and a company, between two companies,
between an individual and a governmental body, etc. The present document is independent of any environment. It can
be applied to any environment e.g. smart cards, SIM cards, special programs for electronic signatures, etc.
The present document is part of a rationalized framework of standards (see ETSI TR 119 000 [i.3]).
ETSI TR 119 100 [i.4] provides guidance on how to use the present document within the aforementioned framework.
ETSI
6 ETSI EN 319 142-1 V1.3.1 (2026-11)
1 Scope
The present document specifies PAdES digital signatures. PAdES signatures build on PDF signature mechanisms
defined in the ISO 32000 series. For documents conforming to ISO 32000-1 [1] PAdES utilizes an extended, alternative
signature encoding. For documents conforming to ISO 32000-2 [9], these signature structures are incorporated natively
by default within the core standard. Both approaches support digital signature formats equivalent to the signature format
CAdES as specified in ETSI EN 319 122-1 [2], by incorporation of signed and unsigned attributes, which fulfil certain
common requirements (such as the long term validity of digital signatures) in a number of use cases.
The present document specifies formats for PAdES baseline signatures, which provide the basic features necessary for a
wide range of business and governmental use cases for electronic procedures and communications to be applicable to a
wide range of communities when there is a clear need for interoperability of digital signatures used in electronic
documents.
The present document defines four levels of PAdES baseline signatures addressing incremental requirements to
maintain the validity of the signatures over the long term, in a way that a certain level always addresses all the
requirements addressed at levels that are below it. Each level requires the presence of certain PAdES attributes, suitably
profiled for reducing the optionality as much as possible.
Procedures for creation, augmentation, and validation of PAdES digital signatures are out of scope and specified in
ETSI EN 319 102-1 [10]. Guidance on creation, augmentation and validation of PAdES digital signatures including the
usage of the different attributes defined in the present document is provided in ETSI TR 119 100 [i.4]. The present
document aims at supporting electronic signatures in different regulatory frameworks.
NOTE: Specifically but not exclusively, PAdES digital signatures specified in the present document aim at
supporting electronic signatures, advanced electronic signatures, qualified electronic signatures,
electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU)
No 910/2014 [i.2].
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found in the
ETSI docbox.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are necessary for the application of the present document.
[1] ISO 32000-1: "Document management — Portable document format — Part 1: PDF 1.7".
[2] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures;
Part 1: Building blocks and CAdES baseline signatures".
[3] IETF RFC 5652 (2009): "Cryptographic Message Syntax (CMS)".
[4] IETF RFC 5280 (2008): "Internet X.509 Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile".
[5] IETF RFC 6960 (2013): "X.509 Internet Public Key Infrastructure Online Certificate Status
Protocol - OCSP".
[6] IETF RFC 3161 (2001): "Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)". ®
[7] W3C Recommendation (2 May 2008): "Canonical XML Version 1.1".
ETSI
7 ETSI EN 319 142-1 V1.3.1 (2026-11)
[8] IETF RFC 5816 (2010): "ESSCertIDv2 Update for RFC 3161".
[9] ISO 32000-2: "Document management — Portable document format —Part 2: PDF 2.0".
[10] ETSI EN 319 102-1: "Electronic Signatures and Trust Infrastructures (ESI); Procedures for
Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document.
[i.1] Void.
[i.2] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on
electronic identification and trust services for electronic transactions in the internal market and
repealing Directive 1999/93/EC.
[i.3] ETSI TR 119 000: "Electronic Signatures and Infrastructures (ESI); The framework for
standardization of digital signatures and trust services; Overview".
[i.4] ETSI TR 119 100: "Electronic Signatures and Infrastructures (ESI); Guidance on the use of
standards for signature creation and validation".
[i.5] Void.
[i.6] ETSI TS 119 312: "Electronic Signatures and Trust Infrastructures (ESI); Cryptographic Suites". ®
[i.7] Adobe XFA: "XML Forms Architecture (XFA) Specification" version 2.5, (June 2007), Adobe
Systems Incorporated".
[i.8] ETSI TS 103 172: "Electronic Signatures and Infrastructures (ESI); PAdES Baseline Profile".
[i.9] IETF RFC 2315 (1998): "PKCS #7: Cryptographic Message Syntax Version 1.5".
[i.10] ETSI TS 119 612: "Electronic Signatures and Trust Infrastructures (ESI); Trusted Lists".
[i.11] ETSI EN 319 142-2: "Electronic Signatures and Trust Infrastructures (ESI); PAdES digital
signatures; Part 2: Additional PAdES signatures profiles".
[i.12] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for
standardization of signatures; Definitions and abbreviations".
[i.13] ETSI TS 119 511: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security
requirements for trust service providers providing long-term preservation of digital signatures or
general data using digital signature techniques".
ETSI
8 ETSI EN 319 142-1 V1.3.1 (2026-11)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ISO 32000-1 [1], ISO 32000-2 [9], ETSI
TR 119 001 [i.12] and the following apply:
digital signature: data appended to, or a cryptographic transformation of a data unit that allows a recipient of the data
unit to prove the source and integrity of the data unit and protect against forgery, e.g. by the recipient
digital signature value: result of the cryptographic transformation of a data unit that allows a recipient of the data unit
to prove the source and integrity of the data unit and protect against forgery, e.g. by the recipient
electronic time-stamp: data in electronic form which binds other electronic data to a particular time establishing
evidence that these data existed at that time
generator: any party which creates, or augments a digital signature
NOTE: This can be the signer or any party that initially validates or further maintains the signature.
legacy PAdES baseline signature: digital signature generated according to ETSI TS 103 172 [i.8]
PAdES signature: digital signature that satisfies the requirements specified within the present document or ETSI
EN 319 142-2 [i.11]
proof of existence: evidence that proves that an object existed at a specific date/time
signature augmentation policy: set of rules, applicable to one or more digital signatures, that defines the technical and
procedural requirements for their augmentation, in order to meet a particular business need, and under which the digital
signature(s) can be determined to be conformant
signature creation policy: set of rules, applicable to one or more digital signatures, that defines the technical and
procedural requirements for their creation, in order to meet a particular business need, and under which the digital
signature(s) can be determined to be conformant
signature handler: software application, or part of a software application, that knows how to perform digital signature
operations (e.g. signing and/or validating) in conformance with ISO 32000-1 [1] or ISO 32000-2 [9] and the
requirements of the appropriate profile
signature policy: signature creation policy, signature augmentation policy, signature validation policy or any
combination thereof, applicable to the same signature or set of signatures
signature validation policy: set of rules, applicable to one or more digital signatures, that defines the technical and
procedural requirements for their validation, in order to meet a particular business need, and under which the digital
signature(s) can be determined to be valid
trust service provider: natural or legal person who provides one or more trust services
validation data: data that is used to validate a digital signature
verifier: entity that wants to validate or verify a digital signature
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.12] and the following apply:
DSS Document Security Store
ETSI
9 ETSI EN 319 142-1 V1.3.1 (2026-11)
4 General syntax
4.1 General requirements for PAdES signatures based on PDF
signatures
PAdES signatures profiled in the present document build on PDF signatures specified in either ISO 32000-1 [1] or
ISO 32000-2 [9] with an alternative signature encoding to support digital signature formats equivalent to the signature
format CAdES as specified in ETSI EN 319 122-1 [2], by incorporation of signed and unsigned attributes described in
clause 5.
The following requirements apply:
a) A DER-encoded SignedData object as specified in ETSI EN 319 122-1 [2] shall be included as the PDF
signature in the entry with the key Contents of the Signature Dictionary as described in ISO 32000-1 [1],
clause 12.8.1 or ISO 32000-2 [9], clause 12.8.1. There shall only be a single signer (i.e. one single component
of SignerInfo type within signerInfos element) in any PDF Signature. Regardless of the PDF version
used, the byte-range covered by the signature shall comprise exactly the entire PDF revision being signed
except for the Contents space itself, leaving no unmapped bytes outside the ByteRange definition.
b) Requirements for handling PDF Signatures specified in ISO 32000-1 [1], clause 12.8 or ISO 32000-2 [9],
clause 12.8 shall apply except where overridden by the present document.
When signatures are generated based on ISO 32000-2 [9], cryptographically secure digest algorithms (defined
in ETSI TS 119 312 [i.6]) shall be used, and legacy algorithms (MD5 and SHA-1) shall not be used for new
signature creation. For signatures based on ISO 32000-1 [1], the use of SHA-256 or stronger algorithms is
highly recommended for signature creation, while SHA-1 and MD5 may be supported solely for verification
purposes of legacy documents.
NOTE 1: Given that PAdES signatures are enveloped inside a PDF document and are detached in the sense of a
CMS signature, the signature placement is implied by ISO 32000-1 [1] or ISO 32000-2 [9].
In ISO 32000-1 [1], clause 12.8.3.3.1 reads "No data shall be encapsulated in the PKCS#7 SignedData
field" whereas in ISO 32000-2 [9], the corresponding clause refers to the field as the CMS SignedData
field.
NOTE 2: ISO 32000-2 [9] deprecates legacy SubFilter values like adbe.pkcs7.sha1. For maximum interoperability
across PDF versions, the SubFilter value ETSI.CAdES.detached should be used, as it is natively
supported by ISO 32000-2 [9] (Table 252) and widely implemented as an extension in ISO 32000-1 [1]
compliant software.
c) Some signature attributes found in ETSI EN 319 122-1 [2] have the same or similar meaning as keys in the
Signature Dictionary described in ISO 32000-1 [1] or ISO 32000-2 [9]. For signature attributes and keys that
have the same or similar meaning only one of them should be used according to the requirements set in
Table 1.
5 Attributes syntax and semantics
5.1 Introduction
This clause provides details on attributes specified within ISO 32000-1 [1], ISO 32000-2 [9], and ETSI
EN 319 122-1 [2] and defines new attributes for building PAdES signatures.
The clause distinguishes between the following types of attributes: CMS and CAdES defined attributes,
ISO 32000-1 [1] or ISO 32000-2 [9] defined attributes, validation data and archive validation data attributes.
• The first ones are the attributes that build the DER-encoded SignedData object included as the PDF signature
in the entry with the key Contents of the Signature Dictionary as described in ISO 32000-1 [1], clause 12.8.1
or ISO 32000-2 [9], clause 12.8.1. Depending on the underlying PDF specification version, this object
conforms either to the PKCS#7 format or the CMS (Cryptographic Message Syntax) format, respectively.
ETSI
10 ETSI EN 319 142-1 V1.3.1 (2026-11)
• The second ones are the attributes that build the Signature Dictionary as described in ISO 32000-1 [1] or
ISO 32000-2 [9].
• The other ones are the attributes where to include validation data and archive validation data that can guarantee
long term validity of digital signatures.
Clause 6.3 provides the requirements concerning how to use the attributes described above.
5.2 CMS and CAdES defined attributes
The attributes included in the following list may be used to generate the DER-encoded SignedData object included as
the PDF signature in the entry with the key Contents of the Signature Dictionary as described in ISO 32000-1 [1],
clause 12.8.1 or ISO 32000-2 [9], clause 12.8.1. Their syntax shall be as defined in ETSI EN 319 122-1 [2], clause 5.
• content-type
• message-digest
• Signing certificate reference attributes
- ESS signing-certificate
May be used for legacy compliance in ISO 32000-1 [1] signatures; shall not be used in ISO 32000-2 [9]
signatures.
- ESS signing-certificate-v2
Shall be used for ISO 32000-2 [9] signatures and is strongly recommended for ISO 32000-1 [1]
signatures using SHA-2 or stronger digest algorithms.
• commitment-type-indication
• signer-attributes-v2
• content-time-stamp
• signature-policy-identifier
• signature-time-stamp
5.3 ISO 32000 defined attributes
The entries of the Signature Dictionary shall be as defined in ISO 32000-1 [1], clause 12.8.1 (Table 252) or
ISO 32000-2 [9], clause 12.8.1 (Table 254).
For the following signature dictionary entries, these additional requirements apply:
• SubFilter
For signatures conforming to ISO 32000-2 [9], this shall be set to ETSI.CAdES.detached. For legacy
compliance with ISO 32000-1 [1], adbe.pkcs7.detached may be supported for verification, but
ETSI.CAdES.detached is preferred for new signature generation.
• Contents
Shall contain the DER-encoded SignedData object as specified in clause 4.1.a).
• ByteRange
Shall be used to identify the bytes of the document covered by the signature, conforming to the gapless
requirement specified in clause 4.1.a).
ETSI
11 ETSI EN 319 142-1 V1.3.1 (2026-11)
• M
The time of signing. The syntax shall conform to the Date format specified in ISO 32000-1 [1] or
ISO 32000-2 [9]).
• Name (Optional)
The name of the person or authority signing the document. This value should be used only when it is not
possible to extract the name from the signature.
• Location (Optional)
To prevent data redundancy and synchronization conflicts during validation, this key shall not be used if
equivalent information is present within the CMS signed attributes of the signature: signer-location.
• Reason (Optional)
To prevent data redundancy and synchronization conflicts during validation, this key shall not be used if
equivalent information is present within the CMS signed attributes of the signature: commitment-type-
indication.
• ContactInfo (Optional)
• Prop_Build (Optional in ISO 32000-1 [1], strongly recommended in ISO 32000-2 [9])
In ISO 32000-2 [9] strongly recommended to build an internal dictionary containing the software application
name, version, and operating system used to create the signature.
5.4 Validation data and archive validation data attributes
5.4.1 Overview
Validation of a digital signature requires data to validate the signature such as CA certificates, Certificate Revocation
List (CRL) or Online Certificate Status Protocol (OCSP) commonly provided by online services (referred to in the
present document as validation data).
This clause describes the mechanism to carry such validation data as necessary to validate a signature, optionally with
Validation Related Information (VRI) which relates the validation data to a specific signature (see clause 5.4.2).
For signatures based on ISO 32000-1 [1], this mechanism is implemented via the Document Security Store (DSS)
extension. For signatures based on ISO 32000-2 [9], this mechanism relies on the native Document Security Store
(DSS) as formally standardized in ISO 32000-2 [9], clause 12.8.4.
The structure of DSS and VRI is illustrated in Figure 1.
ETSI
12 ETSI EN 319 142-1 V1.3.1 (2026-11)
DSS dict
VRI
Indirect references to all Certs
Indirect references to all OCSPs
Indirect references to all CRLs
VRI of a specific signature
Indirect references to required Certs
Indirect references to required OCSPs
Indirect references to required CRLs
Cert1 (value)
Cert2 (value)
OCSP1 (response value)
CRL1 (value)
Certn (value)
OCSPn (value)
CRLn (value)
Figure 1: Illustration of DSS and VRI structures
For PDF documents based on ISO 32000-1 [1], this clause also defines an extension called Document Time-stamp (see
clause 5.4.3) to extend the life-time of protection to the document.
NOTE 1: ISO 32000-2 [9] includes this feature natively.
These extensions support Long Term Validation (LTV) of PDF Signatures. The structure of a PDF document with LTV
data is illustrated in Figure 2.
Document
Security Store
Document
Time-stamp
Figure 2: Illustration of PDF document with extended life-time protection
The life-time of the protection can be further extended beyond the life-time of the last Document Time-stamp applied
by adding further DSS information to validate the previous last Document Time-stamp along with a new Document
Time-stamp. Every time a DSS Dictionary is updated during incremental update, it should contain the values from the
previous DSS Dictionary.
NOTE 2: In general the DSS Dictionary will contain validation data from previous revisions plus validation data
added for the current revision. If entries are removed from a DSS Dictionary during an incremental
update the set of validation data might not be complete for validation of the signatures, but replacement of
validation data - e.g. more up-to-date certificate status information - might be performed for optimization
reasons.
ETSI
13 ETSI EN 319 142-1 V1.3.1 (2026-11)
This is illustrated in Figure 3.
Figure 3: Illustration of PDF Document with repeated LTV data
5.4.2 Document Security Store
5.4.2.1 Catalog
For documents conforming to ISO 32000-1 [1], the DSS entry is added to Table 28 ("Entries in catalogue dictionary").
Added to ISO 32000-1 [1], Table 28 "Entries in catalogue dictionary"
KEY TYPE VALUE
DSS Dictionary (Optional) Document-wide security-related information.
For documents conforming to ISO 32000-2 [9], the DSS entry shall be populated in accordance with Table 31 ("Entries
in the document catalog dictionary") of the PDF 2.0 specification.
5.4.2.2 DSS Dictionary
The Document Security Store (DSS) shall be a dictionary that shall have the value DSS as key in the document catalog
dictionary. This dictionary is used to provide a single place where all of the VRI for some or all signatures in the
document should be placed.
The DSS dictionary, if present, shall contain VRI only for document and time-stamps signatures represented in PKCS#7
and CMS (and its derivatives) format or for XAdES signatures of forms signing dynamic XFA [i.7].
NOTE 1: See ETSI EN 319 142-2 [i.11] for specification of XAdES signatures of forms signing dynamic XFA.
ETSI
14 ETSI EN 319 142-1 V1.3.1 (2026-11)
Entries in a DSS Dictionary (Conforming to ISO 32000-1 [1] extensions or natively to ISO 32000-2 [9], Table 256):
Entries in a DSS Dictionary
KEY TYPE VALUE
Type Name (Optional) It shall be DSS for a document security store
dictionary.
VRI
Dictionary (Optional) This dictionary contains Signature VRI dictionaries in
the document. For ISO 32000-1 [1] documents the key of each
entry in this dictionary is the base-16-encoded (uppercase)
SHA1 digest of the signature to which it applies and the value
is the Signature VRI dictionary which contains the VRI for that
signature.
See additional requirements a), b), c) and d).
Certs Array (Optional) An array of indirect references to streams, each
containing one DER-encoded X.509 certificate (that shall be as
defined in IETF RFC 5280 [4]). This array contains certificates
that can be used in the validation of any signatures in the
document.
OCSPs Array (Optional) An array of indirect references to streams, each
containing a DER-encoded Online Certificate Status
Protocol (OCSP) response, which can be used in the validation
of any signature in the document. The OCSP response shall be
encoded by using the encoding of the OCSPResponse type as
defined in IETF RFC 6960 [5] (see note 2).
CRLs Array (Optional) An array of indirect references to streams, each
containing a DER-encoded Certificate Revocation List (CRL)
(that shall be as defined in IETF RFC 5280 [4]). This array
contains CRLs that can be used in the validation of any
signatures in the document.
Additional requirements for VRI keys:
a) For document signatures or Document Time-stamp signatures the bytes that are hashed shall be those of the
complete hexadecimal string in the entry with the key Contents of the associated Signature Dictionary
containing the signature's DER-encoded binary data object (e.g. PKCS#7, CMS or CAdES objects).
b) For the signatures of CRLs and OCSP responses, the bytes that are hashed shall be the respective signature
objects represented as a BER-encoded OCTET STRING encoded with primitive encoding.
c) When computing the digest of a XAdES signature found in dynamic XFA [i.7], the contents of the ds:Signature
shall be canonicalized using exclusive canonicalization (http://www.w3.org/2001/10/xml-exc-c14n#) as
specified in [7] and then hashed.
Any VRI dictionaries shall be located in document incremental update sections. If the Signature Dictionary to which a
VRI dictionary applies is itself in an incremental update section (see clause 7.5.6 of ISO 32000-1 [1] or clause 7.5.6 of
ISO 32000-2 [9]), the VRI update shall be done later than the signature update.
NOTE 2: To facilitate the verification of signatures created according to previous versions of the signature format
specifications, a verifier can also accept OCSP responses encoded by using the encoding of the
BasicOCSPResponse type as defined in IETF RFC 6960 [5].
ETSI
15 ETSI EN 319 142-1 V1.3.1 (2026-11)
5.4.2.3 Signature VRI Dictionary
The signature VRI dictionary shall contain Validation Related Information (VRI) for a specific signature in the
document to which the validation information applies.
Entries in a Signature VRI Dictionary (Conforming to ISO 32000-1 [1] extensions or natively to ISO 32000-2 [9],
Table 257):
Entries in a Signature VRI Dictionary
KEY TYPE VALUE
Type (Optional),if present, it shall be VRI for a VRI dictionary.
Name
Cert (Optional, if present, it shall not be an empty array) An array of
Array
indirect references to streams, each containing one DER-encoded
X.509 certificate (that shall be as defined in IETF RFC 5280 [4]). This
array should contain all certificates that were used in the validation of
this signature.
CRL Array (Optional, if present, it shall not be an empty array) An array of
indirect references to streams that are all CRLs used to determine the
validity of the certificates in the chains related to this signature. Each
stream shall reference a CRL that is an entry in the CRLs array in the
DSS dictionary.
OCSP (Optional, if present shall not be an empty array) An array of indirect
Array
references to streams that are all OCSP responses used to determine
the validity of the certificates in the chains related to this signature.
Each stream shall reference an OCSP response that is an entry in the
OCSPs array in the DSS dictionary.
TU Date (Optional), the date/time at which this signature VRI dictionary was
created. A signature handler may ignore this entry and use a different
time for the signature validation. This entry shall be absent when the
TS entry is present. Date shall be a date string as defined in
ISO 32000-1 [1], clause 7.9.4 or ISO 32000-2 [9], clause 7.9.4. See
additional requirement a).
TS Stream (Optional), a stream containing the DER-encoded time-stamp token
(that shall be as defined in IETF RFC 3161 [6] updated by IETF
RFC 5816 [8] and which represents the secure time at which this
signature VRI dictionary was created. This entry shall be absent when
a TU entry is present. See note 1 and additional requirement b).
Additional requirements:
a) The TU key should not be used.
b) The TS key should not be used.
c) Exactly one of the following methods to provide a VRI generation claimed time shall be used: the TU entry, the
TS entry or a subsequent Document Time-stamp.
NOTE 1: For PKCS#7 signatures conforming to ISO 32000-1 [1] the datum that is hashed and included in the
messageImprint field of the DER-encoded time stamp stored in TS entry (see IETF RFC 3161 [6] updated
by IETF RFC 5816 [8]) is the encryptedDigest field in the signature's PKCS#7 object (as defined in IETF
RFC 2315 [i.9]). For CMS signatures conforming to ISO 32000-2 [9], the corresponding signature value field
within the SignerInfo structure shall be used.
NOTE 2: The VRI dictionary is optional, since all necessary data to validate the signature can be available from other
sources like the DSS dictionary itself. The VRI dictionary offers possibilities for optimization of the validation
process, since it relates the data to one specific signature.
NOTE 3: The value of TS can be used as a proof of existence for the signature value itself.
Any values in the Cert, CRL and OCSP arrays of a Signature VRI dictionary shall also be present in the DSS dictionary
applicable to the signature for which this Signature VRI dictionary is associated. If this signature (e.g. PKCS#7, CMS
or CAdES object) does not have any associated Certs, CRLs or OCSPs, then the corresponding key shall not be present
in the VRI dictionary.
A Signature VRI dictionary shall not be used to record the information used in an unsuccessful validation attempt.
MDP restrictions (see ISO 32000-1 [1], clause 12.8.2.2 or ISO 32000-2 [9], clauses 12.8.2.2 and 12.7.5.5) shall not
apply to incremental updates to a PDF document containing a DSS dictionary and associated VRI, Certs, CRLs and
OCSPs.
ETSI
16 ETSI EN 319 142-1 V1.3.1 (2026-11)
NOTE: ISO 32000-1 [1], clause 12.8.2.2 and ISO 32000-2 [9], clauses 12.8.2.2 and 12.7.5.5, address the MDP
(Modification, Detection and Prevention) feature whereby a set of permissions can be associated with a
PDF in conjunction with a certification signature. The permissions of MDP are present in the entry with
the P key of the DocMDP transform parameters dictionary and of the signature field lock dictionary, as an
integer in the range 1 through 3. Values of 2 and 3 allow for additional signatures to be included after the
certification but a value of 1 does not allow any change but allows Document Time-stamps.
5.4.3 Document Time-stamp
A Document Time-stamp dictionary shall be a standard Signature Dictionary (as defined in ISO 32000-1 [1],
clause 12.8.1, Table 252) with the following changes.
Modifications to the standard Signature Dictionary for a Document Time-stamp Dictionary:
Modifications to Table 252 for a Document Time-stamp Dictionary of ISO 32000-1 [1]
KEY TYPE VALUE
Type Name (Required) It shall be DocTimeStamp.
SubFilter Name (Required) The value of SubFilter identifies the format of the data contained in
the stream. A conforming reader may use any signature handler that supports the
specified format.
The value of SubFilter should be ETSI.RFC3161.
Other values may be defined by developers, and when used, shall be prefixed
with the registered developer identification as described in ISO 32000-1 [1],
annex E.
Contents
Byte string (Required) When the value of SubFilter is ETSI.RFC3161, the value of
Contents shall be the hexadecimal string (as defined in clause 7.3.4.3 in
ISO 32000-1 [1]) representing the value of TimeStampToken as specified in IETF
RFC 3161 [6] updated by IETF RFC 5816 [8]. The value of the
messageImprint field within the TimeStampToken shall be a hash of the bytes
of the document indicated by the ByteRange. The cryptographic digest algorithm
used for the messageImprint shall comply with the algorithm require
...
SLOVENSKI STANDARD
01-januar-2027
Elektronski podpisi in infrastrukture zaupanja (ESI) - Digitalni podpisi PAdES - 1.
del: Gradniki in izhodiščni podpisi PAdES
Electronic Signatures and Trust Infrastructures (ESI) - PAdES digital signatures - Part 1:
Building blocks and PAdES baseline signatures
Ta slovenski standard je istoveten z: ETSI EN 319 142-1 V1.3.1 (2026-11)
ICS:
35.040.01 Kodiranje informacij na Information coding in general
splošno
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN STANDARD
Electronic Signatures and Trust Infrastructures (ESI);
PAdES digital signatures;
Part 1: Building blocks and PAdES baseline signatures
2 ETSI EN 319 142-1 V1.3.1 (2026-11)
Reference
REN/ESI-0019142-1v131
Keywords
electronic signature, PAdES, profile, security
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part of this document may be reproduced in any form, by any means and in any media, without the prior written
authorization of ETSI and except as expressly permitted below.
By way of exception and when the document is a normative deliverable (European Standard (EN),
Technical Specification (TS), Group Specification (GS) or ETSI Standard (ES)), ETSI authorizes to reproduce
and incorporate into products, services and technical documentation only those extracts (e.g. templates) that are strictly
necessary for the technical implementation of the normative deliverable, to ensure compliance with the latter.
Nothing in this notice shall be construed as limiting any mandatory exceptions to copyright provided by applicable law.
© ETSI 2026.
All rights reserved.
ETSI
3 ETSI EN 319 142-1 V1.3.1 (2026-11)
Contents
Intellectual Property Rights . 4
Foreword . 4
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definition of terms, symbols and abbreviations . 8
3.1 Terms . 8
3.2 Symbols . 8
3.3 Abbreviations . 8
4 General syntax . 9
4.1 General requirements for PAdES signatures based on PDF signatures . 9
5 Attributes syntax and semantics . 9
5.1 Introduction . 9
5.2 CMS and CAdES defined attributes . 10
5.3 ISO 32000 defined attributes . 10
5.4 Validation data and archive validation data attributes . 11
5.4.1 Overview . 11
5.4.2 Document Security Store . 13
5.4.2.1 Catalog . 13
5.4.2.2 DSS Dictionary . 13
5.4.2.3 Signature VRI Dictionary . 15
5.4.3 Document Time-stamp . 16
5.4.4 Validation of PAdES signatures . 16
5.5 Requirements on encryption . 17
5.6 Extensions dictionary and PDF 2.0 conformance . 17
5.6.1 ISO 32000-1 (PDF 1.7) Compliant Documents . 17
5.6.2 ISO 32000-2 (PDF 2.0) Compliant Documents . 18
5.6.3 Version conformance across document revisions . 18
6 PAdES baseline signatures . 18
6.1 Signature levels . 18
6.2 General requirements for PAdES baseline signatures . 19
6.2.1 Algorithm requirements . 19
6.2.2 Notation for requirements . 19
6.3 PAdES baseline signatures . 21
6.4 Legacy PAdES baseline signatures . 27
Annex A (informative): Change history . 28
History . 29
ETSI
4 ETSI EN 319 142-1 V1.3.1 (2026-11)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables (European Standard (EN), Technical Specification (TS),
Group Specification (GS) or ETSI Standard (ES)) may have been declared to ETSI. The declarations pertaining to these
essential IPRs, if any, are publicly available for ETSI members and non-members, and can be found in
ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Foreword
This European Standard (EN) has been produced by ETSI Technical Committee Electronic Signatures and Trust
Infrastructures (ESI).
The present document is part 1 of a multi-part deliverable covering the PDF digital signatures (PAdES), as identified
below:
ETSI EN 319 142-1: "Building blocks and PAdES baseline signatures";
ETSI EN 319 142-2: "Additional PAdES signatures profiles";
ETSI TS 119 142-3: "PAdES Document Time-stamp digital signatures (PAdES-DTS)".
National transposition dates
Date of adoption of this EN: 9 November 2026
Date of latest announcement of this EN (doa): 28 February 2027
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 August 2027
Date of withdrawal of any conflicting National Standard (dow): 31 August 2027
ETSI
5 ETSI EN 319 142-1 V1.3.1 (2026-11)
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
Electronic commerce has emerged as a frequent way of doing business between companies across local, wide area and
global networks. Trust in this way of doing business is essential for the success and continued development of
electronic commerce. It is therefore important that companies using this electronic means of doing business have
suitable security controls and mechanisms in place to protect their transactions and to ensure trust and confidence with
their business partners. In this respect digital signatures are an important security component that can be used to protect
information and provide trust in electronic business.
The present document is intended to cover digital signatures supported by PKI and public key certificates, and aims to
meet the general requirements of the international community to provide trust and confidence in electronic transactions,
including, amongst other, applicable requirements from Regulation (EU) No 910/2014 [i.2].
The present document can be used for any transaction between an individual and a company, between two companies,
between an individual and a governmental body, etc. The present document is independent of any environment. It can
be applied to any environment e.g. smart cards, SIM cards, special programs for electronic signatures, etc.
The present document is part of a rationalized framework of standards (see ETSI TR 119 000 [i.3]).
ETSI TR 119 100 [i.4] provides guidance on how to use the present document within the aforementioned framework.
ETSI
6 ETSI EN 319 142-1 V1.3.1 (2026-11)
1 Scope
The present document specifies PAdES digital signatures. PAdES signatures build on PDF signature mechanisms
defined in the ISO 32000 series. For documents conforming to ISO 32000-1 [1] PAdES utilizes an extended, alternative
signature encoding. For documents conforming to ISO 32000-2 [9], these signature structures are incorporated natively
by default within the core standard. Both approaches support digital signature formats equivalent to the signature format
CAdES as specified in ETSI EN 319 122-1 [2], by incorporation of signed and unsigned attributes, which fulfil certain
common requirements (such as the long term validity of digital signatures) in a number of use cases.
The present document specifies formats for PAdES baseline signatures, which provide the basic features necessary for a
wide range of business and governmental use cases for electronic procedures and communications to be applicable to a
wide range of communities when there is a clear need for interoperability of digital signatures used in electronic
documents.
The present document defines four levels of PAdES baseline signatures addressing incremental requirements to
maintain the validity of the signatures over the long term, in a way that a certain level always addresses all the
requirements addressed at levels that are below it. Each level requires the presence of certain PAdES attributes, suitably
profiled for reducing the optionality as much as possible.
Procedures for creation, augmentation, and validation of PAdES digital signatures are out of scope and specified in
ETSI EN 319 102-1 [10]. Guidance on creation, augmentation and validation of PAdES digital signatures including the
usage of the different attributes defined in the present document is provided in ETSI TR 119 100 [i.4]. The present
document aims at supporting electronic signatures in different regulatory frameworks.
NOTE: Specifically but not exclusively, PAdES digital signatures specified in the present document aim at
supporting electronic signatures, advanced electronic signatures, qualified electronic signatures,
electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU)
No 910/2014 [i.2].
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found in the
ETSI docbox.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents are necessary for the application of the present document.
[1] ISO 32000-1: "Document management — Portable document format — Part 1: PDF 1.7".
[2] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures;
Part 1: Building blocks and CAdES baseline signatures".
[3] IETF RFC 5652 (2009): "Cryptographic Message Syntax (CMS)".
[4] IETF RFC 5280 (2008): "Internet X.509 Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile".
[5] IETF RFC 6960 (2013): "X.509 Internet Public Key Infrastructure Online Certificate Status
Protocol - OCSP".
[6] IETF RFC 3161 (2001): "Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)". ®
[7] W3C Recommendation (2 May 2008): "Canonical XML Version 1.1".
ETSI
7 ETSI EN 319 142-1 V1.3.1 (2026-11)
[8] IETF RFC 5816 (2010): "ESSCertIDv2 Update for RFC 3161".
[9] ISO 32000-2: "Document management — Portable document format —Part 2: PDF 2.0".
[10] ETSI EN 319 102-1: "Electronic Signatures and Trust Infrastructures (ESI); Procedures for
Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long-term validity.
The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's
understanding, but are not required for conformance to the present document.
[i.1] Void.
[i.2] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on
electronic identification and trust services for electronic transactions in the internal market and
repealing Directive 1999/93/EC.
[i.3] ETSI TR 119 000: "Electronic Signatures and Infrastructures (ESI); The framework for
standardization of digital signatures and trust services; Overview".
[i.4] ETSI TR 119 100: "Electronic Signatures and Infrastructures (ESI); Guidance on the use of
standards for signature creation and validation".
[i.5] Void.
[i.6] ETSI TS 119 312: "Electronic Signatures and Trust Infrastructures (ESI); Cryptographic Suites". ®
[i.7] Adobe XFA: "XML Forms Architecture (XFA) Specification" version 2.5, (June 2007), Adobe
Systems Incorporated".
[i.8] ETSI TS 103 172: "Electronic Signatures and Infrastructures (ESI); PAdES Baseline Profile".
[i.9] IETF RFC 2315 (1998): "PKCS #7: Cryptographic Message Syntax Version 1.5".
[i.10] ETSI TS 119 612: "Electronic Signatures and Trust Infrastructures (ESI); Trusted Lists".
[i.11] ETSI EN 319 142-2: "Electronic Signatures and Trust Infrastructures (ESI); PAdES digital
signatures; Part 2: Additional PAdES signatures profiles".
[i.12] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for
standardization of signatures; Definitions and abbreviations".
[i.13] ETSI TS 119 511: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security
requirements for trust service providers providing long-term preservation of digital signatures or
general data using digital signature techniques".
ETSI
8 ETSI EN 319 142-1 V1.3.1 (2026-11)
3 Definition of terms, symbols and abbreviations
3.1 Terms
For the purposes of the present document, the terms given in ISO 32000-1 [1], ISO 32000-2 [9], ETSI
TR 119 001 [i.12] and the following apply:
digital signature: data appended to, or a cryptographic transformation of a data unit that allows a recipient of the data
unit to prove the source and integrity of the data unit and protect against forgery, e.g. by the recipient
digital signature value: result of the cryptographic transformation of a data unit that allows a recipient of the data unit
to prove the source and integrity of the data unit and protect against forgery, e.g. by the recipient
electronic time-stamp: data in electronic form which binds other electronic data to a particular time establishing
evidence that these data existed at that time
generator: any party which creates, or augments a digital signature
NOTE: This can be the signer or any party that initially validates or further maintains the signature.
legacy PAdES baseline signature: digital signature generated according to ETSI TS 103 172 [i.8]
PAdES signature: digital signature that satisfies the requirements specified within the present document or ETSI
EN 319 142-2 [i.11]
proof of existence: evidence that proves that an object existed at a specific date/time
signature augmentation policy: set of rules, applicable to one or more digital signatures, that defines the technical and
procedural requirements for their augmentation, in order to meet a particular business need, and under which the digital
signature(s) can be determined to be conformant
signature creation policy: set of rules, applicable to one or more digital signatures, that defines the technical and
procedural requirements for their creation, in order to meet a particular business need, and under which the digital
signature(s) can be determined to be conformant
signature handler: software application, or part of a software application, that knows how to perform digital signature
operations (e.g. signing and/or validating) in conformance with ISO 32000-1 [1] or ISO 32000-2 [9] and the
requirements of the appropriate profile
signature policy: signature creation policy, signature augmentation policy, signature validation policy or any
combination thereof, applicable to the same signature or set of signatures
signature validation policy: set of rules, applicable to one or more digital signatures, that defines the technical and
procedural requirements for their validation, in order to meet a particular business need, and under which the digital
signature(s) can be determined to be valid
trust service provider: natural or legal person who provides one or more trust services
validation data: data that is used to validate a digital signature
verifier: entity that wants to validate or verify a digital signature
3.2 Symbols
Void.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.12] and the following apply:
DSS Document Security Store
ETSI
9 ETSI EN 319 142-1 V1.3.1 (2026-11)
4 General syntax
4.1 General requirements for PAdES signatures based on PDF
signatures
PAdES signatures profiled in the present document build on PDF signatures specified in either ISO 32000-1 [1] or
ISO 32000-2 [9] with an alternative signature encoding to support digital signature formats equivalent to the signature
format CAdES as specified in ETSI EN 319 122-1 [2], by incorporation of signed and unsigned attributes described in
clause 5.
The following requirements apply:
a) A DER-encoded SignedData object as specified in ETSI EN 319 122-1 [2] shall be included as the PDF
signature in the entry with the key Contents of the Signature Dictionary as described in ISO 32000-1 [1],
clause 12.8.1 or ISO 32000-2 [9], clause 12.8.1. There shall only be a single signer (i.e. one single component
of SignerInfo type within signerInfos element) in any PDF Signature. Regardless of the PDF version
used, the byte-range covered by the signature shall comprise exactly the entire PDF revision being signed
except for the Contents space itself, leaving no unmapped bytes outside the ByteRange definition.
b) Requirements for handling PDF Signatures specified in ISO 32000-1 [1], clause 12.8 or ISO 32000-2 [9],
clause 12.8 shall apply except where overridden by the present document.
When signatures are generated based on ISO 32000-2 [9], cryptographically secure digest algorithms (defined
in ETSI TS 119 312 [i.6]) shall be used, and legacy algorithms (MD5 and SHA-1) shall not be used for new
signature creation. For signatures based on ISO 32000-1 [1], the use of SHA-256 or stronger algorithms is
highly recommended for signature creation, while SHA-1 and MD5 may be supported solely for verification
purposes of legacy documents.
NOTE 1: Given that PAdES signatures are enveloped inside a PDF document and are detached in the sense of a
CMS signature, the signature placement is implied by ISO 32000-1 [1] or ISO 32000-2 [9].
In ISO 32000-1 [1], clause 12.8.3.3.1 reads "No data shall be encapsulated in the PKCS#7 SignedData
field" whereas in ISO 32000-2 [9], the corresponding clause refers to the field as the CMS SignedData
field.
NOTE 2: ISO 32000-2 [9] deprecates legacy SubFilter values like adbe.pkcs7.sha1. For maximum interoperability
across PDF versions, the SubFilter value ETSI.CAdES.detached should be used, as it is natively
supported by ISO 32000-2 [9] (Table 252) and widely implemented as an extension in ISO 32000-1 [1]
compliant software.
c) Some signature attributes found in ETSI EN 319 122-1 [2] have the same or similar meaning as keys in the
Signature Dictionary described in ISO 32000-1 [1] or ISO 32000-2 [9]. For signature attributes and keys that
have the same or similar meaning only one of them should be used according to the requirements set in
Table 1.
5 Attributes syntax and semantics
5.1 Introduction
This clause provides details on attributes specified within ISO 32000-1 [1], ISO 32000-2 [9], and ETSI
EN 319 122-1 [2] and defines new attributes for building PAdES signatures.
The clause distinguishes between the following types of attributes: CMS and CAdES defined attributes,
ISO 32000-1 [1] or ISO 32000-2 [9] defined attributes, validation data and archive validation data attributes.
• The first ones are the attributes that build the DER-encoded SignedData object included as the PDF signature
in the entry with the key Contents of the Signature Dictionary as described in ISO 32000-1 [1], clause 12.8.1
or ISO 32000-2 [9], clause 12.8.1. Depending on the underlying PDF specification version, this object
conforms either to the PKCS#7 format or the CMS (Cryptographic Message Syntax) format, respectively.
ETSI
10 ETSI EN 319 142-1 V1.3.1 (2026-11)
• The second ones are the attributes that build the Signature Dictionary as described in ISO 32000-1 [1] or
ISO 32000-2 [9].
• The other ones are the attributes where to include validation data and archive validation data that can guarantee
long term validity of digital signatures.
Clause 6.3 provides the requirements concerning how to use the attributes described above.
5.2 CMS and CAdES defined attributes
The attributes included in the following list may be used to generate the DER-encoded SignedData object included as
the PDF signature in the entry with the key Contents of the Signature Dictionary as described in ISO 32000-1 [1],
clause 12.8.1 or ISO 32000-2 [9], clause 12.8.1. Their syntax shall be as defined in ETSI EN 319 122-1 [2], clause 5.
• content-type
• message-digest
• Signing certificate reference attributes
- ESS signing-certificate
May be used for legacy compliance in ISO 32000-1 [1] signatures; shall not be used in ISO 32000-2 [9]
signatures.
- ESS signing-certificate-v2
Shall be used for ISO 32000-2 [9] signatures and is strongly recommended for ISO 32000-1 [1]
signatures using SHA-2 or stronger digest algorithms.
• commitment-type-indication
• signer-attributes-v2
• content-time-stamp
• signature-policy-identifier
• signature-time-stamp
5.3 ISO 32000 defined attributes
The entries of the Signature Dictionary shall be as defined in ISO 32000-1 [1], clause 12.8.1 (Table 252) or
ISO 32000-2 [9], clause 12.8.1 (Table 254).
For the following signature dictionary entries, these additional requirements apply:
• SubFilter
For signatures conforming to ISO 32000-2 [9], this shall be set to ETSI.CAdES.detached. For legacy
compliance with ISO 32000-1 [1], adbe.pkcs7.detached may be supported for verification, but
ETSI.CAdES.detached is preferred for new signature generation.
• Contents
Shall contain the DER-encoded SignedData object as specified in clause 4.1.a).
• ByteRange
Shall be used to identify the bytes of the document covered by the signature, conforming to the gapless
requirement specified in clause 4.1.a).
ETSI
11 ETSI EN 319 142-1 V1.3.1 (2026-11)
• M
The time of signing. The syntax shall conform to the Date format specified in ISO 32000-1 [1] or
ISO 32000-2 [9]).
• Name (Optional)
The name of the person or authority signing the document. This value should be used only when it is not
possible to extract the name from the signature.
• Location (Optional)
To prevent data redundancy and synchronization conflicts during validation, this key shall not be used if
equivalent information is present within the CMS signed attributes of the signature: signer-location.
• Reason (Optional)
To prevent data redundancy and synchronization conflicts during validation, this key shall not be used if
equivalent information is present within the CMS signed attributes of the signature: commitment-type-
indication.
• ContactInfo (Optional)
• Prop_Build (Optional in ISO 32000-1 [1], strongly recommended in ISO 32000-2 [9])
In ISO 32000-2 [9] strongly recommended to build an internal dictionary containing the software application
name, version, and operating system used to create the signature.
5.4 Validation data and archive validation data attributes
5.4.1 Overview
Validation of a digital signature requires data to validate the signature such as CA certificates, Certificate Revocation
List (CRL) or Online Certificate Status Protocol (OCSP) commonly provided by online services (referred to in the
present document as validation data).
This clause describes the mechanism to carry such validation data as necessary to validate a signature, optionally with
Validation Related Information (VRI) which relates the validation data to a specific signature (see clause 5.4.2).
For signatures based on ISO 32000-1 [1], this mechanism is implemented via the Document Security Store (DSS)
extension. For signatures based on ISO 32000-2 [9], this mechanism relies on the native Document Security Store
(DSS) as formally standardized in ISO 32000-2 [9], clause 12.8.4.
The structure of DSS and VRI is illustrated in Figure 1.
ETSI
12 ETSI EN 319 142-1 V1.3.1 (2026-11)
DSS dict
VRI
Indirect references to all Certs
Indirect references to all OCSPs
Indirect references to all CRLs
VRI of a specific signature
Indirect references to required Certs
Indirect references to required OCSPs
Indirect references to required CRLs
Cert1 (value)
Cert2 (value)
OCSP1 (response value)
CRL1 (value)
Certn (value)
OCSPn (value)
CRLn (value)
Figure 1: Illustration of DSS and VRI structures
For PDF documents based on ISO 32000-1 [1], this clause also defines an extension called Document Time-stamp (see
clause 5.4.3) to extend the life-time of protection to the document.
NOTE 1: ISO 32000-2 [9] includes this feature natively.
These extensions support Long Term Validation (LTV) of PDF Signatures. The structure of a PDF document with LTV
data is illustrated in Figure 2.
Document
Security Store
Document
Time-stamp
Figure 2: Illustration of PDF document with extended life-time protection
The life-time of the protection can be further extended beyond the life-time of the last Document Time-stamp applied
by adding further DSS information to validate the previous last Document Time-stamp along with a new Document
Time-stamp. Every time a DSS Dictionary is updated during incremental update, it should contain the values from the
previous DSS Dictionary.
NOTE 2: In general the DSS Dictionary will contain validation data from previous revisions plus validation data
added for the current revision. If entries are removed from a DSS Dictionary during an incremental
update the set of validation data might not be complete for validation of the signatures, but replacement of
validation data - e.g. more up-to-date certificate status information - might be performed for optimization
reasons.
ETSI
13 ETSI EN 319 142-1 V1.3.1 (2026-11)
This is illustrated in Figure 3.
Figure 3: Illustration of PDF Document with repeated LTV data
5.4.2 Document Security Store
5.4.2.1 Catalog
For documents conforming to ISO 32000-1 [1], the DSS entry is added to Table 28 ("Entries in catalogue dictionary").
Added to ISO 32000-1 [1], Table 28 "Entries in catalogue dictionary"
KEY TYPE VALUE
DSS Dictionary (Optional) Document-wide security-related information.
For documents conforming to ISO 32000-2 [9], the DSS entry shall be populated in accordance with Table 31 ("Entries
in the document catalog dictionary") of the PDF 2.0 specification.
5.4.2.2 DSS Dictionary
The Document Security Store (DSS) shall be a dictionary that shall have the value DSS as key in the document catalog
dictionary. This dictionary is used to provide a single place where all of the VRI for some or all signatures in the
document should be placed.
The DSS dictionary, if present, shall contain VRI only for document and time-stamps signatures represented in PKCS#7
and CMS (and its derivatives) format or for XAdES signatures of forms signing dynamic XFA [i.7].
NOTE 1: See ETSI EN 319 142-2 [i.11] for specification of XAdES signatures of forms signing dynamic XFA.
ETSI
14 ETSI EN 319 142-1 V1.3.1 (2026-11)
Entries in a DSS Dictionary (Conforming to ISO 32000-1 [1] extensions or natively to ISO 32000-2 [9], Table 256):
Entries in a DSS Dictionary
KEY TYPE VALUE
Type Name (Optional) It shall be DSS for a document security store
dictionary.
VRI
Dictionary (Optional) This dictionary contains Signature VRI dictionaries in
the document. For ISO 32000-1 [1] documents the key of each
entry in this dictionary is the base-16-encoded (uppercase)
SHA1 digest of the signature to which it applies and the value
is the Signature VRI dictionary which contains the VRI for that
signature.
See additional requirements a), b), c) and d).
Certs Array (Optional) An array of indirect references to streams, each
containing one DER-encoded X.509 certificate (that shall be as
defined in IETF RFC 5280 [4]). This array contains certificates
that can be used in the validation of any signatures in the
document.
OCSPs Array (Optional) An array of indirect references to streams, each
containing a DER-encoded Online Certificate Status
Protocol (OCSP) response, which can be used in the validation
of any signature in the document. The OCSP response shall be
encoded by using the encoding of the OCSPResponse type as
defined in IETF RFC 6960 [5] (see note 2).
CRLs Array (Optional) An array of indirect references to streams, each
containing a DER-encoded Certificate Revocation List (CRL)
(that shall be as defined in IETF RFC 5280 [4]). This array
contains CRLs that can be used in the validation of any
signatures in the document.
Additional requirements for VRI keys:
a) For document signatures or Document Time-stamp signatures the bytes that are hashed shall be those of the
complete hexadecimal string in the entry with the key Contents of the associated Signature Dictionary
containing the signature's DER-encoded binary data object (e.g. PKCS#7, CMS or CAdES objects).
b) For the signatures of CRLs and OCSP responses, the bytes that are hashed shall be the respective signature
objects represented as a BER-encoded OCTET STRING encoded with primitive encoding.
c) When computing the digest of a XAdES signature found in dynamic XFA [i.7], the contents of the ds:Signature
shall be canonicalized using exclusive canonicalization (http://www.w3.org/2001/10/xml-exc-c14n#) as
specified in [7] and then hashed.
Any VRI dictionaries shall be located in document incremental update sections. If the Signature Dictionary to which a
VRI dictionary applies is itself in an incremental update section (see clause 7.5.6 of ISO 32000-1 [1] or clause 7.5.6 of
ISO 32000-2 [9]), the VRI update shall be done later than the signature update.
NOTE 2: To facilitate the verification of signatures created according to previous versions of the signature format
specifications, a verifier can also accept OCSP responses encoded by using the encoding of the
BasicOCSPResponse type as defined in IETF RFC 6960 [5].
ETSI
15 ETSI EN 319 142-1 V1.3.1 (2026-11)
5.4.2.3 Signature VRI Dictionary
The signature VRI dictionary shall contain Validation Related Information (VRI) for a specific signature in the
document to which the validation information applies.
Entries in a Signature VRI Dictionary (Conforming to ISO 32000-1 [1] extensions or natively to ISO 32000-2 [9],
Table 257):
Entries in a Signature VRI Dictionary
KEY TYPE VALUE
Type (Optional),if present, it shall be VRI for a VRI dictionary.
Name
Cert (Optional, if present, it shall not be an empty array) An array of
Array
indirect references to streams, each containing one DER-encoded
X.509 certificate (that shall be as defined in IETF RFC 5280 [4]). This
array should contain all certificates that were used in the validation of
this signature.
CRL Array (Optional, if present, it shall not be an empty array) An array of
indirect references to streams that are all CRLs used to determine the
validity of the certificates in the chains related to this signature. Each
stream shall reference a CRL that is an entry in the CRLs array in the
DSS dictionary.
OCSP (Optional, if present shall not be an empty array) An array of indirect
Array
references to streams that are all OCSP responses used to determine
the validity of the certificates in the chains related to this signature.
Each stream shall reference an OCSP response that is an entry in the
OCSPs array in the DSS dictionary.
TU Date (Optional), the date/time at which this signature VRI dictionary was
created. A signature handler may ignore this entry and use a different
time for the signature validation. This entry shall be absent when the
TS entry is present. Date shall be a date string as defined in
ISO 32000-1 [1], clause 7.9.4 or ISO 32000-2 [9], clause 7.9.4. See
additional requirement a).
TS Stream (Optional), a stream containing the DER-encoded time-stamp token
(that shall be as defined in IETF RFC 3161 [6] updated by IETF
RFC 5816 [8] and which represents the secure time at which this
signature VRI dictionary was created. This entry shall be absent when
a TU entry is present. See note 1 and additional requirement b).
Additional requirements:
a) The TU key should not be used.
b) The TS key should not be used.
c) Exactly one of the following methods to provide a VRI generation claimed time shall be used: the TU entry, the
TS entry or a subsequent Document Time-stamp.
NOTE 1: For PKCS#7 signatures conforming to ISO 32000-1 [1] the datum that is hashed and included in the
messageImprint field of the DER-encoded time stamp stored in TS entry (see IETF RFC 3161 [6] updated
by IETF RFC 5816 [8]) is the encryptedDigest field in the signature's PKCS#7 object (as defined in IETF
RFC 2315 [i.9]). For CMS signatures conforming to ISO 32000-2 [9], the corresponding signature value field
within the SignerInfo structure shall be used.
NOTE 2: The VRI dictionary is optional, since all necessary data to validate the signature can be available from other
sources like the DSS dictionary itself. The VRI dictionary offers possibilities for optimization of the validation
process, since it relates the data to one specific signature.
NOTE 3: The value of TS can be used as a proof of existence for the signature value itself.
Any values in the Cert, CRL and OCSP arrays of a Signature VRI dictionary shall also be present in the DSS dictionary
applicable to the signature for which this Signature VRI dictionary is associated. If this signature (e.g. PKCS#7, CMS
or CAdES object) does not have any associated Certs, CRLs or OCSPs, then the corresponding key shall not be present
in the VRI dictionary.
A Signature VRI dictionary shall not be used to record the information used in an unsuccessful validation attempt.
MDP restrictions (see ISO 32000-1 [1], clause 12.8.2.2 or ISO 32000-2 [9], clauses 12.8.2.2 and 12.7.5.5) shall not
apply to incremental updates to a PDF document containing a DSS dictionary and associated VRI, Certs, CRLs and
OCSPs.
ETSI
16 ETSI EN 319 142-1 V1.3.1 (2026-11)
NOTE: ISO 32000-1 [1], clause 12.8.2.2 and ISO 32000-2 [9], clauses 12.8.2.2 and 12.7.5.5, address the MDP
(Modification, Detection and Prevention) feature whereby a set of permissions can be associated with a
PDF in conjunction with a certification signature. The permissions of MDP are present in the entry with
the P key of the DocMDP transform parameters dictionary and of the signature field lock dictionary, as an
integer in the range 1 through 3. Values of 2 and 3 allow for additional signatures to be included after the
certification but a value of 1 does not allow any change but allows Document Time-stamps.
5.4.3 Document Time-stamp
A Document Time-stamp dictionary shall be a standard Signature D
...











