SEC04-BP04 Initiate remediation for non-compliant resources
Use automated remediation through EventBridge, Systems Manager Automation or Security Hub custom actions to fix common misconfigurations without manual handoffs.
Source: AWS Well-Architected Security Pillar, SEC04-BP04. 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
- Remediation success metrics · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- EventBridge rule inventory · Policy repository / GRC workspace
- SSM Automation runbooks · Document repository
- Exception approval workflow · Document repository
First move
Common gaps auditors find
- manual ticket remediation only
- no auto-remediation for public S3 or open security groups
- remediation untested
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 sheetSEC04-BP03 Correlate and enrich security alerts · SEC05-BP01 Create network layers