cm/controlmapping
Sources
Comparison

NIST CSF 2.0 vs Cyber Essentials

NIST Cybersecurity Framework 2.0  ·  UK Cyber Essentials (NCSC)  ·  data 2026-10-27

Requirement-level comparison of NIST Cybersecurity Framework 2.0 and UK Cyber Essentials (NCSC), in both directions, derived from published crosswalks and ControlMapping's curated topics.

Have NIST CSF 2.0 → 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 NIST CSF 2.0, 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 EssentialsRequirementMatchNIST CSF 2.0Evidence
Technical controls · 5
CE 1FirewallsEditorialID.AM-03PR.IR-01Same topic: Firewall / Net Seg (editorial pick)
CE 2Secure ConfigurationEditorialPR.AA-05PR.PS-01Same topic: Mobile Security, Secure Config (editorial pick)
CE 3Security Update ManagementEditorialID.AM-01ID.AM-02ID.AM-04+4Same topic: Asset Management (editorial pick)
CE 4User Access ControlEditorialID.AM-04PR.AA-01PR.AA-03+3Same topic: Cloud Security, Access Control, Multi-Factor Auth (editorial pick)
CE 5Malware protectionEditorialDE.CM-09PR.PS-05Same topic: Endpoint Protection (editorial pick)

Have Cyber Essentials → need NIST CSF 2.0

106 reqs 15 mapped · 0 loosely related · 91 no mapping Open in gap view →

Of 106 NIST Cybersecurity Framework 2.0 requirements, 15 map to something in Cyber Essentials, 0 are only loosely related, and 91 have no mapping in our data.

Likely new work: NIST CSF 2.0 requirements with no mapping to Cyber Essentials (91)
NIST CSF 2.0RequirementMatchCyber EssentialsEvidence
Detect (DE) · 10
DE.AE-02Potentially adverse events are analyzed to better understand associated activitiesNo mapping in our data—No mapping to Cyber Essentials in our data.
DE.AE-03Information is correlated from multiple sourcesNo mapping in our data—No mapping to Cyber Essentials in our data.
DE.AE-04The estimated impact and scope of adverse events are understoodNo mapping in our data—No mapping to Cyber Essentials in our data.
DE.AE-06Information on adverse events is provided to authorized staff and toolsNo mapping in our data—No mapping to Cyber Essentials in our data.
DE.AE-07Cyber threat intelligence and other contextual information are integrated into the analysisNo mapping in our data—No mapping to Cyber Essentials in our data.
DE.AE-08Incidents are declared when adverse events meet the defined incident criteriaNo mapping in our data—No mapping to Cyber Essentials in our data.
DE.CM-01Networks and network services are monitored to find potentially adverse eventsNo mapping in our data—No mapping to Cyber Essentials in our data.
DE.CM-02The physical environment is monitored to find potentially adverse eventsNo mapping in our data—No mapping to Cyber Essentials in our data.
DE.CM-03Personnel activity and technology usage are monitored to find potentially adverse eventsNo mapping in our data—No mapping to Cyber Essentials in our data.
DE.CM-06External service provider activities and services are monitored to find potentially adverse eventsNo mapping in our data—No mapping to Cyber Essentials in our data.
Govern (GV) · 31
GV.OC-01The organizational mission is understood and informs cybersecurity risk managementNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.OC-02Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and consideredNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.OC-03Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managedNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.OC-04Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicatedNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.OC-05Outcomes, capabilities, and services that the organization depends on are understood and communicatedNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.OV-01Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and directionNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.OV-02The cybersecurity risk management strategy is reviewed and adjusted to ensure coverage of organizational requirements and risksNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.OV-03Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments neededNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.PO-01Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforcedNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.PO-02Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational missionNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RM-01Risk management objectives are established and agreed to by organizational stakeholdersNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RM-02Risk appetite and risk tolerance statements are established, communicated, and maintainedNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RM-03Cybersecurity risk management activities and outcomes are included in enterprise risk management processesNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RM-04Strategic direction that describes appropriate risk response options is established and communicatedNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RM-05Lines of communication across the organization are established for cybersecurity risks, including risks from suppliers and other third partiesNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RM-06A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicatedNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RM-07Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussionsNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RR-01Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improvingNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RR-02Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforcedNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RR-03Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policiesNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.RR-04Cybersecurity is included in human resources practicesNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.SC-01A cybersecurity supply chain risk management program, strategy, objectives, policies, and processes are established and agreed to by organizational stakeholdersNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.SC-02Cybersecurity roles and responsibilities for suppliers, customers, and partners are established, communicated, and coordinated internally and externallyNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.SC-03Cybersecurity supply chain risk management is integrated into cybersecurity and enterprise risk management, risk assessment, and improvement processesNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.SC-04Suppliers are known and prioritized by criticalityNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.SC-05Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third partiesNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.SC-06Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationshipsNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.SC-07The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationshipNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.SC-08Relevant suppliers and other third parties are included in incident planning, response, and recovery activitiesNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.SC-09Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycleNo mapping in our data—No mapping to Cyber Essentials in our data.
GV.SC-10Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreementNo mapping in our data—No mapping to Cyber Essentials in our data.
Identify (ID) · 14
ID.AM-05Assets are prioritized based on classification, criticality, resources, and impact on the missionNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.AM-07Inventories of data and corresponding metadata for designated data types are maintainedNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.IM-01Improvements are identified from evaluationsNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.IM-02Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third partiesNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.IM-03Improvements are identified from execution of operational processes, procedures, and activitiesNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.IM-04Incident response plans and other cybersecurity plans that affect operations are established, communicated, maintained, and improvedNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.RA-02Cyber threat intelligence is received from information sharing forums and sourcesNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.RA-03Internal and external threats to the organization are identified and recordedNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.RA-04Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recordedNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.RA-05Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritizationNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.RA-06Risk responses are chosen, prioritized, planned, tracked, and communicatedNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.RA-07Changes and exceptions are managed, assessed for risk impact, recorded, and trackedNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.RA-09The authenticity and integrity of hardware and software are assessed prior to acquisition and useNo mapping in our data—No mapping to Cyber Essentials in our data.
ID.RA-10Critical suppliers are assessed prior to acquisitionNo mapping in our data—No mapping to Cyber Essentials in our data.
Protect (PR) · 15
PR.AA-02Identities are proofed and bound to credentials based on the context of interactionsNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.AA-04Identity assertions are protected, conveyed, and verifiedNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.AA-06Physical access to assets is managed, monitored, and enforced commensurate with riskNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.AT-01Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mindNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.AT-02Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mindNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.DS-01The confidentiality, integrity, and availability of data-at-rest are protectedNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protectedNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.DS-10The confidentiality, integrity, and availability of data-in-use are protectedNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.DS-11Backups of data are created, protected, maintained, and testedNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.IR-02The organization's technology assets are protected from environmental threatsNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situationsNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.IR-04Adequate resource capacity to ensure availability is maintainedNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.PS-03Hardware is maintained, replaced, and removed commensurate with riskNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.PS-04Log records are generated and made available for continuous monitoringNo mapping in our data—No mapping to Cyber Essentials in our data.
PR.PS-06Secure software development practices are integrated, and their performance is monitored throughout the software development life cycleNo mapping in our data—No mapping to Cyber Essentials in our data.
Recover (RC) · 8
RC.CO-03Recovery activities and progress in restoring operational capabilities are communicated to designated internal and external stakeholdersNo mapping in our data—No mapping to Cyber Essentials in our data.
RC.CO-04Public updates on incident recovery are shared using approved methods and messagingNo mapping in our data—No mapping to Cyber Essentials in our data.
RC.RP-01The recovery portion of the incident response plan is executed once initiated from the incident response processNo mapping in our data—No mapping to Cyber Essentials in our data.
RC.RP-02Recovery actions are selected, scoped, prioritized, and performedNo mapping in our data—No mapping to Cyber Essentials in our data.
RC.RP-03The integrity of backups and other restoration assets is verified before using them for restorationNo mapping in our data—No mapping to Cyber Essentials in our data.
RC.RP-04Critical mission functions and cybersecurity risk management are considered to establish post-incident operational normsNo mapping in our data—No mapping to Cyber Essentials in our data.
RC.RP-05The integrity of restored assets is verified, systems and services are restored, and normal operating status is confirmedNo mapping in our data—No mapping to Cyber Essentials in our data.
RC.RP-06The end of incident recovery is declared based on criteria, and incident-related documentation is completedNo mapping in our data—No mapping to Cyber Essentials in our data.
Respond (RS) · 13
RS.AN-03Analysis is performed to establish what has taken place during an incident and the root cause of the incidentNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.AN-06Actions performed during an investigation are recorded, and the records' integrity and provenance are preservedNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.AN-07Incident data and metadata are collected, and their integrity and provenance are preservedNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.AN-08An incident's magnitude is estimated and validatedNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.CO-02Internal and external stakeholders are notified of incidentsNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.CO-03Information is shared with designated internal and external stakeholdersNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.MA-01The incident response plan is executed in coordination with relevant third parties once an incident is declaredNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.MA-02Incident reports are triaged and validatedNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.MA-03Incidents are categorized and prioritizedNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.MA-04Incidents are escalated or elevated as neededNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.MA-05The criteria for initiating incident recovery are appliedNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.MI-01Incidents are containedNo mapping in our data—No mapping to Cyber Essentials in our data.
RS.MI-02Incidents are eradicatedNo mapping in our data—No mapping to Cyber Essentials in our data.
Mapped (15)
NIST CSF 2.0RequirementMatchCyber EssentialsEvidence
Detect (DE) · 1
DE.CM-09Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse eventsEditorialCE 5Same topic: Endpoint Protection (editorial pick)
Identify (ID) · 7
ID.AM-01Inventories of hardware managed by the organization are maintainedEditorialCE 3Same topic: Asset Management (editorial pick)
ID.AM-02Inventories of software, services, and systems managed by the organization are maintainedEditorialCE 3Same topic: Asset Management (editorial pick)
ID.AM-03Representations of the organization's authorized network communication and internal and external network data flows are maintainedEditorialCE 1Same topic: Firewall / Net Seg (editorial pick)
ID.AM-04Inventories of services provided by suppliers are maintainedEditorialCE 3CE 4Same topic: Asset Management, Cloud Security (editorial pick)
ID.AM-08Systems, hardware, software, services, and data are managed throughout their life cyclesEditorialCE 3Same topic: Asset Management (editorial pick)
ID.RA-01Vulnerabilities in assets are identified, validated, and recordedEditorialCE 3Same topic: Vulnerability Mgmt (editorial pick)
ID.RA-08Processes for receiving, analyzing, and responding to vulnerability disclosures are establishedEditorialCE 3Same topic: Vulnerability Mgmt (editorial pick)
Protect (PR) · 7
PR.AA-01Identities and credentials for authorized users, services, and hardware are managed by the organizationEditorialCE 4Same topic: Access Control (editorial pick)
PR.AA-03Users, services, and hardware are authenticatedEditorialCE 4Same topic: Multi-Factor Auth (editorial pick)
PR.AA-05Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of dutiesEditorialCE 2CE 4Same topic: Mobile Security, Access Control, Privileged Access (editorial pick)
PR.IR-01Networks and environments are protected from unauthorized logical access and usageEditorialCE 1CE 4Same topic: Firewall / Net Seg, Cloud Security (editorial pick)
PR.PS-01Configuration management practices are established and appliedEditorialCE 2CE 4Same topic: Secure Config, Mobile Security, Cloud Security (editorial pick)
PR.PS-02Software is maintained, replaced, and removed commensurate with riskEditorialCE 3Same topic: Patch Management (editorial pick)
PR.PS-05Installation and execution of unauthorized software are preventedEditorialCE 5Same topic: Endpoint Protection (editorial pick)

By topic

Both cover (11):

Only NIST CSF 2.0 (39):

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.