SEC01-BP03 Identify and validate control objectives
Derive control objectives from compliance, regulatory and business requirements, document them, and trace each to implemented AWS controls with measurable validation.
4
artefacts
0
held by a system
2
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
- Validation test results · Source control / CI pipeline
- Audit Manager assessments · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Control objectives register · Policy repository / GRC workspace
- Compliance to control mapping spreadsheet · 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
- objectives not documented
- no mapping to specific AWS controls
- controls untested
- drift between policy and implementation
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 sheetSEC01-BP02 Secure account root user and properties · SEC01-BP04 Stay up to date with security threats and recommendations