← NIST CSF 2.0 · RESPOND — Incident Management
RS.MA-02 — Incident reports are triaged and validated
high
incident-response
Requirement
Incident reports are triaged and validated.
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
triagevalidat…confirmconfirmation
Required element 2 — any one of
incidentreportseverityclassificationclassif…
Supporting terms — specificity signals
sev1p1matrixtime to acknowledgedutyfalse positive
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 |
| GLBA | 314.4(h) | Written incident response plan | incident-response |
| GDPR | Art.33 | Notification of a breach to the supervisory authority | incident-response |
| SOC 2 | CC7.4 | Incident response programme | incident-response |
| SOC 2 | CC7.5 | Recovery from identified incidents | incident-response |
| ISO 27001 | A.6.8 | Information security event reporting | incident-response |
| PCI DSS 4.0.1 | 10.7 | Failures of critical security controls are detected and addressed | incident-response |