GV.SC-03 GV · Govern · GV.SC Cybersecurity Supply Chain Risk Management

GV.SC-03 — Supply chain risk in ERM

Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes.

Also written as GV-SC-03, GV.SC-3, CSF 2.0 GV.SC-03, NIST CSF GV.SC.

What NIST CSF GV.SC-03 means

GV.SC-03 is one of 31 subcategories in the Govern (GV) function, under the Cybersecurity Supply Chain Risk Management category (GV.SC). The Core states: “Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes.” Govern is the function CSF 2.0 added, and it is the one most organisations score lowest on: the outcome is not a tool you deploy but a decision someone with authority has to make, record, and revisit.

Evidence that supports GV.SC-03

To demonstrate this outcome in an assessment or audit, gather artefacts such as:

  • Supply chain risks in the enterprise risk register
  • Integration of C-SCRM with incident response and improvement processes
  • Supply chain risk reporting to leadership

ISO 27001 mapping

GV.SC-03 has no direct one-to-one ISO 27001:2022 Annex A equivalent — it is a governance or process outcome that ISO 27001 addresses at the management-system level (Clauses 4–10) rather than through a specific Annex A control. Treat it as its own requirement in your CSF profile.

Map GV.SC-03 to ISO 27001 & SOC 2 →
Crosswalk this subcategory in the Control Mapper & Gap Assessment.
Document the risk →
Record treatment for gaps against GV.SC-03 in the Risk Register.

Other Cybersecurity Supply Chain Risk Management subcategories

GV.SC-01 Supply chain risk management program GV.SC-02 Supplier roles and responsibilities GV.SC-04 Suppliers prioritized by criticality GV.SC-05 Supply chain requirements in contracts GV.SC-06 Due diligence before supplier relationships GV.SC-07 Ongoing supplier risk monitoring GV.SC-08 Suppliers in incident planning GV.SC-09 Supply chain security throughout lifecycle GV.SC-10 Post-relationship supply chain plans

All 31 Govern subcategories →

Frequently asked questions

Is NIST CSF GV.SC-03 mandatory?

No. CSF 2.0 is a voluntary framework of outcomes rather than a set of requirements, and there is no certification against it. GV.SC-03 becomes binding only when something else makes it so — a contract, a regulator that references CSF, or your own Target Profile. That is the practical difference between CSF and an auditable standard like ISO 27001 or SOC 2.

How is GV.SC-03 assessed?

Through profiles rather than pass/fail testing. You record how fully the outcome is achieved today in a Current Profile, state where it needs to be in a Target Profile, and the gap between them becomes your action plan. Implementation Tiers (Partial, Risk Informed, Repeatable, Adaptive) describe how rigorous your governance around the outcome is, not whether you have met it.

Who owns GV.SC-03?

Govern outcomes sit with leadership rather than with the security team — executives, risk owners, and in many organisations the board. If GV.SC-03 has no named owner outside IT, that is usually the finding, because CSF 2.0 introduced Govern precisely to make cybersecurity a management-level accountability.