EvidenceSheet

GV.SC-06 Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships

Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships.

5
artefacts
0
held by a system
2
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

  • Pre contract security assessment reports · Vendor register / contract repository
  • Independent attestations collected during diligence · Document repository

governing documentDocuments that govern the control

  • Due diligence questionnaire with risk based depth · Vendor register / contract repository
  • Risk acceptance decisions tied to diligence outputs · Policy repository / GRC workspace
  • Onboarding checklist closing residual gaps · HR system / LMS

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

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-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 · GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship