+PS Protect Software
---+PS.1 Protect All Forms of Code from Unauthorized Access and Tampering
------+PS.1.1 Store all forms of code – including source code, executable code, and configuration-as-code – based on the principle of least privilege so that only …
---+PS.2 Provide a Mechanism for Verifying Software Release Integrity
------+PS.2.1 Make software integrity verification information available to software acquirers.
---+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 Protect Software

Protect Software

Organizations should protect all components of the software from tampering and unauthorized access

1. Ħarsa ġenerali

PS.1 Protect All Forms of Code from Unauthorized Access and Tampering

Statement

Help prevent unauthorized changes to code, both inadvertent and intentional, which could circumvent or negate the intended security characteristics of the software. For code that is not intended to be publicly accessible, this helps prevent theft of the software and may make it more difficult or time-consuming for attackers to find vulnerabilities in the software.
PS.2 Provide a Mechanism for Verifying Software Release Integrity

Statement

Help software acquirers ensure that the software they acquire is legitimate and has not been tampered with.
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.1 Referenzi

1.2 Rekwiżiti identifikati

1.3 Regolamenti relatati

2. Rekwiżiti identifikati

Rekwiżiti

3. Regolamenti relatati

Regolamenti