+PO.3 Implement Supporting Toolchains
---+PO.3.1 Specify which tools or tool types must or should be included in each toolchain to mitigate identified risks, as well as how the toolchain components …
---+PO.3.2 Follow recommended security practices to deploy, operate, and maintain tools and toolchains.
---+PO.3.3 Configure tools to generate artifacts of their support of secure software development practices as defined by the organization.
|
PO.3 Implement Supporting Toolchains
StatementUse automation to reduce human effort and improve the accuracy, reproducibility, usability, and comprehensiveness of security practices throughout the SDLC, as well as provide a way to document and demonstrate the use of these practices. Toolchains and tools may be used at different levels of the organization, such as organization-wide or project-specific, and may address a particular part of the SDLC, like a build pipeline.
1. Vue d’ensemble
| Intitulé |
Norme |
|
PO.3.1 Specify which tools or tool types must or should be included in each toolchain to mitigate identified risks, as well as how the toolchain components …
|
StatementSpecify which tools or tool types must or should be included in each toolchain to mitigate identified risks, as well as how the toolchain components are to be integrated with each other. Example 1:Define categories of toolchains, and specify the mandatory tools or tool types to be used for each category. Example 2:Identify security tools to integrate into the developer toolchain. Example 3:Define what information is to be passed between tools and what data formats are to be used. Example 4:Evaluate tools’ signing capabilities to create immutable records/logs for auditability within the toolchain. Example 5:Use automated technology for toolchain management and orchestration.
|
|
PO.3.2 Follow recommended security practices to deploy, operate, and maintain tools and toolchains.
|
StatementFollow recommended security practices to deploy, operate, and maintain tools and toolchains. Example 1:Evaluate, select, and acquire tools, and assess the security of each tool. Example 2:Integrate tools with other tools and existing software development processes and workflows. Example 3:Use code-based configuration for toolchains (e.g., pipelines-as-code, toolchains-as-code). Example 4:Implement the technologies and processes needed for reproducible builds. Example 5:Update, upgrade, or replace tools as needed to address tool vulnerabilities or add new tool capabilities. Example 6:Continuously monitor tools and tool logs for potential operational and security issues, including policy violations and anomalous behavior. Example 7:Regularly verify the integrity and check the provenance of each tool to identify potential problems. Example 8:See PW.6 regarding compiler, interpreter, and build tools. Example 9:See PO.5 regarding implementing and maintaining secure environments.
|
|
PO.3.3 Configure tools to generate artifacts of their support of secure software development practices as defined by the organization.
|
StatementConfigure tools to generate artifacts of their support of secure software development practices as defined by the organization. Example 1:Use existing tooling (e.g., workflow tracking, issue tracking, value stream mapping) to create an audit trail of the secure development-related actions that are performed for continuous improvement purposes. Example 2:Determine how often the collected information should be audited, and implement the necessary processes. Example 3:Establish and enforce security and retention policies for artifact data. Example 4:Assign responsibility for creating any needed artifacts that tools cannot generate.
|
1.1 Références
1.2 Exigences identifiées
1.3 Réglementations associées
2. Exigences identifiées
Exigences
| Source |
Exigence |
3. Réglementations associées
Réglementations
| Source |
Réglementation |
Tickets liés
- NIST -
EN: Publications of the National Institute of Standards and Technology (NIST), U.S. Department of Commerce, https://www.nist.gov/, from their electronic versions (OSCAL; SP 800-63-4 from its HTML version, https://pages.nist.gov/800-63-4/). Works of NIST employees are not subject to copyright protection in the United States (17 U.S.C. § 105); the OSCAL content is dedicated to the public domain worldwide (CC0 1.0); outside the United States NIST grants the right to reprint its technical series publications in all formats (NIST copyright statement). Republished courtesy of the National Institute of Standards and Technology; each document names its citation. Divided into sections and converted into the GRCA format, the wording unchanged. Only the versions published by NIST are authoritative.
DE: Veröffentlichungen des National Institute of Standards and Technology (NIST), U.S. Department of Commerce, https://www.nist.gov/, aus ihren elektronischen Fassungen (OSCAL; SP 800-63-4 aus ihrer HTML-Fassung, https://pages.nist.gov/800-63-4/). Werke von NIST-Beschäftigten sind in den USA urheberrechtlich nicht geschützt (17 U.S.C. § 105); die OSCAL-Inhalte sind weltweit gemeinfrei gestellt (CC0 1.0); außerhalb der USA räumt das NIST das Recht ein, seine Technical-Series-Publikationen in allen Formaten neu zu veröffentlichen (Copyright-Hinweis des NIST). „Republished courtesy of the National Institute of Standards and Technology“; jedes Dokument nennt seine Zitierangabe. In Abschnitte aufgeteilt und in das GRCA-Format umgewandelt, der Wortlaut unverändert. Maßgeblich sind allein die vom NIST veröffentlichten Fassungen.
|