ISO 27002:2022
Organizational controls – ISO 27002:2022

ISO 27002:2022 5.31: Legal, statutory, regulatory and contractual requirements

The organization is to identify, record and keep current the requirements (legal, statutory, regulatory and contractual) bearing on information security, together with how it intends to meet them. Purpose: comply with the legal, regulatory and contractual obligations that concern information security. Guidance: external requirements are to be considered when writing security policies and procedures, when designing, implementing or changing controls, when classifying information and assets to set internal or supplier requirements, in risk assessment and treatment, in defining security processes, roles and responsibilities, and in setting contractual requirements for suppliers and the scope of what they supply. On legislation and regulation, the organization should identify all laws and regulations relevant to its security for its type of business; account for every relevant country where it operates, where products and services it uses come from, or where information crosses borders; review the list regularly to catch changes and new laws; and define and record the processes and individual responsibilities for meeting them. Cryptography often carries specific legal rules, so consider restrictions on importing or exporting hardware and software that perform, or are designed to have added, cryptographic functions; restrictions on using cryptography; mandatory or discretionary access by national authorities to encrypted information; and whether digital signatures, seals and certificates are legally valid; legal advice is recommended, especially when encrypted information or tools move across borders. Contractual security requirements include those in client contracts, supplier contracts (5.20) and insurance contracts.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 117 controls across 36 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

ISO 27701:2019 · 19 controls

  • 5.1 General
  • 5.2.2 Understanding the needs and expectations of interested parties
  • 6.15 Compliance
  • 6.15.1 Compliance with legal and contractual requirements
  • 7.2 Conditions for collection and processing
  • 7.2.2 Identify lawful basis
  • 7.2.7 Joint PII controller
  • 7.3.1 Determining and fulfilling obligations to PII principals
  • 7.3.10 Automated decision making
  • 7.5.1 Identify basis for PII transfer between jurisdictions
  • 7.5.2 Countries and international organizations to which PII can be transferred
  • 8.2 Conditions for collection and processing
  • 8.2.2 Organization’s purposes
  • 8.2.4 Infringing instruction
  • 8.3.1 Obligations to PII principals
  • 8.5.1 Basis for PII transfer between jurisdictions
  • 8.5.2 Countries and international organizations to which PII can be transferred
  • 8.5.4 Notification of PII disclosure requests
  • 8.5.5 Legally binding PII disclosures

ISO/IEC 42001:2023 · 12 controls

  • 4.2 Understanding the needs and expectations of interested parties
  • 6.1.2 AI risk assessment
  • 6.1.4 AI system impact assessment
  • 7.5.1 General
  • A.2.3 Alignment with other organizational policies
  • A.5 Assessing impacts of AI systems
  • A.5.2 AI system impact assessment process
  • A.5.4 Assessing AI system impact on individuals or groups of individuals
  • A.7.3 Acquisition of data
  • A.8 Information for interested parties of AI systems
  • A.8.5 Information for interested parties
  • A.9.3 Objectives for responsible use of AI system

NIST SP 800-53 Rev 5 · 8 controls

ISO 22301:2019 · 6 controls

  • 4.1 Understanding the organization and its context
  • 4.2 Understanding the needs and expectations of interested parties
  • 4.2.1 General
  • 4.2.2 Legal and regulatory requirements
  • 6.1 Actions to address risks and opportunities
  • 8.3.1 General

SOC 2 · 6 controls

  • SOC2-CC2.3 CC2.3 Communication with external parties about internal control (COSO principle 15)
  • SOC2-P4.2 P4.2 Retaining personal information
  • SOC2-P6.1 P6.1 Disclosure to third parties with consent
  • SOC2-P6.4 P6.4 Privacy commitments from vendors and third parties
  • SOC2-P6.6 P6.6 Notifying breaches and incidents
  • SOC2-P8.1 P8.1 Inquiries, complaints, disputes and compliance monitoring

FedRAMP High · 5 controls

  • CM-10 Software Usage Restrictions
  • IA-8(2) Identification and Authentication (Non-organizational Users) | Acceptance of External Authenticators (IA-8(2))
  • PL-10 Baseline Selection. Select a control baseline for the system
  • SA-4(10) Use of Approved PIV Products
  • SA-9(5) External System Services | Processing, Storage, and Service Location (SA-9(5))

FedRAMP Moderate · 5 controls

  • CM-10 Software Usage Restrictions
  • IA-8(2) Identification and Authentication (Non-organizational Users) | Acceptance of External Authenticators (IA-8(2))
  • PL-10 Baseline Selection. Select a control baseline for the system
  • SA-4(10) Use of Approved PIV Products
  • SA-9(5) External System Services | Processing, Storage, and Service Location (SA-9(5))

PCI DSS 4.0 · 5 controls

  • 11.4.7 11.4.7 Multi-tenant providers support customer penetration testing
  • 12.1.1 12.1.1 Overall information security policy established and disseminated
  • 12.1.2 12.1.2 Security policy reviewed annually and updated as needed
  • 12.4.1 12.4.1 Executive responsibility for a PCI DSS compliance program
  • 12.8.2 12.8.2 TPSP contracts acknowledging account data responsibility

NIS2 Directive · 4 controls

  • Art.24 Use certified ICT products, services and processes where the Member State requires it
  • Art.26 Establish which Member State has jurisdiction, and designate a Union representative if not established in the Union
  • Art.27.2 Submit the ENISA registry information required of digital infrastructure and digital service providers
  • Art.3.4 Submit and maintain entity registration information with the competent authority
  • 4.3 4.3 Legal, regulatory, and contractual requirements
  • 5.2.3 5.2.3 Legal counsel
  • 8.7 8.7 The importance of legal oversight

C5 (Germany) · 3 controls

  • C5-COM-01 Identification of applicable legal, regulatory, self-imposed or contractual requirements
  • C5-INQ-01 Legal Assessment of Investigative Inquiries
  • C5-INQ-03 Conditions for Access to or Disclosure of Data in Investigation Requests

DORA · 3 controls

HIPAA Security Rule · 3 controls

MTCS (Singapore) · 3 controls

  • 10.2 Compliance with regulatory and contractual requirements
  • 10.5 Use of compliant cryptographic controls
  • A.2 Disclosure: Compliance
  • CPS230-9 Management of the Full Range of Operational Risks
  • CPS230-P12 Key Principles for Operational Risk, Resilience and Service Providers
  • SEC01-BP03 Identify and validate control objectives
  • SEC07-BP01 Understand your data classification scheme
  • ASBv3-DP-5 Use customer-managed key option in data at rest encryption when required
  • ASBv3-LT-6 Configure log storage retention

ISO 27001:2022 · 2 controls

  • 5.20 Addressing information security within supplier agreements
  • 5.31 Legal, statutory, regulatory and contractual requirements
  • NIST-CSF-GV.OC-01 The organizational mission is understood and informs cybersecurity risk management
  • NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
  • 0002 0002 Comply with all Protective Security Directions
  • 0082 0082 Safeguard foreign classified information per the agreement
  • MTSA-101.105 Applicability Determination
  • MTSA-NVIC-02-24 Alignment with Updated USCG Cyber Policy
  • A.4.1 A.4.1 Procedures for legal, regulatory and other requirements

APPI · 1 control

  • APPI-A17 Specification of the Purpose of Use

APRA CPS 234 · 1 control

  • CPS234-36 APRA Notification of Material Control Weakness within 10 Business Days
  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data
  • ISM-1478 Oversight of cyber security program and compliance

CIS Controls v8 · 1 control

GDPR · 1 control

  • 03.14.08 Information Management and Retention
  • NRC7354-1 Cybersecurity Plan, Programme Establishment, and NRC Submission
  • REG Keep an inventory of regulatory requirements and standards developments

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Organizational controls – ISO 27002:2022

You are reading one control. How much of ISO 27002:2022 have you already done?

ISO 27002:2022 5.31 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27002:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27002:2022 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 180 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 117 it maps to, and the evidence behind each claim, over MCP and REST.