GS-3 Define and implement data protection strategy
Define and implement an enterprise data protection strategy covering classification and protection standards, key and certificate management, access control and lifecycle handling.
4
artefacts
0
held by a system
1
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
- Evidence the strategy drives the technical controls in place · Document repository
governing documentDocuments that govern the control
- Enterprise data protection strategy document · Document repository
- Classification and protection standard it mandates · Policy repository / GRC workspace
- Named accountable owner · 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
- strategy written for on-premises and not extended to cloud
- no owner so it is never updated
- strategy and deployed controls diverge with no reconciliation
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 sheetGS-2 Define and implement enterprise segmentation/separation of duties strategy · GS-4 Define and implement network security strategy