hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.3.12.6.2 XML | This element shall be of type RevocationStatusInformationType that is defined as follows: <xs:complexType name="RevocationStatusInformationType"> <xs:sequence> <xs:element name="ValidationObjectId" type="vr:VOReferenceType"/> <xs:element name="RevocationTime" type="xs:dateTime"/> <xs:element name="RevocationReason" typ... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.3.12.7 Crypto Information Element | |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.3.12.7.1 General | Presence: Conditional. This element shall be present when the main status indication is INDETERMINATE and the sub-indication is CRYPTO_CONSTRAINTS_FAILURE. In all other cases, this element may be present. Description: When the validation process determines that the cryptographic algorithm is no longer reliable, this el... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.3.12.7.2 XML | This element shall be of type CryptoInformationType that is defined as follows: <xs:complexType name="CryptoInformationType"> <xs:sequence> <xs:element name="ValidationObjectId" type="vr:VOReferenceType"/> <xs:element name="Algorithm" type="xs:anyURI"/> <xs:element name="AlgorithmParameters" type="vr:TypedDataType" min... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.3.12.8 Additional Validation Report Data | |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.3.12.8.1 General | Presence: Optional. Description: This element can contain any additional information that the validation process provides. Content: When present, this element shall contain one or more of the following: 1) An identifier identifying the type of additional information present. 2) The additional information. |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.3.12.8.2 XML | This element shall be of type AdditionalValidationReportDataType and contain one or more of the following tuples: • An identifier identifying the type of additional information present. • The additional information. and is defined as follows: <xs:complexType name="AdditionalValidationReportDataType"> <xs:sequence> <xs:... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4 Signature Validation Objects | |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.1 General | Presence: Optional. Description: This element is the container for validation objects used during validation. NOTE: This avoids duplication of validation objects, e.g. CRLs, when the validation report contains the report on more than one signature or validation object. Content: When present, this element shall contain ... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.2 XML | The signature validation objects shall be placed in an element named SignatureValidationObjects of type ValidationObjectListType. Each element in this list shall be named ValidationObject and be of type ValidationObjectType. <xs:complexType name="ValidationObjectListType"> <xs:sequence> <xs:element name="ValidationObje... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.3 Object Identifier | Presence: Mandatory. Description: This element allows to uniquely reference this validation object within the validation report. Content: This element shall contain an identifier that is unique within the validation report. XML: This element shall be an attribute of type xs:ID. |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.4 Object Type | Presence: Mandatory. Description: This element identifies the type of the validation object. Content: This element shall contain a URI uniquely able to identify the type of the object. XML: This element shall be an element named ObjectType of type xs:anyURI. |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.5 Validation Object | |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.5.1 General | 4. |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.5.1 General | Presence: Mandatory. Description: This element contains or references the validation object. Content: This element shall contain one or more of the following: 1) the object itself; 2) a base64-encoded version of the object; 3) a cryptographic hash of the object; or 4) a URI where the object can be retrieved. NOTE: When... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.5.2 XML | 4. |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.5.2 XML | Information on the validation object shall be placed in an element named ValidationObjectRepresentation of type ValidationObjectRepresentationType, defined as follows: <xs:complexType name="ValidationObjectRepresentationType"> <xs:choice maxOccurs="unbounded"> <xs:element name="direct" type="xs:anyType"/> <xs:element n... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.6 Proof Of Existence (POE) | |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.6.1 General | Presence: Optional. Description: This element contains information on a proof for the earliest time of the existence of the object. Content: This element shall contain the information on the POE providing the earliest time for the existence of the object. This property shall contain: 1) the time value for that proof in... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.6.2 XML | <xs:complexType name="POEType"> <xs:sequence> <xs:element name="POETime" type="xs:dateTime"/> <xs:element name="TypeOfProof" type="xs:anyURI"/> <xs:element name="POEObject" type="vr:VOReferenceType" minOccurs="0"/> </xs:sequence> </xs:complexType> The element POETime shall contain the time value for the proof of existe... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.7 POE Provisioning | |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.7.1 General | Presence: Optional. Description: When a validation object provides proofs of existence for other objects, this property provides information on these objects. Content: This element shall contain: 1) The time value for that proof in UTC. 2) A list of references to the signature or to signature validation objects within ... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.7.2 XML | <xs:complexType name="POEProvisioningType"> <xs:sequence> <xs:element name="POETime" type="xs:dateTime"/> <xs:element name="ValidationObject" type="vr:VOReferenceType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="SignatureReference" type="vr:SignatureReferenceType" minOccurs="0" maxOccurs="unbounded"/> </xs:... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.4.8 Validation Object validation report | Presence: Optional. This element may be present whenever the signature validation object is a signed object and the signature has been validated during the overall validation. Description: This element contains a validation report for the signature validation object. Content: This element shall contain a validation rep... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.5 Validator Information | 4.5.1 General Presence: Optional. Description: This element identifies the entity validating the signature and creating the validation report. ETSI ETSI TS 119 102-2 V1.4.1 (2023-06) 38 Content: This element shall contain the digital identity of the validation service as specified in clause 5.5.3 of ETSI TS 119 612 [6]... |
2949bd5aae729487a8f07c15de132bb9 | 119 102-2 | 4.6 Validation Report Signature | Presence: Optional. Description: This element contains the validation report signature. Content: When present, this element shall contain the signature over the signature validation report and shall be created by the validation service that performed the validation and created the validation report. EXAMPLE: The follow... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 1 Scope | The present document provides general security and policy requirements for applications for signature creation, validation and augmentation. The present document is primarily relevant to the following actors: • Implementers and providers of applications for signature creation, signature validation and/or signature augm... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 2 References | |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 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 a... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 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 i... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 3 Definitions and abbreviations | |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.7] and the following apply: NOTE: For the sake of readability, the following definitions are reproduced here below. advanced electronic seal: As defined in Regulation (EU) No 910/2014 [i.1]. advanced electronic signature: As... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.7] and the following apply: CA Certification Authority CRL Certificate Revocation List DA Driving Application DN Distinguished Name DTBS Data to be Signed DTBSR Data To Be Signed Representation EC European Commission ICS Implementat... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 4 Signature creation/validation/augmentation model | The hardware/software systems for creating, validating or augmenting a signature, are modelled through several building blocks as shown in figures 1 to 3. Some objectives can be implemented either by the DA or the SVA/SCA/SAA. This is to allow a flexibility in the implementation. However, a complete system meets all ma... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 5 General requirements | |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 5.1 User interface | Control Objective Ensure that the user interface is well designed and easy to use to avoid any problems and misunderstandings in the interaction with the application. This ensures the user confidence. The user interface can be part of the SCA/SVA/SAA or the DA which calls the SCA/SVA/SAA. Controls (User Interface) UI 1... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 5.2 General security measures | Control objective Ensure that the systems on which the application is developed apply appropriate security measures and adapt to specific application environments. Controls (General Security Measures) GSM 1: Appropriate security measures: GSM 1.1: The security measures for the systems on which the application is develo... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 5.3 System completeness requirements | Control objective Ensure that a complete system implements all the mandatory requirements including those that can be implemented either by the DA or by the SVA/SCA/SAA. Controls (System Completeness) SC 1: In a complete system, all mandatory requirements stated in the present document shall be implemented. |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 6 Legal driven policy requirements | |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 6.1 Introduction | When analysing the context of the business application implementing signatures, several legal aspects are considered. In the following clauses, control objectives are defined in connection with the processing of personal data and the accessibility for persons with disabilities. |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 6.2 Processing of personal data | Control objective Ensure that personal data are processed fairly and lawfully in accordance with applicable personal data protection legislation. Controls (Personal Data) PD 1: Evidence shall be provided on how requirements of applicable Privacy and Data Protection regulation legislation (e.g. European Data Protection ... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 6.3 Accessibility for persons with disabilities | Control objective Ensure that SCA/SVA/SAA are accessible for persons with disabilities. Controls (Accessibility for Persons with Disabilities) APD 1: If accessibility for persons with disabilities is required by applicable law, SCA/SVA/SAA shall be made accessible for persons with disabilities where feasible. Applicabl... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 7.1 Introduction | This clause contains the most important requirements for information security and information security management systems. A detailed description can also be found in the ISO/IEC 27000 series [i.4]. The controls defined in this clause cover the environment in which the SCA/SVA/SAA and the driving applications are appli... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 7.2 Network protection | Control objective If the SCA/SVA/SAA receives or sends confidential data over a network, guarantee the protection of this data in networks as well as the protection against network threats on the infrastructure supporting the processing and storage of confidential data. Controls (Network Protection) NP 1: If the SCA/SV... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 7.3 Information systems protection | Control objective Ensure that the information systems handling signature data and the environment of the SCA/SVA/SAA are secured against unauthorized access and misuse, trigger suitable security alarms, and, when applicable, that security events are recorded. ETSI ETSI TS 119 101 V1.1.1 (2016-03) 17 Controls (informati... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 7.4 Software integrity of the application | Control objective Ensure that integrity of the SCA, SVA, SAA and DA is properly protected. Controls (Software Integrity of the Application) SIA 1: SCA/SVA/SAA/DA components shall be protected against viruses and malicious software to ensure their integrity. SIA 2: A change-detection mechanism (for example, file-integri... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 7.5 Data storage security | Control objective Ensure that appropriate data storage security measures are implemented in the SCA/SVA/SAA as well as in the application environment to protect any confidential data. Controls (Data Storage Security) DSS 1: Information systems storing confidential data should be configured according to a predefined sec... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 7.6 Event logs | Control objective To prove the activities related to the signature creation and validation, use event logs in the SCA/SVA/SAA, the driving application or the application environment to capture information which might be needed for later evidences. Controls (Event Logs) EL 1: Information systems storing or processing ev... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1 Signature creation process and systems | |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.1 General | This clause specifies security requirements and recommendations specific to the signature creation. It contains requirements for the SCA, the DA and the user interface. It builds on the definitions, models and technical introduction of ETSI TS 119 102 [i.8]. NOTE 1: Contrary to the model in ETSI TS 119 102, the SVA des... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.2 Main functionalities requirements | Control objective Ensure that the main functionalities of the SCA are well documented. ETSI ETSI TS 119 101 V1.1.1 (2016-03) 19 Controls (Signature Creation Process) SCP 1: The SCA documentation shall indicate: a) All the signature formats (CAdES [i.10], XAdES [i.11], PAdES [i.12], ASiC [i.13]) and signature levels tha... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.3 Data content type requirements | Control objective Ensure that the signature format is appropriate for the document data type that is to be signed and conforms to any legal or business requirements applicable. Controls (Signature Creation Process) SCP 3: The SCA documentation shall specify the data content types the SCA supports and can present correc... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.4 Signature attribute requirements | Control objective Ensure that the signature is applied to the right signature attributes and that the attributes are not altered accidentally or maliciously. Controls (Signature Creation Process) SCP 27: The user interface shall allow the signer to view the signature attributes. In particular, the signer shall be able ... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.5 Time and sequence | Control objective Ensure that the signature creation process follows the foreseen sequence of events. Controls (Signature Creation Process) SCP 46: The SCA shall compute the signature only after the signer has given its consent on calculating the signature. SCP 47: If the business process contains the presentation of t... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.6 Signature invocation requirements | Control objective Ensure that each signature generated is the result of an explicit signature invocation. The user interface can be part of the SCA and/or of the DA. ETSI ETSI TS 119 101 V1.1.1 (2016-03) 24 Controls (Signature Creation Process) SCP 49: The user interface shall limit accidental invocation of the signatu... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.7 Cryptographic algorithm choice | Control objective Ensure that all algorithms involved in calculating any element of the signature are based on algorithms and key lengths that are appropriate for the business requirements. Controls (Signature Creation Process) SCP 57: If the implicit or explicit signature creation policy requires a specific signature ... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.8 Signer's authentication requirements | |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.8.1 General requirements | Control objective Ensure that only the legitimate SCDev user can request creation of a digital signature value. Controls (Signature Creation Process) SCP 60: For knowledge based signer authentication, the authentication data (e.g. PIN or password) should withstand practical guessing and brute force attacks. SCP 61: Whe... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.8.2 Requirements for biometric authentication methods | Control objective Ensure that it is made difficult or practically impossible to make an impersonation attack with fakes of the biometric features. Controls (Signature Creation Process) SCP 74: Environment requirements suitable to prevent attacks to biometric devices, such as submission of "fake" biometric elements (sil... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.9 DTBS preparation requirements | Control objective Ensure that an attacker cannot provide the SCA with forged signature components and prevent the SCA from applying the entire signature components specific to the format chosen to achieve a given purpose. Controls (Signature Creation Process) SCP 79: The SCA shall verify the validity, authenticity and ... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.10 DTBSR preparation | Control objective Ensure that the data to be signed representation (DTBSR) is correctly composed. Controls (Signature Creation Process) SCP 82: The SCA shall select the signature attributes according to the applicable rules or selected implicit or explicit signature creation policy. SCP 83: The SCA shall produce the co... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.11 Signature creation device | Control objective Ensure that the signature creation device used for creating a signature has the right legal and technical level according to the business requirements. NOTE: A possible way to convey this information to the SCA is the signature creation policy. Controls (Signature Creation Process) SCP 86: If the impl... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.12 SCDev/SCA interface (SSI) requirements | The signature creation device (SCDev)/SCA Interface is responsible for the connection between the SCDev and the SCA. Control objective Ensure that the communication between SCA and SCDev is protected. Controls (Signature Creation Process) SCP 88: The SSI component shall prevent data communicated over the interface to b... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.1.13 Bulk signing requirements | Control objective Ensure that a bulk signature process is not less secure than a process where each document would be signed separately. Ensure that no documents are signed that are not intended to be signed by the signer. Controls (Signature Creation Process) SCP 92: When bulk signing is supported, the SCA shall allow... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.2 Signature validation process | |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.2.1 Introduction | The signature validation process validates a signature against a set of validation constraints. These constraints are expressed in a signature validation policy, be it implicit or explicit, which reflects business, legal and security policy requirements. One or more signature validation policies that are adapted to the... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.2.2 Main functionalities requirements | Control objective Ensure that the main functionalities of the SVA are well documented. Controls (Signature Validation Process) SVP 1: The SVA documentation shall contain a description of: a) the supported signature/container formats (e.g. CAdES [i.10], XAdES [i.11], PAdES [i.12], ASiC [i.13], etc.); b) the supported si... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.2.3 Validation process rules | Control objective A sound process for signature validation is defined and followed. Such a process establishes whether a signature is technically valid against a signature validation policy. Controls (Signature Validation Process) SVP 3: Process rules shall be described in the SVA documentation (at least by reference t... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.2.4 Validation policy | Control objective If the signature that is received contains a signature policy identifier, then the DA can use the signature policy identifier to determine which signature validation policy to use, but can also decide that another signature policy is more appropriate. The selection of the implicit or explicit signatur... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.2.5 Validation user interface | Control objective Depending on the business model, the constraints and inputs to the validation process can either be provided by the DA (e.g. a default policy or a policy selected amongst a set of supported policies, according to the context; in this case, the driving application is able to select the signature valida... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.2.6 Validation inputs and outputs | Control objective Ensure that: • During the validation of a signature, the inputs required by the processing rules, the applicable signature validation policy, validation data (e.g. certificates, CRLs and OCSP responses) and a time-source are present and that all checks required by the verifier's signature validation p... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.3 Signature augmentation process | |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.3.1 Introduction | Augmenting signatures is the process by which certain material (e.g. time stamps, validation data and even archival-related material) is incorporated to the signatures for making them more resilient to change or for enlarging their longevity. A Signature Augmentation Application (SAA) receives signatures as well as oth... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.3.2 The three use cases | |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.3.2.1 Signature augmentation process used by a SCA | A SCA provides to verifiers at least a Basic Signature as defined in ETSI TS 119 102 [i.8], so that it can be validated against a signature validation policy. However, if the SCA has an on-line access, it can provide more than this minimum format. The SCA can thus apply, in addition to a signature creation policy, a si... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.3.2.2 Signature augmentation process used by a SVA | A SVA validates signatures against a signature validation policy and indicates to verifiers whether a signature is valid, invalid or whether its status cannot be determined. However, generally the SVA has an on-line access and thus can augment the received signature with validation data, if this is requested by the ver... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.3.2.3 Independent signature augmentation process | In this case, a Signature Augmentation Application (SAA) is used independently of a SCA or of a SVA and adds to the signature the data elements required by the signature augmentation policy. ETSI ETSI TS 119 101 V1.1.1 (2016-03) 33 This independent process can be useful for signatures that have already been successfull... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.3.3 Main functionalities requirements | Control objective Ensure that the main functionalities of the SVA are well documented. Controls (Signature Augmentation Process) SAP 1: The SAA documentation shall indicate: a) all supported signature/container levels to which it can augment the signature/container; and b) any restrictions that apply on the augmentatio... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.3.4 Augmentation procedures | Control objective Ensure that sound procedures for signature augmentation are defined and followed. Controls (Signature Augmentation Process) SAP 3: The implemented signature augmentation procedures shall be described in the SAA documentation (at least by reference to a relevant document). SAP 4: The augmentation proce... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.3.5 Data inclusion | Control objective Ensure that the signature contains all the necessary data after the augmentation of the signature. Controls (Signature Augmentation Process) SAP 6: If the signature creation time is required by the chosen level to which the signature is augmented, then the SAA shall capture a time assertion (e.g. time... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 8.3.6 Validation of the input signature to the augmentation process | Control objective Ensure that the input signature is validated before augmentation if required by the signature augmentation policy. ETSI ETSI TS 119 101 V1.1.1 (2016-03) 34 Controls (Signature Augmentation Process) SAP 8: If required by the signature augmentation policy, the input signature shall be validated. SAP 9: ... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 9 Development and coding policy requirements | |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 9.1 Secure development methods and application security | Control objective Ensure the usage of appropriate (software) development methodology, tools and the implementation of adequate security measures. Controls (Security Development Methods) SDM 1: Use of (software) development methodology. The first set of requirements is related to the use and implementation of a software... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 9.2 Testing conformance requirements | Control objective Ensure implementations are compliant with the standards they implement. Controls (Testing Conformance requirements) TC 1: If conformance to a standard is stated, then the conformance of the application shall be tested as described in the specifications on conformance testing, if such specifications ex... |
75b03dcddc42cf7688d58863cf3b915e | 119 101 | 10 Signature application practice statement | A signature application practice statement (SAPS) may be established. An SAPS may be used on its own to state the rules to be applied to conform to the security and policy requirements or as part of a signature policy as described in ETSI TS 119 172 [i.14]. When such a document is established, its table of content (ToC... |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 1 Scope | The present document specifies a type of PDF digital signatures, as specified in ISO 32000-1 [1], based on time-stamps. It specifies a format for PAdES digital signatures using a Document Time-stamp - as defined in ETSI EN 319 142-1 [2] - as a digital signature intended to specifically prove the integrity and existence... |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 2 References | |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 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 that ar... |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 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 i... |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 3 Definitions | For the purposes of the present document, the terms and definitions given in ISO 32000-1 [1], ETSI EN 319 142-1 [2] 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 a... |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 4 General syntax | |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 4.1 General requirements for PAdES-DTS signatures | The type of PAdES signature defined in the present document is called PAdES-DTS and it builds on PDF signatures as specified in ISO 32000-1 [1]. While other PAdES signature profiles defined in ETSI EN 319 142-1 [2] and ETSI EN 319 142-2 [i.1] incorporate signed and unsigned attributes aimed at proving the authenticity ... |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 4.2 Extending the validity of PAdES-DTS signatures | The lifetime of the protection offered by a PAdES-DTS signature may be further extended beyond the lifetime of its Document time-stamp. In that case, a new Document time-stamp and DSS information shall be added as described in ETSI EN 319 142-1 [2], clause 5.4. ETSI ETSI TS 119 142-3 V1.1.1 (2016-12) 7 |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 5 Attributes syntax and semantics | |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 5.1 Extensions dictionary | The extensions dictionary (see ISO 32000-1 [1], clause 7.12) should include an entry <</ESIC <</BaseVersion /1.7 /ExtensionLevel 1 >> >> to identify that a PDF document includes extensions as identified in clause 4.1. NOTE: As an alternative to the above entry, use of extensions as identified in clause 4.1 can also be ... |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 5.2 Requirements on encryption | A PDF document can be encrypted to protect its contents from unauthorized access. When encryption and signatures are combined together in a single PDF document, encryption shall be applied as described in ETSI EN 319 142-1 [2], clause 5.5. |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 6 PAdES-DTS signature profiles | |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 6.1 Signature levels | The profiles in this clause define PAdES signatures based on the building blocks defined in ETSI EN 319 142-1 [2]. These profiles define two levels of PAdES-DTS signatures. PAdES-DTS-BET level defines requirements for the generation of a basic PAdES-DTS signature providing a proof of existence and integrity of the docu... |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 6.2 General requirements | |
32612c3dc6baea8dc1c17ee9ca2b1a68 | 119 142-3 | 6.2.1 Requirements from Part 1 | The requirements given in clauses 4.1, 5.3, 5.4, 5.5 and 6.2.1 of ETSI EN 319 142-1 [2] (PAdES Part 1) shall apply to all levels in this clause. ETSI ETSI TS 119 142-3 V1.1.1 (2016-12) 8 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.