Cyber Essentials has five controls. That is the whole scheme, and the NCSC overview is the authoritative source for them; use it to check anything here before you rely on it. Everything in the self-assessment questionnaire maps back to one of them, and every failed submission comes down to a gap in one of them.
This checklist is written for a small team that needs the certificate for a bid and does not have a security specialist to hand. Work through it in order, scope first, then each control, and write down your answers as you go. By the end you will have most of the questionnaire filled in and a short list of things to fix.
Step 0: Scope, decide what counts
Before any control, you need to know what the assessment covers. Get this wrong and every later answer is wrong.
Default to the whole organisation. You can scope a subset, but buyers and insurers increasingly expect "whole organisation" on the certificate, and a partial scope invites questions. For most SMEs the whole organisation is also the simplest answer.
List every device that accesses company data or services:
- laptops and desktops, company-owned or not
- phones and tablets used for work email, chat or files, including staff-owned ones
- servers, physical or virtual, on your premises
- network equipment: routers, firewalls, wireless access points
List every cloud service. Email, file storage, accounting, payroll, CRM, project tools, HR, video calling, website hosting, any virtual servers you rent. If staff log into it for work, list it. Cloud services can never be left out of scope, and the questionnaire asks for all of them.
Note who works where. Office, home, hybrid, client sites. This determines how the firewall control applies.
Flag anything old. Any device or application where you are not sure whether the vendor still supports it goes on a separate list. These are your most likely failures.
Tip: a checklist item is only done when you can name the devices and services. "About twenty laptops" is a guess. "Twenty-two laptops, listed by user" is scope.
Control 1: Firewalls
The requirement. Every in-scope device is protected by a firewall at the boundary between your network and the internet, and administrative access to that firewall is protected.
- Your office internet connection goes through a router or firewall with a changed admin password, not the one printed on the label.
- Administrative access to that firewall from the internet is disabled, or protected by MFA and restricted to specific addresses.
- No inbound services are open to the internet unless there is a documented business need. If you are not sure what a port forward is, you probably have none; check anyway.
- For every remote or hybrid worker: the software firewall built into Windows or macOS is turned on. You do not need to buy them a router. You do need to be able to say the setting is on.
- For devices used on untrusted networks (cafés, trains, client sites), the same software firewall is on.
Watch out: the usual failure is a home worker who disabled the Windows firewall years ago because it blocked a printer. Check each remote laptop; do not assume.
In the cloud: for services you rent (Microsoft 365, Google Workspace, your accounting package) the provider runs the boundary. Your part is admin access to the console: behind MFA, never open to a password alone. A virtual server you rent is a server; its firewall rules are yours.
Control 2: Secure configuration
The requirement. Devices and software are configured to reduce vulnerabilities and provide only the services the business needs.
- Default passwords are changed on everything: routers, printers, network storage, any device with a web admin page.
- Software that is not needed is removed: trial software, bundled utilities, games, old tools from a previous owner of the machine.
- Auto-run and auto-play are disabled, so plugging in a USB stick does not execute anything.
- Every user account is protected by a password that is at least 12 characters, or at least 8 characters with technical controls such as lockout or a deny list of common passwords. A password manager makes this painless.
- Where services support passkeys or MFA, they are used. This overlaps with Control 3, and it is fine to tick it once.
- Devices lock after a period of inactivity and require a PIN, password or biometric to unlock. For phones and tablets, a screen lock is mandatory.
Watch out: the usual failure is a printer or router still on its factory password. It is on the scope list; it counts.
In the cloud: a new Microsoft 365 or Google Workspace tenant ships with the provider's defaults, not the scheme's. Older sign-in methods that skip MFA, external sharing, guest accounts and unused apps are configuration you own.
Control 3: User access control
The requirement. Access to data and services is given only to people who need it, through individual accounts, with administrative privileges separated and multi-factor authentication on cloud services.
- Every person has their own account on every system. No shared logins. If three people know the password to "admin@yourcompany", that is the first thing to fix.
- Accounts with administrative rights are separate from everyday accounts. The person who administers Microsoft 365 has an admin account for that and a normal account for email. They do not browse the web as an administrator.
- Administrative rights on laptops are restricted. Most staff should be standard users, not local administrators.
- There is a process for creating accounts when people join and removing them when people leave, and it has been run for the last three leavers. Check.
- MFA is enabled on every cloud service that offers it, for every user. This is not optional and not partial. Email, files, accounting, CRM, payroll, everything on your scope list.
- Where a cloud service does not offer MFA, you have considered whether it should still be in use.
Watch out: the usual failure is MFA turned on for "the important accounts" and not the rest. The requirement is all of them.
In the cloud: this control is yours under every model. MFA on for every user and every admin on every service; admin roles separate inside the tenant; leavers removed from the cloud directory the day they go. Where a service has no MFA of its own but can sign in through one that does, that link must be set up.
Control 4: Malware protection
The requirement. Every in-scope device is protected from malware by anti-malware software, application allow-listing, or both.
- Anti-malware protection is installed and running on every laptop, desktop and server. The protection built into current Windows and macOS is acceptable; you do not have to buy anything.
- It updates automatically and is currently up to date. Open it and look at the date.
- It scans files on access and blocks known malicious websites.
- Nobody has turned it off "temporarily". Check every device, especially the ones that are rarely in the office.
- For phones and tablets, apps are installed only from the official app store, and the device is not jailbroken or rooted.
- If you use application allow-listing instead (on locked-down devices, say), only approved applications can run, and the approved list is maintained.
Watch out: the usual failure is a device where protection was disabled to install something and never re-enabled.
In the cloud: the provider's mail and file filtering is their part. It does not replace protection on the laptops and phones that reach the service, and a rented virtual machine needs its own protection, kept current.
Control 5: Security update management
The requirement. All software is supported by its vendor, licensed, and kept up to date, with high and critical security updates applied within 14 days of release.
- Every operating system on your scope list is still supported by its vendor. If it is not (an old Windows version, an old phone that no longer gets updates), the device is replaced, upgraded or removed from scope. There is no third option.
- Every application in use is supported and licensed. Pay particular attention to browsers, office suites, PDF readers and anything that opens files from the internet.
- Automatic updates are turned on for operating systems and applications wherever the option exists.
- High and critical security updates are applied within 14 days of release. With automatic updates on, this normally happens by itself; your job is to confirm nothing is stuck.
- Devices that are rarely switched on (the spare laptop, the meeting room PC, the director's second machine) are either kept updated or taken out of scope.
- Someone checks, monthly, that updates are landing. A device that reports "update failed" for three months is a fail waiting to happen.
Watch out: the usual failure is one old device that everyone forgot about. It is almost always the one that fails you, and it is almost always on the scope list from Step 0 if you did Step 0 properly.
In the cloud: the provider patches the service you rent; the browsers, devices and any virtual servers that reach or run on it are yours, within the same 14 days.
Step 6: Answer the questionnaire from your notes
If you have worked through the five controls and written down what you found, the questionnaire is now a transcription job. A few habits make it go smoothly:
- Answer truthfully. A senior person signs a declaration that the answers are accurate. The certification body reviews them and may ask follow-ups. A wrong "yes" is worse than a gap you fixed late.
- Be specific where asked. Device counts, operating system versions, the names of cloud services. "Various" is not an answer.
- Fix before you submit, not after. A fail usually comes with a short window to correct and resubmit, but the clock on your bid does not pause for it.
- Keep the evidence. Screenshots of MFA settings, the list of devices, the date you retired the old laptop. You will need it for renewal in 12 months and possibly for a buyer who asks.
The order to do things in
If the bid deadline is close, do the slow things first.
A small team with an ordinary estate can get through items 2 to 6 in a week. Item 1 depends on your supplier. Item 7 is a day. Nobody can promise you a pass, the certification body decides, but a team that has done the checklist honestly goes in with every common failure already fixed.