Virtual desktops, thin clients, VMs and containers in Cyber Essentials scope
Virtual devices count like physical ones in Cyber Essentials. Where virtual desktops, thin clients, VDI servers, hypervisors and containers go in the questions.
Cyber Essentials treats virtual devices like physical ones: v3.3 covers desktops, laptops, thin clients, tablets and smartphones 'whether physical or virtual'. List virtual desktops at A2.6, thin clients at A2.6.1, and servers, hypervisors and VDI servers at A2.7. Thin clients must be supported and receive regular security updates, and devices used to reach virtual desktops are in scope.
- Rule
- Devices include end user devices such as desktops, laptops, thin clients, tablets and smartphones, whether physical or virtual
- Where declared
- Virtual desktops A2.6; thin clients A2.6.1; servers, virtual servers, hypervisors and VDI servers A2.7; IaaS and PaaS A2.9
- Thin clients
- Must be supported and receive regular security updates (A2.6.1). The Danzell security update, user access control, administrative account and malware questions all apply to them
- Connecting devices
- In scope. IASME: 'all user devices that are used to access the solution must be in scope'
- VMs and containers
- In scope. IASME: 'the controls should be applied to them just as for any other device'
- Source
- Requirements for IT Infrastructure v3.3, Sections B and D, Definitions and Scope
Are virtual desktops and virtual machines in scope?
Yes. The v3.3 definition of devices 'includes all types of hosts, networking equipment, servers, networks, and end user devices such as desktop computers, laptops, thin clients, tablets and smartphones - whether physical or virtual'. IASME's Knowledge Hub scope FAQ (checked 9 November 2026) answers 'Are virtual machines and containers in scope for Cyber Essentials?' with 'Yes, they are and the controls should be applied to them just as for any other device.' A virtual desktop is a desktop computer for the purposes of the scheme, and a virtual server is a server.
The question set follows the same line. A2.6 asks for the quantities and operating systems of 'laptops, desktops and virtual desktops', with the edition and feature version of Windows. A2.7 asks for 'servers, virtual servers, virtual server hosts (hypervisors) and Virtual Desktop Infrastructure (VDI) servers', and its guidance gives the example '2 x VMware ESXI 8.0 hosting 8 virtual Windows 2019 servers; 1 x MS Server 2019; 1 x Red Hat Enterprise Linux 8.9'.
| Component | Where declared | Who implements the controls |
|---|---|---|
| Virtual desktops (VDI desktops, Windows 365 Cloud PCs, AVD personal session hosts) | A2.6 | Your organisation, for the desktop operating system and its software |
| Thin clients | A2.6.1 | Your organisation; must be supported and receive regular security updates |
| Physical and virtual servers, hypervisors, VDI servers, AVD pooled session hosts | A2.7 | Your organisation |
| IaaS virtual machines | A2.9 (and A2.7 if you list the servers) | Both you and the provider; you configure and manage the guest |
| PaaS and managed container platforms | A2.9 | Provider for the platform; you for the applications and accounts |
| Devices used to reach a virtual desktop | A2.6 or A2.8 | Your organisation, including BYOD |
Are thin clients in scope?
Yes, and they must be supported and receive regular security updates. Thin clients appear in the v3.3 definition of devices, and A2.6.1 asks for their quantity, make and operating system. Its guidance reads: 'Thin clients are simplified computers with a minimum operating system, primarily designed for accessing virtual desktops. While thin clients can connect to the internet, some can be modified to function more like traditional PCs, which may introduce security risks. To meet Cyber Essentials requirements, thin clients must be supported and receive regular security updates.'
v3.3's 'Applies to' lines name thin clients only under secure configuration, but the Danzell question set applies its security update management, user access control, administrative account and malware protection questions to thin clients too: each of those section introductions says its questions 'apply to: servers, desktop computers, laptops, tablets, thin clients, mobile phones' and cloud services. So answer those questions for your thin clients as well. A5.1 and A5.3 also name thin clients directly: unused software and services removed, and default passwords changed.
Common thin client operating systems include IGEL OS, Dell ThinOS, HP ThinPro and Windows IoT Enterprise LTSC. Check the vendor's lifecycle page for the end-of-support date of both the hardware model and the operating system image, and patch them like any other endpoint. See thin client.
Is the device people use to reach a virtual desktop in scope?
Yes. IASME's scope FAQ says that with Virtual Desktop Infrastructure 'all user devices that are used to access the solution must be in scope for Cyber Essentials', and v3.3 defines organisational services to include 'user interactive desktops', giving Citrix Desktop and virtual desktops as examples. User-owned devices that access organisational data or services are in scope too. A home PC or personal laptop used to open a Citrix, Azure Virtual Desktop or Windows 365 session is therefore BYOD in scope, must be listed at A2.6 and must meet the five controls.
The exception is a device owned by someone Table 2 places out of scope, such as a third-party contractor or an MSP administrator using their own laptop. You remain responsible for confirming those devices are configured correctly, and conditional access or contract terms are the usual way. See BYOD scope and third-party devices.
How are Azure Virtual Desktop, Windows 365 and Citrix treated?
As cloud services plus the desktops and servers they run: you list the platform in A2.9 and the desktops or session hosts at A2.6 or A2.7. v3.3 says the applicant is always responsible for ensuring all controls are implemented on cloud services, while some controls can be implemented by the provider depending on whether the service is IaaS, PaaS or SaaS. Table 1 puts user access control with your organisation in every model. The provider's commitment must be in a contract or a document referenced by contract.
Our interpretation of the common platforms, which you should confirm against each provider's shared responsibility statement:
- Azure Virtual Desktop: session hosts are virtual machines in your own Azure subscription, so you patch, configure and protect them as IaaS, and list Azure in A2.9. Microsoft's AVD terminology page (checked 9 November 2026) says a personal host pool assigns each session host 'to an individual user', while in a pooled host pool 'there can be multiple different users on a single session host at the same time'. We list personal session hosts as virtual desktops at A2.6 and pooled multi-session hosts as VDI servers at A2.7, each with operating system and version.
- Windows 10 on AVD: the A2.6 guidance says that if you use Windows 10 beyond 14 October 2025 'you must be signed up to the Microsoft Extended Security Update program'. Microsoft's AVD ESU page (checked 9 November 2026) says Windows 10 multi-session and single-session VMs in AVD 'are automatically eligible for ESU', but that devices 'require explicit ESU policy enablement' before they receive the updates, so check the policy is applied.
- Windows 365: Microsoft runs the infrastructure, and each Cloud PC is a Windows desktop you manage, usually through Intune. List the Cloud PCs at A2.6 with edition and version, and Windows 365 in A2.9.
- Citrix: with Citrix Cloud the control plane is a cloud service for A2.9, while the machines that run the desktops sit on your hypervisor or IaaS and are listed at A2.6 and A2.7. With on-premises Citrix, the delivery servers are servers at A2.7, and any gateway published to the internet is an inbound connection to approve and document at A4.8.
Are hypervisors and VDI servers in scope?
Yes. A2.7 asks for virtual server hosts by name, so the hypervisor is server software that must be licensed, supported and updated within 14 days for high-risk or critical fixes (A6.1, A6.4). The A6.3 guidance warns that 'for some operating systems, firmware and applications, if annual licensing is not purchased, they will not be receiving regular security updates', which matters for hypervisors sold on subscription. See hypervisor.
Recommended, not required: keep the hypervisor management interface off the internet unless there is a documented business need. The scheme's specific rules for admin interfaces (A4.9 to A4.11: MFA, or an IP allow list with a managed password) are written for boundary firewalls; applying the same protection to a hypervisor console is our advice, not a scheme requirement.
Are containers such as Docker and Kubernetes in scope?
Yes. IASME's scope FAQ answers 'Are virtual machines and containers in scope for Cyber Essentials?' with 'Yes, they are and the controls should be applied to them just as for any other device.' v3.3 itself does not mention containers; its reference to 'mobile device management containers' is about MDM work profiles, not Docker.
Our interpretation of how to apply that: the host that runs the containers is a server or an IaaS instance and is listed at A2.7 or A2.9. Software in v3.3 includes interpreters, scripts and libraries, so the operating system layer and packages inside each image should be supported and patched within 14 days for critical fixes, which in practice means rebuilding images. A managed container platform such as AKS or EKS is a cloud service, with the split of responsibility set by the provider's documentation.
Our interpretation on custom code: v3.3 says 'Bespoke and custom components of web applications are out of scope', and we read that as covering bespoke web application code that happens to run in a container, while the commercial and open-source components beneath it stay in scope. See software development scope.
How do assessors check virtual desktops, thin clients and VDI servers?
Related requirements
- A2.6: laptops, desktops and virtual desktops
- A2.6.1: thin clients
- A2.7: servers, hypervisors and VDI servers
- Cloud services scope
- BYOD scope
- Glossary: virtual desktop infrastructure
- Azure setup guide
- CE Plus test 2: authenticated patch scan
- Check your readinessTest your scope and controls against the auto-fail questions
Frequently asked questions
Yes. The Danzell question set says its security update management, user access control, administrative account and malware protection questions apply to thin clients, alongside servers, desktops, laptops, tablets and phones. Thin clients must also be supported and receive regular security updates (A2.6.1 guidance).
Yes. v3.3 defines devices to include end user devices 'whether physical or virtual', and IASME's scope FAQ says the controls apply to VMs just as for any other device. Virtual desktops are listed at A2.6, virtual servers at A2.7, and IaaS virtual machines are covered as cloud services in A2.9 with the controls split as in Table 1.
Yes. IASME's scope FAQ says all user devices used to access virtual desktop infrastructure must be in scope. List them at A2.6 and make sure each runs a supported operating system with a firewall, malware protection and patching within 14 days.
Yes. A2.7 asks for servers, virtual servers, virtual server hosts (hypervisors) and VDI servers with their operating systems. The guidance example lists the ESXi hosts and the Windows servers they run on separate lines with versions.
Yes. IASME's scope FAQ says containers are in scope and the controls apply as for any other device. Our interpretation is that the container host is a server or IaaS instance, and the operating system packages and libraries inside images must be supported and patched; bespoke web application code is out of scope under v3.3.
Both, in our reading. Windows 365 is a cloud service to list at A2.9, and each Cloud PC is a virtual desktop to list at A2.6 with its Windows edition and version. Check Microsoft's shared responsibility documentation for which controls Microsoft implements.
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
- NCSCCyber Essentials: Requirements for IT Infrastructure v3.3 · April 2026Read on ncsc.gov.uk (opens in a new tab)
- IASMECyber Essentials Danzell Question Set 2026Read on iasme.co.uk (opens in a new tab)
- iasme.atlassian.netIASME Knowledge Hub, Scope FAQ · Checked 9 November 2026Read on iasme.atlassian.net (opens in a new tab)
- Microsoft LearnAzure Virtual Desktop terminology · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- Microsoft LearnExtended Security Updates for Azure Virtual Desktop · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)