+PS.3 Archive and Protect Each Software Release
---+PS.3.1 Securely archive the necessary files and supporting data (e.g., integrity verification information, provenance data) to be retained for each software …
---+PS.3.2 Collect, safeguard, maintain, and share provenance data for all components of each software release (e.g., in a software bill of materials .SBOM).

PS.3 Archive and Protect Each Software Release

Statement

Preserve software releases in order to help identify, analyze, and eliminate vulnerabilities discovered in the software after release.

1. Panoramica

PS.3.1 Securely archive the necessary files and supporting data (e.g., integrity verification information, provenance data) to be retained for each software …

Statement

Securely archive the necessary files and supporting data (e.g., integrity verification information, provenance data) to be retained for each software release.

Example 1:

Store the release files, associated images, etc. in repositories following the organization’s established policy. Allow read-only access to them by necessary personnel and no access by anyone else.

Example 2:

Store and protect release integrity verification information and provenance data, such as by keeping it in a separate location from the release files or by signing the data.
PS.3.2 Collect, safeguard, maintain, and share provenance data for all components of each software release (e.g., in a software bill of materials .SBOM).

Statement

Collect, safeguard, maintain, and share provenance data for all components of each software release (e.g., in a software bill of materials .SBOM).

Example 1:

Make the provenance data available to software acquirers in accordance with the organization’s policies, preferably using standards-based formats.

Example 2:

Make the provenance data available to the organization’s operations and response teams to aid them in mitigating software vulnerabilities.

Example 3:

Protect the integrity of provenance data, and provide a way for recipients to verify provenance data integrity.

Example 4:

Update the provenance data every time any of the software’s components are updated.

1.1 Riferimenti

1.2 Requisiti identificati

1.3 Regolamentazioni correlate

2. Requisiti identificati

Requisiti

3. Regolamentazioni correlate

Regolamentazioni

Ticket collegati

Collegamenti
is blocked by Archiving Software Releases
  • 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.