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.
Source: NIST CSF 2.0, RS.MA-02. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST CSF 2.0 in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
- Trend analysis of false positives · Document repository
governing documentDocuments that govern the control
- Incident intake workflow with validation steps · Document repository
- Triage decision criteria · Document repository
First move
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… · RS.MA-03 Incidents are categorized and prioritized