Guide
Cyber Essentials requirements for IT infrastructure: the 5 controls
Updated
The NCSC sets the Cyber Essentials requirements for IT infrastructure in one document, now version 3.3 (April 2026), read 30 October 2026. It assesses five technical controls.
The Cyber Essentials 5 controls
- 1. Firewalls
- Every device in scope is protected by a correctly configured firewall, or a network device with firewall functionality. Default administrative passwords are changed to strong, unique ones; the admin interface is not reachable from the internet unless there is a documented business need and it is protected by MFA or an IP allow list; unauthenticated inbound connections are blocked by default; inbound rules are approved and documented by an authorised person with the business need; and unused rules are removed. A software firewall is needed on devices used on untrusted networks such as public wifi.
- 2. Secure configuration
- You regularly remove unnecessary accounts and software, change default or guessable passwords, disable auto-run, authenticate users before they reach organisational data, and set device locking: a biometric, password or PIN, protected by throttling (no more than 10 guesses in 5 minutes) or a lock after no more than 10 failed attempts, with at least 6 characters where the credential only unlocks the device.
- 3. Security update management
- All software in scope is licensed and supported, with automatic updates on where possible. Updates fixing vulnerabilities the vendor calls critical or high risk, or with a CVSS v3 base score of 7 or above, are installed within 14 days of release. Unsupported software must be removed or put in a segregated sub-set with no internet traffic.
- 4. User access control
- There is a process to create and approve accounts; every user signs in with unique credentials; accounts are removed or disabled when no longer needed; admin work is done only from separate admin accounts with no email or browsing; and MFA is used where available. Authentication to cloud services must always use MFA.
- 5. Malware protection
- A malware protection mechanism is active on every device in scope: anti-malware software that is kept updated and blocks malicious code and malicious websites, or application allow listing, where only approved applications restricted by code signing can run.
From April 2026, not using MFA on a cloud service where it is available is an automatic fail. So are the two questions on installing critical or high-risk updates within 14 days (IASME, April 2026 changes). The requirements apply to assessment accounts created after 26 April 2026.
Cyber Essentials password policy and password requirements
- Brute-force protection: every password is protected by at least one of MFA, throttling to no more than 10 guesses in 5 minutes, or a lock after no more than 10 failed attempts.
- Password quality, one of: MFA; a minimum of 12 characters with no maximum length; or a minimum of 8 characters with no maximum and automatic blocking of common passwords by a deny list.
- With MFA, the password part must still be at least 8 characters with no maximum length.
- Helping people choose: teach users to avoid common passwords, encourage three random words, provide a password manager or other secure storage, and do not force regular expiry or complexity rules.
- Compromise: have a process to change a password promptly when you know or suspect it has been compromised. Passwordless methods such as passkeys are encouraged.
Cyber Essentials scope, with an example scope
- The assessment should cover the whole IT infrastructure your organisation uses for its business, or a well-defined, separately managed sub-set: a part of the organisation whose network is segregated from the rest by a firewall or VLAN. The NCSC says a whole-organisation scope gives the best protection, and you must justify any partial scope to your assessor.
- Example scope: a firm certifies its office network, its staff laptops and phones, home workers' devices and its Microsoft 365 tenancy, while a separate lab network, walled off by its own firewall with no access to company data, is declared out of scope with the reason.
- A scope with no end-user devices is not acceptable, and cloud services that hold your data cannot be excluded.
- Agree the scope with your certification body before the assessment begins. From April 2026 you also describe what is out of scope and name every legal entity included.
Meeting the controls before you apply
- Inventory every device and cloud service that touches organisational data, including personal phones and home machines.
- Retire or replace unsupported software; it is an automatic fail on its own.
- Turn on MFA for every cloud service, separate admin accounts, and set device-unlock rules.
- Download the current question set and the requirements document free from IASME and the NCSC, do a dry run, then submit, or use the form to get a certification body to prepare and certify you in one engagement. See also how to pass first time.