Cyber Essentials Plus Test 3: the malware protection tests
How the Cyber Essentials Plus assessor tests malware protection: the email test files, the browser download test files, the manual log checks, and the certificate-based allow-listing checks, with the pass and fail wording from the specification.
Test case 3 of Cyber Essentials Plus checks that every sampled device has working malware protection. For anti-malware software the assessor sends test files by email and by browser download: malware files must be blocked and executables must at least prompt before running. Manual log checks cover what test files cannot prove. Allow-listing devices must refuse unsigned executables.
- Test purpose
- To check that all the devices in scope benefit from at least a basic level of malware protection
- Applies to
- Sampled end user devices, servers that provide a user-interactive desktop, and IaaS instances
- Sub-tests
- 3.1.1 email, 3.1.2 browser, 3.1.3 manual checks (anti-malware software); 3.2 (certificate-based application allow listing)
- Test files
- Malware test files (must be blocked) and executable test files (must at least warn and prompt), hosted by the Certification Body (Appendix B)
- Pass rule
- A fail on 3.1 or 3.2 for devices using that method fails the test case
- Control tested
- Malware protection (A8), with secure configuration auto-run (A5.8)
What does Test 3 check?
Test 3 checks that the malware protection you declared at A8.1 works on each sampled device: anti-malware must stop test files delivered by email and browser, and allow listing must stop unsigned applications running.
The self-assessment asks in A8.1 which malware protection option each device uses: anti-malware software (option A) or application allow-listing (option B). Test 3 verifies that choice on the sampled devices. The assessor first identifies which method each device uses, then runs the matching sub-tests.
For each device in the sample set, check that the anti-malware software is installed and running. Depending on the software being used, the assessor will determine whether to test the requirement using test files as described in sub-tests 3.1.1 and 3.1.2 or through manual checks as described in sub-test 3.1.3.
What are the test files?
The Delivery Partner supplies a comprehensive set of inert test files to the Certification Body, which tailors a sub-set to each applicant's platforms. A Mac-only estate is not tested with Windows file types; a mixed estate gets a wider set. Appendix B distinguishes two groups with different pass criteria.
Malware test files: anti-malware should detect these and block the user from accessing them. Executable test files: the user should at least see a warning and a prompt that allows them to decide whether or not to proceed.
- Container formats such as .zip and .gz that the environment can process.
- File types executable by default on common platforms, both native binaries and scripting languages.
- Document and spreadsheet types users regularly receive, containing inert malware samples.
- Executable test files launch obvious behaviour (opening a browser page or a dialog) so the assessor can see execution immediately.
- Malware samples are specific inert files known to be flagged by the majority of common antivirus products.
Sub-test 3.1.1: what happens with the email test?
Performed on any sampled device or service where a user can receive email. The assessor uses an external mail system that performs no filtering and is not deny-listed, so the result reflects your defences rather than the sender's.
Establish a baseline by sending a simple email from your remote test account, with no attachments. Observe the user to verify that this email arrives successfully. Determine what types of file you should test for and ready your test emails. You'll need one email for every type of file to be tested. Attempt to send each test email from your remote test account to the test destination. Observe the user attempting to open each attached test file. If any of the malware test files arrive successfully and the user is not blocked from accessing them then record a fail. If any of the executable test files arrive successfully and can be executed without a prompt that requires additional user interaction then record a fail. Otherwise, record a Pass result for this sub-test.
Sub-test 3.1.2: what happens with the browser download test?
Performed on any sampled device where a user can browse the web. The files are hosted on an external website owned by the Certification Body. You are asked to configure your web filter so this site receives the same level of filtering as most other allowed sites, because the test assumes there is always some allow-listed site a user can download from.
Observe the user access the internet, if they are prevented from accessing the internet record a Pass for this sub-test. Observe the user attempting to download approved test files, if the user is prevented from downloading the approved test files, record a Pass. If the test files are blocked on access record a Pass. If any of the malware test files download successfully and the user is not blocked from accessing them record a fail. If any of the executable test files download successfully and can be executed without a prompt that requires additional user interaction record a fail.
Sub-test 3.1.3: when do manual checks apply?
Where the test files did not prove the software is configured correctly (for example on a server without a mail client, or where a product's behaviour cannot be demonstrated with files), the assessor performs manual checks on every sampled device using anti-malware software.
The anti-malware software is installed and operational through investigation of logs, and the anti-malware software is updated in accordance with the vendor's configuration instructions. If both checks are carried out and confirm the anti-malware software is installed and configured correctly record a Pass for this sub-test, if not record a fail.
Sub-test 3.2: how is application allow-listing tested?
For devices that rely on certificate-based application allow-listing (option B in A8.1), the assessor checks four things on each sampled device.
The list of trusted root certificates is the standard set as provided by the operating system manufacturer, or a subset thereof; additional trusted root certificates are added only with the Applicant's explicit agreement; an unsigned executable, and an executable signed with a certificate that does not chain to a trusted certificate, will not execute on the device; operating system policy settings are appropriate to ensure code signing applies to all executable file formats, as applicable to the device. If all of these are true, record a Pass result for this sub-test. Otherwise, record a Fail result.
How do you pass Test 3?
- Confirm the anti-malware agent is installed, running and reporting on every sampled device, including servers with a desktop and IaaS instances. Check the console for devices that have not reported in.
- Make sure definitions and the engine update per the vendor's instructions (A8.2), and that real-time protection and web protection are on so malicious sites are blocked (A8.3).
- Disable auto-run and auto-execution of downloaded files (A5.8), so executables prompt rather than run.
- Test the email path yourself: send an inert test file such as the EICAR string from an external mailbox and confirm it is blocked at the gateway or on the device.
- If you use a web filter, allow the Certification Body's test site at the same level as ordinary sites, so the test reflects device protection rather than the filter alone.
- For allow-listing (AppLocker, WDAC, Apple managed apps), test an unsigned executable on a sampled device and confirm it is refused.
How do assessors check this?
Related pages
- Cyber Essentials Plus overviewPrerequisites, the five test cases, sampling, pass rules and price
- Test 2: authenticated patch scanFail if a CVSS 7 or above fix has been available for more than 14 days
- Test 4: MFA on cloud servicesObserved login from an untrusted device or incognito session
- Sample sizeHow devices and cloud accounts are sampled
- Pass and fail rulesAny single fail fails the assessment, the under-5% exception, deferrals and the 2026 update management retest rule
- How to prepare for Cyber Essentials PlusPatch first, MFA second, admin separation third
- Cyber Essentials Plus checklistWhat the assessor tests on the day
- CE Plus test specification v3.2The NCSC document the audit follows
Frequently asked questions
No. The test files are inert samples that common antivirus products recognise, plus harmless executables that do something visible such as opening a browser page.
The email sub-test passes if the user is blocked from accessing malware test files and executables at least prompt. The browser test and the manual log checks still apply to the device itself.
Only servers that provide a user-interactive desktop are in this test case, and only where a user can receive email or browse the web on them. Otherwise the manual checks in 3.1.3 apply.
Yes. The A8.2 guidance states that, for the avoidance of doubt, Windows Defender is suitable. On the day it still has to be active, updated in line with Microsoft's instructions, prevent malware running and block malicious websites (A8.2 and A8.3), so check real-time protection and SmartScreen on every sampled build.
That the trusted root certificate list is the vendor's standard set or a subset, extra roots need explicit agreement, unsigned or wrongly signed executables will not run, and policy applies code signing to all executable formats.
Phones and tablets typically rely on the platform app store and code signing (option B). The assessor checks that users cannot sideload unsigned apps and that the device policy enforces it (A8.4 and A8.5).
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
- NCSCNCSC, Cyber Essentials Plus Test Specification v3.2Read on ncsc.gov.uk (opens in a new tab)
- NCSCNCSC, Cyber Essentials: Requirements for IT Infrastructure v3.3 · April 2026Read on ncsc.gov.uk (opens in a new tab)
- IASMEIASME, Cyber Essentials and Cyber Essentials Plus: what is the difference? · 3-month window, 30 days to remediateRead on iasme.co.uk (opens in a new tab)
- IASMEIASME, Important update: changes to Cyber Essentials for April 2026 · Update management retest and revocationRead on iasme.co.uk (opens in a new tab)
- IASMEIASME, Cyber Essentials terms and conditions · Clauses 2.4 and 2.6: 12-month validity, free resubmission within 48 hours of the fail noticeRead on iasme.co.uk (opens in a new tab)
- IASMEIASME, Cyber Essentials frequently asked questionsRead on iasme.co.uk (opens in a new tab)