NormaglobeDigital Compliance

Common controls map

A control implemented once can satisfy several laws and standards. Choose the frameworks that apply to you (GDPR, NIS2, DORA, CRA, AI Act, ISO/IEC 27001, NIST CSF, IEC 62443): for each control, see the matching articles and clauses and the evidence to prepare.

EU laws
Standards
17 controls cover 60 requirements across 4 frameworks

Matrix

ControlGDPRNIS2CRAISO 27001
Governance and management accountability4 of 4Art. 5(2), 24Art. 20Art. 13Cl. 5; A.5.1–A.5.4
Risk assessment and treatment4 of 4Art. 32(2), 35Art. 21(1), 21(2)(a)Art. 13(2)–(3)Cl. 6.1.2, 6.1.3, 8.2–8.3
Inventory of assets, data and components4 of 4Art. 30Art. 21(2)(i)All. I, Parte II(1)A.5.9–A.5.12
Supply chain security4 of 4Art. 28Art. 21(2)(d), 21(3), 22Art. 13(5)A.5.19–A.5.23
Access control and strong authentication4 of 4Art. 32(1)(b)Art. 21(2)(i), (j)All. I, Parte I(2)(d)A.5.15–A.5.18, A.8.2–A.8.5
Cryptography and data protection4 of 4Art. 32(1)(a), 34(3)(a)Art. 21(2)(h)All. I, Parte I(2)(e)–(f)A.8.24
Network security and segmentation3 of 4—Art. 21(1), 21(2)(e)All. I, Parte I(2)(j)A.8.20–A.8.22
Security and privacy by design4 of 4Art. 25Art. 21(2)(e)All. I, Parte IA.8.25–A.8.32
Vulnerability and patch management3 of 4—Art. 21(2)(e), 12All. I, Parte II; art. 13(8)A.8.8
Logging and monitoring3 of 4—Art. 21(2)(b)All. I, Parte I(2)(l)A.8.15–A.8.16
Incident management and reporting4 of 4Art. 33–34Art. 23Art. 14A.5.24–A.5.28, A.6.8
Business continuity and backup4 of 4Art. 32(1)(b)–(c)Art. 21(2)(c)All. I, Parte I(2)(h)A.5.29–A.5.30, A.8.13–A.8.14
Testing, audits and conformity assessment4 of 4Art. 32(1)(d)Art. 21(2)(f), 32–33Art. 32; All. VIIICl. 9; A.5.35–A.5.36
Training and awareness3 of 4Art. 32(4), 39(1)(b)Art. 20(2), 21(2)(g)—Cl. 7.2–7.3; A.6.3
Technical documentation and records3 of 4Art. 5(2), 30—Art. 13(12), 28, 31; All. V, VIICl. 7.5
User information and transparency2 of 4Art. 12–14—Art. 13(18)–(19); All. II—
Data minimisation, quality and deletion3 of 4Art. 5(1)(c)–(e), 17—All. I, Parte I(2)(g), (m)A.8.10–A.8.12

Cells show the reference article or clause; “—” means the framework does not specifically require it.

Control details

Governance and management accountability

What to do: Senior management approves the security and data protection policy, assigns roles and responsibilities, oversees implementation and is accountable for it.

Evidence: Approved policy, organisation chart with roles (CISO, DPO), board minutes

  • GDPRArt. 5(2), 24– Accountability principle
  • NIS2Art. 20– Management bodies approve the measures and are liable
  • CRAArt. 13– Manufacturer obligations
  • ISO 27001Cl. 5; A.5.1–A.5.4

Risk assessment and treatment

What to do: Documented method to identify, assess and treat risks to systems, data and people, repeated at regular intervals and on every significant change.

Evidence: Risk register, treatment plan, DPIAs, product risk assessment

  • GDPRArt. 32(2), 35– Risks to data subjects; DPIA for high-risk processing
  • NIS2Art. 21(1), 21(2)(a)
  • CRAArt. 13(2)–(3)– Documented cybersecurity risk assessment of the product
  • ISO 27001Cl. 6.1.2, 6.1.3, 8.2–8.3

Inventory of assets, data and components

What to do: Up-to-date inventory of systems, applications, data and processing activities; for products, a software bill of materials (SBOM).

Evidence: CMDB or inventory, record of processing activities, SBOM per release

  • GDPRArt. 30– Record of processing activities
  • NIS2Art. 21(2)(i)– Asset management
  • CRAAll. I, Parte II(1)– Mandatory SBOM, at least for top-level dependencies
  • ISO 27001A.5.9–A.5.12

Supply chain security

What to do: Vendor assessment before and during the relationship, contractual security and privacy requirements, control of third-party components.

Evidence: Due diligence questionnaires, contracts and DPAs, ICT third-party register, exit plans

  • GDPRArt. 28– Processor contract
  • NIS2Art. 21(2)(d), 21(3), 22
  • CRAArt. 13(5)– Due diligence on third-party components, including open source
  • ISO 27001A.5.19–A.5.23

Access control and strong authentication

What to do: Least-privilege access, identity management, multi-factor authentication for critical access, periodic review of accounts.

Evidence: Access policy, account review reports, MFA configuration

  • GDPRArt. 32(1)(b)– Confidentiality of systems and services
  • NIS2Art. 21(2)(i), (j)– Point (j) requires multi-factor authentication
  • CRAAll. I, Parte I(2)(d)– Protection from unauthorised access
  • ISO 27001A.5.15–A.5.18, A.8.2–A.8.5

Cryptography and data protection

What to do: Encryption of data at rest and in transit with current algorithms, key management, integrity protection.

Evidence: Cryptographic policy, key and certificate inventory, TLS configurations

  • GDPRArt. 32(1)(a), 34(3)(a)– Encryption may exempt from notifying data subjects
  • NIS2Art. 21(2)(h)
  • CRAAll. I, Parte I(2)(e)–(f)
  • ISO 27001A.8.24

Network security and segmentation

What to do: Network separation by risk level, traffic filtering, reduction of the attack surface and exposed services.

Evidence: Network diagram with zones, firewall rules, scans of exposed services

  • NIS2Art. 21(1), 21(2)(e)
  • CRAAll. I, Parte I(2)(j)– Limit attack surfaces, including external interfaces
  • ISO 27001A.8.20–A.8.22

Security and privacy by design

What to do: Security and privacy requirements in the development and acquisition lifecycle, secure-by-default configurations, change management.

Evidence: Secure development process, code reviews, threat models, change log

  • GDPRArt. 25– Data protection by design and by default
  • NIS2Art. 21(2)(e)
  • CRAAll. I, Parte I– Essential requirements, including secure by default
  • ISO 27001A.8.25–A.8.32

Vulnerability and patch management

What to do: Vulnerability monitoring, coordinated disclosure, timely fixes and security updates throughout the support period.

Evidence: Coordinated disclosure policy, remediation SLAs, security advisories, patch history

  • NIS2Art. 21(2)(e), 12– Vulnerability handling and disclosure
  • CRAAll. I, Parte II; art. 13(8)– Free updates for the support period, normally at least 5 years
  • ISO 27001A.8.8

Logging and monitoring

What to do: Collection and retention of relevant logs, monitoring to detect anomalies and attacks, protection of logs from tampering.

Evidence: Logging policy, SIEM use cases, retention periods

  • NIS2Art. 21(2)(b)
  • CRAAll. I, Parte I(2)(l)
  • ISO 27001A.8.15–A.8.16

Incident management and reporting

What to do: Single procedure to detect, classify, handle and report incidents, covering the different reporting deadlines of each law.

Evidence: Response plan, classification matrix, incident log, notification templates

  • GDPRArt. 33–34– Authority within 72 hours
  • NIS2Art. 23– Early warning 24 h, notification 72 h, final report 1 month
  • CRAArt. 14– Exploited vulnerabilities and severe incidents: 24 h, 72 h; from 11/9/2026
  • ISO 27001A.5.24–A.5.28, A.6.8

Business continuity and backup

What to do: Continuity and recovery plans, tested backups, defined recovery objectives, crisis management.

Evidence: BIA, BC/DR plans, restore test reports

  • GDPRArt. 32(1)(b)–(c)– Availability and timely restoration of data
  • NIS2Art. 21(2)(c)
  • CRAAll. I, Parte I(2)(h)– Availability of essential functions
  • ISO 27001A.5.29–A.5.30, A.8.13–A.8.14

Testing, audits and conformity assessment

What to do: Periodic verification of the effectiveness of the measures: audits, penetration tests, conformity assessment of products before placing them on the market.

Evidence: Audit programme, pentest reports, EU declaration of conformity, certificates

  • GDPRArt. 32(1)(d)
  • NIS2Art. 21(2)(f), 32–33– Supervision of entities by authorities
  • CRAArt. 32; All. VIII– Conformity assessment procedures
  • ISO 27001Cl. 9; A.5.35–A.5.36

Training and awareness

What to do: Periodic, role-appropriate training of staff and management on security, data protection and AI use.

Evidence: Training plan, attendance records, simulated phishing campaigns

  • GDPRArt. 32(4), 39(1)(b)
  • NIS2Art. 20(2), 21(2)(g)– Mandatory training also for management bodies
  • ISO 27001Cl. 7.2–7.3; A.6.3

Technical documentation and records

What to do: Documentation demonstrating compliance, kept and updated: records, product technical documentation, declarations.

Evidence: Technical file, declaration of conformity, records, versioned policies

  • GDPRArt. 5(2), 30
  • CRAArt. 13(12), 28, 31; All. V, VII– Kept for 10 years or the support period, if longer
  • ISO 27001Cl. 7.5

User information and transparency

What to do: Clear information for data subjects and users: privacy notices, product security instructions, transparency on AI use and generated data.

Evidence: Notices, instructions for use, labels and information sheets, declared support period

  • GDPRArt. 12–14
  • CRAArt. 13(18)–(19); All. II– Instructions and support period given to the user

Data minimisation, quality and deletion

What to do: Collect only necessary data, ensure its quality, keep it no longer than necessary and delete it securely.

Evidence: Retention policy, deletion procedures, dataset documentation

  • GDPRArt. 5(1)(c)–(e), 17
  • CRAAll. I, Parte I(2)(g), (m)– Minimisation and secure deletion of data by the user
  • ISO 27001A.8.10–A.8.12

Frameworks covered

GDPR
Regulation (EU) 2016/679 · Anyone processing personal data
NIS2
Directive (EU) 2022/2555 · Essential and important entities
DORA
Regulation (EU) 2022/2554 · Financial entities and critical ICT providers
CRA
Regulation (EU) 2024/2847 · Manufacturers of products with digital elements
AI Act
Regulation (EU) 2024/1689 · Providers and deployers of AI systems
ISO 27001
ISO/IEC 27001:2022 · Information security management system (certifiable)
NIST CSF
NIST Cybersecurity Framework 2.0 · Voluntary framework, widespread in the US
IEC 62443
IEC 62443 series · Industrial and IoT systems and components

The map is indicative: references are summarised and a requirement may be broader or narrower than the control. Always check the official texts and the delegated and implementing acts. Updated November 2026.