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.
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
- 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
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
- 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