EvidenceSheet

5.31 Legal, statutory, regulatory and contractual requirements

Requires the legal, statutory, regulatory and contractual requirements bearing on information security, and the organisation's approach to meeting them, to be identified, documented and kept up to date.

5
artefacts
0
held by a system
2
at each review
hard
to go live
Document 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

  • Records of legal or specialist input where the interpretation is not straightforward · Document repository
  • Evidence of assessment where the organisation operates across borders, including data transfer and cryptography restrictions · Document repository

governing documentDocuments that govern the control

  • The register of legal, statutory, regulatory and contractual requirements relevant to information security, per jurisdiction of operation · Policy repository / GRC workspace
  • The documented approach to meeting each requirement, with the control or process that satisfies it · Document repository
  • Evidence the register is maintained, showing how new and changed obligations are identified and the date of the last update · Policy repository / GRC workspace

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

5.30 ICT readiness for business continuity · 5.32 Intellectual property rights