SA-8 Security and privacy engineering principles
Requires organization-defined systems security and privacy engineering principles to be applied when specifying, designing, developing, implementing and modifying the system and its components, so that protection is desi
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 that check the principles · Document repository
- Evidence the principles are applied to modifications, not only new build · Document repository
governing documentDocuments that govern the control
- Documented set of security and privacy engineering principles adopted by the organization · Policy repository / GRC workspace
- Design documentation showing how the principles were applied to this system · 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
- Principles named in policy but absent from any actual design artefact
- Applied at initial build and abandoned during later changes
- Privacy engineering principles omitted entirely
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