UnixTime

Research Note

ISO27001-A.5.31 Legal, Statutory, Regulatory and Contractual Requirements

The organization must know which legal, statutory, regulatory, and contractual information security requirements apply, document them, keep them current, and define how it will meet them.

On this page

Control Purpose

The organization must know which legal, statutory, regulatory, and contractual information security requirements apply, document them, keep them current, and define how it will meet them.

Use A.5.31 Legal, Statutory, Regulatory and Contractual Requirements for the detailed requirement, implementation guidance, audit checks, evidence expectations, and related ISO 27005 context.

Risk Logic

01 Obligation or IP asset
02 Unclear requirement or licence
03 Non-compliance
04 Legal/contractual impact
05 Legal, Statutory, Regulatory and Contractual Requirements
06 Evidence
07 Audit

No published risk scenario is linked to this control yet. Create or link a risk note under the risk knowledge base before treating this control as fully mapped.

Detailed Note

Evidence Required

Map this control to compliance risk, legal impact, contractual exposure, supplier risk, jurisdictional risk, and residual risk review.

Software Architecture Mapping

Relevant objects: control, compliance_requirement, contract, asset, software_license, evidence, audit_question, finding, corrective_action.

Audit Questions

  • AQ-ISO27001-A.5.31 Audit Question
  • How does the organization prove ISO27001-A.5.31 is implemented and operating?
  • What evidence shows ownership, review cadence, exceptions, and corrective action?
  • Which failed condition would create an audit finding for this control?
  • Iso27001
  • ISO27002
  • Annex a
  • Control
  • Compliance

Note Metadata

Aliases: ISO27001-A.5.31

Source: 06-Control-Knowledge-Base/ISO27001-A.5.31-Legal-Statutory-Regulatory-and-Contractual-Requirements.md

Control dependency map

How this control connects to work products

Generated from the static research graph. It shows navigation and evidence dependencies; it is not an audit conclusion.

4

links

01

Requirement context

Primary control text, framework notes, or adjacent controls this note points to.

02

Evidence required

Evidence packs and proof records that support auditability.

03

Audit checks

Audit questions, checklists, or review material connected to the control.

Graph-sourced resources

Templates and evidence

Implementer templates

Working artifacts for control owners and operators.

Auditor evidence packs

Evidence collections and audit-facing verification material.