Law / Frameworks / Crosswalk / NIST Privacy Framework to ENISA NIS2 guidance

The NIST Privacy Framework, mapped to the ENISA NIS2 Technical Implementation Guidance

12 of NIST Privacy Framework's controls connect to 19 of ENISA NIS2 guidance's through 176 laws in 91 jurisdictions. Two controls connect when the same duties, in at least 2 laws we track, reach both. The connections are our own reading of the law; no framework publisher has reviewed or endorsed them.

From
NIST Privacy Framework, version 1.0, January 2020, National Institute of Standards and Technology
To
ENISA NIS2 Technical Implementation Guidance, version 1.0, June 2025, with mapping table version 1.2, European Union Agency for Cybersecurity (ENISA)
See also
ENISA NIS2 guidance to NIST Privacy Framework, the other way · every pair in the crosswalk · law library as of

Download this mapping, with every law behind each connection: nist-privacy-framework--enisa-nis2-guidance.csv · nist-privacy-framework--enisa-nis2-guidance.json

NIST Privacy FrameworkENISA NIS2 guidanceLawsJurisdictionsWhere the laws stand
ID.IM-P1Systems/products/services that process data are inventoried. 1.1Policy on the security of network and information systems 5 4 5 in force
The 5 laws behind ID.IM-P1 and 1.1
1.2Roles, responsibilities and authorities 5 4 5 in force
The 5 laws behind ID.IM-P1 and 1.2
2.2Compliance monitoring 5 4 5 in force
The 5 laws behind ID.IM-P1 and 2.2
3.2Monitoring and logging 5 4 5 in force
The 5 laws behind ID.IM-P1 and 3.2
12.4Asset inventory 5 4 5 in force
The 5 laws behind ID.IM-P1 and 12.4
CT.DM-P5Data are destroyed according to policy. 1.1Policy on the security of network and information systems 9 9 9 in force
The 9 laws behind CT.DM-P5 and 1.1
3.2Monitoring and logging 9 9 9 in force
The 9 laws behind CT.DM-P5 and 3.2
4.2Backup and redundancy management 8 8 8 in force
The 8 laws behind CT.DM-P5 and 4.2
12.2Handling of assets 8 8 8 in force
The 8 laws behind CT.DM-P5 and 12.2
CT.DM-P8Audit/log records are determined, documented, implemented, and reviewed in accordance... 1.1Policy on the security of network and information systems 5 4 4 in force, 1 not yet in force
The 5 laws behind CT.DM-P8 and 1.1
3.2Monitoring and logging 5 4 4 in force, 1 not yet in force
The 5 laws behind CT.DM-P8 and 3.2
1.2Roles, responsibilities and authorities 4 3 3 in force, 1 not yet in force
The 4 laws behind CT.DM-P8 and 1.2
2.2Compliance monitoring 4 3 3 in force, 1 not yet in force
The 4 laws behind CT.DM-P8 and 2.2
12.4Asset inventory 4 3 3 in force, 1 not yet in force
The 4 laws behind CT.DM-P8 and 12.4
CM.AW-P7Impacted individuals and organizations are notified about a privacy breach or event. 3.1Incident handling policy 38 30 34 in force, 4 proposed
The 38 laws behind CM.AW-P7 and 3.1

and 28 more, every one in the free file.

3.4Event assessment and classification 36 30 32 in force, 4 proposed
The 36 laws behind CM.AW-P7 and 3.4

and 26 more, every one in the free file.

3.5Incident response 36 30 32 in force, 4 proposed
The 36 laws behind CM.AW-P7 and 3.5

and 26 more, every one in the free file.

3.6Post-incident reviews 35 29 31 in force, 4 proposed
The 35 laws behind CM.AW-P7 and 3.6

and 25 more, every one in the free file.

4.3Crisis management 35 29 31 in force, 4 proposed
The 35 laws behind CM.AW-P7 and 4.3

and 25 more, every one in the free file.

6.10Vulnerability handling and disclosure 5 5 5 in force
The 5 laws behind CM.AW-P7 and 6.10
2.1Risk management framework 2 2 2 in force
The 2 laws behind CM.AW-P7 and 2.1
4.1Business continuity and disaster recovery plan 2 2 2 in force
The 2 laws behind CM.AW-P7 and 4.1
6.2Secure development life cycle 2 2 2 in force
The 2 laws behind CM.AW-P7 and 6.2
6.5Security testing 2 2 2 in force
The 2 laws behind CM.AW-P7 and 6.5
9.1Cryptography 2 2 2 in force
The 2 laws behind CM.AW-P7 and 9.1
11.2Management of access rights 2 2 2 in force
The 2 laws behind CM.AW-P7 and 11.2
PR.PO-P7Response plans (Incident Response and Business Continuity) and recovery plans... 1.1Policy on the security of network and information systems 50 36 47 in force, 2 not yet in force, 1 proposed
The 50 laws behind PR.PO-P7 and 1.1

and 40 more, every one in the free file.

1.2Roles, responsibilities and authorities 50 36 47 in force, 2 not yet in force, 1 proposed
The 50 laws behind PR.PO-P7 and 1.2

and 40 more, every one in the free file.

2.2Compliance monitoring 50 36 47 in force, 2 not yet in force, 1 proposed
The 50 laws behind PR.PO-P7 and 2.2

and 40 more, every one in the free file.

3.2Monitoring and logging 50 36 47 in force, 2 not yet in force, 1 proposed
The 50 laws behind PR.PO-P7 and 3.2

and 40 more, every one in the free file.

12.4Asset inventory 50 36 47 in force, 2 not yet in force, 1 proposed
The 50 laws behind PR.PO-P7 and 12.4

and 40 more, every one in the free file.

3.1Incident handling policy 32 24 30 in force, 2 not yet in force
The 32 laws behind PR.PO-P7 and 3.1

and 22 more, every one in the free file.

2.1Risk management framework 28 21 27 in force, 1 not yet in force
The 28 laws behind PR.PO-P7 and 2.1

and 18 more, every one in the free file.

4.1Business continuity and disaster recovery plan 28 21 27 in force, 1 not yet in force
The 28 laws behind PR.PO-P7 and 4.1

and 18 more, every one in the free file.

6.2Secure development life cycle 28 21 27 in force, 1 not yet in force
The 28 laws behind PR.PO-P7 and 6.2

and 18 more, every one in the free file.

6.5Security testing 28 21 27 in force, 1 not yet in force
The 28 laws behind PR.PO-P7 and 6.5

and 18 more, every one in the free file.

6.10Vulnerability handling and disclosure 28 21 27 in force, 1 not yet in force
The 28 laws behind PR.PO-P7 and 6.10

and 18 more, every one in the free file.

9.1Cryptography 28 21 27 in force, 1 not yet in force
The 28 laws behind PR.PO-P7 and 9.1

and 18 more, every one in the free file.

11.2Management of access rights 28 21 27 in force, 1 not yet in force
The 28 laws behind PR.PO-P7 and 11.2

and 18 more, every one in the free file.

3.4Event assessment and classification 11 9 9 in force, 2 not yet in force
The 11 laws behind PR.PO-P7 and 3.4

and 1 more, every one in the free file.

3.5Incident response 11 9 9 in force, 2 not yet in force
The 11 laws behind PR.PO-P7 and 3.5

and 1 more, every one in the free file.

3.6Post-incident reviews 11 9 9 in force, 2 not yet in force
The 11 laws behind PR.PO-P7 and 3.6

and 1 more, every one in the free file.

4.3Crisis management 11 9 9 in force, 2 not yet in force
The 11 laws behind PR.PO-P7 and 4.3

and 1 more, every one in the free file.

PR.PO-P8Response and recovery plans are tested. 2.1Risk management framework 6 5 6 in force
The 6 laws behind PR.PO-P8 and 2.1
3.1Incident handling policy 6 5 6 in force
The 6 laws behind PR.PO-P8 and 3.1
4.1Business continuity and disaster recovery plan 6 5 6 in force
The 6 laws behind PR.PO-P8 and 4.1
6.2Secure development life cycle 6 5 6 in force
The 6 laws behind PR.PO-P8 and 6.2
6.5Security testing 6 5 6 in force
The 6 laws behind PR.PO-P8 and 6.5
6.10Vulnerability handling and disclosure 6 5 6 in force
The 6 laws behind PR.PO-P8 and 6.10
9.1Cryptography 6 5 6 in force
The 6 laws behind PR.PO-P8 and 9.1
11.2Management of access rights 6 5 6 in force
The 6 laws behind PR.PO-P8 and 11.2
1.1Policy on the security of network and information systems 2 2 2 in force
The 2 laws behind PR.PO-P8 and 1.1
1.2Roles, responsibilities and authorities 2 2 2 in force
The 2 laws behind PR.PO-P8 and 1.2
2.2Compliance monitoring 2 2 2 in force
The 2 laws behind PR.PO-P8 and 2.2
3.2Monitoring and logging 2 2 2 in force
The 2 laws behind PR.PO-P8 and 3.2
12.4Asset inventory 2 2 2 in force
The 2 laws behind PR.PO-P8 and 12.4
PR.PO-P10A vulnerability management plan is developed and implemented. 6.10Vulnerability handling and disclosure 16 12 14 in force, 2 not yet in force
The 16 laws behind PR.PO-P10 and 6.10

and 6 more, every one in the free file.

3.1Incident handling policy 16 10 14 in force, 2 not yet in force
The 16 laws behind PR.PO-P10 and 3.1

and 6 more, every one in the free file.

2.1Risk management framework 14 10 12 in force, 2 not yet in force
The 14 laws behind PR.PO-P10 and 2.1

and 4 more, every one in the free file.

4.1Business continuity and disaster recovery plan 14 10 12 in force, 2 not yet in force
The 14 laws behind PR.PO-P10 and 4.1

and 4 more, every one in the free file.

6.2Secure development life cycle 14 10 12 in force, 2 not yet in force
The 14 laws behind PR.PO-P10 and 6.2

and 4 more, every one in the free file.

6.5Security testing 14 10 12 in force, 2 not yet in force
The 14 laws behind PR.PO-P10 and 6.5

and 4 more, every one in the free file.

9.1Cryptography 14 10 12 in force, 2 not yet in force
The 14 laws behind PR.PO-P10 and 9.1

and 4 more, every one in the free file.

11.2Management of access rights 14 10 12 in force, 2 not yet in force
The 14 laws behind PR.PO-P10 and 11.2

and 4 more, every one in the free file.

3.5Incident response 5 5 5 in force
The 5 laws behind PR.PO-P10 and 3.5
1.1Policy on the security of network and information systems 2 2 1 in force, 1 not yet in force
The 2 laws behind PR.PO-P10 and 1.1
1.2Roles, responsibilities and authorities 2 2 1 in force, 1 not yet in force
The 2 laws behind PR.PO-P10 and 1.2
2.2Compliance monitoring 2 2 1 in force, 1 not yet in force
The 2 laws behind PR.PO-P10 and 2.2
3.2Monitoring and logging 2 2 1 in force, 1 not yet in force
The 2 laws behind PR.PO-P10 and 3.2
3.4Event assessment and classification 2 2 2 in force
The 2 laws behind PR.PO-P10 and 3.4
3.6Post-incident reviews 2 2 2 in force
The 2 laws behind PR.PO-P10 and 3.6
4.3Crisis management 2 2 2 in force
The 2 laws behind PR.PO-P10 and 4.3
12.4Asset inventory 2 2 1 in force, 1 not yet in force
The 2 laws behind PR.PO-P10 and 12.4
PR.AC-P1Identities and credentials are issued, managed, verified, revoked, and audited for... 2.1Risk management framework 5 5 5 in force
The 5 laws behind PR.AC-P1 and 2.1
3.1Incident handling policy 5 5 5 in force
The 5 laws behind PR.AC-P1 and 3.1
4.1Business continuity and disaster recovery plan 5 5 5 in force
The 5 laws behind PR.AC-P1 and 4.1
6.2Secure development life cycle 5 5 5 in force
The 5 laws behind PR.AC-P1 and 6.2
6.5Security testing 5 5 5 in force
The 5 laws behind PR.AC-P1 and 6.5
6.10Vulnerability handling and disclosure 5 5 5 in force
The 5 laws behind PR.AC-P1 and 6.10
9.1Cryptography 5 5 5 in force
The 5 laws behind PR.AC-P1 and 9.1
11.2Management of access rights 5 5 5 in force
The 5 laws behind PR.AC-P1 and 11.2
PR.AC-P4Access permissions and authorizations are managed, incorporating the principles of... 2.1Risk management framework 6 3 6 in force
The 6 laws behind PR.AC-P4 and 2.1
3.1Incident handling policy 6 3 6 in force
The 6 laws behind PR.AC-P4 and 3.1
4.1Business continuity and disaster recovery plan 6 3 6 in force
The 6 laws behind PR.AC-P4 and 4.1
6.2Secure development life cycle 6 3 6 in force
The 6 laws behind PR.AC-P4 and 6.2
6.5Security testing 6 3 6 in force
The 6 laws behind PR.AC-P4 and 6.5
6.10Vulnerability handling and disclosure 6 3 6 in force
The 6 laws behind PR.AC-P4 and 6.10
9.1Cryptography 6 3 6 in force
The 6 laws behind PR.AC-P4 and 9.1
11.2Management of access rights 6 3 6 in force
The 6 laws behind PR.AC-P4 and 11.2
PR.AC-P6Individuals and devices are proofed and bound to credentials, and authenticated... 2.1Risk management framework 2 1 2 in force
The 2 laws behind PR.AC-P6 and 2.1
3.1Incident handling policy 2 1 2 in force
The 2 laws behind PR.AC-P6 and 3.1
4.1Business continuity and disaster recovery plan 2 1 2 in force
The 2 laws behind PR.AC-P6 and 4.1
6.2Secure development life cycle 2 1 2 in force
The 2 laws behind PR.AC-P6 and 6.2
6.5Security testing 2 1 2 in force
The 2 laws behind PR.AC-P6 and 6.5
6.10Vulnerability handling and disclosure 2 1 2 in force
The 2 laws behind PR.AC-P6 and 6.10
9.1Cryptography 2 1 2 in force
The 2 laws behind PR.AC-P6 and 9.1
11.2Management of access rights 2 1 2 in force
The 2 laws behind PR.AC-P6 and 11.2
PR.DS-P2Data-in-transit are protected. 2.1Risk management framework 5 5 5 in force
The 5 laws behind PR.DS-P2 and 2.1
3.1Incident handling policy 5 5 5 in force
The 5 laws behind PR.DS-P2 and 3.1
4.1Business continuity and disaster recovery plan 5 5 5 in force
The 5 laws behind PR.DS-P2 and 4.1
6.2Secure development life cycle 5 5 5 in force
The 5 laws behind PR.DS-P2 and 6.2
6.5Security testing 5 5 5 in force
The 5 laws behind PR.DS-P2 and 6.5
6.10Vulnerability handling and disclosure 5 5 5 in force
The 5 laws behind PR.DS-P2 and 6.10
9.1Cryptography 5 5 5 in force
The 5 laws behind PR.DS-P2 and 9.1
11.2Management of access rights 5 5 5 in force
The 5 laws behind PR.DS-P2 and 11.2
PR.DS-P5Protections against data leaks are implemented. 2.1Risk management framework 39 35 38 in force, 1 not yet in force
The 39 laws behind PR.DS-P5 and 2.1

and 29 more, every one in the free file.

3.1Incident handling policy 39 35 38 in force, 1 not yet in force
The 39 laws behind PR.DS-P5 and 3.1

and 29 more, every one in the free file.

4.1Business continuity and disaster recovery plan 39 35 38 in force, 1 not yet in force
The 39 laws behind PR.DS-P5 and 4.1

and 29 more, every one in the free file.

6.2Secure development life cycle 39 35 38 in force, 1 not yet in force
The 39 laws behind PR.DS-P5 and 6.2

and 29 more, every one in the free file.

6.5Security testing 39 35 38 in force, 1 not yet in force
The 39 laws behind PR.DS-P5 and 6.5

and 29 more, every one in the free file.

6.10Vulnerability handling and disclosure 39 35 38 in force, 1 not yet in force
The 39 laws behind PR.DS-P5 and 6.10

and 29 more, every one in the free file.

9.1Cryptography 39 35 38 in force, 1 not yet in force
The 39 laws behind PR.DS-P5 and 9.1

and 29 more, every one in the free file.

11.2Management of access rights 39 35 38 in force, 1 not yet in force
The 39 laws behind PR.DS-P5 and 11.2

and 29 more, every one in the free file.

Not connected to the ENISA NIS2 guidance: 88 of NIST Privacy Framework's controls

Short of 2 laws

The same duties reach these and a ENISA NIS2 guidance requirement, in fewer than 2 of the laws we track.

No ENISA NIS2 guidance requirement on the same duties

Laws reach these, but no duty that reaches one of them also reaches a ENISA NIS2 guidance requirement.

  • ID.IM-P2 Owners or operators (e.g., the organization or third parties such as service..., 2 laws
  • ID.IM-P4 Data actions of the systems/products/services are inventoried., 37 laws
  • ID.IM-P5 The purposes for the data actions are inventoried., 1 law
  • ID.IM-P7 The data processing environment is identified (e.g., geographic location, internal,..., 17 laws
  • ID.BE-P1 The organization’s role(s) in the data processing ecosystem are identified and communicated., 3 laws
  • ID.BE-P3 Systems/products/services that support organizational priorities are identified and..., 1 law
  • ID.RA-P2 Data analytic inputs and outputs are identified and evaluated for bias., 8 laws
  • ID.RA-P3 Potential problematic data actions and associated problems are identified., 5 laws
  • ID.RA-P5 Risk responses are identified, prioritized, and implemented., 15 laws
  • ID.DE-P1 Data processing ecosystem risk management policies, processes, and procedures are..., 1 law
  • ID.DE-P2 Data processing ecosystem parties (e.g., service providers, customers, partners,..., 29 laws
  • ID.DE-P5 Data processing ecosystem parties are routinely assessed using audits, test results,..., 7 laws
  • GV.PO-P1 Organizational privacy values and policies (e.g., conditions on data processing such..., 98 laws
  • GV.PO-P3 Roles and responsibilities for the workforce are established with respect to privacy., 54 laws
  • GV.PO-P4 Privacy roles and responsibilities are coordinated and aligned with third-party..., 10 laws
  • GV.PO-P5 Legal, regulatory, and contractual requirements regarding privacy are understood and managed., 225 laws
  • GV.RM-P1 Risk management processes are established, managed, and agreed to by organizational..., 1 law
  • GV.AT-P1 The workforce is informed and trained on its roles and responsibilities., 9 laws
  • GV.AT-P3 Privacy personnel understand their roles and responsibilities., 1 law
  • GV.MT-P1 Privacy risk is re-evaluated on an ongoing basis and as key factors, including the..., 2 laws
  • GV.MT-P3 Policies, processes, and procedures for assessing compliance with legal requirements..., 16 laws
  • GV.MT-P4 Policies, processes, and procedures for communicating progress on managing privacy..., 7 laws
  • GV.MT-P5 Policies, processes, and procedures are established and in place to receive, analyze,..., 3 laws
  • GV.MT-P6 Policies, processes, and procedures incorporate lessons learned from problematic data actions., 1 law
  • GV.MT-P7 Policies, processes, and procedures for receiving, tracking, and responding to..., 32 laws
  • CT.PO-P2 Policies, processes, and procedures for enabling data review, transfer, sharing or..., 233 laws
  • CT.PO-P3 Policies, processes, and procedures for enabling individuals’ data processing..., 371 laws
  • CT.DM-P1 Data elements can be accessed for review., 69 laws
  • CT.DM-P2 Data elements can be accessed for transmission or disclosure., 22 laws
  • CT.DM-P3 Data elements can be accessed for alteration., 23 laws
  • CT.DM-P4 Data elements can be accessed for deletion., 22 laws
  • CT.DM-P6 Data are transmitted using standardized formats., 8 laws
  • CT.DM-P7 Mechanisms for transmitting processing permissions and related data values with data..., 1 law
  • CT.DM-P9 Technical measures implemented to manage data processing are tested and assessed., 2 laws
  • CT.DM-P10 Stakeholder privacy preferences are included in algorithmic design objectives and..., 78 laws
  • CT.DP-P1 Data are processed to limit observability and linkability (e.g., data actions take..., 8 laws
  • CT.DP-P2 Data are processed to limit the identification of individuals (e.g., de-identification..., 10 laws
  • CT.DP-P4 System or device configurations permit selective collection or disclosure of data elements., 10 laws
  • CT.DP-P5 Attribute references are substituted for attribute values., 1 law
  • CM.PO-P1 Transparency policies, processes, and procedures for communicating data processing..., 2 laws
  • CM.AW-P2 Mechanisms for obtaining feedback from individuals (e.g., surveys or focus groups)..., 1 law
  • CM.AW-P3 System/product/service design enables data processing visibility., 13 laws
  • CM.AW-P4 Records of data disclosures and sharing are maintained and can be accessed for review..., 12 laws
  • CM.AW-P5 Data corrections or deletions can be communicated to individuals or organizations..., 54 laws
  • CM.AW-P6 Data provenance and lineage are maintained and can be accessed for review or..., 2 laws
  • CM.AW-P8 Individuals are provided with mitigation mechanisms (e.g., credit monitoring, consent..., 5 laws
  • PR.PO-P1 A baseline configuration of information technology is created and maintained..., 1 law
  • PR.PO-P5 Protection processes are improved., 7 laws
  • PR.PO-P9 Privacy procedures are included in human resources practices (e.g., deprovisioning,..., 14 laws
  • PR.AC-P2 Physical access to data and devices is managed., 6 laws
  • PR.AC-P5 Network integrity is protected (e.g., network segregation, network segmentation)., 2 laws
  • PR.DS-P4 Adequate capacity to ensure availability is maintained., 1 law
  • PR.MA-P1 Maintenance and repair of organizational assets are performed and logged, with..., 1 law
  • PR.PT-P3 Communications and control networks are protected., 1 law
  • PR.PT-P4 Mechanisms (e.g., failsafe, load balancing, hot swap) are implemented to achieve..., 6 laws

No law we track reaches these

No duty in the laws we track reaches these controls.

  • ID.IM-P3 Categories of individuals (e.g., customers, employees or prospective employees,...
  • ID.IM-P8 Data processing is mapped, illustrating the data actions and associated data elements...
  • ID.BE-P2 Priorities for organizational mission, objectives, and activities are established and...
  • ID.RA-P1 Contextual factors related to the systems/products/services and the data actions are...
  • ID.DE-P4 Interoperability frameworks or similar multi-party approaches are used to manage data...
  • GV.PO-P6 Governance and risk management policies, processes, and procedures address privacy risks.
  • GV.RM-P2 Organizational risk tolerance is determined and clearly expressed.
  • GV.RM-P3 The organization’s determination of risk tolerance is informed by its role(s) in the...
  • GV.AT-P2 Senior executives understand their roles and responsibilities.
  • GV.AT-P4 Third parties (e.g., service providers, customers, partners) understand their roles...
  • GV.MT-P2 Privacy values, policies, and training are reviewed and any updates are communicated.
  • CT.PO-P4 A data life cycle to manage data is aligned and implemented with the system...
  • CT.DP-P3 Data are processed to limit the formulation of inferences about individuals’ behavior...
  • CM.PO-P2 Roles and responsibilities (e.g., public relations) for communicating data processing...
  • PR.PO-P4 Policy and regulations regarding the physical operating environment for organizational...
  • PR.PO-P6 Effectiveness of protection technologies is shared.
  • PR.AC-P3 Remote access is managed.
  • PR.DS-P6 Integrity checking mechanisms are used to verify software, firmware, and information integrity.
  • PR.DS-P7 The development and testing environment(s) are separate from the production environment.
  • PR.DS-P8 Integrity checking mechanisms are used to verify hardware integrity.
  • PR.MA-P2 Remote maintenance of organizational assets is approved, logged, and performed in a...

How these connections are drawn

Each requirement line in the laws we track is read against the framework for its subject (the AI, scraping and news aggregation laws against the NIST AI RMF, the privacy, communications and age assurance laws against the NIST Privacy Framework, the cybersecurity laws against the NIST CSF 2.0); laws on liability and content moderation are not read against any framework yet. A line reaches the ENISA NIS2 guidance through a kind of duty its law carries, and only where that kind of duty also reaches, on that same line, the NIST framework for the line's own subject. Two controls connect when lines in at least 2 laws reach both. That says the same duties reach both; it does not say the two are alike, or that running either one does what a law asks.

A line placed on a control in the framework for its own subject, whose law carries a kind of duty that reaches another of the three frameworks read line by line, is read against that one as well: every such line, or only those whose wording reaches into it. For these two:

Laws onRead against the NIST Privacy Framework
cybersecurityevery such line

Every duty line in the cybersecurity laws we track has been read against the framework for its subject.

Sources and licenses

ENISA Technical Implementation Guidance on Commission Implementing Regulation (EU) 2024/2690, version 1.0 (June 2025), © European Union Agency for Cybersecurity (ENISA), 2025, licensed under CC BY 4.0. The section titles and requirement text are the Annex to Implementing Regulation (EU) 2024/2690 as ENISA prints it (© European Union); each section carries its first point as its text, and ENISA's guidance, examples of evidence and tips are not reproduced.