SEC01-BP04 Stay up to date with security threats and recommendations
Subscribe to threat intelligence sources, AWS security bulletins and CVE feeds, and incorporate emerging threats into risk assessments and detection rules.
Source: AWS Well-Architected Security Pillar, SEC01-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
none for this control
periodic reviewEvidence produced at each review
- Monthly threat review minutes · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Threat intel feed subscriptions · Document repository
- AWS Security Bulletin tracker · Document repository
- CVE triage workflow · Policy repository / GRC workspace
First move
Common gaps auditors find
- no formal threat feed subscription
- AWS bulletins ignored
- no link from intel to detections
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-BP03 Identify and validate control objectives · SEC01-BP05 Reduce security management scope