SEC01-BP05 Reduce security management scope
Reduce the surface the team must secure itself by preferring AWS managed services that shift provisioning, patching and backup of underlying components to the provider, and weigh that management overhead when selecting s
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
- Service selection record showing managed versus self-managed options considered · Document repository
governing documentDocuments that govern the control
- Shared responsibility mapping per service in the workload · Document repository
- Total cost of ownership analysis covering security maintenance effort · Document repository
- AWS Artifact compliance reports relied on for the managed components · 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
- self-managing databases, queues or key stores with no rationale
- no record of which controls the provider operates
- shared responsibility boundary undocumented so patching ownership is ambiguous
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-BP04 Stay up to date with security threats and recommendations · SEC01-BP06 Automate deployment of standard security controls