Requirement
The entity evaluates security events to determine whether they could or have resulted in a failure to meet objectives, and if so, takes action to prevent or address such failures.
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.
Required element 1 — any one of
security eventincidenttriageseverity
Supporting terms — specificity signals
classificationescalationp1sev1assessmentroot cause
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.5.24 | Information security incident management planning and preparation | incident-response |
| GLBA | 314.4(h) | Written incident response plan | 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 |
| ISO 27001 | A.6.8 | Information security event reporting | incident-response |