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.
Source: AWS Well-Architected Security Pillar, SEC01-BP03. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open AWS Well-Architected Security Pillar in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
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