Guides

Are ChatGPT, Copilot and other AI tools in scope for Cyber Essentials?

AI tools are not named in the rules, but a work AI account fits the v3.3 cloud service definition: list it in A2.9, apply MFA (A7.16, A7.17), control accounts.

By Precursor SecurityIASME Certification Body
Published
Reviewed
Reading time
10 min

Reviewed against Requirements v3.3 and Danzell v16.3.

Short answer

Cyber Essentials v3.3 never mentions AI tools. An AI service such as ChatGPT or Copilot Chat that staff sign in to with a work account and use with organisational data fits the v3.3 definition of a cloud service in our reading, so it is in scope: list it, apply MFA for users and administrators, and control who has accounts.

Key takeaways

  1. The NCSC Requirements for IT Infrastructure v3.3 do not name AI tools; this guide applies the v3.3 cloud services rules to them, and that application is our interpretation.
  2. v3.3 defines a cloud service as on-demand, scalable, hosted on shared infrastructure, accessed via an account and storing or processing your organisation's data, and says cloud services cannot be excluded from scope.
  3. For SaaS, the v3.3 responsibility table puts user access control on your organisation, so MFA for every user and administrator (A7.16, A7.17) is your job, and a no to either fails automatically.
  4. AI browser extensions and desktop apps are software under v3.3, which lists extensions in its definition, so they must be licensed, supported and updated within 14 days for critical fixes (A6.5).
Key facts
Named in the requirements?
How they are treated (our interpretation)
Must list
Automatic fails
Extensions and apps

Staff are using AI assistants, whether or not there is a policy for it. The question we get during assessments is whether those tools belong in the Cyber Essentials scope. The short answer is that the requirements never mention AI, but they do define a cloud service, and most AI tools used for work fit that definition. This guide applies the v3.3 rules, labels clearly where we are interpreting, and lists the questions that are affected. Facts were checked on 9 November 2026.

Do the Cyber Essentials requirements mention AI tools?

No: neither the NCSC Requirements for IT Infrastructure v3.3 nor the Danzell question set names ChatGPT, Copilot, Gemini or AI in general.

That is not a loophole. The scheme is written in terms of devices, software, accounts and cloud services, and leaves you to decide which category each tool falls into. Every AI tool your staff use falls into at least one of them.

Our interpretation

Is an AI chat service a cloud service under Cyber Essentials?

Yes, in our reading: when staff sign in with a work account and use it with organisational data, it meets the v3.3 definition of a cloud service.

The scheme requires you to apply this definition from v3.3: a cloud service is "an on-demand, scalable service, hosted on shared infrastructure, and accessible via the internet". For Cyber Essentials, it "will be accessed via an account (which may be credentials issued by your organisation, or an email address used for business purposes), and will store or process data for your organisation." Question A7.14 prints the same definition.

A ChatGPT, Claude, Gemini or Copilot Chat account opened with a work email and used to draft documents or summarise files meets each part. v3.3 then states that if your data or services are hosted on cloud services, "these services must be in scope. Cloud services cannot be excluded from scope." Question A2.9 asks you to list them all, and the question set adds that social media accounts count too, so the bar for what counts is low.

Who is responsible for which controls on an AI service?

For SaaS, v3.3 says user access control is typically yours, configuration is shared, and firewalls, updates and malware protection are typically the provider's.

v3.3 also says "the applicant organisation is always responsible for ensuring all controls are implemented". Where the provider implements a control for you, v3.3 says you must make sure the provider "has committed to implementing this via contractual clauses or documents referenced by contract", such as published security statements.

What do you have to do for MFA on AI tools?

The scheme requires MFA for every user and every administrator of every cloud service that offers it, and a no to either question is an automatic fail.

A7.16AUTO-FAIL covers administrators and A7.17AUTO-FAIL covers users. The question set says MFA must be used "in conjunction with a password of at least 8 characters", and that "the assessment will fail if the answer is no." If an AI tool genuinely offers no MFA, list it in A7.15AUTO-FAIL, but that question also fails automatically if a service you list does offer MFA.

In practice there are two routes. One is single sign-on through your identity provider, so your existing MFA policy applies to the AI tool. The other is the tool's own MFA setting, which each user turns on. The table shows what each vendor's help pages said on 9 November 2026; plans and settings change, so recheck before you submit.

Our interpretation
Common failure

Which user access control rules apply to AI accounts?

All of them: accounts must be approved, unique to a person, limited to what the job needs, and removed when no longer required.

The scheme requires a process to create and approve user accounts (A7.1), least privilege (A7.4), separate administrator accounts for administration (A7.6), and removal of unnecessary accounts (A5.2). For AI tools that means no shared team login, no admin role for everyday users, and an owner who removes leavers.

Recommended, not required

Are AI browser extensions and desktop apps in scope?

Yes: v3.3 defines software to include "extensions", so AI extensions and installed apps on in-scope devices must meet the security update management rules.

The scheme requires all software on in-scope devices to be "licensed and supported" and critical or high-risk fixes to be installed within 14 days of release. A6.2 adds that unsupported software must be removed, and "this includes frameworks and extensions". A6.5AUTO-FAIL applies the 14-day rule to "software (including any associated files and extensions)" and is an automatic fail on a no. If you protect devices by limiting installation to approved applications (option B in A8.1), A8.5 requires a current list of approved applications.

Our interpretation

What about AI services your developers build on?

Platforms your developers use to build AI features are cloud services, usually SaaS or PaaS, so they go in the A2.9 list and their administrator accounts need MFA under A7.16.

v3.3's software development section says "Bespoke and custom components of web applications are out of scope" and points to the UK Government's Software Security Code of Practice; its change log reads "Software Security Code of Practice introduced in Software Development section". Our software development scope page explains where the boundary sits. Cyber Essentials does not assess the AI features you build or the data you send to a model provider; for that, see Cyber Essentials and UK GDPR.

What about AI apps connected to Microsoft 365 or Google?

An AI meeting note-taker, email assistant or agent that a user connects to your Microsoft 365 or Google tenant is a separate cloud service in our reading, and it also holds a permission inside your tenant.

The service itself goes in the A2.9 list and needs MFA on its own accounts (A7.16, A7.17) if it has a login. The permission is the part teams miss: when a user clicks "accept" on a consent screen, the app can read mail, files or calendars without any further sign-in. A7.1 requires a process to approve accounts, and A5.1 asks you to check cloud services and "disable any services that are not required for day-to-day use".

Recommended, not required

What should you do before your next assessment?

Find every AI tool in use, decide which are approved, and treat each approved one like any other SaaS.

  1. Inventory AI services from expense records, single sign-on logs and a short staff survey.
  2. Add each one used with work data to your A2.9 cloud services list. See cloud services in scope.
  3. Turn on MFA for every user and administrator, preferably through single sign-on. Follow the Microsoft 365 and Entra ID setup guide if you use Microsoft.
  4. Remove unsupported or unapproved AI extensions and apps, and turn on automatic updates for the rest.
  5. Name an owner for each service who approves accounts and removes leavers.

Then check your readiness against the full 2026 question set. If you would rather an assessor reviewed your cloud services list before you submit, Precursor Security's gap analysis starts from £500, and Cyber Essentials from £1,500 with the IASME fee included.

Frequently asked questions

If staff use it for work with an organisational account or business email, yes, in our interpretation. A2.9 asks for all cloud services provided by a third party and says they cannot be excluded from scope. v3.3 defines a cloud service as accessed via an account, which may be a business email address, that stores or processes data for your organisation. A work ChatGPT account fits.

Our view is that Copilot features reached through your Microsoft 365 sign-in are part of the Microsoft 365 service you already list, protected by the same Entra ID account and MFA. A separately purchased AI service with its own login is a separate cloud service. Microsoft says Copilot Chat users should sign in with their Microsoft Entra account to get enterprise data protection.

List it in A7.15 as a service that does not provide MFA, but check carefully first. The question set says A7.15 fails automatically if a service you list does offer MFA. If it truly has none, the password-based authentication rules in v3.3 still apply to the accounts, including protection against brute-force guessing (A7.10).

Yes, in our reading, whoever paid. The v3.3 cloud service definition has two parts: the service is accessed via an account, which 'may be credentials issued by your organisation or an email address used for business purposes', and it stores or processes data for your organisation. A free or paid AI account opened with a work email and used for work meets both, so list it in A2.9 and make sure MFA is on (A7.17).

Possibly. The v3.3 cloud service definition covers accounts using 'credentials issued by your organisation or an email address used for business purposes'. In our reading, a personal address that staff use for work can meet the second part, so the account may be in scope. The safer route is to move that work to an approved work account, list the service in A2.9 and turn on MFA.

It can be. v3.3 defines software to include extensions, and A6.2 says unsupported software, including extensions, must be removed. A6.5 applies the 14-day rule for critical updates to extensions. If you protect devices by limiting installation to approved applications (option B in A8.1), A8.5 requires an approved list. An unmaintained extension from an unknown developer fails all three tests.

No. Cyber Essentials covers technical controls on accounts, devices and software, not what data people share with a service or how the provider uses it. That is a data protection and acceptable use question. See our guide to Cyber Essentials and UK GDPR for what the scheme does and does not cover.

Free readiness check

Would you pass the 2026 question set?

Answer 24 yes or no questions, built by Precursor Security, an IASME Cyber Essentials Certification Body, and get a readiness score in about five minutes, with any auto-fail questions you miss flagged first in your results.

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

Scheme changes, once a month

Question-set updates, end-of-support dates and what our assessors are failing this month. No sales sequence. What each issue covers.

Your email is used only to send these updates. Unsubscribe in one click. Read the privacy policy.