← GLBA · Safeguards Rule (16 CFR 314)
314.4(h) — Written incident response plan
Requirement
A written incident response plan is designed to promptly respond to and recover from any security event materially affecting customer information. It addresses the plan's goals, internal response processes, clear roles and decision-making authority, internal and external communications, remediation of identified weaknesses, documentation and reporting of events, and evaluation and revision after events.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| SOC 2 | CC7.3 | Evaluation of security events | incident-response |
| ISO 27001 | A.5.24 | Information security incident management planning and preparation | incident-response |
| NIST CSF 2.0 | RS.MA-01 | The incident response plan is executed | incident-response |
| NIST CSF 2.0 | RS.MA-02 | Incident reports are triaged and validated | incident-response |
| NIST CSF 2.0 | RS.AN-03 | Root cause is determined | incident-response |
| NIST CSF 2.0 | RC.CO-03 | Recovery activities are communicated | incident-response |
| GDPR | Art.33 | Notification of a breach to the supervisory authority | incident-response |
| SOC 2 | CC7.4 | Incident response programme | incident-response |