GV.SC-06 Planning and due diligence are performed to reduce risks before entering into formal supplier or other…
Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships
Source: NIST CSF 2.0, GV.SC-06. 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.
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
none for this control
periodic reviewEvidence produced at each review
- Pre contract security assessment reports · Vendor register / contract repository
governing documentDocuments that govern the control
- Due diligence questionnaire with risk based depth · Vendor register / contract repository
- Independent attestations collected during diligence · Document repository
- Risk acceptance decisions tied to diligence outputs · Policy repository / GRC workspace
- Onboarding checklist closing residual gaps · HR system / LMS
First move
Common gaps auditors find
- Diligence skipped for urgent procurement
- Attestations accepted without scope verification
- Risk acceptance not signed at appropriate level
- Onboarding gaps never closed
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-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated… · GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded…