Cyber Essentials Plus: what the technical audit checks and how to prepare
Cyber Essentials Plus adds a hands-on audit to the self-assessment. The assessor scans your internet addresses and a sample of devices for missing updates, sends test malware, watches cloud sign-ins for an MFA prompt and checks everyday accounts can't run admin tasks. One failed test fails the audit unless IASME's minor-issue exception applies.

Cyber Essentials is a UK scheme run for the NCSC by IASME.
Free toolCyber Essentials readiness checkerCheck your answers against the v3.3 requirements before the audit tests them. Nothing you enter is stored.Cyber Essentials Plus checks the same five controls as Cyber Essentials, but an assessor tests them on your systems instead of reading your answers. In practice that means five tests: a scan of your internet-facing addresses, a scan of sampled devices for missing security updates, test malware sent by email and offered for download, a watched sign-in to each cloud service to see whether it asks for multi-factor authentication (MFA), and a check that an ordinary user account can't run an admin task. You can rehearse most of these yourself before the audit day, and this guide covers each one in that order.
It doesn't repeat what Cyber Essentials itself asks for. For the five controls, scope and the basic certificate, read Cyber Essentials explained first.
The document the audit follows
The NCSC publishes the Cyber Essentials Plus Test Specification. Its current version is v3.2, dated 28 April 2025 on the NCSC's Cyber Essentials resources page. It is written mainly for assessors, but the NCSC says applicants may want to read it to understand the test criteria.
Treat it as a model rather than the exact script. The specification says it exists to help the Delivery Partner, IASME, write its own test specifications for its Certification Bodies, so that applicants get the same outcome whichever Certification Body they use. Your Certification Body works to IASME's version.
What the tests check against is the Requirements for IT Infrastructure, currently v3.3, effective from 27 April 2026 according to the NCSC's resources page.
When you can book it
Plus is not a separate route. IASME says the verified self-assessment is a prerequisite, and that you buy Plus by contacting a Certification Body, which quotes for it. The IASME Cyber Essentials page offers a form that passes your details to up to three Certification Bodies, or you can approach one directly. IASME does not list a Plus price: it says the audit is priced by the size and complexity of your network. For comparison, it lists the self-assessment from £320 + VAT for 0 to 9 employees, as listed on 21 November 2026.
The timing rule is in IASME's FAQ: if you achieved the self-assessment certificate less than 3 months before certifying to Plus, you won't need to repeat the self-assessment questions stage. IASME also says the question set is part of the Plus process, so an older certificate may mean answering them again. Both certificates expire after 12 months, IASME says.
The test specification adds that, before any testing, the assessor must:
- get your written permission;
- check that the Plus scope matches the scope on your valid Cyber Essentials certificate, and check it by technical means against the networks being assessed;
- if your scope is not the whole organisation, check by technical means that the parts left out are properly separated;
- agree which devices will be sampled and when they will be tested.
Any issue with these has to be resolved before testing starts. IASME's FAQ says the audit can be run remotely or in person.
The five tests, one at a time
1. A scan from the internet
The assessor identifies every IP address you currently use, including any cloud servers you run (infrastructure as a service), and scans them with a scanner IASME has approved. The stated purpose is to see whether an opportunist attacker on the internet could get in with typical low-skill methods. Each service found on those addresses gets a pass or fail. If your office broadband has a changing IP address, the scope can be defined by DNS names instead. IASME's FAQ describes the audit as including both an internal and an external vulnerability scan.
2. A scan of each sampled device for missing updates
On each sampled laptop, desktop, server and cloud server, the assessor runs an authenticated vulnerability scan, meaning the scanner signs in to the device and looks at what is installed. A device fails if it is missing a fix that has been available for more than 14 days for a vulnerability that the vendor rates critical or high risk, that scores 7 or above on CVSS v3, or for which the vendor gives no severity. That mirrors the 14-day rule in the v3.3 requirements. The specification also says "virtual patching" (blocking an exploit in front of an old system instead of updating it) won't be accepted as a long-term answer for unsupported operating systems.
3. Test malware by email and by web
This runs on sampled user devices, servers with a desktop users sign in to, and cloud servers. The assessor first checks that anti-malware is installed and running. Then:
- They send a plain email with no attachment from an outside, unfiltered account and watch it arrive.
- They send one email per type of test file and watch the user try to open each attachment.
- They have the user browse to a website the Certification Body runs and try to download test files.
Two kinds of file are used. Malware test files are harmless samples that common antivirus products flag; these must be blocked. Executable test files only do something obvious, such as opening a browser page; these must not run without at least a warning that asks the user whether to go ahead. The browser test passes if the user is stopped from reaching the internet, from downloading, or from opening the file. If the test files don't prove the point, the assessor checks the anti-malware logs and its update status by hand instead.
Devices that rely on application allow listing rather than anti-malware are checked differently. The assessor confirms that the trusted root certificates are the operating system's standard set or fewer, that unsigned programs won't run, and that code-signing rules cover every kind of executable file.
4. An observed sign-in to each cloud service
Every cloud service is tested for both user and administrator access. The assessor watches a user sign in with their work account on an untrusted device or in a private (incognito) browser window, or shares an incognito session from their own device if that isn't possible. If the user or admin is asked for a form of MFA before getting in, it passes. Where several services share one sign-in service, for example several apps that all use one company sign-in, the test only needs doing once for that sign-in service. This is the v3.3 requirement that sign-in to cloud services must always use MFA, tested in practice.
5. An everyday account trying an admin task
On each sampled device, and in cloud environments where admin tasks can run, a user signed in with a standard account tries to run an administrative process. It passes only if they are asked for a separate sign-in and the task does not run with their own account. The requirement behind it is separate accounts for admin work.
How many devices get tested
On all but the smallest networks the assessor tests a representative sample, not every device. The specification says that where you build laptops and servers to a standard configuration, a few samples can cover a lot of equipment, and that the number needed depends on how much your devices vary. The assessor must check the sample size has been calculated using IASME's method. IASME's FAQ says the sample is typically around 10 per cent, after which the assessor decides whether more testing is needed.
Cloud services are sampled by account: at least one normal user and one admin user for every cloud service, though the same people can be used across services.
The practical point for a small firm is that a device built differently from the rest, or one person's account set up by hand, is more likely to end up tested on its own.
How the result is decided
Every test and sub-test is marked pass or fail. The specification is blunt: any single fail means the whole assessment fails, unless the specification states an exception. The assessor should still finish every test so you get a complete picture, and can add advisory notes with improvements.
There are two ways a day can end without a straight verdict:
- Deferral. If testing can't finish on the day because of technical problems, the assessor can, at IASME's discretion, defer tests to a later date. The NCSC recommends not deferring for more than one month.
- Minor issues. If failures come from only a small number of minor issues, IASME may still allow a pass. The NCSC expects this to cover marginal deviation in less than 5% of the tests performed, where the evidence doesn't point to a wider failure of your security processes.
Neither is something to plan on. A pass shows the sampled devices and accounts met the tests on the day; it does not make the rest of the year safe on its own.
Rehearsing the audit yourself
Each test can be tried before the assessor arrives. Rehearsing shows you what the assessor is likely to see; it is not a prediction of the result.
- Find every public address. List the IP addresses and DNS names your business uses, including any cloud servers, so the scope you agree matches what the assessor will scan.
- Close the 14-day gap. Check that operating systems, browsers and apps on every in-scope device have installed every critical or high-risk update within 14 days of its release, and remove software that is no longer supported. The requirements allow unsupported software to stay only in a separate sub-set that has no internet traffic in or out.
- Try a private-window sign-in. For each cloud service, sign in as a normal user and as an admin from a private browser window and confirm you are asked for MFA before you reach any data.
- Try an admin task as a normal user. On one device of each build, sign in with an everyday account and try installing software. You should be asked for separate admin credentials. Before removing admin rights from anyone's everyday account, sign in with their separate admin account on that same device and confirm it works, so nobody is left without a way to manage the machine.
- Check anti-malware is on and current on every in-scope Windows and Mac device (unless you use application allow listing instead), and that it is set to block malicious websites as the requirements describe.
- Ask about the test site. The specification says you may need to allow the Certification Body's test file website through your web filter. Ask your Certification Body what it needs and set it up before the day.
- Have people ready. The assessor needs users with working email and browsers on the sampled devices, and a normal and an admin account for each cloud service.
Finally, book the audit while your self-assessment certificate is less than 3 months old if you want to avoid answering the questions a second time, as IASME's FAQ describes.
Common questions
- How soon after Cyber Essentials do we need to do Plus?
- IASME says that if you achieved the self-assessment certificate less than 3 months before certifying to Plus, you won't need to repeat the self-assessment questions stage. The Plus scope must also match the scope on your valid Cyber Essentials certificate.
- Does the assessor test every laptop?
- Not usually. On all but the smallest networks they test a representative sample, sized using IASME's method. IASME's FAQ says this is typically around 10 per cent, and the assessor then decides whether more testing is needed. Cloud services are tested with at least one normal and one admin account each.
- Does one failed test mean we fail?
- Normally yes: the test specification says any single fail fails the whole assessment. IASME can allow a pass where the failures are a small number of minor issues that don't point to a wider failure, and can let tests that couldn't be finished on the day be deferred.
Sources
Every requirement, price and figure in this guide comes from these pages, read on 21 November 2026. Schemes, prices and products change: check the source before you rely on one.
- Cyber Essentials Plus Test Specification, v3.2, 28 April 2025 (NCSC)
- Cyber Essentials: Requirements for IT Infrastructure, v3.3, April 2026 (NCSC)
- Cyber Essentials: Help & resources (NCSC)
- Cyber Essentials (NCSC)
- Cyber Essentials (IASME)
- Frequently Asked Questions (IASME)
Spotted something wrong or out of date? Tell us and we will correct it.
Keep reading
More small business guides
All small business guides
Security and Cyber EssentialsReporting a personal data breach to the ICO: when you must and how
21 Nov 2026 7 minRead
Security and Cyber EssentialsCyber Essentials explained: what it covers, what it costs and how to get certified
19 Nov 2026 8 min