At a glance
- Owner
- NCSC, delivered by IASME
- Version
- Requirements for IT Infrastructure v3.3 (Danzell question set)
- Published
- 27 Apr 2026
- Applies to
- Any organisation, of any size, in any sector
- Mandatory
- Voluntary; contractual for some UK government contracts
- Assessed by
- Certification bodies licensed by IASME
- Cost model
- Cyber Essentials at a fixed fee set by IASME, banded by organisation size; Cyber Essentials Plus quoted by the certification body
Key points
- Five technical controls: firewalls, secure configuration, security update management, user access control and malware protection.
- Two levels. Cyber Essentials is a verified self assessment. Cyber Essentials Plus tests the same controls with a hands on technical audit.
- Version 3.3 of the requirements, with the Danzell question set, applies to assessment accounts created from 27 April 2026.
- Multi factor authentication on every cloud service that offers it, and high or critical updates applied within 14 days, are automatic fail items.
- Cloud services can no longer be excluded from scope.
What it is
Cyber Essentials sets a minimum standard for five technical controls across the devices, networks and cloud services an organisation uses. It targets commodity, untargeted attacks: exploitation of unpatched software, default credentials, password guessing and malware delivered by email or the web. It does not address targeted attacks, governance, incident response or supplier assurance.
The NCSC owns the technical requirements. IASME is the scheme's delivery partner and licenses the certification bodies that carry out assessments.
There are two levels:
- Cyber Essentials is a verified self assessment. The applicant answers the question set, a board member or director signs a declaration, and a certification body reviews the answers.
- Cyber Essentials Plus applies the same requirements and adds a technical audit: an assessor tests a sample of in scope devices and the external perimeter against the Cyber Essentials Plus Test Specification.
Certification is valid for 12 months.
The five controls
- Firewalls
Every in scope device is protected by a correctly configured firewall or equivalent boundary control. Inbound connections are blocked by default, and firewall administrative interfaces are not reachable from the internet unless there is a documented business need and the interface is protected by multi factor authentication or an IP allow list.
- Secure configuration
Unnecessary user accounts, software and services are removed or disabled, default passwords are changed, and auto run is disabled. Devices require a credential or biometric to unlock.
- Security update management
All software is licensed and supported. High risk and critical updates, including vendor approved configuration fixes, are applied within 14 days of release. Unsupported software is removed or isolated from the scope.
- User access control
Accounts are issued on need, administrative accounts are separate and used only for administrative work, and multi factor authentication is enforced on cloud services. Passwordless methods, including FIDO2 passkeys, are recognised.
- Malware protection
Anti malware software is installed and kept up to date, or applications are restricted through allow listing.
What changed in version 3.3
Changes from v3.2 (Willow) to v3.3 (Danzell)
- Multi factor authentication. Mandatory on every in scope cloud service where the service offers it, whether the service is free, bundled or paid. Not enabling it is an automatic fail.
- Security updates. Questions A6.4 (operating systems and router or firewall firmware) and A6.5 (applications) are automatic fail items for the 14 day rule.
- Cloud services. A definition of cloud services is added, and cloud services cannot be excluded from scope.
- Scope criteria. The qualifiers "untrusted" (inbound) and "user initiated" (outbound) are removed, so devices with allow listed inbound connections, or automated outbound connections, can fall into scope.
- Scope description. Scope descriptions are no longer length limited and appear on the digital certificate. Out of scope areas must be described and justified, including how they are segregated, but are not published. Every in scope legal entity must be named.
- Point in time. Compliance is judged at the certificate issue date. The director's declaration now includes maintaining compliance for the whole certification period.
- Application development. The web applications section is renamed and references the Software Security Code of Practice.
- Cyber Essentials Plus. Self assessment answers are locked before testing starts. A sample that fails the update test requires remediation and a retest of the original sample plus a new random sample, so the fix must hold across the wider environment. A second failure revokes the verified self assessment certificate.
Assessment accounts created before 27 April 2026 had six months to certify against v3.2. That transition window has now closed.
Scope
Scope is where most applications go wrong. The default is the whole organisation. A sub set can be certified only if it is segregated from the rest of the estate by a properly configured firewall or VLAN, and the scope description must say what is excluded and why.
In scope by default:
- Servers, desktops, laptops, tablets and mobile phones that access organisational data or services, including personal devices used for work.
- Network devices that provide the boundary, including corporate supplied home routers. Internet service provider routers in employees' homes are out of scope.
- Every cloud service that stores or processes organisational data, across infrastructure, platform and software as a service.
- Publicly accessible commercial web applications. Bespoke components the organisation develops itself are outside the scheme's technical controls.
Practitioner note
Bring your own device is the usual scope trap. Personal phones used for email or collaboration apps are in scope, so they need a supported operating system, a screen lock and multi factor authentication on the cloud services they reach. Decide early whether to bring them in with mobile device management or conditional access, or to remove organisational data access from them. Phones used only for native voice calls, native text messages and authenticator apps are the exception.
How it is assessed
Cyber Essentials. The applicant completes the question set on the IASME portal. A certification body assessor reviews the answers. Non compliant answers on simple issues can be corrected and resubmitted within two working days of the assessor's feedback. A board member or equivalent signs the declaration that the answers are accurate.
Cyber Essentials Plus. Must be completed within three months of the Cyber Essentials certificate. The assessor:
- Confirms the Plus scope matches the verified self assessment.
- Runs an external vulnerability scan of internet facing IP addresses.
- Tests a random sample of end user devices for missing updates, malware protection, the handling of malicious email attachments and web downloads, and multi factor authentication on cloud services.
- Where the update test fails, requires remediation and retests the original sample plus a new random sample.
Evidence expected
Assessors expect the applicant to show, for the sampled devices and services: operating system and application versions against the vendor's current supported releases; patch dates for any update rated critical or high by the vendor, or scored CVSS v3 7.0 or above, or for which the vendor gives no severity, within 14 days of release; the multi factor authentication setting on each cloud service's tenant; local administrator membership; and anti malware status and signature currency.
Common nonconformities
Common nonconformity
- Unsupported operating systems or applications left on in scope devices, often a forgotten kiosk, a lab machine or an old browser extension.
- Multi factor authentication enforced for administrators only, or only on Microsoft 365 while other cloud services (HR, finance, CRM) are left on password only sign in.
- Firmware on firewalls and routers not tracked against the 14 day rule.
- Users with standing local administrator rights on their daily account.
- A scope that excludes a business unit without evidence of network segregation.
Where it fits
Cyber Essentials is a floor, not a programme. It maps to a small part of the Protect function in the NIST Cybersecurity Framework and to a handful of contributing outcomes in the NCSC Cyber Assessment Framework, mainly in principles B2 and B4. For organisations handling NHS patient data, certification supports, but does not replace, the Data Security and Protection Toolkit.
Practitioner note
Treat certification as evidence of hygiene for customers and insurers, and track the five controls continuously rather than once a year. The v3.3 director's declaration now asks for compliance throughout the certification period, so a year with drift between assessments is a declaration problem, not just a security one.