Cyber Essentials Requirements: A Plain-English Checklist
The Cyber Essentials requirements explained in plain English: the five technical controls, MFA and scope rules, what changed in version 3.3 and why applicants fail.
Key Takeaways
- The Cyber Essentials requirements rest on five technical controls: firewalls, secure configuration, security update management, user access control and malware protection.
- Version 3.3 (Danzell) keeps the five controls but treats missing cloud MFA and late critical patches more severely.
- Cloud services cannot be excluded, and personal devices that access company data are in scope.
- Critical and high-risk updates must be installed within 14 days; unsupported software must go or be isolated.
- Microsoft 365 and Intune can cover much of the checklist and provide evidence.
If you are preparing for certification, the Cyber Essentials requirements are shorter and more specific than most people expect. Five technical controls, applied to every in-scope device and cloud service, decide whether you pass.
The difficulty is rarely the controls themselves. It is scope, multi-factor authentication and patching discipline, because these are where assessors find gaps. The latest version of the rules has also made some of those gaps an automatic fail.
This guide walks through the current Cyber Essentials requirements in plain English, with a practical Cyber Essentials checklist you can work through before you open the Cyber Essentials questionnaire. It reflects the NCSC requirements document (v3.3) and the NCSC Cyber Essentials overview. If you want the wider process first, start with our Cyber Essentials certification guide.
What the Cyber Essentials requirements actually cover
Cyber Essentials is the UK government-backed baseline scheme, delivered by IASME on behalf of the NCSC. The requirements are published in a document called Requirements for IT Infrastructure. It sets out what must be true of your devices, networks, accounts and cloud services on the day you are certified.
The scheme is built around five technical controls:
- Firewalls: a filter between your devices and the internet.
- Secure configuration: devices and software set up to reduce easy ways in.
- Security update management: software kept supported and patched.
- User access control: the right people, with the right level of access.
- Malware protection: detecting and stopping malicious code.
Certification is for the organisation as a whole, or a clearly defined and separately managed part of it. IASME states that the certificate is valid for 12 months, so you will repeat the process every year.
↑ Back to ContentsWhich version applies now, and what changed
The current document is version 3.3, known as Danzell. It replaced version 3.2 (Willow). According to the SureCloud summary of the v3.3 changes, the Danzell question set applies to assessment accounts created on or after 27 April 2026. If you started an assessment earlier, check with your certification body which question set you are on.
The five controls themselves have not changed. What has changed is the wording around scope and the consequences of getting things wrong. The main differences from v3.2 are:
| Area | What changed in v3.3 |
|---|---|
| Cloud services | Now formally defined, and they cannot be excluded from scope. |
| Passwordless | Definition updated so that FIDO2 authenticators count as multi-factor authentication. |
| Scope wording | The reference to untrusted connections was removed. Anything excluded needs a specific justification. |
| Software development | Refers to the Software Security Code of Practice. |
| Backups | Given more emphasis, but still recommended rather than a technical requirement. |
| Auto-fail points | Per the SureCloud summary, not enabling available MFA on cloud services and missing the 14-day fix window for critical or high-risk updates now fail the assessment outright. |
The v3.2 release in April 2025 had earlier introduced passwordless guidance and renamed "home working" to "home and remote working". Check the NCSC site for the latest document before you start, because versions are updated roughly annually.
↑ Back to ContentsThe five technical controls in plain English
Here is what each of the five technical controls asks for, based on the NCSC requirements document (v3.3).
1. Firewalls
Every in-scope device needs a correctly configured firewall, either a hardware firewall at the network edge or a software firewall on the device itself. Default administrator passwords must be changed, or remote administration switched off. Unauthenticated inbound connections should be blocked by default, and any inbound rule needs an approved, documented business reason.
2. Secure configuration
Remove or disable accounts and software you do not need, including guest accounts and unused admin accounts. Change default passwords. Disable auto-run features. Lock devices when the user steps away, and limit password guessing on devices to no more than 10 attempts in 5 minutes, or lock after no more than 10 failures.
3. Security update management
All software must be licensed and supported. Anything unsupported must be removed, or isolated from the internet entirely. Updates that fix critical or high-risk vulnerabilities (vendor rating high or critical, or a CVSS v3 score of 7 or above) must be applied within 14 days of release. Our Windows 10 end-of-support guide explains why this catches out many businesses.
4. User access control
Accounts need an approval process and unique credentials. Remove them promptly when someone leaves. Admin tasks must use a separate admin account that is never used for email or browsing. Multi-factor authentication applies, and is mandatory for cloud services.
5. Malware protection
Every in-scope device needs anti-malware that is kept up to date, stops malicious code running and blocks malicious websites, or an application allow list limited to approved, code-signed software.
↑ Back to ContentsA practical Cyber Essentials checklist
Use this Cyber Essentials checklist as a pre-assessment sweep. If you cannot answer yes to every line, that is your work list.
Build an asset list
List every laptop, desktop, server, phone, tablet, router and firewall, plus every cloud service holding company data. Include personal devices that access email or files.
Agree the scope
Define the organisation, network boundary and locations. Be ready to justify anything you exclude. End-user devices and cloud services cannot be left out.
Check firewalls
Confirm default admin passwords are changed, inbound rules are documented, and a software firewall is on every laptop used off the office network.
Clean up accounts and software
Remove leavers, guest accounts and unused admin accounts. Uninstall applications nobody needs. Separate admin accounts from daily accounts.
Turn on MFA
Enable it on every cloud service, every admin account and anything reachable from the internet.
Patch and retire
Enable automatic updates. Find and replace unsupported operating systems and applications. Confirm critical and high-risk fixes land within 14 days.
Confirm malware protection
Check coverage and update status on every in-scope device, including servers and Macs.
Get board sign-off
A senior person must confirm the answers are accurate before submission. Gather evidence that supports each answer.
Multi-factor authentication rules
Multi-factor authentication (MFA) is the area where most applicants need to change something. The rules in the current version are straightforward:
- MFA must be used wherever it is available, and always for cloud services.
- It should also protect administrative accounts and any account accessible from the internet.
- The password element of MFA must be at least 8 characters, with no maximum length.
- Acceptable extra factors include an app on a trusted device, a managed device, a physically separate token or a known trusted account.
- SMS codes are the weakest option. They still count, but an authenticator app or security key is better.
- FIDO2 passkeys and security keys are accepted as MFA.
If you cannot use MFA on an account, the password rules apply instead. You need brute-force protection, plus either a minimum of 12 characters, or 8 characters with a deny list of common passwords. Do not force regular password changes, and do provide a password manager.
↑ Back to ContentsScope: BYOD, cloud services and home working
Scope mistakes are a common reason applicants fail, because they either leave things out or never find them. The NCSC requirements document (v3.3) is specific:
| Area | In scope? | What to know |
|---|---|---|
| BYOD | Yes, if the device accesses organisational data or services | Personal devices used only for calls, texts or an MFA app are out of scope. |
| Cloud services | Yes, always | You remain responsible, even where the provider handles some controls. For SaaS you must still configure the service securely. |
| Home and remote working | Yes, by default | An organisation-supplied router is in scope. Other routers are not, so devices need a software firewall. |
| Third-party accounts | Yes, if organisation-owned | This includes accounts used by contractors and your IT provider. Third-party-owned devices are out of scope. |
| Wireless devices | Depends | In scope if reachable from the internet. Out of scope behind an ISP home router. |
Where a corporate VPN is used, the internet boundary sits at the company or cloud firewall. Employee BYOD is in scope, while student BYOD is not. Whatever you exclude, you will need to justify it to your assessor.
↑ Back to ContentsMeeting the requirements with Microsoft 365 and Intune
Most NetMonkeys customers run on Microsoft 365, and much of the scheme can be met with tools they already license. Which ones depend on your plan, so check this against your own licences. Our Microsoft 365 support team sets these up regularly.
| Requirement | Microsoft 365 and Intune approach |
|---|---|
| MFA on cloud services | Entra ID Conditional Access or security defaults, with authenticator app or FIDO2 keys. |
| Device configuration and locking | Intune configuration profiles for screen lock, auto-run and sign-in attempt limits. |
| Software firewall | Windows Firewall enforced through Intune policy, including on home networks. |
| Security updates | Windows Update for Business rings, with compliance reporting for the 14-day window. |
| Malware protection | Microsoft Defender, deployed and monitored through Intune. |
| Leavers and admin accounts | Entra ID user lifecycle, separate admin accounts and role-based access. |
| BYOD | App protection policies or enrolment, depending on how much control you want. |
Intune also gives you evidence. A compliance report showing every device is patched and protected is far easier to defend than a spreadsheet kept by hand. If you want help preparing, see our Cyber Essentials service. NetMonkeys supports preparation and remediation, while the assessment itself is carried out by a certification body.
↑ Back to ContentsWhy Cyber Essentials fails: the common reasons
When people ask why Cyber Essentials fails, the answer is usually a handful of recurring gaps rather than anything exotic.
- Unsupported software. Old Windows versions, unsupported browsers and end-of-life routers or firewalls are the classic cause.
- Patches missed. Critical or high-risk fixes older than 14 days. Laptops that are rarely switched on are the usual culprits.
- MFA not enabled. Cloud services with MFA available but off. Under the current rules this can end the assessment on the spot.
- Scope too narrow. Leaving out personal phones, remote laptops or a cloud service that holds company data.
- Shared and stale accounts. Generic logins, leavers still active and daily admin use.
- Guessing at the questionnaire. Answering yes without checking, then being unable to evidence it.
- Unreviewed firewall rules. Open inbound ports with no documented reason.
Check before you submit
Answers are signed off by a senior person, and the declaration now acknowledges compliance throughout the certificate period. Verify each answer on a real device first.
For a deeper look at the next level, read our Cyber Essentials and Cyber Essentials Plus comparison and our Cyber Essentials Plus audit guide.
↑ Back to ContentsHow the Cyber Essentials questionnaire works
According to IASME, you buy the assessment for your organisation size and have up to six months to complete it. You answer the online Cyber Essentials questionnaire, a senior person confirms the answers, and a qualified assessor reviews them, typically within three working days. If more information is needed you resubmit. Once everything is met, the certificate is issued and you receive a digital badge.
Download the question set and the requirements document before buying, and answer a draft offline. Fees vary by organisation size, so check the current IASME price list rather than relying on a quoted figure. Cyber Essentials Plus adds a hands-on technical audit on top, arranged through a certification body.
↑ Back to ContentsConclusion: meeting the Cyber Essentials requirements first time
The Cyber Essentials requirements come down to five controls, applied consistently to every device, account and cloud service in your scope. Get MFA, patching and scope right and you remove most reasons for failure.
Work through the checklist, gather evidence from your Microsoft 365 or Intune tenant, and treat the 14-day patch rule as a standing process rather than an annual scramble. If you would like a second pair of eyes before you submit, our cyber security audit services can test your readiness.
↑ Back to ContentsFrequently asked questions
What are the Cyber Essentials requirements?
The Cyber Essentials requirements are five technical controls: firewalls, secure configuration, security update management, user access control and malware protection. They apply to all in-scope devices, accounts and cloud services. The current document is the NCSC's Requirements for IT Infrastructure version 3.3, and certification is valid for 12 months.
What are the five technical controls?
The five technical controls are firewalls, secure configuration, user access control, malware protection and security update management. Together they cover how your devices are protected from the internet, how they are set up, who can access them, how they are patched and how malicious software is stopped.
Is multi-factor authentication mandatory for Cyber Essentials?
MFA is mandatory for cloud services and must be used wherever it is available. It is also expected for administrator accounts and any account reachable from the internet. Authenticator apps, security keys and FIDO2 passkeys are accepted. SMS is the weakest permitted option, though still better than no MFA.
Are personal devices included in Cyber Essentials scope?
Yes. Personal devices that access organisational data or services are in scope, including employee-owned phones and laptops. Devices used only for calls, texts or an MFA app are out of scope. Student-owned devices are also excluded, so BYOD policy and enforcement need to be clear before assessment.
Can cloud services be excluded from scope?
No. Under version 3.3, cloud services that hold organisational data or services cannot be excluded. You stay responsible for the controls even where the provider implements some of them. For software-as-a-service, you must still configure the service securely, including enabling MFA.
How quickly must security updates be installed?
Updates that fix critical or high-risk vulnerabilities must be installed within 14 days of release. That covers vendor ratings of high or critical, or a CVSS v3 score of 7 or above. Installing all updates within 14 days is strongly recommended, though not mandatory.
Why does Cyber Essentials fail?
Common reasons are unsupported software, critical patches older than 14 days, MFA not enabled on cloud services, a scope that leaves out devices or services, shared or stale accounts, and unreviewed firewall rules. Under version 3.3, some of these, such as missing MFA, can fail an assessment outright.
How long does the Cyber Essentials questionnaire take?
Time depends on how well documented your IT is. IASME gives you up to six months to complete the questionnaire once purchased, and assessors typically review submissions within three working days. A prepared organisation with a current asset list can often finish in a day or two of focused effort.
Related Cyber Security Services
Cyber Essentials Support
Certification preparation and support from a Microsoft Solutions Partner.
View Service →SecurityCyber Security Audit
An independent review of accounts, devices, email and backups, with prioritised fixes.
View Service →IT SupportManaged IT Support
Helpdesk, monitoring and patching that keep your controls in place after you certify.
View Service →Microsoft 365Microsoft 365 Support
MFA, conditional access and device management configured properly.
View Service →Want a readiness check before you submit?
NetMonkeys helps UK organisations prepare for Cyber Essentials, from scoping and Microsoft 365 or Intune configuration to fixing the gaps assessors look for. Talk to us before you buy the assessment.
Speak to our team 0161 834 9345