RS.MA-02 Incident reports are triaged and validated
Incident reports are triaged and validated. Control from NIST Cybersecurity Framework 2.0 framework, domain: RS - Respond.
5
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Sample report validation evidence · Document repository
- Triage analyst quality reviews · Document repository
governing documentDocuments that govern the control
- Incident intake workflow with validation steps · Document repository
- Triage decision criteria · Document repository
- Trend analysis of false positives · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Validation skipped under volume
- Criteria inconsistent across shifts
- Quality reviews not performed
- False positives not analyzed for tuning
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-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared · RS.MA-03 Incidents are categorized and prioritized