Skip to content

Cyber Essentials Checklist: The Five Controls, Explained for US Companies

A Cyber Essentials checklist covering the five controls, scope, the Plus audit, the question set, and what a US company needs to certify for UK contracts.

Azad KhanBy , Senior GRC & ComplianceOmar KhandakerReviewed by Omar Khandaker, Senior Security ConsultantUpdated 14 min read

Vulnerability Assessment ServicesFrom $1,500 per assessmentFixed scope, free re-scan, no hourly billing.

Get my fixed price

Cyber Essentials is the UK government’s baseline cybersecurity certification, run by the National Cyber Security Centre (NCSC) and delivered through IASME and its licensed certification bodies. It is deliberately narrow: five technical controls that stop the majority of commodity attacks, assessed either by self-assessment (Cyber Essentials) or by an independent technical audit (Cyber Essentials Plus). US companies encounter it when a UK public-sector contract, a Ministry of Defence supply-chain requirement, or a UK enterprise customer puts it on the list.

This checklist walks through the five controls the way an assessor checks them, the scope decisions that trip most applicants up, the Plus audit itself, and what is different for a company outside the UK. A one-page version you can print and tick off follows the five controls. If the audit is already booked, Cyber Essentials Plus readiness testing runs the assessor’s checks before the assessor does.

Cyber Essentials vs Cyber Essentials Plus

Cyber Essentials Cyber Essentials Plus
Method Self-assessment questionnaire, verified by a certification body Hands-on technical audit of your systems by the certification body
Evidence Your answers, signed off by a board member or equivalent Vulnerability scans, device sample checks, and control tests performed on your estate
Timing Certificate valid for 12 months Must be completed within three months of passing the self-assessment
Typical effort Days Weeks, including remediation
Who asks for it UK public-sector contracts as a minimum Government, defense, and enterprise buyers who want independent verification

Plus builds on the self-assessment: you cannot take the audit without first passing the questionnaire, and the audit checks that what you declared is true on a sample of your devices.

Scope: decide this first

Most failed applications go wrong before the controls are even considered.

  • Whole organization or a defined subset? Whole-organization scope is simpler to defend and what most buyers expect. A subset is permitted where it is a clearly separated business unit or network boundary, and it must be named on the certificate.
  • Every device that accesses organizational data is in scope. Laptops, desktops, servers, mobile phones, and tablets, including personal devices under a bring-your-own-device arrangement if they touch company email or data.
  • Home workers are in scope. Their devices are assessed; their home routers generally are not, provided a software firewall is active on the device.
  • Cloud services are in scope. Microsoft 365, Google Workspace, and any SaaS the organization uses are assessed for the controls the customer is responsible for, above all multi-factor authentication. A Microsoft 365 security assessment checks that side of the tenant before the audit does, and our Google Workspace security checklist covers the same MFA settings for Workspace tenants.
  • Unsupported operating systems fail the assessment. An end-of-life OS in scope is an automatic fail unless it is removed or genuinely isolated.

The five controls below follow the NCSC’s Cyber Essentials: Requirements for IT Infrastructure v3.3, dated April 2026. Where this checklist and that document differ, the document wins.

Control 1: Firewalls

What the assessor checks:

  • A boundary firewall or equivalent protects every internet connection, and a host-based firewall is active on every device, including laptops used away from the office.
  • Default administrative passwords on firewalls and routers have been changed to strong, unique ones.
  • Administrative interfaces are not reachable from the internet, or are protected by multi-factor authentication or an IP allow list where remote administration is unavoidable.
  • Every inbound rule that opens a service to the internet is documented with a business justification and an owner.
  • Rules that are no longer needed are removed promptly.

Control 2: Secure configuration

The configuration checks, applied to every in-scope device:

  • Unused accounts, especially default and guest accounts, are removed or disabled.
  • Default passwords are changed on every device and service.
  • Software and services that are not required are removed or disabled.
  • Auto-run and auto-play are disabled so removable media cannot execute code automatically.
  • Devices lock after a period of inactivity and require a PIN, password, or biometric to unlock. Mobile devices enforce a minimum of six characters or biometric unlock.
  • Accounts are protected against brute force: lockout after no more than ten failed attempts, or throttling that keeps guessing impractically slow.

Control 3: Security update management

The patching checks, including the one that fails the most audits:

  • All software in scope is licensed and supported by its vendor. Unsupported software is removed.
  • Automatic updates are enabled wherever the software supports them.
  • Updates that fix vulnerabilities rated critical or high (CVSS version 3 score of 7 or above, or described as critical or high by the vendor) are applied within 14 days of release. This applies to operating systems, applications, firmware, and browser plugins alike.
  • There is a process to discover updates for software that does not update itself, and someone owns it.

The 14-day rule is the control most often failed at the Plus audit, because the authenticated scan of sample devices finds the browser, PDF reader, or runtime that nobody realized was out of date. Monthly vulnerability scanning between audits catches it early. Our vulnerability scanning pricing starts at $1,500 for up to 250 devices.

Control 4: User access control

The account and authentication checks:

  • Every user has a unique account; shared accounts are eliminated.
  • Accounts are created through an approval process and removed promptly when people leave or change roles.
  • Administrative privileges are granted only to those who need them, and administrator accounts are used only for administration, not for email and browsing.
  • Multi-factor authentication is enabled for every user and administrator of every in-scope cloud service that offers it.
  • Password policy meets the scheme’s requirements. Password quality is managed by one of three technical controls: multi-factor authentication, a minimum length of at least 12 characters, or a minimum length of at least 8 characters with a deny list that blocks common passwords automatically. None of the options may set a maximum length. Passwords are also protected against guessing by MFA, throttling (no more than 10 guesses in 5 minutes) or lockout after no more than 10 failed attempts. Passwordless authentication is accepted under the current requirements.
  • Users are told how to choose passwords and what to do if they suspect a compromise.

Control 5: Malware protection

The malware protection checks:

  • Anti-malware software is installed, active, and kept updated on every in-scope device, or application allow-listing is used so only approved software can run.
  • Anti-malware protection scans files on access and blocks known malicious websites.
  • Mobile devices only install applications from approved stores, and application allow-listing is used where the platform supports it.

Sandboxing is no longer accepted as a standalone malware protection option under the current requirements; the choice is anti-malware software or allow-listing.

Cyber Essentials checklist: the five controls on one page

Print this section and tick each line. Every line is a pass condition from the sections above, so a line you cannot tick is a line the assessor will find.

Area Check Done
Scope Scope is the whole organization, or a named subset with a real network boundary
Scope Every device and cloud service that touches organizational data is listed, including BYOD and home workers
Scope No unsupported operating system or software is in scope
Firewalls A boundary firewall covers every internet connection and a host firewall is on every device
Firewalls Default admin passwords are changed and admin interfaces are not reachable from the internet without MFA or an IP allow list
Firewalls Every inbound rule has a documented business need and an owner
Secure configuration Unused accounts, default passwords and unneeded software are removed
Secure configuration Auto-run is disabled and devices lock, with brute-force protection
Security updates Automatic updates are on wherever supported
Security updates Critical and high fixes are applied within 14 days of release
User access Every user has a unique account, and leavers are removed promptly
User access Admin accounts are separate and not used for email or browsing
User access MFA is on for every user of every cloud service that offers it
User access Passwords meet one of the three accepted options
Malware protection Anti-malware is active and updated on every device, or allow-listing is enforced
Plus audit External scan, authenticated device sample scan, malware tests and MFA checks have been rehearsed

IASME also runs a free Cyber Essentials Readiness Tool that asks a series of questions and returns tailored guidance. The NCSC links to it from its Cyber Essentials resources page, next to the current requirements document.

The annual question set

NCSC and IASME revise the requirements roughly once a year, and each version is named and dated. The current version is Requirements for IT Infrastructure v3.3 with the Danzell question set, which applies to assessment accounts created after April 26, 2026. An account created before that date has six months to certify under the previous version (the April 2025 question set, called Willow). v3.3 makes MFA mandatory on every cloud service where it is available, and a missing MFA is an automatic fail. A high-risk or critical update not installed within 14 days is now an automatic fail too. v3.3 also defines a cloud service: an on-demand, scalable service on shared infrastructure, reached over the internet. Earlier versions expanded vulnerability fixes beyond CVSS scores to include vendor-rated critical and high fixes, and accepted passwordless authentication. Always confirm which version your certification body will assess against before you start. (IASME, April 2026 changes)

What the Plus audit actually does

The certification body’s assessor, usually working remotely, performs four kinds of checks within three months of your self-assessment pass:

  1. An external vulnerability scan of your internet-facing addresses, looking for exposed services and known vulnerabilities rated high or critical.
  2. An authenticated vulnerability scan of a sample of devices, sized to your estate and operating-system mix, checking patch status and configuration against the 14-day rule and the secure configuration control.
  3. Malware protection tests on the sampled devices: test files delivered by email and by download, and access to a known-malicious test URL, to confirm the controls block them.
  4. Account and MFA checks, confirming that MFA is enforced on cloud services and that administrator separation is real.

Failures are reported, and a limited window is usually allowed for remediation and re-check before the application is marked as failed.

Where applicants fail, and how readiness testing prevents it

The failures we see are consistent: an unsupported OS on one forgotten machine, a browser or runtime past its 14-day patch window, a cloud service with MFA enforced for administrators but not users, a device with the built-in firewall disabled, and default credentials on a network device nobody logs into. All of them are found by running the same checks the assessor runs, before the assessor runs them. That is why our Cyber Essentials Plus service starts with readiness testing: an external test of the boundary, authenticated checks across the same kind of device sample, and a free retest of anything that failed. We then arrange the Plus audit with an IASME-licensed certification body, which runs the audit and issues the certificate. Invadel is not the certification body.

The readiness check of the boundary looks for the exposed services and missing patches the assessor’s scan will flag. If you also want to know what an attacker could do with what is exposed, that is the job of an external network penetration test, which goes further than the scheme requires.

For US companies

Certification is open to organizations anywhere, and IASME-licensed certification bodies audit overseas applicants remotely. US companies typically pursue it because a UK central government contract involving personal data or ICT services requires it, because a UK prime contractor flows a Ministry of Defence requirement down, or because a UK enterprise customer treats it as a minimum bar alongside SOC 2 and ISO 27001. If you hold one of those and are weighing the other, see ISO 27001 vs SOC 2.

Three practical notes. The scope can be limited to the business unit that serves the UK, provided the boundary is real. The question set uses UK terminology, but the controls are universal, and the evidence a US company already holds for SOC 2 (MFA enforcement, patch management, endpoint protection) covers most of it. Teams that already work from the CIS Controls are in a similar position, because the Implementation Group 1 Safeguards address all five controls. The Cyber Essentials self-assessment fee is set by IASME according to organization size; the Plus audit, readiness testing and any remediation are priced separately.

SOC 2 evidence a US company can reuse

Control SOC 2 evidence you probably hold What Cyber Essentials adds
Firewalls Network diagram, firewall rule reviews A host firewall on every laptop, and a written business need for each inbound rule
Secure configuration Hardening baseline, MDM or endpoint management policy Proof on sampled devices: no default accounts, auto-run off, screen lock enforced
Security update management Patch policy, vulnerability scan reports The fixed 14-day window for critical and high fixes, checked by an authenticated scan
User access control Access reviews, onboarding and offboarding tickets, MFA settings MFA for every user of every cloud service, and separate admin accounts
Malware protection Endpoint protection deployment report Live tests on sampled devices with test files and a test URL

SOC 2 evidence shows the control was designed and operated over a period. The Plus audit checks the devices in front of the assessor on the day, so evidence gets you most of the way through the questionnaire and none of the way through the device sample.

What Cyber Essentials costs for a US company

There are four costs, and only the last two are in your control.

  1. The self-assessment fee. IASME sets it by organization size and you pay it through the certification body. Check the current fee with IASME or your certification body before you budget, because it is revised.
  2. The Plus audit. Each certification body prices it from the size of your estate and the device sample, so get the quote against a written scope.
  3. Readiness testing. Ours is priced as a fixed scope once the estate and the device sample are confirmed, with a free retest of any failed checks.
  4. Remediation and scanning between audits. Validated vulnerability scanning starts at $1,500 for up to 250 devices.

Certification lasts 12 months. At renewal you are assessed against the requirements version current on that date, not the one you passed under, so read the change list each April before you start.

Frequently asked questions

How long does Cyber Essentials take? The self-assessment can be completed in days if the controls are already in place. Plus takes a few weeks including the audit and any remediation, and must be finished within three months of the self-assessment pass.

Is Cyber Essentials the same as ISO 27001? No. Cyber Essentials verifies five technical controls; ISO 27001 certifies an entire information security management system. Many organizations hold both, with Cyber Essentials as the technical baseline and ISO 27001 as the governance framework.

Does it cover phishing? Not directly. The controls reduce what a successful phishing attack can achieve (MFA, least privilege, malware protection), but user awareness is outside the scheme. A social engineering assessment covers that separately.

What happens if we fail the Plus audit? The certification body reports the failures, and most allow a short remediation and re-check period. Readiness testing beforehand is far cheaper than a second audit.

How much does Cyber Essentials Plus cost for a US company? It is the sum of the IASME self-assessment fee, which is set by organization size, the certification body’s Plus audit fee, which depends on your estate and device sample, and any readiness testing and remediation. Ask the certification body for both fees in writing against your scope before you start.

Can a US company use a remote IASME assessor? Yes. Certification is open to organizations anywhere, and IASME-licensed certification bodies audit overseas applicants remotely, including the device sample checks.

Does SOC 2 evidence count toward Cyber Essentials? It helps you answer the questionnaire, because MFA enforcement, patch management and endpoint protection are already documented. It does not replace the Plus audit, which tests a sample of your devices directly.

How often must Cyber Essentials be renewed? Every 12 months. Each renewal is assessed against the requirements version current at the time, and Plus must again be completed within three months of the new self-assessment pass.

Certifying for a UK contract from the US? Scope a readiness assessment and we will run the assessor’s checks first, so the audit confirms what you already fixed.

Azad Khan

Written by

Azad Khan, Senior GRC & Compliance

26+ years in the field. Focus: GRC, ISO 27001 & PCI DSS consulting. Part of the team that scopes, tests, and reports for our clients. Full profile →

Find out what an attacker sees.

Tell us what to test and see your fixed price.

Prefer the full scoping questionnaire? 
Start the conversation

Get a quick proposal

We are online