Cyber Essentials MFA requirements (v3.3, 2026)
Cyber Essentials v3.3 requires MFA on every cloud service for every user and administrator. What counts as MFA, the A7.16 and A7.17 automatic fails, A7.15 and CE Plus test case 4.
Cyber Essentials v3.3 makes MFA mandatory on every cloud service that offers it, for every user and every administrator, with a password element of at least 8 characters. Under the 2026 Danzell question set a No to A7.16 or A7.17 is an automatic fail, and so is listing a service at A7.15 that does offer MFA.
- Requirement
- Implement MFA where available. Authentication to cloud services must always use MFA
- Applies to
- Every user and administrator account on every cloud service in A2.9: IaaS, PaaS, SaaS and social media accounts
- Threshold
- Password element of at least 8 characters, with no maximum length
- Automatic fails
- A No to A7.16 or A7.17. Listing a service at A7.15 that does offer MFA
- What changed in 2026
- MFA failures on cloud services became automatic fails from 27 April 2026. FIDO2 authenticators are named and regarded as MFA
Is MFA mandatory for Cyber Essentials?
Yes, for cloud services: the scheme requires MFA on every account that signs in to a cloud service your organisation uses, whether it belongs to a director, a part-time volunteer or an outside support company. The only exception is a service that offers no MFA option of any kind, which you declare at A7.15.
implement MFA, where available – authentication to cloud services must always use MFA
Outside cloud services, MFA is one of several accepted controls rather than a blanket rule. On a laptop or an internal server, MFA is one way to meet the brute-force and password quality rules, alongside throttling, lockout and minimum length (see password requirements). A firewall admin interface reachable from the internet needs either MFA or an IP allow list combined with a properly managed password, which A4.9 asks about.
QuestionsA7.14A7.16AUTO-FAILA7.17AUTO-FAIL
Which accounts need MFA?
Every user account and every administrator account on every cloud service, meaning on-demand, scalable services accessed via an account that store or process your data. The A2.9 guidance adds that social media accounts such as Facebook, LinkedIn and X count as cloud services, so the company LinkedIn page and the marketing team's scheduling tool are in scope alongside Microsoft 365.
It is required that all administrator accounts on cloud service must apply multi-factor authentication in conjunction with a password of at least 8 characters.
All users of your cloud services must use MFA in conjunction with a password of at least 8 characters.
Third-party accounts are included too. v3.3 says your control of user accounts 'also includes third party accounts', for example accounts used by your support services. An IT provider's login to your tenant needs MFA in the same way as your own staff.
Emergency access (break-glass) accounts are not an exception. Microsoft's emergency access guidance (updated June 2026, checked 9 November 2026) says to give these Global Administrator accounts a passkey (FIDO2), or certificate-based authentication, which 'satisfy the mandatory multifactor authentication requirements', and to exclude them only from Conditional Access policies 'that block or restrict sign-in'. Microsoft's mandatory MFA for the Azure portal, Entra admin center, Intune admin center and Microsoft 365 admin center also applies to break-glass accounts.
QuestionsA7.16AUTO-FAILA7.17AUTO-FAILA2.9
What counts as MFA for Cyber Essentials?
A password plus any second factor from the four v3.3 types counts, including an SMS code, and a FIDO2 authenticator counts as MFA on its own.
Multi-Factor Authentication (MFA) is a method of authenticating a user which uses two or more verification factors
There are four types of additional factor to consider: a managed/enterprise device, an app on a trusted device, a physically separate token, a known or trusted account
This includes FIDO2 authenticators which are considered as Passkeys. FIDO2 authenticators are regarded as MFA because user authentication is performed.
SMS is not the most secure type of MFA but still offers a huge advantage over not using any MFA at all. Any multi-factor authentication is better than not having it at all.
| Method | Counts as MFA? | Basis |
|---|---|---|
| SMS one-time code | Yes | v3.3: not the most secure type, but far better than none |
| Authenticator app push or code | Yes | v3.3 factor type: an app on a trusted device |
| Hardware security key (FIDO2) | Yes | v3.3: FIDO2 authenticators are regarded as MFA |
| Passkey built on FIDO2 | Yes | v3.3: FIDO2 authenticators are considered passkeys and regarded as MFA |
| Passkey sign-in with no password at all | Yes (our reading) | See the interpretation below: A7.16 and A7.17 mention a password of at least 8 characters |
| Sign-in only from a managed, compliant device | Yes, as the additional factor | v3.3 factor type: a managed/enterprise device |
| Password plus security questions | No (our reading) | Both are things you know, so there is no second factor type |
What if a cloud service has no MFA, or only on a paid tier?
A service with no MFA option of any kind goes in A7.15; a service where MFA is only on a paid tier still has MFA available, so you must turn it on, upgrade, replace the service or stop using it. IASME's April 2026 update says organisations that fail to implement MFA for cloud services 'whether it is free, included, or a paid option' will automatically fail, and listing such a service at A7.15 is itself an automatic fail.
You must provide a list of cloud services that are in use by your organisation that do not provide any option for MFA. Please note that this will be an automatic fail if a cloud service listed here does have the option for MFA.
Single sign-on is the other route. The A7.14 guidance says that where a cloud service does not have MFA of its own but can be configured to link to another cloud service that provides MFA, such as Microsoft 365, Azure or Google Workspace, 'that link must be configured'. A service that has its own MFA can use either its own MFA or single sign-on.
Accounts on a service with no MFA of any kind still fall under the password rules.
QuestionsA7.14A7.15AUTO-FAIL
Which MFA questions fail automatically?
Three of the four MFA questions carry fail wording in the Danzell guidance: A7.15, A7.16 and A7.17.
| Question | What it asks | Answer type | Fail rule |
|---|---|---|---|
| A7.14 | Do all your cloud services have MFA available? | Yes/No | No fail wording. Yes goes to A7.16, No goes to A7.15 |
| A7.15 | List the cloud services that provide no MFA option | Notes | Automatic fail if a listed service does have an MFA option |
| A7.16 | Has MFA been applied to all administrators of your cloud services? | Yes/No | Automatic fail on No |
| A7.17 | Has MFA been applied to all users of your cloud services? | Yes/No | Automatic fail on No |
How does Cyber Essentials Plus test MFA?
Test case 4 passes only if a sampled user and a sampled administrator are each prompted for MFA before access is granted to every cloud service. The assessor watches users sign in with their organisation-issued account on an untrusted device or in an incognito browser session; if that is not possible, the assessor shares an incognito session from their own device and observes. Where several services share one authentication service, such as Microsoft Entra ID, the test is done once for that authentication service. See CE Plus test case 4 for the full steps.
If the test results in the user or administrator being prompted for a form of MFA before access is granted, then award a Pass. Otherwise, record a Fail.
This must consist of at least one normal user and one administrative user for every cloud service used. The same users can be used across multiple cloud services.
QuestionsA7.16AUTO-FAILA7.17AUTO-FAIL
How do you meet the MFA requirement in Microsoft 365?
Turn on one of three Microsoft mechanisms for every user and administrator: security defaults (free), per-user MFA (free) or a Conditional Access policy (needs Microsoft Entra ID P1). Microsoft recommends Conditional Access where you hold P1, and says not to combine per-user MFA with Conditional Access.
- Block legacy authentication (security defaults do this; with Conditional Access add a block policy), because legacy protocols cannot present a second factor.
- Turn off SMTP AUTH for the tenant unless a device genuinely needs it.
- Do not exclude trusted locations or office IP ranges from MFA.
- Give break-glass accounts a FIDO2 key or passkey, as Microsoft's emergency access guidance says.
| Option | Licence | How Microsoft says it prompts | Admin path | CE Plus test case 4 (our reading) |
|---|---|---|---|---|
| Security defaults | None. Every Microsoft 365 plan includes Entra ID Free with security defaults | All users register for MFA; listed admin roles such as Global Administrator do MFA at every sign-in; other users are prompted 'when necessary' based on factors such as location, device, role and task; legacy authentication is blocked | Entra admin center > Entra ID > Overview > Properties > Manage security defaults > Enabled | Admins pass. Test a standard user from an incognito window first, because Microsoft decides when they are prompted |
| Per-user MFA | Included in Office 365 licensing (Microsoft's MFA licensing comparison) | Microsoft: users enabled individually 'perform MFA each time they sign in', with exceptions for trusted IPs and 'remember MFA on trusted devices'. In the Enabled state legacy authentication keeps working until the user registers | Entra admin center > Identity > Users > All users > Per-user MFA > select users > Enable MFA | Predictable if trusted IPs and remember-MFA are off and every user, including new starters, is moved to Enforced |
| Conditional Access | Microsoft Entra ID P1: in Business Premium, Microsoft 365 E3, E5, F1 and F3, or bought standalone | MFA is required for sign-ins that match the policy, for the users and apps you target | Entra admin center > Entra ID > Conditional Access > Create new policy from templates > Require multifactor authentication for all users > On | Predictable for each new sign-in session, provided no trusted-location exclusion covers the room the test is run from |
QuestionsA7.16AUTO-FAILA7.17AUTO-FAIL
How do you meet the MFA requirement in Google Workspace?
Enforce 2-Step Verification for every organisational unit, including the one that holds super administrators. Google's 2-Step Verification deployment guide (last updated 26 October 2026, checked 9 November 2026) gives the path: Admin console > Security > Authentication > 2-step verification, select the organisational unit, tick 'Allow users to turn on 2-Step Verification', and set Enforcement to 'On'. Only a super administrator can do this.
Third-party apps that you sign in to with your Google account then rely on that sign-in, which is the A7.14 'link' the guidance asks for; apps with their own username and password still need their own MFA. The Google Workspace setup guide lists the other admin console paths and the evidence to keep.
QuestionsA7.14A7.16AUTO-FAILA7.17AUTO-FAIL
What are the most common MFA mistakes?
In our assessments these are the gaps that most often turn a Yes at A7.16 or A7.17 into a fail:
- A cloud service missing from A2.9, typically payroll, accounting, a CRM, the domain registrar or a social media account, so its MFA setting is never checked.
- MFA enforced in Microsoft 365 but not on services that use their own sign-in rather than single sign-on.
- Legacy authentication protocols such as IMAP, POP and SMTP AUTH left on, which cannot present a second factor.
- Trusted locations or office IP ranges excluded from MFA, which the CE Plus incognito test exposes.
- A break-glass Global Administrator that signs in with a password only.
- One shared admin login with MFA tied to one person's phone. MFA is applied, but the account is not unique, which fails A7.2.
QuestionsA2.9A7.2A7.15AUTO-FAIL
What should you write in the A7.15 notes field?
A7.15 is a notes question that only appears if you answer No to A7.14. Name each service, say what it holds, say how you checked that no MFA option exists, and describe how the accounts are protected instead. An adaptable model:
[Service name] (rota scheduling, holds staff names and shift times). Checked on [date] against the vendor's security settings and current help documentation, and confirmed by the vendor by email on [date]: no MFA is available on any plan and the service cannot use single sign-on. Three named staff hold accounts, each with a unique password of at least 12 characters stored in our password manager. The service locks an account after repeated failed attempts. We review the vendor's MFA status at each renewal and will enable MFA as soon as it is offered.
How do assessors check MFA answers?
Related requirements
- User access control requirementsThe control hub: every A7 requirement
- A7.16: MFA for cloud administratorsAutomatic fail on a No
- A7.17: MFA for all cloud usersAutomatic fail on a No
- A7.15: cloud services without MFAThe conditional automatic fail
- CE Plus test case 4: MFA on cloud servicesThe incognito sign-in test
- Cyber Essentials password requirementsLength, deny lists and brute-force limits
- Cyber Essentials admin account requirementsSeparate accounts for admin tasks only
- Which Microsoft 365 licence do you need?Plans compared feature by feature
- Cloud services in scopeWhy cloud services cannot be excluded
- Check your readinessTest your answers against the auto-fail questions first
Frequently asked questions
Yes. v3.3 says SMS is not the most secure type of MFA but still offers a huge advantage over not using any MFA at all. The NCSC recommends an alternative, such as an authenticator app, a passkey or a hardware key, where one will work for your users.
FIDO2 passkeys do. v3.3 says FIDO2 authenticators are considered passkeys and are regarded as MFA because user authentication is performed. A7.16 and A7.17 mention a password of at least 8 characters; our interpretation is that a FIDO2 passkey sign-in without a password still meets them, and you should describe it in your A7.11 notes.
Not on its own. Microsoft enforces MFA for sign-ins to the Azure portal, Entra admin center, Intune admin center and Microsoft 365 admin center, and says users aren't required to use MFA for other applications. A7.16 covers all administrator accounts on the service, so our reading is that you still need security defaults, per-user MFA or Conditional Access.
MFA is still available, so the requirement applies. IASME's April 2026 update says failing to implement MFA for cloud services, whether free, included or a paid option, is an automatic fail. Upgrade, replace the service, or stop using it for organisational data. Do not list it at A7.15.
In our reading, yes. Security defaults make every user register for MFA and require administrators to complete MFA at every sign-in. Microsoft decides when ordinary users are prompted, so test a standard user's sign-in from an incognito window before a Cyber Essentials Plus audit, where an MFA prompt must appear.
- NCSCCyber Essentials: Requirements for IT Infrastructure v3.3 · April 2026Read on ncsc.gov.uk (opens in a new tab)
- IASMECyber Essentials Danzell Question Set 2026Read on iasme.co.uk (opens in a new tab)
- NCSCCyber Essentials Plus Test Specification v3.2Read on ncsc.gov.uk (opens in a new tab)
- NCSCMulti-factor authentication for your corporate online servicesRead on ncsc.gov.uk (opens in a new tab)
- IASMEImportant update: changes to Cyber Essentials for April 2026 (MFA free, included or paid; automatic fail) · Checked 9 November 2026Read on iasme.co.uk (opens in a new tab)
- Microsoft LearnManage emergency access admin accounts (updated June 2026) · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- Microsoft LearnPlan for mandatory Microsoft Entra multifactor authentication · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- Microsoft LearnSecurity defaults in Microsoft Entra ID · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- Microsoft LearnEnable per-user multifactor authentication · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- Microsoft LearnMicrosoft Entra multifactor authentication versions and licensing · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- Microsoft LearnMicrosoft Entra licensing (Entra ID P1 plans) · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- knowledge.workspace.google.comGoogle Workspace Admin Help: Deploy 2-Step Verification · Checked 9 November 2026Read on knowledge.workspace.google.com (opens in a new tab)
- knowledge.workspace.google.comGoogle Workspace Admin Help: Security best practices for administrator accounts · Checked 9 November 2026Read on knowledge.workspace.google.com (opens in a new tab)