Zum Hauptinhalt springen
Starter Kit · Register

Legal Compliance Register

Updated on 2 min Reviewed by: Cenedril-Redaktion
A.5.31 ISO 27001NIS2 Art. 21

The legal compliance register captures all legal, regulatory and contractual requirements relevant to your ISMS. It answers one question: which external obligations does your organisation have — and are you meeting them?

ISO 27001 A.5.31 (Legal, Statutory, Regulatory and Contractual Requirements) requires that relevant requirements are identified, documented and reviewed at planned intervals. Without a maintained legal register, you cannot demonstrate in an audit that you know your regulatory landscape.

What does it contain?

Each row represents one external requirement. The columns:

  • ID / Regulation / Article — unique identifier, name of the law or contract and relevant section
  • Requirement — summary of the concrete obligation
  • Applicability / Obligation Type — which data, systems or processes the requirement applies to and whether it is organisational or technical
  • Responsible — accountable person (e.g. DPO, ISO, legal department)
  • Evidence / Status / Next Review — reference to proof, current compliance status and next review date

How to use it

Initial population: Start with the obvious regulations (GDPR, national data protection acts, NIS2 if applicable) and then add contractual obligations from customer and supplier agreements. For each entry, define a responsible person and link the evidence.

Ongoing maintenance: When laws change, new contracts are signed or the business expands into new markets, update the register. The responsible person reviews the compliance status and documents any required action.

Audit preparation: Auditors sample entries and check whether the stated evidence actually exists and is current. A complete register with well-maintained evidence references accelerates this process considerably.

Register Template
IDRegulationArticle / SectionRequirementApplicabilityObligation TypeResponsibleEvidenceStatusNext Review
LR-001GDPR (EU 2016/679)Art. 5Principles of processing (lawfulness fairness transparency purpose limitation data minimisation accuracy storage limitation integrity confidentiality accountability)All personal data processingOrganisationalDPOData Protection Policy + RoPACompliant2026-12-31
LR-002GDPRArt. 6Lawful basis required for each processing activityAll personal data processingOrganisationalDPOLegal basis documented in RoPACompliant2026-12-31
LR-003GDPRArt. 13-14Information to data subjects at collectionCustomer and employee dataOrganisationalDPOPrivacy notice on website + HR handbookCompliant2026-12-31
LR-004GDPRArt. 15-22Data subject rights (access rectification erasure restriction portability objection)All personal dataOrganisationalDPOSAR procedure + logCompliant2026-12-31
LR-005GDPRArt. 24 25Responsibility of controller + privacy by designAll processingTechnical + OrganisationalDPODPIA procedure + control implementationCompliant2026-12-31
LR-006GDPRArt. 28Processor contracts (DPA) requiredAll processorsContractualDPOData processing agreements with all processorsCompliant2026-06-30
LR-007GDPRArt. 30Records of processing activitiesOrganisation (>250 or high risk)OrganisationalDPORoPA (records of processing)Compliant2026-12-31
LR-008GDPRArt. 32Security of processing (appropriate technical and organisational measures)All processingTechnical + OrganisationalISOISMS controls + TOM documentCompliant2026-12-31
LR-009GDPRArt. 33Breach notification to supervisory authority within 72 hoursAll processingProceduralDPOIncident Response Plan breach section + logCompliant2026-12-31
LR-010GDPRArt. 34Breach notification to affected data subjects (if high risk)All processingProceduralDPOIRP + communication templatesCompliant2026-12-31
LR-011GDPRArt. 35Data protection impact assessment required for high-risk processingNew processing activitiesProceduralDPODPIA procedure + completed DPIAsCompliant2026-12-31
LR-012GDPRArt. 37-39Designation and tasks of data protection officerOrganisationOrganisationalTop managementDPO appointment letterCompliant2027-01-31
LR-013GDPRArt. 44-49Transfers to third countries require legal basis (SCC adequacy BCR)Any international transferContractualDPOTransfer impact assessments + SCCsCompliant2026-12-31
LR-014NIS2 (EU 2022/2555)Art. 20Governance: management bodies must approve and supervise risk measures and take trainingEssential or important entityOrganisationalTop managementManagement training record + approved ISMS docsCompliant2026-12-31
LR-015NIS2Art. 21(1)Appropriate and proportionate technical operational and organisational measuresEssential or important entityTechnical + OrganisationalISOISMS + SoACompliant2026-12-31
LR-016NIS2Art. 21(2)(a)Risk analysis and information system security policiesEntityOrganisationalISORisk Management Policy + Information Security PolicyCompliant2026-12-31
LR-017NIS2Art. 21(2)(b)Incident handlingEntityProceduralISOIncident Response PlanCompliant2026-12-31
LR-018NIS2Art. 21(2)(c)Business continuity (backup management disaster recovery crisis management)EntityProceduralBCM LeadBCP + DRP + crisis commsCompliant2026-12-31
LR-019NIS2Art. 21(2)(d)Supply chain security including supplier and service provider relationshipsEntityOrganisationalProcurementSupplier Security Policy + registerCompliant2026-12-31
LR-020NIS2Art. 21(2)(e)Security in network and information systems acquisition development and maintenance including vulnerability handling and disclosureEntityTechnicalIT Operations LeadSecure Development + Vuln Mgmt procedureCompliant2026-12-31
LR-021NIS2Art. 21(2)(f)Policies and procedures to assess effectiveness of cybersecurity risk measuresEntityOrganisationalISOInternal audit + management reviewCompliant2026-12-31
LR-022NIS2Art. 21(2)(g)Basic cyber hygiene practices and cybersecurity trainingEntityOrganisationalISOAwareness training recordsCompliant2026-12-31
LR-023NIS2Art. 21(2)(h)Policies and procedures on use of cryptography and where appropriate encryptionEntityTechnicalISOCryptography PolicyCompliant2026-12-31
LR-024NIS2Art. 21(2)(i)Human resources security access control policies and asset managementEntityOrganisationalHR + ISOHR Security + Access Control + Asset MgmtCompliant2026-12-31
LR-025NIS2Art. 21(2)(j)Use of MFA or continuous auth solutions secured voice/video/text communications and secured emergency communicationsEntityTechnicalIT Operations LeadMFA rollout + secure commsPartially compliant2026-06-30
LR-026NIS2Art. 23Early warning (24h) incident notification (72h) intermediate report final report (1 month)Entity on significant incidentsProceduralISOIRP notification workflowCompliant2026-12-31
LR-027NIS2Art. 27Registration with competent authorityEntityOrganisationalISORegistration confirmationCompliant2027-01-31

Sources

ISO 27001 Controls Covered

A.5.31 Legal, statutory, regulatory and contractual requirements

Frequently asked questions

Which laws belong in the register?

Every law, regulation and contractual obligation that affects your information security. Typical entries: GDPR, national data protection acts, NIS2 (where applicable), sector-specific regulation (e.g. DORA for financial services), NDAs with customers and supplier contracts with security clauses.

How often should the register be updated?

At least annually and whenever triggered by events — new legislation, contract changes or business activity in new jurisdictions. The CSV template includes a Next Review column so you do not miss the next check.

Do I need to quote the exact legal text?

In the register, a summary of the requirement plus a reference to the relevant article or section is sufficient. Archive full legal texts separately (or link to them). Auditors want to see that you understood the requirement and assigned a responsible person.