PO.1 Define Security Requirements for Software Development

Statement

Identify and document all security requirements for the organization’s software development infrastructures and processes, and maintain the requirements over time.

Example 1:

Define policies for securing software development infrastructures and their components, including development endpoints, throughout the SDLC and maintaining that security.

Example 2:

Define policies for securing software development processes throughout the SDLC and maintaining that security, including for open-source and other third-party software components utilized by software being developed.

Example 3:

Review and update security requirements at least annually, or sooner if there are new requirements from internal or external sources, or a major security incident targeting software development infrastructure has occurred.

Example 4:

Educate affected individuals on impending changes to requirements.

Statement

Identify and document all security requirements for organization-developed software to meet, and maintain the requirements over time.

Example 1:

Define policies that specify risk-based software architecture and design requirements, such as making code modular to facilitate code reuse and updates; isolating security components from other components during execution; avoiding undocumented commands and settings; and providing features that will aid software acquirers with the secure deployment, operation, and maintenance of the software.

Example 2:

Define policies that specify the security requirements for the organization’s software, and verify compliance at key points in the SDLC (e.g., classes of software flaws verified by gates, responses to vulnerabilities discovered in released software).

Example 3:

Analyze the risk of applicable technology stacks (e.g., languages, environments, deployment models), and recommend or require the use of stacks that will reduce risk compared to others.

Example 4:

Define policies that specify what needs to be archived for each software release (e.g., code, package files, third-party libraries, documentation, data inventory) and how long it needs to be retained based on the SDLC model, software end-of-life, and other factors.

Example 5:

Ensure that policies cover the entire software life cycle, including notifying users of the impending end of software support and the date of software end-of-life.

Example 6:

Review all security requirements at least annually, or sooner if there are new requirements from internal or external sources, a major vulnerability is discovered in released software, or a major security incident targeting organization-developed software has occurred.

Example 7:

Establish and follow processes for handling requirement exception requests, including periodic reviews of all approved exceptions.

Statement

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

Example 1:

Define a core set of security requirements for software components, and include it in acquisition documents, software contracts, and other agreements with third parties.

Example 2:

Define security-related criteria for selecting software; the criteria can include the third party’s vulnerability disclosure program and product security incident response capabilities or the third party’s adherence to organization-defined practices.

Example 3:

Require third parties to attest that their software complies with the organization’s security requirements.

Example 4:

Require third parties to provide provenance data and integrity verification mechanisms for all components of their software.

Example 5:

Establish and follow processes to address risk when there are security requirements that third-party software components to be acquired do not meet; this should include periodic reviews of all approved exceptions to requirements.