NIST SP 800-161 Rev 1
C-SCRM Family: Supply Chain Risk Management

NIST SP 800-161 Rev 1 SR-8: Notification Agreements

Establishes agreements requiring suppliers to notify the organization of compromise, vulnerability and relevant change.

What else in your programme already covers this

This control maps to 39 controls across 24 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 · 3 controls

  • CIS-15.4 Ensure Service Provider Contracts Include Security Requirements
  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • CIS-17.6 Define Mechanisms for Communicating During Incident Response
  • NIST-CSF-GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties
  • NIST-CSF-GV.SC-08 Relevant suppliers and other third parties are included in incident planning, response, and recovery activities
  • NIST-CSF-RS.CO-02 Internal and external stakeholders are notified of incidents
  • CPS230-27 Identification and Escalation of Incidents and Near Misses
  • CPS230-50 Formal Agreement Content for Material Arrangements

APRA CPS 234 · 2 controls

  • CPS234-35 APRA Notification of Material Incidents within 72 Hours
  • CPS234-36 APRA Notification of Material Control Weakness within 10 Business Days

FedRAMP High · 2 controls

  • IR-6(3) Incident Reporting | Supply Chain Coordination. Provide incident information to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system components
  • SR-8 Notification Agreements (SR-8)

FedRAMP Moderate · 2 controls

  • IR-6(3) Incident Reporting | Supply Chain Coordination. Provide incident information to the provider of the product or service and other organizations involved in the supply chain or supply chain governance for systems or system components
  • SR-8 Notification Agreements (SR-8)

HIPAA Security Rule · 2 controls

ISO 27701:2019 · 2 controls

  • 6.13.1 Management of information security incidents and improvements
  • 8.5.8 Change of subcontractor to process PII

NIST SP 800-171 Rev 3 · 2 controls

  • 03.17.02 Acquisition Strategies, Tools, and Methods
  • 03.17.03 Supply Chain Requirements and Processes

NIST SP 800-218 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC2.3 COSO principle 15: Communicates with external parties regarding matters affecting controls
  • SOC2-P6.5 Obtains commitments from vendors and other third parties with access to personal information to notify the entity in the event of actual or suspected unauthorized disclosures of personal information. Such notifications are reported to
  • CBPR-PR-25 Processor obligation to report data quality issues

APPI · 1 control

  • APPI-A26 Report of Leakage to the Commission and Notification to the Person
  • ASBv3-IR-2 Preparation - setup incident notification

C5 (Germany) · 1 control

DORA · 1 control

ISO 27001:2022 · 1 control

  • 5.20 Addressing information security within supplier agreements

ISO 27002:2022 · 1 control

  • 5.20 Addressing information security within supplier agreements
  • SR-8 Notification Agreements (SR-8)
  • SR-8 Notification Agreements (SR-8)
  • SR-8 Notification Agreements (SR-8)

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: Supply Chain Risk Management

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

NIST SP 800-161 Rev 1 SR-8 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 39 it maps to, and the evidence behind each claim, over MCP and REST.