Home/Blog/Cyber Essentials
Cyber Essentials · 2 November 2026 · 5 min read

Cyber Essentials Six Months After Danzell

Where organisations are still getting caught out

Cyber Essentials
Since 27 April 2026, every new Cyber Essentials application has been assessed against version 3.3 of the NCSC’s Requirements for IT Infrastructure, using the new Danzell question set that replaced Willow. Six months on, many organisations that certified just before April are now approaching their first renewal under the new rules.

Much of the 2026 update was billed as clarification rather than new controls, and that framing has lulled some organisations into treating renewal as a box-ticking exercise. It isn’t. A handful of changes to how answers are marked have turned what used to be a tolerable non-compliance into an automatic fail, and a stricter Cyber Essentials Plus process means a failed audit can now cost you your basic certificate too.

If your renewal is due in the next few months, these are the areas we would look at first.

What has actually changed

A quick recap of the changes that matter most with Cyber Essentials Danzell:

  • MFA is now mandatory wherever a cloud service offers it. If MFA is available and not enabled, the assessment fails automatically. The relevant Cyber Essentials Danzell questions are A7.14 to A7.17.
  • The 14-day patching rule is now compulsory. Questions A6.4 (operating systems, router, and firewall firmware) and A6.5 (applications and extensions) were reclassified. Previously, an organisation could carry up to two major non-compliances and still pass.
  • Cloud services cannot be excluded from scope. Version 3.3 defines a cloud service for the first time, and any service that stores or processes your organisation’s data is in.
  • Scoping is stricter. Out-of-scope networks must be justified, group companies face tougher tests to certify as a “whole organisation”, and test and development environments must be formally descoped.
  • Cyber Essentials Plus is less forgiving. You can’t proceed to Plus with any major non-compliance, and a new second-sample rule catches organisations that only patch the devices being tested.

Six places organisations are getting caught out

1. The cloud services nobody told IT about

The biggest surprise for most organisations is simply how many cloud services they use. Microsoft 365 or Google Workspace are the obvious ones, but the definition also captures the CRM, the HR platform, the design tool marketing signed up for, the email marketing platform, and corporate social media accounts, even when a third party manages them.

Every one of these needs to be declared, and every one needs MFA switched on if it’s available. You can’t secure, or honestly declare, what you don’t know you have, so a proper cloud inventory is the starting point for everything else. If you need help mapping your external facing assets, our Aegis Platform can help.

2. MFA that is “available” but not switched on

The new rule is clear: if MFA is offered, it must be enabled. That includes MFA that is only available on a higher licence tier. Cost is no longer an acceptable reason to leave it off.

A few nuances catch people out. If a service doesn’t offer MFA itself but supports single sign-on through Microsoft or Google, you’re expected to use SSO. If MFA can’t be enforced by policy, you need to check manually that every user has turned it on. SMS codes are still accepted, and passwordless options such as passkeys and FIDO2 keys count.

3. The 14-day clock

High-risk and critical security updates must be installed within 14 days of release. That has always been the requirement, but missing it is now fatal to the assessment rather than a black mark.

The usual blind spots are not laptops managed by Intune. They are router and firewall firmware, browser extensions, the line-of-business application that someone updates “when they get a chance”, and devices sitting in a drawer. If a patch genuinely breaks business-critical software, the only accepted mitigation is to isolate the affected system completely from the internet. Realistically, meeting the 14-day rule needs automated patch management and some form of regular vulnerability scanning between assessments.

4. Scope statements copied from last year

It’s tempting to reuse last year’s scope description. Under Cyber Essentials Danzell, that’s risky. Group structures that previously qualified as a “whole organisation” may no longer do so if the companies share network infrastructure. Test and development networks must now be carved out. Personal devices and contractor laptops are in scope if they’re used to access organisational data, including through a virtual desktop.

A fresh look at your networks, devices, remote working arrangements and cloud services is the only safe way to answer the scoping questions consistently.

5. Patching the sample, not the estate

This is where we see most organisations getting caught out. In a Cyber Essentials Plus audit, if the first sample of devices fails the vulnerability scan, the assessor now selects a completely new second sample. If the same vulnerability appears there, the Plus assessment fails and IASME revokes your underlying Cyber Essentials certificate.

The rule exists because some organisations were fixing only the devices they knew would be retested. The lesson is simple: when a finding comes up, fix it everywhere.

6. Forgetting when “point in time” actually is

IASME has clarified that certification is assessed as at the date your certificate is issued, not the date you submitted your questionnaire. Any software that falls out of support between submission and issue can trip you up. Windows 10 devices are acceptable only while they’re receiving vendor security updates through Extended Security Updates.

A pre-renewal checklist

Before you start the Cyber Essentials Danzell questionnaire:

  • Build or refresh an inventory of every cloud service, including social media and departmental tools
  • Confirm MFA (or SSO) is enabled on each, for both admin and standard users
  • Check patch status across operating systems, applications, extensions and network device firmware
  • Re-examine your scope: group entities, test and development environments, BYOD and contractors
  • Make sure every device in scope is running supported software, and will still be on the date of issue
  • If you’re going for Plus, run your own vulnerability scan first and fix findings across the whole estate

Beyond the badge

Cyber Essentials remains a baseline, not a security programme. But the 2026 changes move it closer to measuring how organisations actually work today: in the cloud, with identity as the front door. Directors now explicitly accept responsibility for keeping controls in place throughout the year, not just on assessment day, and customers increasingly expect suppliers to hold a current certificate.

The organisations finding renewal easiest are those that treat these controls as business-as-usual rather than an annual scramble: continuous visibility of their attack surface, automated patching and a living asset register.

If you’d like a second pair of eyes before your renewal, or help building the continuous monitoring that makes Cyber Essentials a formality, our vCISO team can help. Talk to a vCISO.

Keep reading

More insights

View all posts →

Talk to a vCISO

Need help turning these insights into action? Talk to our team.