Virtual Desktop Infrastructure (VDI) isn’t new or experimental. It’s a proven, decades-old architecture. The idea is simple: CUI lives in one locked-down desktop in the cloud, and a user’s machine becomes a window into it. There’s less to protect, less to document, and less that can go wrong.

When the rules keep changing and AI keeps lowering the cost of attacks, shrinking what you have to protect is the most dependable way to reduce risk.

PreVeil VDI explained. Clips from the 2026 PreVeil CMMC Summit.

What is VDI, and why does it matter for CMMC?

VDI stands for virtual desktop infrastructure. You work on a computer that runs in a secure data center, not the one on your desk. Your laptop shows the screen and sends your keystrokes and mouse clicks. The files, apps and data stay on the server.

That matters for CMMC because of scope. Under CMMC Level 2, every asset that stores, processes or transmits CUI is in scope, plus everything that secures those assets and anything not separated from them. Every in-scope laptop has to be hardened, and that hardening has to be documented and proven to your assessor.

DoD’s official CMMC FAQ addresses this directly: an endpoint used to reach a VDI can be considered out of scope, as long as it’s configured so no CUI is processed, stored or transmitted beyond keyboard, video and mouse. The virtual desktop environment itself stays in scope.

For a longer walkthrough, read How VDI Can Simplify Your Path to CMMC Compliance.

Introducing PreVeil VDI

PreVeil VDI is a managed virtual desktop for CUI: a familiar Windows desktop in AWS GovCloud with PreVeil Email and Drive, Microsoft Office, Okta and ThreatLocker already set up for CMMC. CUI stays inside the virtual desktop, so the laptops people use to reach it stay out of your assessment boundary.

It comes with a documentation package built for assessment, including a System Security Plan (SSP), standard operating procedures and a shared responsibility matrix. PreVeil VDI has been through multiple CMMC assessments by C3PAOs, including PreVeil’s own, which scored a perfect 110.

Shrink the problem to the people who touch CUI

Most of your company never touches CUI. Sales, HR, accounting and the front office don’t open drawings or handle test data. So why should their laptops be part of your assessment?

That’s the core idea of PreVeil VDI. Instead of protecting every person, laptop and location, you protect one environment and the few people who use it. Fewer in-scope assets means less to secure, document and assess.

Physical Protection is a good example. With your CUI in AWS GovCloud rather than on your premises, those controls are fully inherited from PreVeil, so there’s no CUI in your office to lock up.

Built for a moving target

CMMC rules shift. If your CUI is spread across 20 laptops, every change means re-engineering 20 laptops and rewriting your documentation. With PreVeil VDI, configuration management is centralized. When a requirement changes, PreVeil updates the environment and its documentation, and customers inherit the update instead of rebuilding.

Here’s how the 110 CMMC controls split with PreVeil VDI:

62controls fully inherited from PreVeil
38controls shared between you and PreVeil
10controls that are entirely yours

To see which controls fall where, and what you’re responsible for in each, explore the interactive shared responsibility matrix.

VDI in the age of AI

AI makes attacks cheaper and faster to run. Several 2026 CMMC Summit keynotes, including Dr. Ron Ross on NIST and CMMC in the era of AI attacks, made the same point: assume someone will get in, and design so the damage stays small.

VDI helps in three plain ways:

  • Fewer endpoints to attack. Three locked-down virtual desktops are a much smaller target than twenty laptops in twenty places.
  • CUI never reaches the laptop. There’s no local file for malware to grab, and nothing for AI assistants, copilots or browser extensions on the laptop to upload, sync or index.
  • Damage stays contained. Ross listed virtual machines as one way to limit the damage after a breach. A compromised laptop doesn’t hand over the CUI, because the CUI was never there.

It isn’t magic. Anything shown on a screen can still be seen. But keeping the data itself off the device removes the easiest paths out.

What it costs, and what it saves

PreVeil VDI is priced per user plus a flat annual platform fee. You only pay for the people who need VDI (three seats for the median customer).

What you save is the work you no longer have to do:

  • Hardening every endpoint individually. With core PreVeil, you remove local admin rights, configure OS settings and set screen locks and login banners on each machine. VDI desktops arrive already configured.
  • Deploying and documenting endpoint encryption. No managing BitLocker across your fleet or proving CUI-at-rest encryption on each device, because with VDI, CUI never resides on the laptop.
  • Ongoing patch and vulnerability management. No keeping every in-scope machine patched, running vulnerability scans and tracking remediation. The environment is patched and scanned for you.
  • Deploying and monitoring antivirus/EDR and intrusion detection. No rolling out endpoint protection across devices or managing the alerts. It’s built into the managed desktop.
  • Building and maintaining application allowlisting. No configuring ThreatLocker policies machine by machine or managing user software-install requests. It runs inside the VDI.
  • Standing up MFA, password policy and identity lifecycle. No configuring lockouts, password rules or account provisioning across your environment. Identity runs through Okta.
  • Managing the logging and SIEM infrastructure. No collecting, protecting, retaining or alerting on audit logs yourself. It’s managed.
  • Designing and maintaining your network boundary. No firewalls, deny-by-default rules or exception reviews to own. The boundary lives in managed GovCloud.
  • Controlling removable media and backups. No managing USBs, sanitizing drives, encrypting portable media, protecting backups or sanitizing equipment before disposal, because CUI isn’t on your hardware.
  • Restricting mobile access and external connections to CUI. Managed for you.

You also skip physical protection for CUI on your premises, writing an SSP, procedures and a responsibility matrix from scratch, and re-engineering when the rules change.

VDI is one of four common paths to CMMC compliance, and they often blend. Any of the other three can be combined with VDI.

The Four Paths to CMMC Compliance
PathInternal timeWhat drives the costBiggest risk
DIYHighestTools plus internal hours. The hours are the cost people leave out.Underestimating the documentation and evidence work
Partner-directedHighA project fee that grows with your scopeA good plan your team has no time to carry out
Partner-ledLowPer endpoint, per month, for as long as they run itYour partner becomes part of your assessment
VDILowSetup cost, then a per-user subscriptionYour share of the controls still has to be done

To go deeper, watch two Summit sessions: Protecting CUI Without Overpaying: What to Buy, What to Skip, What’s Free and Four Paths to Compliance: Which Is Right for Your Company? Or download the guide DIY, Partner or VDI? Choosing Your Path to CMMC Compliance.

What VDI doesn’t do

VDI shrinks your scope. It doesn’t erase your responsibilities.

  • People. You still train users, screen personnel and manage who gets access.
  • Policy. You still own your policies, incident response and your share of the 38 shared controls, plus the 10 that are fully yours.
  • Evidence. You still have to show an assessor that the controls work, at each three-year assessment, and affirm compliance every year in between. PreVeil packages much of that evidence for you.
  • Setup discipline. Laptops stay out of scope only if CUI never lands on them. That’s why PreVeil VDI blocks printing by default.

Before you pick any VDI provider, ask three questions: What documentation comes with it? What do I have left to do? Have customers passed assessments on it?

Frequently asked questions

Does DoD allow VDI to keep laptops out of scope?

Yes, when it’s set up correctly. DoD’s CMMC FAQ says an endpoint used to reach a VDI can be considered out of scope if it’s configured so no CUI is processed, stored or transmitted beyond keyboard, video and mouse. The VDI itself stays in scope.

Does VDI make my company CMMC compliant?

No. It shrinks what you have to protect. With PreVeil VDI, 62 of the 110 controls are inherited, 38 are shared and 10 are entirely yours. People, policy and evidence are still your job.

Who needs a VDI license?

Only the people who handle CUI. PreVeil’s median VDI customer licensed 3 users out of a median company size of 20.

How does VDI help with AI-driven attacks?

AI lowers the cost of attacks, so the fewer places CUI lives, the better. With VDI, CUI never lands on the laptop. There are fewer endpoints to attack and no local files for an attacker, or an AI tool on the laptop, to copy, sync or index.

When is VDI not the right choice?

If most of your company handles CUI, you work from one building you control, your devices are company-issued, and you have strong IT staff who know NIST 800-171, hardening your own endpoints may cost less.

This post is educational and is not legal advice. Confirm your scope and approach with your assessor or RPO before you commit to a path.