How to prepare for Cyber Essentials Plus without wasting weeks
Most of the time lost on Cyber Essentials Plus is not spent fixing difficult technical problems. It goes on avoidable delays: a scope that was never properly agreed, evidence that nobody started collecting until the assessor asked for it, and a handful of devices or cloud accounts that quietly fell outside the controls everyone assumed were in place.
In my work with UK SMEs the pattern is consistent. The organisations that get through quickly are not necessarily the most mature. They are the ones that understood what is actually being tested and prepared for that, rather than for a vague idea of "being secure".
What Cyber Essentials Plus actually is
Cyber Essentials is the UK government-backed scheme, delivered by IASME, the NCSC's Cyber Essentials partner, built around five technical controls:
- Firewalls – controlling traffic at the boundary of your network and on devices.
- Secure configuration – removing default settings, unnecessary software and accounts.
- Security update management – keeping software patched and supported.
- User access control – making sure people only have the access they need, with stronger authentication where it counts.
- Malware protection – stopping malicious software from running.
Cyber Essentials Plus does not add extra controls. It uses the same five. The difference is how you prove them. Basic Cyber Essentials is a self-assessment questionnaire, verified by a certification body. Cyber Essentials Plus builds on that self-assessment with an external, hands-on technical verification carried out by an assessor from an IASME-licensed certification body.
In practice the assessor independently tests a sample of your devices and services. Expect vulnerability scans, tests to see whether your malware protection actually stops malicious files arriving by email and web browser, and checks that multi-factor authentication is in place on your cloud services. You must hold Cyber Essentials first, and the Plus assessment has to happen within a limited window after that certificate is issued, so confirm the current timescale with your certification body before you book anything.
One clarification that saves confusion later: asset management is not a Cyber Essentials control. The NCSC is explicit that it is not a separate requirement, but that knowing what you own is what makes all five controls achievable. You cannot patch, configure or protect a device you do not know exists.
Get the scope right before anything else
Scope is where I see the most wasted weeks. The self-assessment asks you to describe what is in scope, and the assessor tests against that description. If the two do not match, you are in for awkward conversations and possibly a re-test.
The common mistakes are predictable:
- Forgetting cloud services. Microsoft 365, Google Workspace and other software-as-a-service platforms are in scope. If staff use them for business, the accounts need to meet the access control requirements, including MFA.
- Ignoring personal devices. If staff access organisational email or data from their own phones or laptops, those devices are in scope. The only ways to take them out are to stop them accessing organisational data or services altogether, or to rely on the narrow exemption for devices used only for calls, texts or MFA apps.
- Leaving unsupported software lying around. An old operating system on a forgotten machine in a back office can fail the assessment on its own. Either remove it, upgrade it, or segregate it properly and scope it out.
- Choosing a sub-set without a real boundary. You can certify part of an organisation, but only if that part is genuinely separated. A sub-set that shares the same network and accounts as everything else is not a boundary.
Agree the scope in writing internally, compare it with what your device management and identity tools actually report, and resolve the differences before you submit the self-assessment.
Close the gaps the assessor will find
Once scope is settled, prepare for the tests rather than for the questionnaire. A few areas cause most of the failures.
Security update management. Updates rated critical or high by the vendor, or scoring 7 or above on CVSS v3, need to be applied within 14 days of release. Run your own vulnerability scan of a representative set of devices a few weeks before the assessment. If the scan finds missing patches, the assessor's scan will too.
MFA coverage. Most organisations have MFA switched on. Far fewer have it on every account. Service accounts, shared mailboxes with sign-in enabled, old administrator accounts and "temporary" exceptions that were never removed are the usual culprits. Export your user list and check each one.
Malware protection that actually blocks. Having anti-malware installed is not the same as having it configured to stop things. Check that email filtering and browser protections behave as you expect, on every device type in your sample, including Macs and mobile devices if they are in scope.
Administrative access. Day-to-day work should not happen in an administrator account. Make sure admin rights are separate, limited and reviewed, because user access control is tested, not just asked about.
Secure configuration. Remove default passwords, disable auto-run, delete unused accounts and uninstall software nobody needs. These are dull tasks, which is exactly why they get skipped.
Gather evidence early, not when asked
The single biggest time saver is starting evidence collection at the beginning, not at the end. When the assessor asks for something you have not prepared, the clock stops while someone goes looking for it, and that can stretch a planned few days into several weeks.
Useful evidence to have ready before booking:
- A current device list from your endpoint or mobile device management tool, matched against your stated scope.
- Patch compliance reports showing updates applied within the required window.
- An export of user accounts with MFA status, plus a short explanation for any exceptions.
- A record of who holds administrative rights and why.
- Your firewall and router configuration, including any open inbound ports and the business reason for each.
Collecting this also acts as your own rehearsal. If you cannot produce a clean MFA report, you have found a gap while there is still time to fix it.
A realistic sequence
If I were starting from scratch, the order would be: confirm scope, check it against reality, run an internal vulnerability scan and MFA review, fix what you find, gather evidence, complete the Cyber Essentials self-assessment, with the Plus assessment date already pencilled in with your certification body so it falls within the required window after the certificate is issued. Certification bodies book up weeks ahead, so treat the booking as part of the plan rather than an afterthought. Doing the steps in that order means the assessor is confirming work you have already checked, rather than discovering it for you.
None of this is complicated, but it does need someone to own it and to be honest about where the gaps are. If you would like help planning your Cyber Essentials Plus preparation or a second opinion on your scope, get in touch through my contact page, or read more about my services and security strategy work for UK SMEs.