NIST Cybersecurity Framework 2.0 NIST-CSF-RS.MA-03: Incidents are categorized and prioritized

What else in your programme already covers this

This control maps to 48 controls across 31 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 · 5 controls

CIS-13.1 Centralize Security Event Alerting
CIS-16.6 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities
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

DORA · 3 controls

DORA-Art.17 ICT-related incident management process
DORA-Art.18 Classification of ICT-related incidents and cyber threats
DORA-Art.23 Operational or security payment-related incidents

AWS Well-Architected Security Pillar · 2 controls

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

C5 (Germany) · 2 controls

C5-SIM-01 Policy for security incident management
C5-SIM-02 Processing of security incidents

CMMC 2.0 · 2 controls

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

FedRAMP High · 2 controls

IR-4 Incident Handling
IR-8 Incident Response Plan

FedRAMP Moderate · 2 controls

IR-4 Incident Handling
IR-8 Incident Response Plan

ISO 27001:2022 · 2 controls

5.24 Information security incident management planning and preparation
5.25 Assessment and decision on information security events

ISO 27002:2022 · 2 controls

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

NIST Cybersecurity Framework 1.0 · 2 controls

RS.AN-2 RS.AN-2: The impact of the incident is understood
RS.AN-4 RS.AN-4: Incidents are categorized consistent with response plans

NIST Cybersecurity Framework 1.1 · 2 controls

RS.AN-2 RS.AN-2: The impact of the incident is understood
RS.AN-4 RS.AN-4: Incidents are categorized consistent with response plans

NIST SP 800-53 Rev 5 · 2 controls

NIST800-IR-4 IR-4 Incident Handling
NIST800-IR-8 IR-8 Incident Response Plan

PCI DSS 4.0 · 2 controls

10.4.3 10.4.3 Exceptions and anomalies from log review addressed
12.10.5 12.10.5 Plan covers alerts from security monitoring systems

ACSC Essential Eight · 1 control

E8-APP-ML2 Application Control (ML2)

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

ANSSI-HYG-40 Define a Security Incident Management Procedure

APRA CPS 234 · 1 control

CPS234-P25 Response Plan Content and Escalation 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

Australian Information Security Manual · 1 control

ISM-0043 Cyber security incident response plan contents

Azure Security Benchmark · 1 control

ASBv3-IR-5 Detection and analysis - prioritize 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)(ii) Response and Reporting (Required)

ISO 27701:2019 · 1 control

6.13.1 Management of information security incidents and improvements

NIST SP 800-171 Rev 3 · 1 control

03.06.01 Incident Handling

NIST SP 800-218 · 1 control

SP800-218-RV.2.1 Assess, Prioritize, and Remediate Vulnerabilities

NIST SP 800-61 Rev. 3 · 1 control

RS.MA-03 RS.MA-03 Incidents categorized by type, prioritized and given a response strategy

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(6)(ii) Response and Reporting (Required)

SOC 2 · 1 control

SOC2-CC7.3 CC7.3 Evaluating security events to identify incidents

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-03 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