GV.SC-04 Suppliers are known and prioritized by criticality
Suppliers are known and prioritized by criticality. Control from NIST Cybersecurity Framework 2.0 framework, domain: GV - Govern.
5
artefacts
0
held by a system
1
at each review
hard
to go live
Vendor register / contract repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Quarterly tiering refresh records · Document repository
governing documentDocuments that govern the control
- Supplier inventory with criticality scoring · Vendor register / contract repository
- Crown jewel mapping to supplier dependencies · Vendor register / contract repository
- Concentration risk analysis by service · Document repository
- Supplier exit plan summary for top tier · Vendor register / contract repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Inventory limited to procurement records
- Shadow IT vendors not captured
- Concentration risk underestimated
- Exit plans absent for critical vendors
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetGV.SC-03 Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processes · GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties