How should teams handle supplier incidents under NIST SP 800-161 Rev. 1 supply-chain risk management?
Handle supplier incidents by activating incident response and supply chain risk management together. NIST SP 800-161 Rev. 1 says supply chain compromises can span suppliers, developers, system integrators, external system service providers, and other third parties, and it requires organizations to define how incidents will be reported, shared, coordinated, and recovered under policy and contract terms.
A practical response should include incident triage, escalation, containment, recovery, and lessons learned. It should also identify which supplier, product, service, or third-party relationship was affected, what evidence must be preserved, who can authorize action, and how the event will be communicated to internal stakeholders and relevant external parties.
- Declare the event an incident when it meets your incident criteria and assign an incident lead.
- Notify the supplier, relevant internal owners, and other third parties according to your response plan and contract terms.
- Preserve incident data and metadata, including logs, tickets, reports, and chain-of-custody records when needed.
- Contain and eradicate the issue, then verify restoration before returning to normal operations.
- Record the root cause, impacted assets, and any supplier obligations that need follow-up or reassessment.
- Update supplier risk assessments, contracts, and contingency plans if the incident changes the risk profile.
Primary NIST C-SCRM source for supplier-incident escalation, evidence, ownership, response coordination, and reassessment expectations.
Primary NIST source for the CSF Core, Organizational Profiles, Tiers, and implementation approach.
Primary NIST source for the integrated security and privacy control catalog.