SEC04-BP02 Capture logs, findings, and metrics in standardized locations
Aggregate security telemetry into standardised destinations such as S3 log archive buckets, Security Hub and a centralised SIEM so analysts and automation can correlate across sources.
Source: AWS Well-Architected Security Pillar, SEC04-BP02. 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
- S3 log archive bucket policies · SIEM / log platform
- Security Hub aggregator configuration · SIEM / log platform
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Security Lake setup · Policy repository / GRC workspace
- SIEM ingestion pipelines · Policy repository / GRC workspace
First move
Common gaps auditors find
- logs scattered across accounts
- no Security Hub aggregator region
- SIEM missing key sources
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-BP01 Configure service and application logging · SEC04-BP03 Correlate and enrich security alerts