NIST SP 800-161 Rev 1
C-SCRM Family: Incident Response

NIST SP 800-161 Rev 1 161R1-IR-6: Incident Reporting

Reports supply chain incidents to the parties who need to know, including other users of the same supplier or component.

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

What else in your programme already covers this

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

  • NIST-CSF-RC.CO-03 Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholders
  • NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
  • NIST-CSF-RS.CO-03 Information is shared with designated internal and external stakeholders
  • NIST-CSF-RS.MA-01 The incident response plan is executed in coordination with relevant third parties once an incident is declared

CIS Controls v8 · 3 controls

  • CIS-17.2 Establish and Maintain Contact Information for Reporting Security Incidents
  • CIS-17.3 Establish and Maintain an Enterprise Process for Reporting Incidents
  • CIS-17.6 Define Mechanisms for Communicating During Incident Response

APRA CPS 234 · 2 controls

  • CPS234-35 APRA Notification of Material Incidents within 72 Hours
  • CPS234-P25 Response Plan Content and Escalation Mechanisms

C5 (Germany) · 2 controls

  • C5-OPS-21 Involvement of Cloud Customers in the Event of Incidents
  • C5-SIM-03 Documentation and reporting of security incidents
  • CFTC-SS-16 Security Incident Response Plan and Testing
  • CFTC-SS-19 Prompt Notification to the Commission

FedRAMP High · 2 controls

  • IR-6 Incident Reporting
  • IR-6(3) Incident Reporting | Supply Chain Coordination (IR-6(3))

FedRAMP Moderate · 2 controls

  • IR-6 Incident Reporting
  • IR-6(3) Incident Reporting | Supply Chain Coordination (IR-6(3))

ISO 22301:2019 · 2 controls

  • 7.4 Communication
  • 8.4.3 Warning and communication

ISO 27001:2022 · 2 controls

  • 5.5 Contact with authorities
  • 6.8 Information security event reporting

ISO 27002:2022 · 2 controls

  • 5.5 Contact with authorities
  • 6.8 Information security event reporting

APPI · 1 control

  • APPI-A26 Report of Leakage to the Commission and Notification to the Person
  • CPS220-19 APRA Notification of Framework Breach within 10 Business Days
  • CPS230-P33 APRA Notification of Operational Risk Incidents within 72 Hours
  • SEC10-BP01 Identify key personnel and external resources
  • ASBv3-IR-2 Preparation - setup incident notification

CMMC 2.0 · 1 control

DORA · 1 control

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.13.1 Management of information security incidents and improvements
  • 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

SOC 2 · 1 control

  • SOC2-P6.6 P6.6 Notifying breaches and 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.

Other controls in C-SCRM Family: Incident Response

You are reading one control. How much of NIST SP 800-161 Rev 1 have you already done?

NIST SP 800-161 Rev 1 161R1-IR-6 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-161 Rev 1 your existing evidence covers. Hold C5 (Germany) and 94 of 191 NIST SP 800-161 Rev 1 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. 0 were rejected on the C5 (Germany) pair alone.

Query this from an agent

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