EvidenceSheet

A.5.31 Legal, statutory, regulatory and contractual requirements

Identify, document and keep current the legal and contractual obligations relevant to security, and your approach to meeting them.

12
artefacts
1
held by a system
3
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

  • Updated legal requirements log · SIEM / log platform

periodic reviewEvidence produced at each review

  • Annual legal review meeting minutes · Policy repository / GRC workspace
  • Signed service level agreements · Vendor register / contract repository
  • Pci dss attestation of compliance · Vendor register / contract repository

governing documentDocuments that govern the control

  • Master legal obligations register · Policy repository / GRC workspace
  • Vendor contracts with security clauses · Vendor register / contract repository
  • Contractual compliance checklist · Document repository
  • Gdpr compliance report · Document repository
  • Industry regulatory license renewal certificate · Document repository
  • Data protection impact assessment template · Policy repository / GRC workspace
  • Completed pi a for new system · Policy repository / GRC workspace
  • Privacy risk treatment plan · Policy repository / GRC workspace

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

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

A.5.30 ICT readiness for business continuity · A.5.32 Intellectual property rights