cm/controlmapping
Sources
Comparison

NIS2 vs Cyber Essentials

NIS2 Implementing Regulation (EU) 2024/2690  ·  UK Cyber Essentials (NCSC)  ·  data 2026-10-27

Requirement-level comparison of NIS2 Implementing Regulation (EU) 2024/2690 and UK Cyber Essentials (NCSC), in both directions, derived from published crosswalks and ControlMapping's curated topics.

Have NIS2 → need Cyber Essentials

5 reqs 5 mapped · 0 loosely related · 0 no mapping Open in gap view →

Of 5 UK Cyber Essentials (NCSC) requirements, 5 map to something in NIS2, 0 are only loosely related, and 0 have no mapping in our data.

Cyber Essentials certifies five technical controls only; governance, risk assessment, incident response and backup are deliberately outside its scope. All links are editorial.

Mapped (5)
Cyber EssentialsRequirementMatchNIS2Evidence
Technical controls · 5
CE 1FirewallsEditorial6.76.8Same topic: Firewall / Net Seg (editorial pick)
CE 2Secure ConfigurationEditorial6.3Same topic: Secure Config (editorial pick)
CE 3Security Update ManagementEditorial6.56.66.10+1Same topic: Vulnerability Mgmt, Patch Management (editorial pick)
CE 4User Access ControlEditorial6.111.111.2+5Same topic: Cloud Security, Access Control (editorial pick)
CE 5Malware protectionEditorial6.9Same topic: Endpoint Protection (editorial pick)

Have Cyber Essentials → need NIS2

49 reqs 16 mapped · 3 loosely related · 30 no mapping Open in gap view →

Of 49 NIS2 Implementing Regulation (EU) 2024/2690 requirements, 16 map to something in Cyber Essentials, 3 are only loosely related, and 30 have no mapping in our data.

NIS2 here is the technical measures of Implementing Regulation (EU) 2024/2690, which applies directly to digital-infrastructure and ICT-service providers; other NIS2 entities follow their country's transposition of Article 21. Incident reporting deadlines (Article 23) are not in scope. ENISA's mapping is non-binding.

Likely new work: NIS2 requirements with no mapping to Cyber Essentials (30)
NIS2RequirementMatchCyber EssentialsEvidence
1. Policy on the security of network and information systems · 2
1.1Policy on the security of network and information systemsNo mapping in our data—No mapping to Cyber Essentials in our data.
1.2Roles, responsibilities and authoritiesNo mapping in our data—No mapping to Cyber Essentials in our data.
2. Risk management policy · 2
2.2Compliance monitoringNo mapping in our data—No mapping to Cyber Essentials in our data.
2.3Independent review of information and network securityNo mapping in our data—No mapping to Cyber Essentials in our data.
3. Incident handling · 6
3.1Incident handling policyNo mapping in our data—No mapping to Cyber Essentials in our data.
3.2Monitoring and loggingNo mapping in our data—No mapping to Cyber Essentials in our data.
3.3Event reportingNo mapping in our data—No mapping to Cyber Essentials in our data.
3.4Event assessment and classificationNo mapping in our data—No mapping to Cyber Essentials in our data.
3.5Incident responseNo mapping in our data—No mapping to Cyber Essentials in our data.
3.6Post-incident reviewsNo mapping in our data—No mapping to Cyber Essentials in our data.
4. Business continuity and crisis management · 2
4.1Business continuity and disaster recovery planNo mapping in our data—No mapping to Cyber Essentials in our data.
4.2Backup managementNo mapping in our data—No mapping to Cyber Essentials in our data.
5. Supply chain security · 2
5.1Supply chain security policyNo mapping in our data—No mapping to Cyber Essentials in our data.
5.2Directory of suppliers and service providersNo mapping in our data—No mapping to Cyber Essentials in our data.
6. Security in acquisition, development and maintenance · 1
6.4Change management, repairs and maintenanceNo mapping in our data—No mapping to Cyber Essentials in our data.
7. Assessing the effectiveness of cybersecurity risk-management measures · 1
7.1Policies and procedures to assess the effectiveness of cybersecurity risk-management measuresNo mapping in our data—No mapping to Cyber Essentials in our data.
8. Basic cyber hygiene practices and security training · 2
8.1Awareness raising and basic cyber hygiene practicesNo mapping in our data—No mapping to Cyber Essentials in our data.
8.2Security trainingNo mapping in our data—No mapping to Cyber Essentials in our data.
9. Cryptography · 1
9.1CryptographyNo mapping in our data—No mapping to Cyber Essentials in our data.
10. Human resources security · 4
10.1Human resources securityNo mapping in our data—No mapping to Cyber Essentials in our data.
10.2Verification of BackgroundNo mapping in our data—No mapping to Cyber Essentials in our data.
10.3Termination or change of employment proceduresNo mapping in our data—No mapping to Cyber Essentials in our data.
10.4Disciplinary processNo mapping in our data—No mapping to Cyber Essentials in our data.
12. Asset management · 4
12.1Asset classificationNo mapping in our data—No mapping to Cyber Essentials in our data.
12.2Handling of assetsNo mapping in our data—No mapping to Cyber Essentials in our data.
12.3Removable media policyNo mapping in our data—No mapping to Cyber Essentials in our data.
12.5Deposit, return or deletion of assets upon termination of employmentNo mapping in our data—No mapping to Cyber Essentials in our data.
13. Environmental and physical security · 3
13.1Supporting utilitiesNo mapping in our data—No mapping to Cyber Essentials in our data.
13.2Protection against physical and environmental threatsNo mapping in our data—No mapping to Cyber Essentials in our data.
13.3Perimeter and physical access controlNo mapping in our data—No mapping to Cyber Essentials in our data.
Check these: only loosely related (a shared CSF outcome, not a mapping) (3)
NIS2RequirementMatchCyber EssentialsEvidence
2. Risk management policy · 1
2.1Risk management frameworkLoosely relatedCE 3Only shares CSF ID.RA-01: related, not a mapping
4. Business continuity and crisis management · 1
4.3Crisis managementLoosely relatedCE 1Only shares CSF ID.AM-03: related, not a mapping
6. Security in acquisition, development and maintenance · 1
6.2Secure development life cycleLoosely relatedCE 3Only shares CSF ID.AM-08: related, not a mapping
Mapped (16)
NIS2RequirementMatchCyber EssentialsEvidence
6. Security in acquisition, development and maintenance · 8
6.1Security in acquisition of ICT services, ICT systems or ICT productsEditorialCE 4Same topic: Cloud Security (editorial pick)
6.3Configuration managementEditorialCE 2Same topic: Secure Config (editorial pick)
6.5Security testingEditorialCE 3Same topic: Vulnerability Mgmt (editorial pick)
6.6Security patch managementEditorialCE 3Same topic: Patch Management (editorial pick)
6.7Network securityEditorialCE 1Same topic: Firewall / Net Seg (editorial pick)
6.8Network segmentationEditorialCE 1Same topic: Firewall / Net Seg (editorial pick)
6.9Protection against malicious and unauthorised softwareEditorialCE 5Same topic: Endpoint Protection (editorial pick)
6.10Vulnerability handling and disclosureEditorialCE 3Same topic: Vulnerability Mgmt (editorial pick)
11. Access control · 7
11.1Access control policyEditorialCE 4Same topic: Access Control (editorial pick)
11.2Management of access rightsEditorialCE 4Same topic: Access Control (editorial pick)
11.3Privileged accounts and system administration accountsEditorialCE 4Same topic: Privileged Access (editorial pick)
11.4Administration systemsEditorialCE 4Same topic: Privileged Access (editorial pick)
11.5IdentificationEditorialCE 4Same topic: Access Control (editorial pick)
11.6AuthenticationEditorialCE 4Same topic: Multi-Factor Auth (editorial pick)
11.7Multi-factor authenticationEditorialCE 4Same topic: Multi-Factor Auth (editorial pick)
12. Asset management · 1
12.4Asset inventoryEditorialCE 3Same topic: Asset Management (editorial pick)

By topic

Both cover (10):

Only NIS2 (33):

Only Cyber Essentials (1):

Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · Loosely related only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. Mapped = curated together in a ControlMapping topic, or linked directly. Crosswalks don't prove compliance. Methodology · Download the data · Report a mistake.