EvidenceSheet

6.12.1 Information security in supplier relationships

Supplier agreements must state whether personal data is processed and the minimum technical and organizational measures the supplier must meet for the organization to satisfy its own security and privacy obligations, mus

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

  • Independent audit reports or certifications obtained and reviewed, not merely required · Vendor register / contract repository

governing documentDocuments that govern the control

  • Supplier agreements stating whether personal data is processed and the minimum measures required · Vendor register / contract repository
  • Responsibility allocation matrix across the organization, partners, suppliers and third parties · Vendor register / contract repository
  • Compliance support mechanism written into the agreement · Vendor register / contract repository
  • Where the organization is a processor, contract terms limiting subcontractor processing to its instructions · 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

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

6.11.3 Test data · 6.12.2 Supplier service delivery management