Information security obligations do not exist in isolation.
They are shaped — and constrained — by law, regulation, and contract.
Annex A 5.31 exists to ensure organisations identify, understand, and integrate their legal, statutory, regulatory, and contractual information security obligations into the ISMS, rather than treating compliance as a separate or reactive activity.
This control is about knowing the rules you operate under and designing security accordingly.

Annex A 5.31 of ISO 27001:2022 focuses on identifying and complying with information security-related obligations.
At a practical level, this means:
The control does not list specific laws or prescribe compliance methods. It expects organisations to understand their own obligations and reflect them appropriately within the ISMS.
Organisations are subject to multiple external obligations, including:
Failure to understand or meet these obligations can result in:
Annex A 5.31 ensures that information security decisions are legally and contractually informed, rather than technically convenient but non-compliant.
This control replaces and consolidates earlier ISO 27001:2013 controls relating to legal requirements and cryptographic regulation.
A pragmatic approach to Annex A 5.31 typically includes the following elements.
Organisations should identify obligations relevant to their context, including:
Obligations may vary by:
Identification should be deliberate and documented.
Not all obligations affect information security in the same way.
Organisations should consider how obligations influence:
Understanding impact matters more than compiling long lists of laws.
Identified obligations should inform:
This integration ensures compliance is embedded, not bolted on.
Annex A 5.31 explicitly recognises that cryptography may be subject to:
Organisations using encryption should be aware of:
Cryptography decisions should be informed by both security need and legal context.
Contracts often impose specific information security requirements.
These may relate to:
Contractual obligations should be identified, understood, and reflected in operational controls and supplier management.
Legal, regulatory, and contractual requirements change.
Organisations should ensure:
Compliance degrades quietly when obligations are treated as static.
Annex A 5.31 does not expect organisations to:
It does expect organisations to:
This control is about informed governance, not legal perfection.
Most failures occur through assumption, not intent.
Annex A 5.31 is about operating securely within defined boundaries.
When legal, regulatory, and contractual obligations are understood and integrated:
Information security does not exist outside the law.
Annex A 5.31 ensures organisations recognise — and design for — that reality.
We can help you understand your actual security needs and even if we cant help we can point you in the right direction
Talk to a security expert today