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
4
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
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
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
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