DSP-07 Data Protection by Design and Default
Design security into systems, products and business practices from the outset rather than adding it afterwards, following recognised practice.
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 or architecture review records · Cloud console / configuration management
- Evidence the approach applies to business practices, not only technology · Document repository
governing documentDocuments that govern the control
- Design documentation showing security requirements set at the design stage · Document repository
- The recognised practice or standard being followed · Policy repository / GRC workspace
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
- Security review inserted just before release and treated as design input
- Approach applied to new build only, with change to existing systems exempt
- No standard named, so security by design means whatever the reviewer thinks
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 sheetDSP-06 Data Ownership and Stewardship · DSP-08 Data Privacy by Design and Default