PO.1.1 Define Security Requirements for Software Development
Identify and document security requirements for developed software, considering customer obligations, regulatory expectations, internal policy, and known threats. Make the requirements accessible to development teams and update them as the threat landscape changes.
Source: NIST SP 800-218 (SSDF), PO.1.1. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-218 (SSDF) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Annual review record of security requirements · Document repository
governing documentDocuments that govern the control
- Secure development policy · Policy repository / GRC workspace
- Requirements traceability between policy and product backlog · Policy repository / GRC workspace
- Examples of new requirements driven by emerging threats · Document repository
First move
Common gaps auditors find
- requirements live in security wiki but are never referenced in tickets
- regulatory mapping not refreshed after new obligations apply
- no mechanism for security to inject new requirements into backlogs
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet