SEC04-BP03 Correlate and enrich security alerts
Enrich findings with asset, identity, business owner and threat intel context so responders can triage quickly, and correlate signals across GuardDuty, Security Hub and other tools.
Source: AWS Well-Architected Security Pillar, SEC04-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
none for this control
governing documentDocuments that govern the control
- Enrichment pipeline architecture · Policy repository / GRC workspace
- Asset inventory feed to SIEM · Policy repository / GRC workspace
- Correlation rule documentation · Policy repository / GRC workspace
- Ownership tags · Policy repository / GRC workspace
First move
Common gaps auditors find
- raw alerts without context
- no asset to owner mapping
- duplicate alerts across tools
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-BP02 Capture logs, findings, and metrics in standardized locations · SEC04-BP04 Initiate remediation for non-compliant resources