PW.1.1 Design Software to Meet Security Requirements
Design software so that it meets security requirements and mitigates known risks from the start. Use threat modelling to identify how an attacker could abuse the system and feed mitigations back into the design.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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
- Design review records · Document repository
- Training records for threat modelling facilitators · Physical access / facilities
governing documentDocuments that govern the control
- Threat model artifacts per significant feature · Document repository
- Linkage between threat model findings and code changes · 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
- threat models produced once at feature start, never updated
- no linkage from threat model findings to backlog tickets
- only the security team performs modelling
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 sheetPS.3.2 Software Bill of Materials · PW.1.2 Track Security Requirements, Risks, and Decisions