SEF-01 Security Incident Management Policy and Procedures
Keep an approved governing document covering how security incidents are managed, how electronic discovery is handled and how forensics is performed in cloud environments, and review it at least yearly.
4
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
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
- Annual review record · Document repository
- Evidence of communication to the response teams · Policy repository / GRC workspace
governing documentDocuments that govern the control
- The approved incident management, e-discovery and forensics policy · Policy repository / GRC workspace
- Procedures covering evidence handling and forensic readiness in cloud environments · 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
- Policy covers incident response and omits e-discovery and forensics entirely
- Forensic procedures written for on-premises systems and unusable in cloud
- Annual review missed
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 sheetLOG-13 Failures and Anomalies Reporting · SEF-02 Service Management Policy and Procedures