What is the most common gap auditors find on GV.SC-05?

Requirements not enforced in long term contracts

`GV.SC-05` Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated…

Q: What evidence do auditors commonly ask for on GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated…?

Standard supplier security requirements catalog; Contract clause library with cyber obligations; Requirements tailoring guide by supplier tier; Negotiation log capturing accepted deviations; Contract management workflow with security review gate.

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

Source: NIST CSF 2.0, GV.SC-05. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST CSF 2.0 in the compliance library.

artefacts

held by a system

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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Negotiation log capturing accepted deviations · SIEM / log platform

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

Standard supplier security requirements catalog · Vendor register / contract repository
Contract clause library with cyber obligations · Vendor register / contract repository
Requirements tailoring guide by supplier tier · Vendor register / contract repository
Contract management workflow with security review gate · Vendor register / contract repository

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

Requirements not enforced in long term contracts
Deviations approved without risk acceptance
Clauses lack audit and notification provisions
Renewals not re assessed against current standard

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 sheet

GV.SC-04 Suppliers are known and prioritized by criticality · GV.SC-06 Planning and due diligence are performed to reduce risks before entering into formal supplier or other…