NIST SP 800-161 Rev. 1 Update 1

What the authority establishes

Foundational NIST guidance for integrating cybersecurity supply-chain risk management into enterprise risk management. It covers strategy, policy, risk assessment, acquisition, supplier oversight, controls, and risk response across organizational levels and the system life cycle.

It gives buyers a defensible operating model for identifying, assessing, and mitigating risk in products, services, suppliers, and downstream supply chains. It is a strong reference point for program design, assessment criteria, evidence requirements, supplier monitoring, and fourth-party visibility.

The record is written for operational interpretation, not legal advice. Applicability depends on entity type, jurisdiction, relationship, service, data, criticality, contractual commitments, and later authority guidance.

Who should read it

The primary audiences named in this review are CISOs and cybersecurity leaders, third-party risk and supply-chain risk leaders, federal agencies and government contractors, procurement and acquisition teams, risk, compliance, and internal-audit teams. Those roles may divide responsibility differently, but the operating record should still show scope, accountable ownership, evidence, review, exceptions, and the final decision.

Third-party lifecycle implications

Program Governance

Teams should determine what this authority expects at the program governance stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Planning

Teams should determine what this authority expects at the planning stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Due Diligence And Selection

Teams should determine what this authority expects at the due diligence and selection stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Contracting And Acquisition

Teams should determine what this authority expects at the contracting and acquisition stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Ongoing Monitoring

Teams should determine what this authority expects at the ongoing monitoring stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Issue Remediation

Teams should determine what this authority expects at the issue remediation stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Termination And Transition

Teams should determine what this authority expects at the termination and transition stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Capabilities that may support the work

These links identify relevant operating capabilities; they do not state that any product creates compliance.

Intake And Inventory

establishing an accountable record of relationships, products, owners, and critical services. Buyers should test the workflow against their own scope and evidence requirements.

Inherent Risk Tiering

using relationship context to determine proportional diligence and review. Buyers should test the workflow against their own scope and evidence requirements.

Due Diligence And Assessments

collecting and reviewing evidence before and during a relationship. Buyers should test the workflow against their own scope and evidence requirements.

Evidence Collection

preserving source material, responses, and reviewer context. Buyers should test the workflow against their own scope and evidence requirements.

Continuous Monitoring

bringing material external and internal change into an owned response workflow. Buyers should test the workflow against their own scope and evidence requirements.

Issue Remediation

assigning findings, deadlines, exceptions, and closure evidence. Buyers should test the workflow against their own scope and evidence requirements.

Fourth-Party Visibility

identifying and explaining important downstream dependencies. Buyers should test the workflow against their own scope and evidence requirements.

Regulatory Mapping

connecting program records to obligations and examination needs. Buyers should test the workflow against their own scope and evidence requirements.

Reporting

turning program activity into operator, executive, and board-ready information. Buyers should test the workflow against their own scope and evidence requirements.

Offboarding

closing access, data, evidence, and residual obligations when a relationship ends. Buyers should test the workflow against their own scope and evidence requirements.

What software cannot decide

Software can structure records, route work, preserve evidence, surface change, and support reporting. It cannot determine legal applicability, set risk appetite, negotiate accountable contract terms, validate every external claim, accept residual risk, or make management responsible for an outcome. Those remain organizational decisions.

Related market changes