Official documents · PDF

NCSC Cyber Essentials Plus Test Specification v3.2

The official NCSC specification that tells assessors how to run a Cyber Essentials Plus audit: prerequisites, sampling, the five test cases and the pass and fail rules. Summary and link to the original PDF.

Official documentUpdated 3 November 2026
Short answer

The Cyber Essentials Plus Test Specification v3.2 defines the five test cases an assessor runs: remote vulnerability assessment, authenticated patch scan, malware protection checks, MFA configuration on cloud services, and account separation. It sets the pass rule that any single sub-test fail fails the assessment, and the exception for marginal deviation in under 5% of tests.

Key takeaways

  1. The NCSC Cyber Essentials Plus Test Specification v3.2 defines five test cases: remote vulnerability assessment, authenticated patch scan, malware protection, MFA configuration and account separation.
  2. Under v3.2, any single sub-test fail fails the assessment, unless only marginal deviation is found in under 5% of tests and the Delivery Partner allows a pass.
  3. Every cloud service is tested with at least one normal user and one administrative user, and the assessor keeps the sample-size evidence for the lifetime of the certificate.
At a glance
Format
Access
Who it is for
Sections
Written against
Last updated
Official document

NCSC Cyber Essentials Plus Test Specification v3.2

Published by the NCSC or IASME. We link to the original rather than re-host it. Opens in a new tab.

Open the original

What is this document?

The NCSC's instructions to Cyber Essentials Plus assessors, published as a PDF by the NCSC. It exists so that "Applicants should be able to expect the same certification outcome, no matter which Certification Body they ultimately use". Every Plus audit runs the five test cases in it.

What does each test case check?

The Cyber Essentials Plus hub explains each in full, with what the assessor runs and how to prepare for each test.

What does it say about sampling?

All cloud services are tested with at least one normal user and one administrative user per service; the same users can cover several services. Devices are sampled to be representative, and the assessor must verify the sample size was calculated with the Delivery Partner's method and retain the evidence for the lifetime of the certificate.

Note

What changed in how the specification is applied from April 2026?

IASME's April 2026 update added two rules on top of the v3.2 specification.

IASME gives the reason for the first rule: some organisations updated only the devices in the sample. Patch the whole scope before the day.

How do you prepare for each test case?

The Cyber Essentials Plus day post walks through the audit in the order it runs, and how to prepare gives the remediation order.

What is inside

#Section
01Purpose and before you begin: permissions, scope match, sub-set verification, sampling
02General prerequisites: test emails, test files, users and browsers
03Success criteria: pass, fail and advisory notes
04Test case 1: remote vulnerability assessment
05Sample testing: devices, servers, cloud services, one user and one admin per service
06Test case 2: check patching by authenticated vulnerability scan
07Test case 3: check malware protection (sub-tests 3.1 and 3.2)
08Test case 4: check multi-factor authentication configuration
09Test case 5: check account separation
10Conclude the assessment, deferral and the marginal-deviation exception
11Appendix A: vulnerability scanning; Appendix B: types of test file

Frequently asked questions

Assessors. It addresses the assessor directly and includes notes for the Delivery Partner. Applicants can read it to see what will be tested; the preparation workbook on this site turns it into a set of self-checks.

Where a fail results from a small number of minor issues, the Delivery Partner may at their discretion allow a pass. The specification expects this to cover marginal deviation in less than 5% of performed tests where the evidence does not indicate a wider failure of the applicant's processes.

The specification is still v3.2, but IASME changed how it is operated from April 2026. A failed update management sample is remediated and retested on the original sample plus a new random sample, and a second failure revokes the verified self-assessment certificate. The self-assessment must also be finalised and unchanged before Plus testing starts.

IASME's FAQ says that if your verified self-assessment certificate is less than three months old when you certify to Cyber Essentials Plus, you do not need to repeat the self-assessment stage. Book the audit when you book the self-assessment so the dates line up.

Yes, with the Delivery Partner's agreement, where the day cannot be concluded because of technical difficulties. The specification recommends not allowing deferral for more than one month.

More from the library

Cyber Essentials Plus

Ready for the technical audit?

A 20-minute scoping call with an IASME-accredited assessor fixes your scope and device sample, then you get a written price from £3,000 + VAT within 48 hours and testing booked inside your three-month window.

  • IASME Certification Body
  • CREST accredited
  • UK offices in Leeds, Newcastle, London and Edinburgh
Sources