NIST Cybersecurity Framework 2.0 NIST-CSF-RS.MA-04: Incidents are escalated or elevated as needed

What else in your programme already covers this

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

ISO 27001:2022 · 3 controls

5.24 Information security incident management planning and preparation
5.25 Assessment and decision on information security events
5.26 Response to information security incidents

NIST SP 800-53 Rev 5 · 3 controls

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

Australian Information Security Manual · 2 controls

ISM-0123 Reporting incidents to the CISO
ISM-0733 CISO awareness of all incidents

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

CCM-SEF-03 Incident Response Plans
CCM-SEF-06 Event Triage Processes

NIST Cybersecurity Framework 1.0 · 2 controls

RS.AN-2 RS.AN-2: The impact of the incident is understood
RS.CO-4 RS.CO-4: Coordination with stakeholders occurs 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.CO-4 RS.CO-4: Coordination with stakeholders occurs consistent with response plans

PCI DSS 4.0 · 2 controls

10.4.3 10.4.3 Exceptions and anomalies from log review addressed
10.7.3 10.7.3 Respond promptly to critical security control failures

APRA CPS 230 Operational Risk Management · 1 control

CPS230-27 Identification and Escalation of Incidents and Near Misses

APRA CPS 234 · 1 control

CPS234-P25 Response Plan Content and Escalation Mechanisms

AWS Well-Architected Security Pillar · 1 control

SEC10-BP01 Identify key personnel and external resources

Australia My Health Records Act 2012 · 1 control

MYHR-ENF-1 Mandatory data breach notification

Azure Security Benchmark · 1 control

ASBv3-IR-2 Preparation - setup incident notification

C5 (Germany) · 1 control

C5-SIM-01 Policy for security incident management

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

CFTC-SS-16 Security Incident Response Plan and Testing

CIS Controls v8 · 1 control

CIS-17.5 Assign Key Roles and Responsibilities

CMMC 2.0 · 1 control

IR.L2-3.6.1 Incident Handling

FedRAMP High · 1 control

IR-7 Incident Response Assistance

HIPAA Security Rule · 1 control

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

ISO 27002:2022 · 1 control

5.26 Response to information security incidents

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.02 Incident Monitoring, Reporting, and Response Assistance

NIST SP 800-172 · 1 control

3.6.2e Establish and Maintain a Cyber Incident Response Team

NIST SP 800-61 Rev. 3 · 1 control

RS.MA-04 RS.MA-04 Incidents escalated or elevated through tracked status

NIST SP 800-66 Rev 2 · 1 control

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

SOC 2 · 1 control

SOC2-CC7.4 CC7.4 Responding to security 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-04 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