- ClassificationCategorySupply Chain SecurityDomainCybersecurityFramework FamilyNIST Special Publications
- Regulatory ContextTypeGuidanceLegal InstrumentGuidanceSectorCross-SectorIndustryCross-Industry
- Region / PublisherRegionGlobalRegion DetailUnited StatesPublisherNational Institute of Standards and Technology (NIST)
- VersioningVersionRevision 1 (May 2022), Update 1 of November 1, 2024; supersedes SP 800-161 (April 2015)Effective DateMay 5, 2022 (Update 1: November 1, 2024)Issue DateMay 5, 2022 (Update 1 issued November 1, 2024)
- AdoptionAdoption ModelVoluntaryImplementation ComplexityHigh
- Official ReferenceOpen Link in New TabSource
License included / downloadable: Yes
SP 800-161 Rev. 1 is a U.S. government publication, free of charge from NIST and not subject to copyright in the United States (attribution is appreciated); the platform links to the official text.
Framework text is licensed by its publisher and is included only where stated above.
- NIST SP 800-161 Rev. 1 is NIST's foundational guidance for cybersecurity supply chain risk management (C-SCRM) across the ICT and OT supply chain.
- Published May 5, 2022, superseding the 2015 edition, with Update 1 of November 1, 2024 as the current text.
- It is voluntary for non-federal organizations and written to support federal agencies, which use FedRAMP first for cloud providers.
- It integrates C-SCRM into enterprise risk management at three levels and adds supply chain guidance to 20 control families.
- SmartSuite Third Party Risk Management assesses supplier risk across the lifecycle, with Compliance Management for the Appendix A controls.
Overview
NIST SP 800-161 Revision 1, Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, is NIST's foundational guidance for identifying, assessing and mitigating cybersecurity risks in the ICT and operational technology supply chain at every level of an enterprise. Jon Boyens and Angela Smith of NIST and four Boston Consulting Group co-authors published it on May 5, 2022, superseding the original SP 800-161 of April 8, 2015. Update 1 of November 1, 2024 is the current text, and NIST's C-SCRM project page still names Revision 1 as its foundational publication. It is voluntary guidance for non-federal organizations and written to support federal agencies.
NIST developed it under the Federal Information Security Modernization Act of 2014, and its Authority statement says nongovernmental organizations may use it on a voluntary basis. Section 1.1 defines cybersecurity supply chain risk management (C-SCRM) as a systematic process for managing exposure to cybersecurity risks throughout the supply chain and developing response strategies, policies, processes and procedures. Section 1.3 tells federal agencies assessing cloud service providers to use FedRAMP first and then apply this document to what FedRAMP does not address.
The publication has three sections and eleven appendices. Section 2 integrates C-SCRM into enterprise-wide risk management at three levels, Section 3 sets out critical success factors, Appendix A adds C-SCRM guidance to 20 control families, Appendix C is a risk exposure framework with six threat scenarios, Appendix D holds four templates, and Appendix E covers the Federal Acquisition Supply Chain Security Act. How requirements pass down to suppliers is covered on a separate page: NIST SP 800-161 Rev. 1 (Flow Down).
Why does it matter?
Organizations buy products and services whose development, integration and operation they cannot fully see, and the abstract names the resulting risks: malicious functionality, counterfeits and vulnerabilities from poor manufacturing and development practices. Section 2.2 gives examples, from an insider at a system integrator stealing intellectual property to a chip designer implanting a backdoor, and section 2.1 explains why a C-SCRM capability is now required of any enterprise that depends on digital technology. The 2018 SECURE Technology Act and the formation of the Federal Acquisition Security Council are cited as evidence of public and private consensus.
Key benefits include:
- Know the exposed assets
Section 2.1 says an established C-SCRM program lets an enterprise understand which critical assets are most susceptible to supply chain weaknesses and vulnerabilities.
- One approach at three levels
Section 2.3 gives each level its own deliverables: enterprise strategy, policy and implementation plan; mission and business process strategies; and system-level C-SCRM plans.
- A control set built on SP 800-53
Appendix A adds Supplemental C-SCRM Guidance, with the levels where each control applies, to 20 control families including Supply Chain Risk Management (SR).
- Templates to adapt
Appendix D provides a C-SCRM strategy and implementation plan template, a policy template, a plan template and a supply chain risk assessment (C-SCRA) template whose Table 26 is the information gathering and scoping questionnaire.
- Federal acquisition context
Appendix E applies the Federal Acquisition Supply Chain Security Act of 2018 (Title II of the SECURE Technology Act) to agency risk assessments; Appendix F points to NIST's online guidance for Executive Order 14028.
How does it work?
Section 2.3 follows the three risk management levels of SP 800-39: Level 1 enterprise, Level 2 mission and business process, and Level 3 operational. A C-SCRM Program Management Office (2.3.5) can serve as a service provider to all three, with advisory services, supplier and product risk assessments, information sharing and a C-SCRM risk register, staffed by security, procurement, risk management, engineering, software, IT, legal and HR representatives. Appendix G runs the risk management steps Frame, Assess, Respond and Monitor at each level.
Section 3 lists critical success factors: C-SCRM in acquisition (3.1), supply chain information sharing (3.2), training and awareness (3.3), key practices (3.4), capability implementation measurement and measures (3.5) and dedicated resources (3.6). Section 3.4 sorts practices into foundational, sustaining and enhancing, and Section 1.1 states that the publication offers a general prioritization but no roadmap and is not one-size-fits-all: each enterprise adopts and tailors it to its size, resources and risk.
Appendix A explains how controls were selected from SP 800-53 Rev. 5, tailored and given C-SCRM supplemental guidance, with the levels, 1, 2 and 3, at which each should be implemented, and Appendix B summarizes them in Table 6. Appendix C describes how to build threat scenarios and a risk exposure framework, with six worked scenarios: foreign government influence over suppliers, telecommunications counterfeits, industrial espionage, malicious code insertion, unintentional compromise and vulnerable reused components.
Key Elements
- Multilevel risk management (2.3)
Enterprise, mission and business process, and operational levels, each with its own C-SCRM strategies, policies and plans.
- C-SCRM PMO (2.3.5)
A cross-disciplinary office that provides advisory services, supplier and product risk assessments, information-sharing management and the C-SCRM risk register.
- Key practices (3.4)
Foundational practices such as a dedicated multidisciplinary C-SCRM team and senior leadership support, then sustaining and enhancing practices as capability matures.
- C-SCRM security controls (Appendix A)
Supplemental C-SCRM Guidance for 20 control families, with a Level(s) line for each control and the SR family at its end.
- Risk exposure framework (Appendix C)
Threat scenarios that turn risk assessment findings into a narrative, with likelihood and impact analysis and six worked scenarios.
- Templates (Appendix D)
C-SCRM strategy and implementation plan, policy, plan and C-SCRA templates, each with a sample outline and sample text.
- FASCSA and EO 14028 (Appendices E and F)
Guidance for federal executive agencies on supply chain risk assessment factors, severity levels and response, plus a pointer to NIST's online software supply chain guidance.
What does it cover?
Section 1.2 lists the audience: authorizing officials, CIOs and chief information security officers; mission owners, program managers, engineers and developers; acquisition officials and contracting officers; logistics and property managers; system owners and administrators; auditors and assessors; and commercial entities that produce component products, systems or services. The text uses the word enterprise for any organization, and the guidance covers products and services from suppliers, developers, system integrators, external system service providers and other ICT and OT-related service providers. Its Authority statement says it does not apply to national security systems without approval of the responsible federal officials.
What are its objectives?
Section 1.1 sets the purpose of the publication.
Provide guidance on how to identify, assess, select and implement risk management processes and mitigating controls across the enterprise to manage cybersecurity risks throughout the supply chain.
Integrate C-SCRM into risk management activities through a multilevel approach with a strategy and implementation plan, policies, plans and product and service risk assessments.
Treat C-SCRM as the shared responsibility of different disciplines with different authorities and legal considerations.
Offer practices to adopt and tailor to the enterprise's size, resources and risk circumstances, with a general prioritization of foundational, sustaining and enhancing practices.
Support a C-SCRM capability that is measured and funded through dedicated resources (3.5 and 3.6).
Framework in Context
Section 1.7 says the publication builds on NIST CSF 2.0, FIPS 199, SP 800-30 Rev. 1, SP 800-37 Rev. 2, SP 800-39, SP 800-53 Rev. 5, SP 800-53B and SP 800-160 Vol. 1 Rev. 1 and Vol. 2 Rev. 1. NIST's C-SCRM project page adds related publications: SP 1326, the Due Diligence Assessment Quick-Start Guide, finalized July 8, 2026, and SP 800-18 Rev. 2, on developing security, privacy and C-SCRM plans for systems, finalized June 30, 2026. A fillable version of the SCRM Assessment Scoping Questionnaire (Table 26) has been available from December 2, 2025.
Common Framework Mappings
Organizations map SP 800-161 Rev. 1 to the frameworks below so that supplier risk work serves several programs at once.
Mapped frameworks include:
EU DORA
ISO 28000
ISO 27001:2022
ISO 27002:2022
ISO/IEC 27036
MITRE ATT&CK
NIST CSF 2.0
NIST 800-53 Rev.5
How SmartSuite Supports NIST SP 800-161 Rev. 1
SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.
Use Third Party Risk Management to assess and monitor supplier risk across the full lifecycle, Procurement Operations to connect purchase requests, vendors and contracts, Compliance Management for the Appendix A controls and their evidence, and Cyber & IT Risk for cyber risks and vulnerabilities, with each record carrying the level, 1, 2 or 3, at which it belongs.
Supplier Inventory and Criticality
Record each supplier with its products and services, the systems they support and an assigned criticality level, and review the inventory on a set frequency (control SR-13).
Three-Level Strategy and Plan Records
Hold the C-SCRM strategy and implementation plan, the Level 1 and 2 policies and the Level 3 system plans, with owners and revision dates, using the Appendix D templates.
Supplier Risk Assessments
Run supplier and product assessments with the Appendix D C-SCRA template and keep scoping answers, threat, vulnerability and impact findings and the response for each.
Control Library with Levels
Load the Appendix A controls as requirements with their Level 1, 2 or 3 assignment, owner, implementation status and evidence in Compliance Management.
Scenario and Risk Register
Log Appendix C threat scenarios with likelihood, impact and the chosen response in Cyber & IT Risk, linked to the suppliers and systems they involve.
Practice Maturity and Measures
Track foundational, sustaining and enhancing practices and the section 3.5 measures in Enterprise Reporting dashboards for leadership.
Related frameworks

DORA (Regulation (EU) 2022/2554) requires EU financial entities to manage ICT risk, report major incidents, test resilience and control ICT third-party risk, applying from January 17, 2025.

ISO 28000:2022 specifies requirements for a security management system, including supply chain aspects, for any type or size of organization. ISO published it on March 15, 2022.

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

MITRE ATT&CK is a free knowledge base of adversary tactics, techniques and sub-techniques from The MITRE Corporation, updated twice a year; the current release is v20.0.
Frequently Asked Questions For NIST SP 800-161 Rev. 1 (Cybersecurity Supply Chain Risk Management)
It is NIST's guidance on cybersecurity supply chain risk management (C-SCRM), published May 5, 2022 and superseding SP 800-161 of April 8, 2015. Update 1, dated November 1, 2024, is the current text, and NIST's project page still calls Revision 1 its foundational C-SCRM publication. It is voluntary for organizations outside the federal government.
Appendix K lists the changes. NIST deleted Table 3-1 (C-SCRM in the procurement process) as confusing, added a semiconductor manufacturer example to section 2.2, updated references from CSF 1.1 to CSF 2.0 and to SP 800-160 Rev. 1 volumes, and revised guidance for controls such as AC-17, RA-3 and RA-5. It also updated the online Appendix F for OMB M-22-18 software attestations and software bills of materials.
Section 2.3 uses the three levels of SP 800-39: enterprise, mission and business process, and operational. Level 1 sets the C-SCRM strategy, policy and implementation plan, Level 2 tailors them to mission and business processes, and Level 3 writes system-level C-SCRM plans. A cross-disciplinary C-SCRM Program Management Office (2.3.5) can support all three levels.
Section 3.4 groups key practices by maturity. Foundational practices include a dedicated multidisciplinary C-SCRM team or PMO and senior leadership support. Sustaining practices build on them, for example continuous monitoring and reassessment of suppliers and C-SCRM metrics. Enhancing practices, such as automation and quantitative risk analysis, come once sustaining practices are standardized across the enterprise.
The Authority statement says nongovernmental organizations may use it voluntarily. Section 1.3 tells federal agencies assessing cloud service providers to apply FedRAMP guidelines first and then this document for what FedRAMP does not address. Appendix E adds guidance for federal executive agencies on supply chain risk assessments under the Federal Acquisition Supply Chain Security Act of 2018.

Put this framework to work in SmartSuite
Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.


