CC7.4 Responds to identified security incidents through defined procedures
Executes a defined incident response program once a security incident is identified, with roles and responsibilities assigned, the nature and severity of the incident understood, the active threat contained and mitigated
6
artefacts
1
held by a system
3
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
- Incident tickets carrying detection, containment, eradication and recovery timestamps · Ticketing / ITSM
periodic reviewEvidence produced at each review
- Severity assessment and containment strategy record for individual incidents · Document repository
- Remediation records tying each incident to closure of the underlying vulnerability · Vulnerability scanner / patch tooling
- Periodic evaluation or exercise of the response program with resulting changes · Document repository
governing documentDocuments that govern the control
- Incident response program naming roles, escalation paths and the use of external resources · Policy repository / GRC workspace
- Records of communication to affected parties and, where privacy is in scope, to data subjects and regulators · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Ticketing / ITSM on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- A response plan exists but no incident record shows it was followed
- Containment recorded while the vulnerability that allowed the incident stays open
- No evidence that affected parties were told anything
- Effectiveness never evaluated, so the same root cause recurs across periods
- Roles named in the plan no longer match the people who actually respond
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.3 Evaluates security events to determine incident status · CC7.5 Identifies the root cause of security incidents