NIST CSF 2.0 is the second version of the US National Institute of Standards and Technology's Cybersecurity Framework, published on 26 February 2024. It organises outcomes into six functions, with supply chain risk management under the new Govern function.
What NIST CSF 2.0 means
NIST published CSF 2.0 as NIST CSWP 29. It is voluntary and written for organisations of any size or sector, not only critical infrastructure. Its six functions are Govern, Identify, Protect, Detect, Respond and Recover. Govern is new in version 2.0 and covers strategy, roles, policy and oversight of cybersecurity risk.
Cybersecurity supply chain risk management sits in Govern as category GV.SC, with ten outcomes. They include knowing and prioritising suppliers by criticality (GV.SC-04), building requirements into contracts (GV.SC-05), planning and due diligence before entering relationships (GV.SC-06), managing supplier risk over the relationship (GV.SC-07) and planning for activities after it ends (GV.SC-10).
For a third-party programme, GV.SC gives a lifecycle that maps cleanly to intake, tiering, contracting, monitoring and offboarding. Many US organisations use it as the common language for internal policy, and vendors often map their own controls to it. NIST SP 800-161r1 gives more detailed supply chain practices.
What to check in vendor documents
- Whether the vendor maps its controls to CSF 2.0 and will share the mapping or a current profile.
- Evidence for the outcomes you rely on, such as incident response and recovery testing.
- How the vendor manages its own suppliers, as GV.SC expects of you.
- Whether your contract carries the GV.SC-05 requirements set for this vendor's tier.
In ProcureCortex
Internal policies built on CSF 2.0 outcomes can be among the rules selected for a vendor, and each finding names the rule it was checked against.
How an assessment worksRelated terms
- Vendor tieringVendor tiering is the practice of sorting vendors into risk tiers, based on factors such as the data they handle, the functions they support and how hard they are to replace, so that review depth, evidence and monitoring match the risk.
- Vendor due diligenceVendor due diligence is the assessment an organisation carries out before contracting with a vendor, and again at renewal, to confirm the vendor can deliver the service safely and meet the legal, security, financial and operational requirements that apply.
- Continuous vendor monitoringContinuous vendor monitoring is the ongoing tracking of a vendor's risk between formal assessments, using triggers such as new reports, incidents, contract or sub-processor changes, financial events and external signals, so reviews happen when risk changes.
- Vendor offboardingVendor offboarding is the controlled end of a vendor relationship: removing access, retrieving or deleting data, settling contractual obligations and updating records, so no data, access or liabilities are left behind.
- Third-party risk management (TPRM)Third-party risk management (TPRM) is the discipline of identifying, assessing, monitoring and controlling the risks an organisation takes on through any outside party it relies on, including vendors, partners, outsourcers and their own suppliers.
Sources
- NIST, Cybersecurity Frameworkwww.nist.gov/cyberframework
- NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0doi.org/10.6028/NIST.CSWP.29
- NIST SP 800-161r1, Cybersecurity Supply Chain Risk Management Practicescsrc.nist.gov/pubs/sp/800/161/r1/upd1/final
Summarised for practitioners, not legal advice. Check the source text for your own obligations.