Cyber Essentials Knowledge & Assessment

A practical SPI learning and project tool for understanding the UK Government-backed Cyber Essentials scheme and preparing an organisation for assessment. Learn the five technical controls, define scope, record evidence, identify gaps and manage actions. This tool supports readiness; it does not provide Cyber Essentials certification.

NCSC v3.3 Danzell 2026 5 Technical Controls Readiness Assessment
5
Technical controls
0%
Assessment complete
0%
Readiness score
0
Open gaps
KNOWLEDGE
PROJECT

What is Cyber Essentials?

Cyber Essentials is the UK Government-backed certification scheme developed by the National Cyber Security Centre (NCSC). It is designed to help organisations protect themselves against common internet-based cyber attacks through five technical controls.

Current basis: this SPI tool is structured around Cyber Essentials Requirements for IT Infrastructure v3.3, effective 27 April 2026, and the 2026 Danzell question set. Always verify the latest controlled requirements before certification.

The five controls

πŸ”₯ Firewalls

Protect devices and networks from unauthorised access from the internet.

βš™ Secure configuration

Reduce vulnerabilities by securely configuring devices, accounts, software and services.

πŸ”„ Security update management

Keep supported software and devices appropriately updated against known vulnerabilities.

πŸ‘€ User access control

Give people only the access they need and protect privileged accounts.

πŸ›‘ Malware protection

Prevent malicious software from executing or causing harm using appropriate controls.

Readiness journey

Understand the requirements
Use NCSC/IASME controlled guidance and establish who owns cyber security.
Define scope
Identify internet-connected infrastructure, cloud services, end-user devices, networks and justified exclusions.
Build an asset picture
Know the devices, operating systems, applications, cloud services and accounts that must be controlled.
Assess the five controls
Record objective evidence, gaps and actions rather than relying on assumptions.
Close gaps and verify
Implement actions, recheck evidence and prepare accurate certification responses.
Certify through the official scheme
Use IASME / an authorised Certification Body. SPI does not issue Cyber Essentials certificates.

Scope is fundamental

An assessment can only be meaningful when the organisation clearly understands what is included. Under v3.3, cloud services hosting organisational data or services are in scope; exclusions should be justified and segregation explained.

Common failure mode: an incomplete asset picture can make otherwise good controls ineffective because unmanaged devices, services or software are missed.

Consider

  • Internet-connected networks and boundary devices
  • Laptops, desktops, servers, mobile devices and relevant home-working equipment
  • Cloud services: SaaS, PaaS and IaaS
  • Operating systems and applications
  • Remote access and administrative interfaces
  • BYOD where it can access organisational data/services
  • Publicly available commercial web applications where applicable
  • Third-party managed systems and shared-responsibility boundaries

Asset discovery checklist

Networks
Locations, VLANs, Wi-Fi, internet gateways, routers and firewalls.
Devices
Type, owner, OS/version, support status and management method.
Software
Browsers, office tools, business applications, server software and plugins.
Cloud
Provider, service type, authentication, administrator accounts and responsibility split.
People/accounts
Normal users, administrators, service accounts, joiners/movers/leavers.

The Five Technical Controls

ControlIntentPractical checksUseful evidence
FirewallsPrevent unauthorised access to/from the internet.Boundary and host firewalls enabled; inbound rules justified; admin interfaces protected; default credentials changed.Firewall configuration, rule review, screenshots/exports, device inventory.
Secure configurationRemove insecure defaults and unnecessary attack surface.Unused accounts/software/services removed; auto-run controlled; authentication required; device locking configured.Build standard, MDM/GPO policy, configuration records, sampled device settings.
Security update managementPrevent exploitation of known vulnerabilities.Supported software; vulnerability/security updates applied within required timescales; high-risk issues prioritised.Patch reports, software inventory, vulnerability records, update policies.
User access controlLimit access and privilege.Unique accounts; least privilege; admin separated where appropriate; MFA used where required; access removed promptly.Account lists, access reviews, MFA configuration, leaver records.
Malware protectionStop untrusted/malicious code.Approved anti-malware, application allow-listing or sandboxing approaches as applicable; web/email protections considered.Endpoint management console, policy, protection status and sampled devices.
Assessment principle: record what is actually implemented and demonstrable. Do not answer the official assessment based only on policy intent.

Cyber Essentials

The organisation completes a verified self-assessment against the scheme requirements. The answers are reviewed through the official certification process and signed off by an appropriate senior person.

Think: documented and independently reviewed self-assessment.

Cyber Essentials Plus

CE+ covers the same five controls but adds independent technical testing of systems to provide greater assurance that the controls work in practice.

Think: the same baseline controls plus technical verification.

Important distinction

Cyber Essentials is not a substitute for a full information security management system, penetration-testing programme, incident-response capability or wider risk-management framework. It is a focused baseline against common cyber threats.

Evidence-based readiness

Document

Policies, standards, procedures, asset registers and defined responsibilities.

Configure

Technical settings showing the intended control is actually enabled.

Sample

Check representative devices, accounts and services rather than assuming fleet-wide compliance.

Report

MDM, endpoint, patching, vulnerability, identity and firewall reports.

Trace

Demonstrate joiner/leaver, administrator approval, patch exception or firewall-change examples.

Verify

Challenge the evidence: is it current, complete, representative and within scope?

Evidence quality: a policy saying β€œall devices are patched” is weaker than a current fleet report showing versions, outstanding updates, exceptions and owners.

Supply-chain assurance

Cyber Essentials can be used as a supplier assurance requirement. Buyers should define the contractual requirement, scope, certification level and how evidence is maintained.

  • Record supplier CE / CE+ status and expiry.
  • Verify certificates through the official certificate search.
  • Define whether whole-organisation or relevant-scope certification is required.
  • Flow cyber requirements through the supply chain where contractually required.
  • Assess higher-risk suppliers beyond CE where the information, service or threat warrants it.

Supplier review questions

What service/data is exposed?
Understand business impact before deciding assurance depth.
Is certification current?
Record certificate, scope and expiry rather than a simple yes/no.
Are sub-tiers involved?
Identify cloud, IT and other providers that materially support delivery.
What happens after a cyber incident?
Contractual reporting, containment, evidence preservation and recovery expectations should be understood.

Assessment Project

Project method: work through every assessment line, choose a status, record evidence and create actions for gaps. The score is a readiness indicator onlyβ€”not an official certification result.

Best Practice Example Project

Load a realistic worked example for a fictional UK engineering SME. It demonstrates good evidence notes, a mostly mature control environment, genuine gaps, owners and corrective actions. Use it to understand what a well-managed readiness project can look like.

Cyber Essentials Readiness Assessment

Assess implementation against practical control themes. Select Compliant only when you have objective evidence.

ControlAssessment questionStatusEvidence / notes

Gap & Action Plan

ActionOwnerDuePriorityStatus

Readiness Summary

Before official submission

  • Confirm the current NCSC requirements and IASME question set.
  • Revalidate scope and asset inventory.
  • Resolve non-compliant items or understand the official requirement.
  • Check evidence is current and representative.
  • Ensure assessment answers accurately describe the real environment.
  • Use the official IASME certification process / authorised Certification Body.
Not certification: an SPI readiness score cannot determine whether an official assessor will award Cyber Essentials.