NIST Cybersecurity Framework 2.0
RS - Respond

NIST Cybersecurity Framework 2.0 NIST-CSF-RS.MA-01: The incident response plan is executed in coordination with relevant third parties once an incident is declared

The incident response plan is executed in coordination with relevant third parties once an incident is declared

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

FedRAMP High · 11 controls

  • AU-5 Response to Audit Logging Process Failures
  • CP-2(1) Coordinate with Related Plans
  • CP-4(1) Coordinate with Related Plans
  • IR-2 Incident Response Training
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
  • IR-4 Incident Handling
  • IR-4(1) Automated Incident Handling Processes
  • IR-6(3) Incident Reporting | Supply Chain Coordination (IR-6(3))
  • IR-7 Incident Response Assistance
  • IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))
  • IR-8 Incident Response Plan

FedRAMP Moderate · 11 controls

  • AU-5 Response to Audit Logging Process Failures
  • CP-2(1) Coordinate with Related Plans
  • CP-4(1) Coordinate with Related Plans
  • IR-2 Incident Response Training
  • IR-3(2) Incident Response Testing | Coordination with Related Plans (IR-3(2))
  • IR-4 Incident Handling
  • IR-4(1) Automated Incident Handling Processes
  • IR-6(3) Incident Reporting | Supply Chain Coordination (IR-6(3))
  • IR-7 Incident Response Assistance
  • IR-7(1) Incident Response Assistance | Automation Support for Availability of Information and Support (IR-7(1))
  • IR-8 Incident Response Plan

NIST SP 800-53 Rev 5 · 8 controls

ISO 22301:2019 · 6 controls

  • 8.2.2 Business impact analysis
  • 8.4 Business continuity plans and procedures
  • 8.4.2 Response structure
  • 8.4.3 Warning and communication
  • 8.4.4 Business continuity plans
  • 8.5 Exercise programme

PCI DSS 4.0 · 6 controls

  • 10.7.1 10.7.1 Service providers detect critical control failures (superseded)
  • 12.10.1 12.10.1 Incident response plan ready for activation
  • 12.10.2 12.10.2 Annual review and testing of the incident response plan
  • 12.10.7 12.10.7 Response procedures for PAN found in unexpected locations
  • 12.8.2 12.8.2 TPSP contracts acknowledging account data responsibility
  • 12.8.4 12.8.4 Annual monitoring of TPSP compliance status

ISO 27001:2022 · 5 controls

  • 5.19 Information security in supplier relationships
  • 5.20 Addressing information security within supplier agreements
  • 5.24 Information security incident management planning and preparation 
  • 5.26 Response to information security incidents
  • 5.5 Contact with authorities

APRA CPS 234 · 4 controls

  • CPS234-21 Implementation of Information Security Controls
  • CPS234-25 Internal Audit Review of Information Security Controls
  • CPS234-30 Detection and Response Mechanisms
  • CPS234-P24 Information Security Response Plans

ISO 27002:2022 · 4 controls

  • 5.24 Information security incident management planning and preparation
  • 5.26 Response to information security incidents
  • 5.29 Information security during disruption
  • 5.5 Contact with authorities

ISO 27701:2019 · 4 controls

  • 6.13 Information security incident management
  • 6.13.1 Management of information security incidents and improvements
  • 6.9 Operations security
  • 6.9.1 Operational procedures and responsibilities

NIST SP 800-161 Rev 1 · 4 controls

API 1164 · 3 controls

  • API1164-17 Wireless and Field Communications
  • API1164-18 Field Device Security
  • API1164-19 Safety Instrumented Systems Interface
  • ASD37-28 Continuous incident detection and response (Excellent)
  • ASD37-31 Hunt to discover incidents (Very Good)
  • ASD37-33 Capture network traffic (Limited)
  • ISM-0141 Incident reporting obligations for providers
  • ISM-1618 CISO oversight of incident response
  • ISM-1819 Enacting cyber security incident response plans

BSI IT-Grundschutz · 3 controls

  • BSI-18 Incident response planning and testing
  • BSI-20 Incident reporting and notification
  • BSI-21 Forensic analysis capabilities
  • IS.AR.215 Information Security Incident Response
  • IS.D.OR.225 External Reporting of Information Security Events
  • IS.I.OR.225 External Reporting
  • FFIEC-23 Regulatory reporting requirements
  • FFIEC-24 Customer notification procedures
  • FFIEC-25 Post-incident review and improvement

HIPAA Security Rule · 3 controls

IEC 62443 · 3 controls

  • IEC62443-16 Incident response plan for operational disruptions
  • IEC62443-17 Recovery plan for critical systems
  • IEC62443-20 Exercises and drills for OT incidents

ISO 22320:2018 · 3 controls

  • ISO-22320-5.2 Incident management process
  • ISO-22320-B Annex B: Incident management plan structure
  • ISO-22320-C Annex C: Incident management task examples

ISO/IEC 27019:2024 · 3 controls

  • ISO27019-16 Incident response plan for operational disruptions
  • ISO27019-18 Reporting obligations to authorities
  • ISO27019-20 Exercises and drills for OT incidents

NIST SP 1800-32 · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

OSFI B-13 · 3 controls

  • OSFIB13-3 Cyber Security: Identification, Protection, Detection, Response, Recovery
  • OSFIB13-7 Incident Reporting to OSFI and Regulatory Coordination
  • OSFIB13-8 Metrics, Monitoring, Continuous Improvement, Maturity

PCI P2PE · 3 controls

  • PCI-P2PE-21 Incident detection and classification
  • PCI-P2PE-22 Incident response and containment
  • PCI-P2PE-25 Post-incident review and improvement

PCI PIN Security · 3 controls

  • PCI-PIN-23 Regulatory reporting requirements
  • PCI-PIN-24 Customer notification procedures
  • PCI-PIN-25 Post-incident review and improvement

PCI SSF · 3 controls

  • PCI-SSF-21 Incident detection and classification
  • PCI-SSF-24 Customer notification procedures
  • PCI-SSF-25 Post-incident review and improvement
  • PICERL-C2 System Backup
  • PICERL-C3 Long-Term Containment
  • PICERL-L3 Plan Improvement

SOC 2 · 3 controls

  • SOC2-CC7.4 CC7.4 Responding to security incidents
  • SOC2-CC7.5 CC7.5 Recovering from security incidents
  • SOC2-P6.5 P6.5 Vendor commitments to report unauthorised disclosures
  • SOCI-CIRMP-PHYSICAL CIRMP hazard vector: Physical security and natural hazards
  • SOCI-S30CB Statutory incident response planning
  • SOCI-S35AB Ministerial authorisation for government assistance

APPI · 2 controls

  • APPI-A41 Preparation and Handling of Pseudonymized Personal Information
  • APPI-A43 Preparation of Anonymized Personal Information
  • SEC10-BP01 Identify key personnel and external resources
  • SEC10-BP02 Develop incident management plans

Bahrain PDPL · 2 controls

  • CFTC-SS-16 Security Incident Response Plan and Testing
  • CFTC-SS-27 Coordination of the Recovery Plan with Members and Market Participants

CIS Controls v8 · 2 controls

  • CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents
  • CIS-17.4 Establish and Maintain an Incident Response Process
  • CA-ITSG33-SC-01 Security Control Catalogue
  • ITSG33-IR Incident Response (IR)
  • CSL-Art34 CII Operator Security Obligations - Art. 34
  • CSL-Art51 Cybersecurity Monitoring and Early Warning - Art. 51
  • DSL-Art23 Data Security Emergency Response (Art. 23)
  • DSL-Art29 Risk Monitoring, Remediation and Incident Notification (Art. 29)

DORA · 2 controls

  • UAE-PDPL-Art.10 Data Protection Officer (DPO) (UAE PDPL Article 10)
  • UAE-PDPL-Art.18_19_20_21 Security measures, controller/processor relationship, DPIA (UAE PDPL Articles 18-21)

ISO/IEC 30111:2019 · 2 controls

  • 30111-3 Terms and definitions
  • 30111-5.2 Vulnerability handling team
  • RS.CO-4 RS.CO-4: Coordination with stakeholders occurs consistent with response plans
  • RS.RP-1 RS.RP-1: Response plan is executed during or after an event
  • RS.CO-4 RS.CO-4: Coordination with stakeholders occurs consistent with response plans
  • RS.RP-1 RS.RP-1: Response plan is executed during or after an incident
  • NJDPA-2 Consumer Rights - Access, Correct, Delete, Portability, Appeal
  • NJDPA-6 Reasonable Data Security and Incident Response

Open Banking Security · 2 controls

  • OPENBANK-7 Logging, Monitoring, Regulatory Reporting, SLA, Availability
  • OPENBANK-8 Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

PSD2 SCA · 2 controls

  • PSDTWO-3 Common and Secure Communication, API Access for AISPs and PISPs
  • PSDTWO-4 Fraud Reporting and Incident Management

Peru DPL · 2 controls

  • PERU-7 DPO, Records, Retention, Marketing, Training
  • PERU-8 Breach Notification, ANPD Cooperation, Sanctions, Compliance

Qatar DPL · 2 controls

  • QATAR-5 Security of Processing
  • QATAR-8 Breach Notification, Compliance, Enforcement
  • SSAE18-CC7.4 CC7.4 - Incident Response
  • SSAE18-CC7.5 CC7.5 - Incident Recovery

Saudi Arabia PDPL · 2 controls

  • SA-PDPL-16 Data breach notification requirements
  • SA-PDPL-17 Security incident response procedures

South Korea PIPA · 2 controls

  • PIPA-CPO-DPO-Privacy-Officer-PIA-Personal-Information-Impact-Assessment-Articles-31-33 Korea PIPA CPO + DPO + Privacy Officer + PIA + Personal Information Impact Assessment + Articles 31-33
  • PIPA-Sensitive-Information-Unique-ID-Resident-Registration-Numbers-CCTV-Articles-23-24-25 Korea PIPA Sensitive Information + Unique ID + RRN + CCTV + Articles 23-25
  • D.1 Incident Response Planning
  • D.2 Incident Reporting
  • E8-APP-ML3 Application Control (ML3)
  • PMF-M.4 Privacy Incident Management
  • ANSSI-HYG-40 Define a Security Incident Management Procedure
  • CPS230-13 Board Accountability for Operational Risk Management
  • 4.4.7 Emergency and Incident Response
  • AWWA-G430-10 Incident Response for Water Utilities
  • AESCSF-IR-1 Incident response plan
  • ASBv3-IR-1 Preparation - update incident response plan and handling process
  • BB-DPA-20 Sections 50-60 - Registration and Responsibilities
  • BE-CF-18 Incident response planning and testing
  • BMA-11 Information Technology Incident Management

C2M2 · 1 control

  • RESPONSE-2 Respond to and Recover from Cybersecurity Incidents

C5 (Germany) · 1 control

  • C5-SIM-01 Policy for security incident management

CMMC 2.0 · 1 control

  • CA-12 Deploys Through Policies and Procedures
  • PIPL-Art57 Breach Remediation and Notification
  • CAT-D5-1 Incident planning and strategy
  • FTC-Safeguards-IR-Plan-BoardReporting-FTC-Notification Written Incident Response Plan + Board Reporting + FTC Breach Notification (16 CFR 314.4(h), (i), (j))
  • ISO28001-PC-04 Supply Chain Continuity Planning
  • ISO20000-11 Incident management

ISO/IEC 27010:2015 · 1 control

  • 27010-16.1 Continuity of Sharing

ISO/IEC 27400:2022 · 1 control

  • 27400-6.5 Security monitoring and incident response

ITIL 4 · 1 control

  • ITIL4-11 Incident management
  • NFPA1600-6.3 Emergency Response Operations

NIS2 Directive · 1 control

NIST SP 800-122 · 1 control

NIST SP 800-144 · 1 control

  • NISTSP144-8 Monitoring, Incident Response, Exit Strategy, and Compliance

NIST SP 800-145 · 1 control

  • NISTSP145-8 Governance, Reporting, and Stakeholder Education on Cloud Definition

NIST SP 800-146 · 1 control

NIST SP 800-172 · 1 control

  • 3.6.2e Establish and Maintain a Cyber Incident Response Team

NIST SP 800-190 · 1 control

  • RS.MA-01 RS.MA-01 Incident response plan executed with third parties once an incident is declared
  • NISTSP82-7 OT Incident Response, Forensics, Recovery, and Continuity
  • NRFCS-7 Detection, Logging, Incident Response, Breach Notification, and Fraud Detection
  • NGCB-6 Incident Response, 72-Hour NGCB Notification, and Independent Investigation
  • NGOB-5 Fraud Monitoring, Incident Notification, and Reporting to CBN
  • OMANCS-6 Security Monitoring, Detection, Incident Response, and OmanCERT Notification
  • OREGONCPA-3 Consent, Sensitive Data, Children and Teen Protections
  • PASONE-6 Incident Management, Audit, Handover, Operational Phase, Decommissioning

PDPA Singapore · 1 control

  • PDPASG-8 Data Breach Notification, Incident Response, and Enforcement

PDPA Thailand · 1 control

  • PDPATH-8 Data Breach Notification, Complaints, Compliance, Enforcement

POPIA · 1 control

  • POPIASA-5 Security Safeguards, Encryption, Access Control, Operator Obligations
  • PNGCYBER-4 Incident Response, Investigation, Evidence Preservation, Data Retention
  • NORWAY-8 Breach Notification, Complaints, Compliance, Enforcement

Privacy Act 2020 · 1 control

  • NZPRV-7 Notifiable Privacy Breach Scheme
  • SEC-CYB-16 External Counsel and Forensic Engagement Protocols

South Korea ISMS-P · 1 control

  • ISMSP-SYS-05 Incident Response
  • TSAPIPE-2 OT/IT Network Segmentation and Access Control

Taiwan PDPA · 1 control

  • TAIWAN-3 Data Subject Rights
  • TANZANIA-4 Security and Cross-Border
  • TSSR-NOT-2 Security Incident Notification
  • TEXASTDPSA-2 Consumer Rights
  • TRINIDAD-3 Data Subject Rights
  • UKGDPRREG-3 Controller and Processor (Articles 24-43)
  • UKGAMBLE-4 Resilience and Incident Response
  • OB-OPS.4 Incident Management
  • UK-TSA-MON-02 Incident Notification

Uruguay DPL · 1 control

  • URUGUAY-4 Security and Cross-Border

Vietnam PDPD · 1 control

  • VIETNAMPDP-2 Consent and Notice

Virginia CDPA · 1 control

  • VIRGINIAVCDPA-3 Sensitive Data Consent and Children

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.

Other controls in RS - Respond

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-01 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.

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.

Query this from an agent

The graph holds this control, the 293 it maps to, and the evidence behind each claim, over MCP and REST.