CC7.5 Identifies the root cause of security incidents
Identifies, develops, and implements activities to recover from identified security incidents.
5
artefacts
0
held by a system
4
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
- Root cause analysis records, distinguishing the immediate technical cause from the control failure that allowed it · Document repository
- Records of the restoration of operations, including verification the system was returned to a known good state · Backup / DR tooling
- Evidence of improvements implemented as a result, with owners and completion · Document repository
- Evidence of testing or exercising of incident recovery, and lessons taken from it · Document repository
governing documentDocuments that govern the control
- Recovery procedures for identified security incidents, and evidence they were applied to incidents in the period · 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
- Recovery recorded as service restored with no verification the cause was removed, so the incident recurs
- Root cause recorded as human error, which stops the analysis before it reaches the control weakness
- Improvement actions raised and left open, with no tracking to closure
- Recovery procedures never exercised, so their first use is under real pressure
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 sheetCC7.4 Responds to identified security incidents through defined procedures · CC8.1 Change management processes are in place