Skip to main content
Free tool

Cyber Essentials readiness checker

21 questions, each taken from one requirement in the NCSC's Cyber Essentials: Requirements for IT Infrastructure v3.3. Answer them to see which requirements you would likely fail and what to fix first.

This is not an assessment. It can't tell you that you will pass or that you are certified. Only an assessment through IASME or a licensed Certification Body can do that, and the real question set is longer than this check. Use it to find gaps before you apply.

Your answers stay in this browser tab. Nothing is saved or sent, and they are gone when you close the page.

Scope
  1. Will your assessment cover every cloud service your business uses, such as Microsoft 365 or Google Workspace?

    A cloud service here is one you sign in to with a work account that stores or handles your business's data.

    What the requirement says, and how to fix it

    If your organisation's data or services are hosted on cloud services, those services must be in scope. Cloud services cannot be left out.

    If not: List every cloud service staff sign in to for work and include them all. Where the provider runs a control for you, keep the contract or published security statement that commits them to it.

    From: D. Scope, (iv) Cloud services

  2. Will it cover the laptops, desktops, tablets and phones people use for work, including their own phones if they open work email or files on them?

    A personal phone used only for calls, texts or an authenticator app is out of scope.

    What the requirement says, and how to fix it

    A scope that leaves out end-user devices is not acceptable. Personal devices that access organisational data or services are in scope, except those used only for native voice, native text or MFA apps.

    If not: Make a list of every device used for work, including personal phones with work email or files. Either bring them up to the requirements or stop them reaching work data.

    From: D. Scope, overview and (i) Bring your own device

Firewalls
  1. Is every computer protected by a firewall that is switched on, with a software firewall on laptops that leave the office?

    The firewall built into Windows or macOS counts. A laptop used at home or on public Wi-Fi needs its own firewall on.

    What the requirement says, and how to fix it

    Every device in scope must be protected by a correctly configured firewall. Devices used on untrusted networks, such as public Wi-Fi, must use a software firewall.

    If not: Turn on the operating system's own firewall on every computer, and check it stays on (a device management tool such as Intune can enforce it).

    From: E1. Firewalls, Requirements

  2. Has the default admin password on your office router or firewall been changed to a strong, unique one, or remote admin turned off?

    What the requirement says, and how to fix it

    Change default administrative passwords on firewalls to a strong and unique password, or disable remote administrative access entirely.

    If not: Sign in to the router or firewall, set a long unique admin password and keep it in a password manager. Turn off remote admin if you don't need it.

    From: E1. Firewalls, Requirements

  3. Is the router or firewall's admin page closed to the internet?

    Answer yes if it is open only because there is a documented business need and it is protected by MFA or limited to a few trusted IP addresses.

    What the requirement says, and how to fix it

    Block access to the firewall's administrative interface from the internet, unless there is a clear, documented business need and it is protected by MFA or by an IP allow list with properly managed passwords.

    If not: Turn off remote management on the router, or limit it to MFA or a short list of trusted addresses, and write down why it is needed.

    From: E1. Firewalls, Requirements

  4. Does the firewall block incoming connections by default, with every rule that lets traffic in approved, written down with its reason, and removed when it is no longer needed?

    Port forwards on a router are inbound rules.

    What the requirement says, and how to fix it

    Block unauthenticated inbound connections by default. Inbound rules must be approved and documented by an authorised person with the business need, and removed or disabled when no longer needed.

    If not: Review every port forward and inbound rule. Remove the ones nobody can explain, and record who approved each one that stays and why.

    From: E1. Firewalls, Requirements

Secure configuration
  1. Have unused accounts on your computers and devices, such as guest accounts and admin accounts nobody uses, been removed or disabled, and default or guessable passwords changed?

    What the requirement says, and how to fix it

    Regularly remove and disable unnecessary user accounts, such as guest accounts and unused administrative accounts, and change any default or guessable account passwords.

    If not: Check the local accounts on each computer and the accounts on routers, printers and other kit. Disable what nobody uses and change any default passwords.

    From: E2. Secure configuration, Requirements

  2. Have you removed or disabled software and services that aren't needed, and turned off auto-run so files can't run without the user agreeing?

    What the requirement says, and how to fix it

    Regularly remove or disable unnecessary software, including applications, system utilities and network services, and disable any auto-run feature that allows file execution without user authorisation.

    If not: Uninstall software nobody uses (including trial software that came with the device) and switch off auto-run and autoplay.

    From: E2. Secure configuration, Requirements

  3. Does every device need a PIN, password or biometric to unlock, and does it lock or slow down after repeated wrong guesses?

    A PIN or password only used to unlock the device needs at least 6 characters. The device should allow no more than 10 guesses in 5 minutes, or lock after no more than 10 wrong attempts, where it can be set.

    What the requirement says, and how to fix it

    A biometric, password or PIN must be in place before a user can use a device. It must be protected against brute-force guessing (no more than 10 guesses in 5 minutes, or locking after no more than 10 failed attempts, where configurable), and a device-unlock password or PIN must be at least 6 characters.

    If not: Set a screen-lock policy on every device: a PIN or password of at least 6 characters (or biometrics), with a lockout or delay after failed attempts.

    From: E2. Secure configuration, Device unlocking credentials

Security update management
  1. Is every operating system and app on your devices licensed and still supported by its vendor with security fixes?

    Software the vendor has stopped fixing has to come off the device, or the device has to be cut off from the internet in a separate sub-set.

    What the requirement says, and how to fix it

    All software on in-scope devices must be licensed and supported, and removed when it becomes unsupported (or removed from scope with a defined sub-set that prevents all traffic to or from the internet).

    If not: List the operating system and apps on each device, check each vendor's end-of-support date, and upgrade, replace or remove anything past it.

    From: E3. Security update management, Requirements

  2. Are automatic updates turned on wherever the software allows it?

    What the requirement says, and how to fix it

    All software on in-scope devices must have automatic updates enabled where possible.

    If not: Turn on automatic updates for the operating system, browsers and apps on every device, and for router or firewall firmware where it is offered.

    From: E3. Security update management, Requirements

  3. Are critical and high-risk security updates installed within 14 days of release on every device, including routers, firewalls and phones?

    This covers updates the vendor calls critical or high risk, fixes for flaws scored 7 or above (CVSS v3), and updates where the vendor gives no severity at all.

    What the requirement says, and how to fix it

    Updates must be installed within 14 days of release where they fix vulnerabilities the vendor calls critical or high risk, address vulnerabilities with a CVSS v3 base score of 7 or above, or come with no details of the severity they fix.

    If not: Decide who checks updates each week and how you would prove a device is up to date. A device management tool can report which devices are behind.

    From: E3. Security update management, Requirements

User access control
  1. Do you have a set way to create and approve new accounts, and do you remove or disable accounts when someone leaves or stops using them?

    What the requirement says, and how to fix it

    Have a process to create and approve user accounts, and remove or disable accounts when they are no longer required, for example when someone leaves or after a defined period of inactivity.

    If not: Write a short joiners and leavers checklist: who approves a new account, and who disables accounts on the day someone leaves.

    From: E4. User access control, Requirements

  2. Does everyone sign in with their own account, with no shared logins?

    What the requirement says, and how to fix it

    Authenticate users with unique credentials before granting access to applications or devices.

    If not: Give each person their own account. Where a shared mailbox is needed, give people access to it from their own accounts instead of sharing a password.

    From: E4. User access control, Requirements

  3. Is multi-factor authentication (MFA) switched on for every account that signs in to your cloud services?

    That means every user in Microsoft 365 or Google Workspace, and every other cloud service you use for work, not only the admins.

    What the requirement says, and how to fix it

    Implement MFA where available. Authentication to cloud services must always use MFA.

    If not: Turn MFA on for every user of every cloud service. An authenticator app or a security key is better than a text message, though any MFA is better than none.

    From: E4. User access control, Requirements

  4. Do people who do admin work use a separate admin account only for that, never for email or browsing?

    What the requirement says, and how to fix it

    Use separate accounts to perform administrative activities only: no email, web browsing or other standard user activities.

    If not: Give each admin a second account used only for admin work, and take admin rights off their everyday account.

    From: E4. User access control, Requirements

  5. When someone changes role, do you take away admin rights and access they no longer need?

    What the requirement says, and how to fix it

    Remove or disable special access privileges when no longer required, for example when a member of staff changes role.

    If not: Review who has admin rights at least every few months and whenever someone changes role, and remove what isn't needed.

    From: E4. User access control, Requirements

  6. Do accounts used by your IT supplier, contractors or managed service provider follow the same rules, and could you show that they do?

    What the requirement says, and how to fix it

    All accounts your organisation owns are in scope, even when a supplier, contractor or managed service provider uses them. If you use externally managed services, you must be able to confirm the controls are met.

    If not: Ask your IT supplier, in writing, how their accounts on your systems meet each requirement (separate admin accounts, MFA, removal when no longer needed).

    From: D. Scope, (v) Accounts used by third parties, and E4. User access control

  7. Where people sign in with a password and no MFA, are passwords protected against guessing and long enough?

    Protected means a lockout after no more than 10 attempts or a delay that grows with each wrong guess. Long enough means at least 12 characters, or at least 8 with common passwords blocked. Answer yes if every sign-in uses MFA.

    What the requirement says, and how to fix it

    Password-based authentication must be protected against brute-force guessing (MFA, throttling to no more than 10 guesses in 5 minutes, or locking after no more than 10 attempts), and password quality managed with MFA, a 12-character minimum, or an 8-character minimum with a deny list of common passwords, with no maximum length.

    If not: Set the password policy in your identity system (for example Microsoft Entra ID or Google Workspace): a minimum length of 12, or 8 with banned common passwords, plus lockout. Better still, use MFA everywhere.

    From: E4. User access control, Password-based authentication

Malware protection
  1. Does every Windows and Mac computer have anti-malware switched on and kept up to date, set to stop malware running and to block malicious websites?

    Protection built into the operating system counts if it does all of this. So does allowing only approved, signed apps to run.

    What the requirement says, and how to fix it

    A malware protection mechanism must be active on all devices in scope. Anti-malware software must be updated in line with the vendor's recommendations, prevent malware and malicious code from running, and prevent connections to malicious websites. Application allow listing is the other option.

    If not: Check each computer's protection is on, updating, and has web protection turned on. A device management tool can report any computer where it is off.

    From: E5. Malware protection, Requirements

  2. On phones and tablets used for work, can people install only approved apps that are properly signed?

    For phones and tablets the requirements describe application allow listing: only approved, code-signed apps run, and users can't install unsigned ones.

    What the requirement says, and how to fix it

    Application allow listing: only approved applications, restricted by code signing, may run. You must approve applications before deploying them and keep a current list; users must not be able to install unsigned applications or ones with an invalid signature.

    If not: Keep a list of the apps approved for work phones and tablets, and block installing apps from outside the approved, signed sources (device management can enforce this).

    From: E5. Malware protection, Application allow listing

When you are ready

  1. Build a fuller action plan with the free Cyber Essentials Readiness Tool (IASME, for the NCSC), and read the free preview of the assessment questions (IASME).
  2. Get help if you need it: free advice from an NCSC-assured Cyber Advisor (IASME), or find a Certification Body (IASME).
  3. Apply through the official route: buy a Cyber Essentials assessment (IASME). Our Cyber Essentials guide explains the cost, the routes and what the controls mean.

Questions based on Cyber Essentials: Requirements for IT Infrastructure v3.3 (NCSC, in effect from 27 April 2026), read on 19 November 2026. Spotted something out of date? Tell us.