← Back to blog

Cyber Essentials MFA Requirements: What v3.3 Expects

November 15, 2026
Cyber Essentials MFA Requirements: What v3.3 Expects

If your organisation uses a cloud service that offers multi-factor authentication (MFA), you must switch it on for every account to pass Cyber Essentials. Since 27 April 2026, under version 3.3 of the scheme (known as Danzell), leaving it off ends the assessment as an automatic fail, with no partial credit and no chance to fix it mid-assessment. This guide sets out what counts as MFA, which accounts are covered, what evidence to keep and how to get ready before you submit. As a CREST-accredited Certification Body for Cyber Essentials, we assess this every day, and it is the part of the scheme where well-run small organisations most often trip up.

Solusec
solusec.co.uk
Prepare for Cyber Essentials v3.3
Solusec’s CREST-accredited team assesses Cyber Essentials and can help your organisation understand the certification requirements.
Fast Cyber Essentials

Key Takeaways

  • MFA means signing in with two or more verification factors, such as a password plus an authenticator app or a security key. Cyber Essentials v3.3 requires it for authentication to cloud services.
  • For assessments on accounts created after 27 April 2026, a cloud service that offers MFA where you have not enabled it is an automatic failure.
  • Where MFA is in place, the password only needs to be 8 characters long. Without MFA, you need 12 characters, or 8 with common passwords blocked, plus protection against guessing.
  • Keep dated evidence: registration reports, sign-in logs and a note of the method used on each service.
  • A pre-assessment check of every cloud account is the cheapest way to avoid a failed submission and a re-sit.

Table of Contents

What MFA means in Cyber Essentials

MFA is a way of proving who you are that uses two or more separate pieces of evidence. The v3.3 requirements document from the NCSC (the National Cyber Security Centre, the UK government's cyber authority) defines it as a method of authenticating a user that uses two or more verification factors. The password is the first factor. The scheme then lists what can serve as an additional factor:

  • a managed or enterprise device, meaning one your organisation controls;
  • an app on a trusted device;
  • a physically separate token;
  • a known or trusted account.

The same document says MFA should be implemented wherever it is available, and that authentication to cloud services must always use it. In plain terms: for anything hosted online where staff sign in with a work account, a password on its own is no longer enough.

What changed in April 2026

Before version 3.3, the MFA expectation already existed. What changed is how it is marked. IASME, the body that runs the scheme's delivery network, describes the update as a change to marking rather than a brand-new rule. Questions A7.14 to A7.17 are now automatic-fail questions. If a cloud service has MFA available and you have not implemented it, the assessment stops there, whatever you scored elsewhere. The same source states that this applies to assessment accounts created after 27 April 2026.

Computer Weekly reported that this was the first time MFA became a strict pass-or-fail item, with no discretion for the assessor to give you the benefit of the doubt. Our own summary of the v3.3 changes and the April 2026 changes overview cover the other updates in the same release.

The practical effect is simple. Before April 2026, a missing MFA setting might cost you marks. Now it costs you the whole attempt, along with the time and fee that go with a re-assessment.

What changed in April 2026

Which accounts and services are covered

The scope is wider than most people expect, because the scheme defines a cloud service broadly. In v3.3, a cloud service is an on-demand, scalable service hosted on shared infrastructure and reached over the internet. It is accessed through an account (credentials issued by your organisation, or a business email address) that stores or processes your organisational data. If your data or services sit on cloud services, they must be in scope and cannot be excluded from the assessment.

For a typical small organisation, that usually means:

  • Email and productivity suites: Microsoft 365 and Google Workspace, including every user and every admin account.
  • Finance and HR tools: online accounting packages, payroll and HR platforms.
  • Customer and project systems: CRM, ticketing, project management and file-sharing services.
  • Hosting and infrastructure consoles: the admin portals for your website host, domain registrar, and cloud platform.
  • Education and charity specifics: management information systems, safeguarding platforms, donor databases and learning platforms, wherever staff log in with organisational credentials.

The point that catches people is the long tail. The main suite is usually secured. The forgotten marketing tool that one person signed up to with a work email address is not, and it is still in scope.

Users and administrators alike

MFA is not just for administrators. The requirement applies to authentication to the cloud service, so it covers ordinary users as well as admins. Admin accounts also need to be separate from day-to-day accounts, which is worth sorting at the same time. Our Cyber Essentials checklist lists the other account controls an assessor looks at alongside MFA.

Which MFA methods are accepted

The NCSC's wording is deliberately broad. Passwordless methods are recognised as well as the familiar code-based ones. According to the requirements, the following all count:

MethodHow it worksNotes for a small organisation
Authenticator appA number-matching prompt or code on a trusted phoneThe usual choice: free with Microsoft 365 and Google Workspace
Security key or tokenA physical device that is plugged in or tappedFIDO2 authenticators are regarded as MFA; strongest option for admins
Passkeys and biometricsA device-bound credential unlocked by fingerprint or faceCounts as MFA when built on a managed or trusted device
Push notificationAn approval request sent to a registered appConvenient; pair with number matching to cut approval fatigue
One-time codesA code generated by an app or sent by textAccepted
SMS text messageA code sent to a mobile numberAcceptable, but less secure

On text messages, the NCSC's own requirements document says SMS is not the most secure type of MFA but still gives a large advantage over having no MFA at all, and recommends using alternatives where they work for your situation. If you are choosing from scratch, an authenticator app or a security key is a better starting point than texts. Our comparison of Duo and Microsoft Authenticator for a UK SME helps you pick between the two most common app options.

Password rules when MFA is on, and when it is not

MFA changes the password rules in your favour. The NCSC requirements set out two situations:

With MFA in place: the password element must be at least 8 characters, with no maximum length restriction. MFA satisfies both the brute-force protection control and the password-quality control.

Without MFA (for example, a service where it genuinely cannot be used): you need protection against guessing, either throttling to no more than 10 guesses in 5 minutes or lockout after no more than 10 failed attempts. You also need either a minimum of 12 characters, or a minimum of 8 characters with automatic blocking of common passwords through a deny list.

Password controls with and without MFA

The same guidance advises against forced regular password expiry and complexity rules. It promotes unique, multi-word passwords instead. So once MFA is on, you can drop the "change it every 90 days, include a symbol" policy that staff dislike and that no longer earns you anything.

What if a cloud service has no MFA?

The requirement is to implement MFA where it is available. That wording matters. If a service offers MFA in any form, including in a higher licence tier or as a setting hidden in an admin console, the assessor will expect it to be on. Check the vendor's documentation and your plan before you declare that a service lacks it.

If you find a service that truly has no MFA option, list it honestly in your assessment answers and have the vendor's documentation to hand. Then ask whether the service is worth keeping. A tool that cannot protect your organisation's data with a second factor is a risk beyond the scheme, and moving to an alternative that supports MFA is usually the cleaner answer. Computer Weekly's reporting notes that organisations with services that genuinely lack MFA, or that sit in grey areas, have no partial credit or in-cycle fix to fall back on, so settle these cases before submitting rather than during the assessment.

A worked example: a 12-person charity

Take a charity with 12 staff and volunteers using Microsoft 365, an online accounting package, a donor database, a website host and a domain registrar. A sensible readiness pass looks like this:

  1. List every service where someone signs in with a work email or organisational credentials. Ask each team, not just IT. Expect to find two or three that nobody mentioned.
  2. Check MFA availability for each in the vendor's help pages and on your current plan.
  3. Turn it on for everyone, admins first. In Microsoft 365 that means enforcing it across all users, so no one is left on a password alone.
  4. Retire legacy sign-in routes that bypass MFA, such as old email protocols on a few shared mailboxes.
  5. Set the password policy to 8 characters minimum with no maximum, drop expiry rules, and encourage multi-word passphrases.
  6. Export the evidence and file it with the date.

A small team can usually do this in a day or two. Finding the forgotten service is the slow part.

Evidence to keep

It is not enough for MFA to be configured; you should be able to show it is implemented and in use. The most useful evidence is:

  • Registration reports: in Microsoft Entra ID, the user registration details exported as dated CSV files show who has registered an MFA method.
  • Sign-in logs: entries that show MFA sign-ins actually happening.
  • A short register of services: each cloud service, who administers it, and which MFA method it uses.
  • Vendor documentation for any service where MFA is unavailable.

Dated exports matter because they show the position at the time of the assessment, not a screenshot someone took a year ago. Keep them with your other certification records.

Common reasons organisations fail on MFA

The failures follow a few patterns:

  • Shadow accounts: a service signed up to by one person with a work email and never added to the list.
  • Exempt users: a director, a shared mailbox or a service account excluded from the MFA policy "temporarily".
  • Licence assumptions: believing MFA needs a premium plan when a basic setting exists, or the reverse.
  • Mixed-up scope: treating a cloud service as out of scope because it is "only" used for a small task. The scheme says cloud services holding organisational data cannot be excluded.
  • Answering from memory: ticking yes without checking each account.

The automatic-fail design means these are no longer minor deductions. They are the whole result.

Does Cyber Essentials Plus change anything?

The same MFA rule applies. Cyber Essentials Plus is the version where an assessor technically verifies your controls rather than relying only on your answers, so a gap that slips through a self-assessment is far more likely to be found. If you are weighing the two levels, our guide on Cyber Essentials versus Cyber Essentials Plus explains which one a contract or customer is asking for.

Getting assessed with Solusec

Our Cyber Essentials certification is priced at £320 to £600 one-off, depending on your organisation's size. A gap analysis for Cyber Essentials is £300 one-off, and an urgent turnaround is available for an extra £100 one-off, which suits organisations that need the certificate for a tender or contract deadline. You deal directly with the assessors who review your answers, not a sales team, and the advice you get is practical and in plain English.

Solusec

If you are not sure which of your cloud accounts are in scope, start with the gap analysis on our Cyber Essentials page. It maps your current set-up against the scheme before you submit, so MFA gaps are found when they are cheap to fix. If a customer or funder is driving the deadline, see Cyber Essentials for a contract. Schools and colleges can read our guide to Cyber Essentials for schools, and if you are not sure the scheme applies to you, who needs Cyber Essentials sets it out.

FAQ

Is MFA mandatory for Cyber Essentials?

Yes, for cloud services that offer it. Under v3.3, authentication to cloud services must use MFA, and for assessment accounts created after 27 April 2026 an available but unused MFA option is an automatic fail. The requirement applies to every user and administrator account on those services.

Is SMS text message MFA accepted?

Yes. The NCSC accepts SMS as an additional factor, while noting it is less secure than other methods. An authenticator app or security key is the better long-term choice, particularly for administrator accounts.

How long must passwords be if I use MFA?

At least 8 characters, with no maximum length restriction. Without MFA the minimum is 12 characters, or 8 with common passwords automatically blocked, alongside limits on repeated guessing.

What evidence will an assessor want for MFA?

Expect to show that MFA is both set up and used. Dated registration reports, sign-in logs showing MFA sign-ins and a record of the method used on each cloud service cover most cases.

Does MFA apply to Cyber Essentials Plus as well?

Yes. The same requirement applies, and the technical verification in the Plus assessment makes any gap easier to spot.

Sources

This article was created with assistance of AI. We never use AI with your data unless given explicit permission.