EvidenceSheet
ISO/IEC 27001:2022 · Organizational controls

A.5.31 Legal, statutory, regulatory and contractual requirements

The organization is to identify, record and keep current every requirement bearing on information security, whether it comes from law, statute, regulation or contract, together with how it intends to meet each one. Purpose (stated in ISO/IEC 27002:2022): keeps the organization compliant with the laws, regulations and contracts that concern information security. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 5.31.

Source: ISO/IEC 27001:2022, A.5.31. 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 ISO/IEC 27001:2022 in the compliance library.

Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.

5
artefacts
0
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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

  • Records of periodic review of the register and of new or changed legislation identified · Policy repository / GRC workspace
  • Evidence that the register informed policies, control design, classification, risk assessment and supplier requirements · Vendor register / contract repository
  • An assessment of cryptography import, export, usage and lawful access rules for each relevant jurisdiction, with legal advice where encryption crosses borders · Cloud console / configuration management

governing documentDocuments that govern the control

  • Statement of Applicability entry for control A.5.31, showing inclusion or justified exclusion, implementation status and the risks it treats · Policy repository / GRC workspace
  • A register of applicable laws, regulations and contractual obligations for information security, with the countries covered, the approach to meeting each and a named responsible owner · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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