Cyber Essentials

Danzell: Every Change in the 2026 Cyber Essentials Update Explained

> series: cyber_essentials_demystified —— part: 08/10 —— update: danzell_v3.3 —— effective: 27_april_2026<span class="cursor-blink">_</span>_

Hedgehog Security 26 March 2026 14 min read

Everything that changes on 27 April 2026.

The Danzell question set replaces Willow on 27 April 2026, introducing version 3.3 of the NCSC Requirements for IT Infrastructure. While the five core controls remain unchanged, the assessment criteria, marking rules, and certification process have been significantly tightened. This article consolidates every change into a single reference — the auto-fail criteria, the cloud scoping changes, the CE Plus process revisions, and the transition timelines.


Recommended

Getting certified doesn't have to be painful.

We handle the Cyber Essentials process end to end — from gap analysis to certification.

Start Your Certification

Three ways to fail automatically.

Danzell introduces three categories of automatic failure — areas where non-compliance results in immediate assessment failure regardless of performance across all other controls. Previously, these areas were assessed as major non-compliances and organisations could still pass with up to two major non-compliances. That flexibility is gone.

Auto-Fail Requirement Scope
MFA not enabled MFA must be enabled for all users on all cloud services where MFA is available — whether free, bundled, paid, or via IdP. Every cloud service in scope. Microsoft 365, Google Workspace, Xero, CRMs, password managers, remote access tools, social media — all in scope.
A6.4 — OS and firmware patching All high-risk and critical security updates for operating systems, router firmware, and firewall firmware must be installed within 14 days of release. Every in-scope device running an operating system. Every router and firewall in scope.
A6.5 — Application patching All high-risk and critical security updates for applications, including associated files and browser extensions, must be installed within 14 days of release. Every application on every in-scope device. Explicitly includes browser extensions.

The new definition and scoping rules.

Danzell introduces a formal definition of cloud services for the first time. A cloud service is defined as an on-demand, scalable service hosted on shared infrastructure and accessible via the internet. Cloud services can no longer be excluded from scope without explicit justification and evidence of genuine segregation. If organisational data is stored or processed in a cloud service, that service is in scope.

This closes a loophole that some organisations used under previous versions to keep cloud platforms out of their assessment scope. Under Danzell, everything counts — Microsoft 365, Google Workspace, your CRM, HR systems, cloud storage, accounting software, project management tools, and business social media accounts. IASME maintains a reference list of cloud services and their MFA capability, though the list is not exhaustive and the onus is on the applicant.


Tighter rules for what is in and out.

Group Company Certification
If you are part of a group and wish to certify only one company as a 'whole organisation', you must now demonstrate: different legal responsibility (no shared director), different network infrastructure (no shared networks), and separate legal entities (distinct companies with no shared governance). If any of these conditions are not met, you must certify as a sub-set.
Test and Development Environments
All organisations with test and development environments will no longer be able to obtain a 'whole organisation' certification — these networks must be formally de-scoped. This reflects the reality that test environments frequently run insecure or deliberately vulnerable configurations.
Scope Transparency
Organisations must now provide detailed descriptions of excluded infrastructure and justify all out-of-scope networks. This information is not made public but is available to the assessor. The previous character limit on certificate scope descriptions has been removed, allowing more detailed scope statements.
Individual Entity Certificates
IASME has introduced new certificate types allowing individual certificates for each legal entity within a group certification — providing clearer evidence for supply chain due diligence.

A tighter technical audit.

The CE Plus assessment process has been revised under Danzell to address practices identified through IASME's ongoing audits — particularly selective patching, where organisations applied updates only to sampled devices rather than across the estate.

Change Impact
VSA must be finalised before CE+ begins The verified self-assessment must be completed and locked before the CE Plus technical audit starts. Answers can no longer be changed based on what the CE+ audit finds. Your self-assessment is your declaration of your actual state.
Double sampling on retest If the initial random device sample fails due to missing updates, remediation is required. The retest now covers both the original sample AND a new random sample. You cannot fix just the devices the assessor tested.
Second failure = revocation A second failure during CE+ retesting results in revocation of the verified self-assessment certificate. You lose your CE as well as failing CE+.
Non-compliances block CE+ progression Non-compliances can no longer be accepted in the CE self-assessment if you intend to proceed to CE+. You must resolve all non-compliances before the technical audit begins.

A stronger commitment.

The director declaration — the formal sign-off required from a board-level individual — now includes a commitment to maintain Cyber Essentials controls throughout the certification period. Certification is no longer a point-in-time exercise. The declaration makes the director personally accountable for ongoing compliance, not just assessment-day compliance. This aligns Cyber Essentials with the direction of travel in UK cyber regulation — continuous obligation, not periodic checkbox.


When to act and which version to use.

Willow to Danzell Transition Timeline
── Now ────────────────────────────────────────────────────
Danzell question set available on IASME website
Download and review against your current estate

── Before 27 April 2026 ───────────────────────────────────
Create assessment account → assessed under Willow
6 months to complete CE (deadline: 26 October 2026)
Additional 3 months for CE+ (deadline: 26 January 2027)

── After 27 April 2026 ────────────────────────────────────
All new assessment accounts use Danzell (v3.3)
New auto-fail criteria in effect
New CE Plus process in effect

── Decision ───────────────────────────────────────────────
If confident of compliance → start under Willow before April
If any doubt → prepare for Danzell and do it properly

Other notable changes.

Danzell repositions backup guidance to a more prominent place in the Requirements for IT Infrastructure document. While backups are not assessed as a technical control, this repositioning signals that resilience and recovery may take on greater importance in future versions of the scheme. Organisations should ensure backup processes are documented and tested — not because Danzell requires it, but because the direction of travel is clear.

Web applications developed in-house are now more explicitly addressed. If your organisation develops web applications, the requirements around secure development practices, input validation, and protection against common vulnerabilities (including those in the OWASP Top 10) are more clearly stated. For organisations with bespoke web applications, a web application penetration test provides assurance that goes well beyond Cyber Essentials requirements.


Part 9 preview.

Next week, we compare Cyber Essentials and Cyber Essentials Plus in detail — what the Plus assessment actually involves, when you need it, what it costs, and how to prepare for the technical audit. If you are deciding between the two levels, Part 9 will give you the information to make the right choice.


We are already assessing against the new requirements.

As an IASME-approved certification body, we help organisations transition from Willow to Danzell with confidence. Our <a href="/cyber-essentials/concierge">Concierge service</a> includes a gap analysis against the Danzell requirements, MFA audit, patching review, and full certification support. For ongoing security beyond the certificate, <a href="https://www.socinabox.co.uk">SOC in a Box</a> provides continuous monitoring and compliance support.

Next Step

Getting certified doesn't have to be painful.

We handle the Cyber Essentials process end to end — from gap analysis to certification.

Start Your Certification

Related Articles