hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1e77440904685da89cefd2bd994bd735 | 119 462 | 6.3 Issuer discovery | Discovery of issuer capabilities and prerequisites is performed via Issuer Metadata retrieved and validated by the wallet. The metadata is a JWS whose protected header carries the issuer's access certificate chain (x5c), and whose body enumerates supported credential configurations, formats, and optional registration c... |
1e77440904685da89cefd2bd994bd735 | 119 462 | 6.4 Electronic Attestation of Attribute issuance | Issuance follows the OpenID4VCI [i.25] profile and supports Authorization Code and Pre-Authorized Code flows. In the case of the Issuer-started process, the Credential Offer is sent to the EUDIW which then proceeds through the Pushed Authorization Request (PAR) and Authorization Request as well, Token Request, and is c... |
1e77440904685da89cefd2bd994bd735 | 119 462 | 6.5 Electronic Attestation of Attribute lifecycle management | Lifecycle management covers status changes and re-issuance mechanics signalled through the issuance profile and related policies: • Revocation and status: Issuers can later signal status via mechanisms associated with the EAA format and ecosystem policies; wallets are expected to process status and embedded disclosure ... |
1e77440904685da89cefd2bd994bd735 | 119 462 | 7 Interfaces for the creation of an electronic signature | |
1e77440904685da89cefd2bd994bd735 | 119 462 | 7.1 Interface components | |
1e77440904685da89cefd2bd994bd735 | 119 462 | 7.1.1 Functional model | The present document uses the functional model of a Signature Creation Environment (SCE) specified in clause 4.1 of ETSI EN 319 102-1 [i.16], consisting of: • a signer who wants to create a signature; • a Driving Application (DA) which represents the environment (e.g. a business application) that the signer uses to acc... |
1e77440904685da89cefd2bd994bd735 | 119 462 | 7.2 Signing initiation interface | The signer, using the EUDIW, provides the DA with instructions for selecting the signing method, indicating the choice of SCA. The relying party prepares the document through the DA, and the DA initiates the signing flow with the SCA. The DA may be part of the relying party, a standalone signing portal, possibly merged... |
1e77440904685da89cefd2bd994bd735 | 119 462 | 7.3 Signature attributes interface | The signer, using the EUDIW, provides Signature attributes to the SCA, which collects and assembles them with the SD(R) and the certificate identifier into the DTBS. ETSI TS 119 479-3 [i.45] regarding support for EAA within AdES signatures is under development. Supporting standards: Standard Description OpenID4VP [i.26... |
1e77440904685da89cefd2bd994bd735 | 119 462 | 7.4 Signature activation interface | The signer authenticates to the SCA using the EUDIW; the SCA then initiates Signature Activation with the SSA controlling the SCDev. The EUDIW acts as the SIC and runs SAP with the SAM to generate SAD, which the SAM verifies to enable SCDev to create the signature value. Supporting standards: Standard Description OpenI... |
1e77440904685da89cefd2bd994bd735 | 119 462 | 7.5 Identity data interface | The EUDIW provides the signer's identity data for just-in-time certificate issuance (e.g. one-time signing key), which is then returned and bound to the active signing session. Interfaces for online identification and authentication, and for a signature request are described in clauses 5.2 and 5.3 of the present docume... |
1e77440904685da89cefd2bd994bd735 | 119 462 | 8 Wallet interface for other trust services | |
1e77440904685da89cefd2bd994bd735 | 119 462 | 8.1 General provisions | Trust services use the EUDIW for user identification and authentication. The identification process may utilize the PID functionality or specific attributes provided by the EUDIW. Depending on the type of service and the legal and regulatory requirements, the services may use identification with varying Levels of Assur... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 1 Scope | The present document provides specific actions differentiated by available resources for three parties in the software ecosystem toward implementing evaluable, effective software security. For end user customers, it specifies what to ask. For software development organizations, it specifies what to do. For governmental... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 2 References | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 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... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 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... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 3 Definition of terms, symbols and abbreviations | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 3.1 Terms | For the purposes of the present document, the following terms apply: agile: software lifecycle model that is characterized by the division of tasks into short phases of work and frequent reassessment and adaptation of plans artifact: digital evidence generated as a part of the development process and not for the sole p... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 3.2 Symbols | Void. |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACM Association for Computing Machinery AFCEA Armed Forces Communications and Electronics Association AFIPS American Federation of Information Processing Societies AI Artificial Intelligence ANSSI Agence nationale de la sécurité des systèmes d... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 4 Evolution of the Security by Design Ecosystem | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 4.1 Introduction | The challenges of information security emerged early. David Kahn in his reference book "The Code Breakers" [i.35] describes many of them over the millennia. GCHQ's (United Kingdom's Government Communications Headquarters) authorized history points to the extensive use of cryptography by spymaster Francis Walsingham dur... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 4.2 Achieving and Assessing Security by Design | The present document is intended as a resource for software development organizations, end users, and compliance authorities who seek to answer the question "is this software (or the software delivered by this vendor or service provider) Secure by Design (SbD)?" This has long been a difficult question, and it is more c... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0 Structure of the SSDIF | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0.1 Objectives and methods | Secure by Design encompasses what developers regard as "design" as well as security of implementation and security of default configuration. The objective of Secure by Design is that systems and particularly software be "sufficiently secure" to meet the needs of the end users/organizations that rely on them and that th... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0.2 SSDIF Development Groups | Not all software development organizations possess the same degree of technical expertise or complexity. As such, processes will differ across software development organizations in concert with their characteristics. This need for differentiation by available resources, including SMEs, and organizational maturity is re... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0.3 SSDIF Roles | The SSDIF identifies specific roles that support the Secure by Design lifecycle and are responsible for the identified practices and actions. These roles are listed in Table 5.0-3, below. Table 5.0-3: List of SSDIF Roles Role Type Role Description CISO Team Responsible for policies, standards, configuration, and operat... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0.4 Assessment and Evidence | For evaluation and legal purposes, software development organizations need to demonstrate that their products are "Secure by Design (SbD)." This does not mean that the software is vulnerability-free - there is no such thing. For purposes of the present document, secure-by-design means that the software development orga... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.0.5 Use of Artificial Intelligence and Machine Learning | The use of Artificial Intelligence and Machine Learning (AI/ML) is an important consideration for software development and software security. There are four domains for application of AI/ML in secure software development: 1) The components under development may incorporate AI/ML components whose security is assured. As... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.1 Essential 1: Secure Software Design | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.1.0 Overview | Secure software design begins with a set of security objectives that the software satisfies and a set of security threats that the software should resist. Although specific systems - especially systems targeted at specific applications or customers - may have very specific objectives, most commercial products and onlin... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.1.1 SSDIF Essential 1 Tasks - Secure Software Design | Task ID PO.1.2 Identify and document all security requirements for organization-developed software to meet and maintain the requirements over time. CSC Safeguard; SAFECode practices 16.1, 16.2; N/A SSDIF PO.1.2 DG Specific Actions DG 1/2/3: The organisation 1. shall establish a documented secure development process (in... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.2 Essential 2: Secure Development | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.2.0 Overview | Software development, encompassing coding, testing, rollout to customers, and maintenance throughout the lifecycle, has historically been the source of most product vulnerabilities. At a high level, all secure development processes are similar and encompass the practices enumerated in the SSDF. However, the details of ... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.2.1 SSDIF Essential 2 Tasks - Secure Development | Task ID PO.2.1 Create new roles and alter responsibilities for existing roles as needed to encompass all parts of the SDLC. Periodically review and maintain the defined roles and responsibilities, updating them as needed. CSC Safeguard; SAFECode practices 16.1; N/A SSDIF PO.2.1 DG Specific Actions DG 1/2/3: The organis... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.3 Essential 3: Secure Default Configuration | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.3.0 Overview | Software products frequently include myriad configuration settings and options that system administrators may use to enable or disable features or adjust product behaviour. Although users can adjust those settings, many will fail to do so. Experience has shown that many users and administrators accept default settings.... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.3.1 SSDIF Essential 3 Tasks - Secure Default Configuration | Task ID PW.9.1 Define a secure baseline by determining how to configure each setting that has an effect on security or a security-related setting so that the default settings are secure and do not weaken the security functions provided by the platform, network infrastructure, or services. CSC Safeguard; SAFECode practi... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.4 Essential 4: Supply Chain Security | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.4.0 Overview | The term "supply chain security" refers to the challenge to Secure by Design that is posed by software development organizations' use of software that they did not themselves create (often referred to as "third party code") Such software should have been developed with the full panoply of SbD requirements for the syste... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.4.1 SSDIF Essential 4 Tasks - Supply Chain Security | Task ID PO.1.3 Communicate requirements to all third parties who will provide commercial software components to the organization for reuse by the organization's own software. [Formerly PW.3.1] CSC Safeguard; SAFECode practices 16.4; Manage security risk inherent in use of third party components SSDIF PO.1.3 DG Specific... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.5 Essential 5: Code Integrity | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.5.0 Overview | Secure design and development practices enable a software development organization to produce software that addresses potential threats once it is in use, but the software development organization also plays a role in ensuring that the software that end users/organizations rely on is the software that they intended to ... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.5.1 SSDIF Essential 5 Tasks - Code Integrity | Task ID PO.1.1 Identify and document all security requirements for the organization's software development infrastructures and processes, and maintain the requirements over time. CSC Safeguard; SAFECode practices 1.1, 2.1, 3.1, 4.1, 5.1, 6.1, 7.1, 8.1, 11.1, 12.3, 15.2, 16.1, 17.4, 18.1: N/A SSDIF PO.1.1 DG Specific Ac... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.6 Essential 6: Vulnerability Disclosure and Remediation | |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.6.0 Overview | Vulnerability response and remediation are part of any secure development process. Software that is perfect and vulnerability-free is infeasible except in very limited circumstances. Development teams should implement processes to accept reports of product vulnerabilities, investigate the reports, and remedy the vulner... |
de285799766f4daf6762dd9ff9d06a60 | 104 219 | 5.6.1 SSDIF Essential 6 Tasks - Vulnerability Disclosure and Remediation | Task ID RV.1.1 Gather information from software acquirers, users, and public sources on potential vulnerabilities in the software and third-party components that the software uses and investigate all credible reports. CSC Safeguard; SAFECode practices 7.2, 7.2, 7.3, 16.2; Create and Manage a Vulnerability Response Proc... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.