A.5 Organizational controls

A.5.31 Legal, statutory, regulatory and contractual requirements

Not mandatory by default – decided in your SoA

What it means in plain language

Identify the laws, regulations and contracts that affect information security and keep up with changes.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Teams should turn legal awareness into a maintained operational register that affects controls, contracts, and accountability. A practical approach tracks applicable obligations, assigns monitoring responsibility, and records how changes are assessed for impact on the ISMS, avoiding the common failure of keeping law in legal inboxes instead of in working security decisions.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • The register lists regulations, but scope is unclear, so teams cannot tell which obligations apply to which services, countries, or data types.
  • Legal and contractual changes are not reviewed on a defined cadence, leaving policy, supplier clauses, or notices outdated after business or regulatory changes.
  • Ownership is ambiguous, so no one records impact analysis, implementation actions, or evidence that obligations were communicated to relevant process owners.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Build the register around obligation type, jurisdiction, business process, data category, and contract reference. Name an accountable owner in legal, compliance, or privacy, with operational reviewers from security, procurement, HR, and service owners so each entry has someone who can interpret it and trigger updates.
  • Capture the practical effect of each item, not just the citation: retention periods, breach notice windows, transfer restrictions, monitoring duties, sector rules, or customer-imposed security clauses. Link each obligation to the policy, procedure, or supplier agreement it influences, and note the control owner responsible for implementation.
  • Review the register when laws change, contracts renew, new countries or services are added, or incidents reveal a missed obligation. Record the source of change, impact assessment, decision, and follow-up actions; use a simple log so auditors can trace why a requirement was added, revised, or deemed not applicable.
  • Retain evidence of periodic review, such as counsel comments, change alerts, contract markups, and management approvals. Where obligations conflict, document the resolution path and residual risk decision so the ISMS shows informed treatment rather than informal assumptions or single-person memory.

What an auditor will ask to see

  • Legal & Regulatory Requirements Register with applicability, owner, impact notes, and review date.
  • Change assessment note linking a new obligation to affected processes, contracts, and updates.
  • Counsel or compliance review email with marked-up obligations and approved follow-up actions.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.31. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.34 — Privacy and protection of personal identifiable information (PII) and A.5.20 — Addressing information security within supplier agreements. Keep the ownership and evidence consistent across these activities.

NIS2 and ISO/IEC 27001: reuse controls and check legal gaps for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.