Skip to main content

Blog

Cyber Essentials and Cloud Services: What Counts, What Is Yours, and the One Question That Fails You

Key takeaways

  • A cloud service is anything reached over the internet with an account that holds your data. None of it can be left out of scope.
  • Who does each control depends on the model: with SaaS the provider runs boundary and patching; with IaaS the virtual machines are yours.
  • User access control is always yours: MFA on, admin roles separate, leavers removed. The provider cannot do that for you.
  • Saying a service has no MFA option when it does is an automatic fail. Check every service; link a sign-in with MFA where there is none.

Ten years ago a small business's IT was a cupboard with a server in it. Today it is a login page. Email, files, accounting, payroll, the CRM, the phone system, the backups: most of it runs on someone else's computers, reached through a browser.

Cyber Essentials caught up with that some time ago, and in a way that trips people up. The scheme is explicit that cloud services are always in scope, it asks you to list every one you use, and one of its three automatic fails is a cloud question. At the same time, the five controls mean something different for a service you rent than for a laptop you own.

This article sets out what counts as a cloud service, which of the five controls are the provider's job and which are yours, and how to answer the MFA question without failing on it. The NCSC requirements are the authoritative source; check anything here against them.

What counts as a cloud service

The scheme's definition is broader than "we use the cloud" usually means. A cloud service is one that is:

  • on demand and scalable, so you pay for what you use rather than running it;
  • hosted on shared infrastructure you do not control;
  • reached over the internet, through an account;
  • and it stores or processes your organisation's data.

That covers the obvious (Microsoft 365, Google Workspace, Dropbox, Xero, HubSpot) and the less obvious: the payroll portal, the online backup, the website host, the e-signature tool, the project board, the video-calling service, the virtual server you rent to run an old application. If staff log into it for work and it holds anything of yours, it counts.

Watch out: cloud services cannot be excluded from scope. You can, in some circumstances, certify a subset of your organisation, but every cloud service that subset uses stays in, and the questionnaire asks you to list them all. A list that misses the accountant's portal is a wrong answer, not a small one.

Listing every cloud serviceEmail and calendar; Files and document storage; Accounting, invoicing and payroll; CRM, sales and marketing tools; HR, recruitment and e-signature; Video calling, chat and phone system; Backups and archiving; Website and domain hosting; Virtual servers, databases or hosting you rent to run your own software; Anything a department signed up for with a company card;Listing every cloud serviceEmail and calendarFiles and document storageAccounting, invoicing and payrollCRM, sales and marketing toolsHR, recruitment and e-signatureVideo calling, chat and phone systemBackups and archivingWebsite and domain hostingVirtual servers, databases or hostingyou rent to run your own softwareAnything a department signed up forwith a company card

Three models, and who does what

How much of each control is yours depends on how much of the stack you control. The scheme uses the three standard models:

  • Software as a service (SaaS): you use an application the provider runs. Microsoft 365, Google Workspace, Xero, Salesforce.
  • Platform as a service (PaaS): you deploy your own code or data onto a platform the provider runs. A managed database, a web app host, a function platform.
  • Infrastructure as a service (IaaS): you rent virtual machines, storage and networks and run whatever you like on them. A Windows server in Azure or AWS is a server; it just lives elsewhere.
ControlSaaSPaaSIaaS
FirewallsProvider runs the boundary; you protect admin accessProvider, mostly; you set any exposure of your appYours: the virtual firewall and the rules on it
Secure configurationShared: the provider secures the service, you set the tenantShared: the platform is theirs, your deployment is yoursYours: the operating system and everything on it
User access controlYours: accounts, MFA, admin roles, leaversYoursYours
Malware protectionProvider, for the service; your devices are still yoursSharedYours: protection on each virtual machine
Security updatesProvider patches the service; you patch what reaches itProvider patches the platform; you patch your code's dependenciesYours: every operating system and application, within 14 days

Two things stand out. User access control is yours under every model, because nobody else can decide who in your organisation gets an account, whether MFA is on, or when a leaver loses access. And a rented virtual machine carries exactly the obligations of a physical one: supported operating system, patches within 14 days, malware protection, a firewall. Moving a server to the cloud moves the hardware, not the responsibility.

Tip: the requirements document carries the scheme's own table of responsibility by model. When you are unsure which column you are in, that table is the final word, not the provider's marketing page.

The split for a typical SME on SaaSThe provider does compared with You do. Boundary: The provider does, Firewalls around the service; You do, Keep admin access to the console behind MFA, never open to the internet. Patching: The provider does, The service itself; You do, The browsers, laptops and phones that reach it, within 14 days. Accounts: The provider does, Offers MFA and admin roles; You do, Turns MFA on for everyone, separates admin accounts, removes leavers. Settings: The provider does, Secures the platform; You do, Sets the tenant: sharing, guest access, legacy sign-in methods off. Malware: The provider does, Filters the service's mail and files; You do, Keeps protection on and updating on every device.The split for a typical SME onSaaSThe provider doesYou doBoundaryFirewalls around theserviceKeep admin access tothe console behindMFA, never open tothe internetPatchingThe service itselfThe browsers, laptopsand phones that reachit, within 14 daysAccountsOffers MFA and adminrolesTurns MFA on foreveryone, separatesadmin accounts,removes leaversSettingsSecures the platformSets the tenant:sharing, guestaccess, legacysign-in methods offMalwareFilters the service'smail and filesKeeps protection onand updating on everydevice

The five controls, in the cloud

What each control means for the cloud services you use1. Firewalls: The provider runs the boundary; your admin access to the console is behind MFA and never open to the internet 2. Secure configuration: The tenant's defaults are yours to set: external sharing, guest access, legacy sign-in methods, unused apps 3. User access control: MFA for every user and admin on every service; admin roles separate; leavers removed from the cloud directory 4. Malware protection: The provider's mail filtering does not replace protection on your devices; virtual machines need their own 5. Security update management: SaaS is patched by the provider; rented servers and the browsers that reach the cloud are yours, within 14 daysWhat each control means for thecloud services you use1FirewallsThe provider runs the boundary; youradmin access to the console is behindMFA and never open to the internet2Secure configurationThe tenant's defaults are yours toset: external sharing, guest access,legacy sign-in methods, unused apps3User access controlMFA for every user and admin on everyservice; admin roles separate; leaversremoved from the cloud directory4Malware protectionThe provider's mail filtering does notreplace protection on your devices;virtual machines need their own5Security update managementSaaS is patched by the provider;rented servers and the browsers thatreach the cloud are yours, within 14days

Firewalls

For SaaS, the provider runs the boundary and you cannot touch it. Your part is the way in for administrators: the admin console must sit behind MFA and must not be reachable from anywhere with a password alone. For IaaS, the virtual network and its firewall rules are yours. "It's in the cloud" does not mean a server can be left listening to the whole internet; the default-deny rule applies to a security group exactly as it applies to a router.

Secure configuration

A new Microsoft 365 or Google Workspace tenant is not configured the way the scheme expects; it is configured the way the provider ships it. Switching off older sign-in methods that bypass MFA, deciding who can share files outside the organisation, removing guest accounts nobody uses, disabling apps nobody asked for: these are configuration choices, and they are yours. For a rented server, everything the secure-configuration control says about a physical one applies unchanged.

User access control

This is the control that does not move whichever model you use. Every person has their own account on every service. Administrators of the tenant use separate accounts for that work and ordinary accounts for email. Leavers are removed from the cloud directory the day they leave, which also removes them from everything that signs in through it. And multi-factor authentication is on for every user, on every service that offers it.

In the tender: "the supplier must hold a valid Cyber Essentials certificate" does not say anything about the cloud, and does not need to. Every service you use is inside the certificate's scope automatically.

Malware protection

For SaaS, the provider filters the service's mail and scans its files; that is their part. It does not change the requirement on your side: protection on, updating and scanning on every laptop, desktop and phone that reaches the service. The attachment the filter missed still lands on a device. For a rented virtual machine, malware protection on the machine is yours to install and keep current.

Security update management

The provider patches the SaaS application; you never see it happen. What reaches the application is yours: browsers, operating systems, office applications and phones, with high and critical updates within 14 days. On IaaS, the operating system and every application on the virtual machine are yours, within the same 14 days. On PaaS, your own code's dependencies are yours, and an old library in a deployed web app is the same kind of finding as an old application on a laptop.

The MFA question that fails you

Three questions in the assessment are automatic fails: two about the 14-day patching window, and one about cloud services. The cloud one asks you to list any service you use that offers no MFA option. If you list a service as having no MFA option when it does, the assessment fails.

That is a question of fact, checkable against the provider's own documentation, and it catches organisations that answered from memory. Three steps avoid it:

  1. Check every service, not the ones you remember. The list from the start of this article is the list to check. For each, find the provider's own page on multi-factor or two-step verification.
  2. Separate "available" from "on". The scheme asks both: does the service offer MFA, and is it enforced for administrators and for users. A service with MFA available but switched on only for the directors is a non-compliant answer on the second question, not the first.
  3. Use the linked sign-in where there is no native MFA. Some services have no MFA of their own but let you sign in through your Microsoft or Google account, or another identity provider, that does. Where that link exists, the scheme expects it to be configured. "No MFA option" is only a true answer when neither the native option nor a linked one exists.

Example: a small practice uses an industry-specific booking system with no MFA setting of its own. Its vendor supports "Sign in with Microsoft". Linking it to the practice's Microsoft 365 tenant, where MFA is enforced, brings the booking system inside MFA without the vendor adding a feature. Listing it as "no MFA option" would have been both wrong and a fail.

Microsoft 365 and Google Workspace in practice

Most UK SMEs run on one of the two, and both can satisfy every cloud-side control when configured. In both, the work is the same four jobs: enforce MFA for every account, with no exceptions for service accounts that a person logs into; create separate administrator accounts and keep the everyday ones unprivileged; switch off the older sign-in methods that skip MFA; and review guest and external sharing settings so data does not leave by default.

Neither platform does any of this for you out of the box. Both make it a few settings once you know they exist, and both show you, in their admin centres, which accounts still lack MFA. That report is your evidence.

How a guided platform helps here

Scope is where cloud work goes wrong, and it goes wrong early: the accountant's portal nobody mentioned, the booking tool a department bought, the virtual server from a project three years ago. A guided readiness check asks for every service by category, keeps the list in one place, records for each whether MFA is available and enforced, and flags where a service known to offer MFA has been answered "no". The judgement about your own systems stays with you; what you get is a list that does not depend on anyone's memory, and a prompt where an answer is about to fail you.

Decide what is yours, then do it

Write down every cloud service. For each, decide which model it is and read off which controls are yours. Turn MFA on everywhere it exists, link what has no MFA of its own, separate the admin accounts, fix the tenant defaults, and treat every rented server as the server it is. That is the cloud part of Cyber Essentials, and for most small businesses it is most of Cyber Essentials.

Frequently asked questions

What counts as a cloud service for Cyber Essentials?

Any service you use over the internet, through an account, that stores or processes your organisation's data on shared infrastructure you do not run. Email, file storage, accounting, payroll, CRM, HR, video calling, backups, website hosting and virtual servers all count. If staff log into it for work, it is in scope.

Can I exclude cloud services from my Cyber Essentials scope?

No. The scheme is explicit that cloud services cannot be excluded. You can scope a subset of your organisation in some circumstances, but every cloud service that subset uses stays in scope, and the assessment asks you to list them all.

Is MFA required on every cloud service?

Yes, for every user and every administrator, on every cloud service that offers it. Where a service has no MFA of its own but can be linked to a sign-in that does, such as your Microsoft or Google account, that link must be set up. Partial MFA is a non-compliant answer.

Who patches a cloud service, me or the provider?

It depends on the model. For software as a service, the provider patches the service; you keep the browsers and devices that reach it updated. For virtual servers you rent, the operating system and everything on it are yours to patch within 14 days, exactly as for a server in your office.

Is Microsoft 365 or Google Workspace enough on its own?

They cover a lot, but only when configured. Both offer MFA, admin roles, device and sharing controls, but the defaults are not the compliant settings. Turning MFA on for every user, separating admin accounts and removing leavers are your jobs inside the tenant, whichever platform you use.