RS.MA-03 Incidents are categorized and prioritized
Incidents are categorized and prioritized. Control from NIST Cybersecurity Framework 2.0 framework, domain: RS - Respond.
5
artefacts
2
held by a system
1
at each review
moderate
to go live
Ticketing / ITSM
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Incident ticket evidence showing categories and severity · Ticketing / ITSM
- Reporting metrics by category and severity · Policy repository / GRC workspace
periodic reviewEvidence produced at each review
- Periodic review of taxonomy completeness · Document repository
governing documentDocuments that govern the control
- Incident categorization taxonomy · Document repository
- Severity scoring rubric · Document repository
First move
Start with the 2 of 5 artefacts that already live in a system (Ticketing / ITSM); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Taxonomy stale relative to current threats
- Severity downgraded informally
- Tickets miss category assignment
- Metrics not used for trend analysis
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 sheetRS.MA-02 Incident reports are triaged and validated · RS.MA-04 Incidents are escalated or elevated as needed