ISO 27001 Control A.5.31: Legal, Statutory, Regulatory and Contractual Requirements

· 7 min read · Lyudmil Arkov

Every organization operates inside a web of obligations. Data protection law, sector rules, customer contracts, insurance conditions and employment law all say something about how information must be handled. Most teams know a few of them well and are dimly aware of the rest. A.5.31 asks you to bring them all into the light, write them down and keep the list current. It is the 31st of 37 organizational controls in our walk through Annex A, and the first of the compliance group that closes the section.

We should say plainly that we are information security consultants, not lawyers. What this control asks for is a management process: knowing what you must comply with, deciding how, and checking. Interpreting a specific law for your situation is a job for qualified legal advice.

What the control requires

Annex A control 5.31 of ISO 27001:2022 states that legal, statutory, regulatory and contractual requirements relevant to information security and the organization’s approach to meet these requirements shall be identified, documented and kept up to date.

The key elements:

  • Legal, statutory, regulatory and contractual requirements - laws, rules from regulators, and promises made in contracts and customer agreements
  • Relevant to information security - requirements about confidentiality, integrity, availability, privacy, record keeping, reporting and similar topics
  • The organization’s approach to meet these requirements - not only the list, but how you comply: the controls, owners and processes
  • Identified, documented and kept up to date - a register that is created, written down and maintained as laws and contracts change

A.5.31 is a preventive control in the attributes of ISO/IEC 27002:2022. Annex A states the control; ISO 27002 gives guidance, including involving specialists, considering the jurisdictions where you operate and where data travels, and covering topics such as cryptography rules, records and privacy. The requirement ties directly to clause 4.2, since legal and contractual obligations are among the needs and expectations of understanding the needs and expectations of interested parties.

Build the register

Create a simple table. Each row is a requirement, and the columns say where it comes from, what it demands in practice, who owns compliance, which controls address it and when it was last reviewed. Sources to consider include:

  • Data protection and privacy laws in every place you have staff, customers or data subjects. Our post on ISO 27001 and GDPR shows where the standard and that regulation overlap, and data privacy frameworks gives wider context.
  • Sector rules and regulators, for example in finance, health, critical infrastructure or telecoms. Directives such as NIS2 may apply to some organizations, depending on sector and size; see our overview of NIS2 and confirm applicability with legal advice.
  • Employment and monitoring law, which affects background checks, device monitoring and what you can do with staff data.
  • Contractual obligations with customers, partners and suppliers: security schedules, audit rights, incident notification clauses and data location promises.
  • Cryptography and export rules, which differ between jurisdictions.
  • Industry standards you have committed to, such as payment card rules or customer security questionnaires that became contract terms.
  • Insurance conditions, which often require specific controls to be in place.

Do not try to be exhaustive on day one. Start with the obligations that carry real consequences or that customers regularly ask about, and extend the register as you learn.

Mine your contracts

Contracts are the most overlooked source. Sales teams agree to security clauses in the middle of a deal, and the signed document then disappears into a folder. Make a habit of extracting the security obligations from every significant customer agreement: notification windows, encryption requirements, right to audit, subcontractor approval, data return and deletion. Record them in the register or in a linked sheet per customer. Doing this once for your top customers usually reveals a handful of promises that nobody in operations knew about.

For the reverse direction, the obligations you place on suppliers belong in addressing information security within supplier agreements and information security in supplier relationships.

Decide how you comply and who owns it

For each requirement, state in a sentence how you meet it and which control, policy or process does the work. A data breach notification duty might point to your incident procedure, a retention rule to your record handling, and a customer’s encryption clause to your cryptography standard. Give each row an owner who is responsible for watching changes. Often that owner is not in the security team: HR owns employment law items, finance owns financial record keeping, and the privacy lead owns data protection.

Where you cannot comply fully, record it. A known gap with an owner, a plan and management’s acknowledgement is far better than an unspoken one. Feed the gaps into your information security risk assessment and your Statement of Applicability, where legal requirements are one of the reasons a control is selected, as described in our post on the ISO 27001 Statement of Applicability.

Keep it up to date

Laws and contracts change, and so do your operations. Set a rhythm: review the register at least annually, whenever you enter a new market or launch a new product, and when a significant contract is signed or renewed. Decide how you will hear about changes: a legal adviser’s updates, regulator newsletters, industry bodies, or the groups described in contact with special interest groups. Each review should leave a dated trace. Version your documents as set out in control of documented information, so you can show what the register said at any point in the past.

A.5.1 connection. Policies for information security should reflect the legal and contractual requirements identified here.

A.5.5 connection. Contact with authorities supports knowing and meeting regulator expectations.

A.5.19 and A.5.20 connection. Information security in supplier relationships and addressing information security within supplier agreements pass requirements down to your suppliers.

A.5.12 connection. Classification of information often has a legal driver, such as personal data or regulated records.

Clause 4.1 and 4.2 connection. Understanding the organization and its context and understanding the needs and expectations of interested parties require you to understand external issues and stakeholder requirements, which include legal ones.

Clause 9.2 connection. Internal audit can check compliance with the register. Later in the series, compliance with policies, rules and standards for information security (A.5.36) covers the checking in more detail.

Forward reference. The next controls take up specific legal topics: intellectual property rights (A.5.32), protection of records (A.5.33) and privacy and protection of personal identifiable information (A.5.34).

What auditors check

A maintained register. Auditors look for a documented list of legal, regulatory and contractual requirements with owners and review dates.

Coverage. They test whether the list reflects reality, for instance by asking about the jurisdictions you operate in or the customers you serve, then checking that matching obligations appear.

Approach to compliance. For sampled requirements, they ask how you meet them and look for the underlying evidence.

Contract awareness. They may take a customer contract and ask whether its security clauses are known to the people who must deliver them.

Currency. Review records and evidence of how you track changes show the register is not a one-off exercise.

Handling of gaps. They look for risks and actions linked to requirements you do not yet fully meet.

Common mistakes to avoid

A list copied from the internet. A generic legal list that does not reflect your actual customers and locations proves little.

Only IT owns it. Legal and contractual compliance needs input from legal, HR, finance and sales.

Ignoring contracts. Promises in customer agreements are legally binding, and they are the obligations most likely to be forgotten.

Never updating. A register that has not changed in three years probably does not match your business any more.

Confusing certification with compliance. An ISO 27001 certificate does not by itself demonstrate compliance with any particular law. Treat them as related but separate.

Guessing at legal meaning. Where interpretation matters, involve qualified legal advice rather than relying on a consultant’s or engineer’s reading.

How 27kay can help

We help organizations build a practical requirements register that connects each obligation to the controls and people responsible for it. As part of ISO 27001 implementation, we work alongside your legal advisers, extract security terms from key contracts and prepare the evidence an auditor will want. For the full picture, see our ISO 27001 knowledge hub.

If your biggest customer asked tomorrow which security promises you made in their contract, could you answer from a single list? Get in touch - we will help you build that list and keep it honest.