NIST Cybersecurity Framework 2.0 NIST-CSF-RS.MA-02: Incident reports are triaged and validated

What else in your programme already covers this

This control maps to 60 controls across 34 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CIS Controls v8 · 6 controls

CIS-13.1 Centralize Security Event Alerting
CIS-13.11 Tune Security Event Alerting Thresholds
CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
CIS-17.4 Establish and Maintain an Incident Response Process
CIS-17.9 Establish and Maintain Security Incident Thresholds
CIS-8.11 Conduct Audit Log Reviews

NIST SP 800-53 Rev 5 · 5 controls

NIST800-IR-4 IR-4 Incident Handling
NIST800-IR-5 IR-5 Incident Monitoring
NIST800-IR-6 IR-6 Incident Reporting
NIST800-IR-7 IR-7 Incident Response Assistance
SP800-53-IR Incident Response Family

PCI DSS 4.0 · 4 controls

10.4.3 10.4.3 Exceptions and anomalies from log review addressed
10.7.2 10.7.2 Detect and alert on critical security control failures
12.10.5 12.10.5 Plan covers alerts from security monitoring systems
5.4.1 5.4.1 Mechanisms detect and protect against phishing

ISO 22301:2019 · 3 controls

10.2 Continual improvement
8.4.2 Response structure
9.2.1 General

SOC 2 · 3 controls

SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents
SOC2-CC7.4 CC7.4 Responding to security incidents
SOC2-P8.1 P8.1 Inquiries, complaints, disputes and compliance monitoring

AWS Well-Architected Security Pillar · 2 controls

SEC10-BP02 Develop incident management plans
SEC10-BP04 Develop and test security incident response playbooks

CMMC 2.0 · 2 controls

AU.L2-3.3.6 Reduction & Reporting
IR.L2-3.6.1 Incident Handling

DORA · 2 controls

DORA-Art.17 ICT-related incident management process
DORA-Art.23 Operational or security payment-related incidents

FedRAMP High · 2 controls

IR-1 Policy and Procedures
IR-5 Incident Monitoring

FedRAMP Moderate · 2 controls

IR-1 Policy and Procedures
IR-5 Incident Monitoring

ISO 27001:2022 · 2 controls

5.25 Assessment and decision on information security events
6.8 Information security event reporting

ISO 27002:2022 · 2 controls

5.25 Assessment and decision on information security events
6.8 Information security event reporting

ISO 27701:2019 · 2 controls

5.8.1 Nonconformity and corrective action
6.13.1 Management of information security incidents and improvements

NIST Cybersecurity Framework 1.0 · 2 controls

RS.AN-1 RS.AN-1: Notifications from detection systems are investigated
RS.AN-2 RS.AN-2: The impact of the incident is understood

NIST Cybersecurity Framework 1.1 · 2 controls

RS.AN-1 RS.AN-1: Notifications from detection systems are investigated
RS.AN-2 RS.AN-2: The impact of the incident is understood

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-40 Define a Security Incident Management Procedure

APRA CPS 230 Operational Risk Management · 1 control

CPS230-27 Identification and Escalation of Incidents and Near Misses

APRA CPS 234 · 1 control

CPS234-30 Detection and Response Mechanisms

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-28 Continuous incident detection and response (Excellent)

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-STEP5 Step 5 - Manage and report security incidents

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-3 Audit logging and access monitoring

Australian Information Security Manual · 1 control

ISM-1228 Analysing cyber security events for incidents

Azure Security Benchmark · 1 control

ASBv3-IR-3 Detection and analysis - create incidents based on high-quality alerts

C5 (Germany) · 1 control

C5-SIM-02 Processing of security incidents

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-16 Security Incident Response Plan and Testing

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-SEF-06 Event Triage Processes

HIPAA Security Rule · 1 control

164.308(a)(6)(i) Security Incident Procedures (Standard)

ISO/IEC 42001:2023 · 1 control

A.8.3 External reporting

NIST SP 800-171 Rev 3 · 1 control

03.06.02 Incident Monitoring, Reporting, and Response Assistance

NIST SP 800-172 · 1 control

3.6.1e Establish Security Operations Center (SOC)

NIST SP 800-218 · 1 control

SP800-218-RV.1.1 Identify and Confirm Vulnerabilities on an Ongoing Basis

NIST SP 800-61 Rev. 3 · 1 control

RS.MA-02 RS.MA-02 Incident reports triaged and validated, including third-party reports

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(i) Security Incident Procedures (Standard)

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

You are reading one control. How much of NIST Cybersecurity Framework 2.0 have you already done?

NIST Cybersecurity Framework 2.0 NIST-CSF-RS.MA-02 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST Cybersecurity Framework 2.0 your existing evidence covers. Hold ISO 27001:2022 and 73 of 106 NIST Cybersecurity Framework 2.0 controls already carry evidence.

If you hold ISO 27001:202268.9% covered · 33 gaps If you hold NIST SP 800-53 Rev 567.9% covered · 34 gaps If you hold C5 (Germany)67% covered · 35 gaps If you hold FedRAMP Moderate63.2% covered · 39 gaps If you hold ISO 27002:202258.5% covered · 44 gaps If you hold CIS Controls v853.8% covered · 49 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 174 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 each Browse the graph free