Previous All Posts Next

VDI for CMMC keeps laptops out of an assessor's scope when CUI stays in a virtual desktop, shrinking the number of endpoints a defense contractor must harden and document.

The analysis was published by PreVeil, a managed virtual desktop provider, in an article titled "Simple and Proven: Why VDI Makes CMMC Easier" (preveil.com/blog/vdi-makes-cmmc-easier). It matters most to defense contractors handling Controlled Unclassified Information under CMMC Level Two, and to the executives who sign the assessments, fund the remediation and carry the annual affirmations. The timing is notable: the CMMC Program rule took effect under 32 CFR Part 170 in December 2024, the acquisition rule followed in late 2025, and in July 2026 the DoD CIO suspended the Phase Two deadline while Phase One self-assessments remain in force. Contractors now have a window to re-architect before certification pressure returns, and architecture choices made now will determine assessment scope for years.

Key Takeaways

  • DoD's official CMMC FAQ states that an endpoint used to reach a VDI can be considered out of scope, as long as it is configured so no CUI is processed, stored or transmitted beyond keyboard, video and mouse. The virtual desktop environment itself stays in scope.
  • Scope shrinks to the people who actually touch CUI. PreVeil's median VDI customer licensed 3 users out of a median company size of 20, meaning most laptops never enter the assessment boundary.
  • VDI reduces work but does not eliminate responsibility. With PreVeil VDI, 62 of the 110 controls are inherited, 38 are shared and 10 are entirely the customer's.
  • PreVeil VDI has been through multiple CMMC assessments by C3PAOs, including PreVeil's own, which scored a perfect 110.
  • Setup discipline is the catch: laptops stay out of scope only if CUI never lands on them, which is why PreVeil VDI blocks printing by default.

What Happened: The Facts in Detail

The claim, and where it comes from

PreVeil's article makes a claim that sounds too convenient to be true: that a properly set up virtual desktop keeps the devices used to reach it out of your CMMC assessment. The grounding for that claim is not the vendor's marketing. It is DoD's official CMMC FAQ, which addresses the question directly. An endpoint used to reach a VDI can be considered out of scope if it is configured so that no CUI is processed, stored or transmitted beyond keyboard, video and mouse. The virtual desktop environment itself remains in scope.

That distinction matters. The laptop is not magically exempt; it is exempt because of what it does. If it only renders a screen and forwards keystrokes and clicks, it is a display terminal. If CUI ever lands on it, the exemption evaporates and the laptop becomes an in-scope asset that must be hardened and evidenced like any other.

How VDI works, mechanically

Virtual desktop infrastructure is not new. PreVeil describes it as a proven, decades-old architecture. 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, applications and data stay on the server.

Under CMMC Level Two, 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. VDI attacks the problem at the architectural level: instead of protecting every person, laptop and location, you protect one environment and the few people who use it.

The numbers behind the scope reduction

The most concrete figure in the article is the licensing pattern. PreVeil's median VDI customer licensed 3 users out of a median company size of 20. In other words, at a typical contractor, roughly the engineers or program staff who actually open drawings or handle test data need seats in the virtual desktop. Sales, HR, accounting and the front office do not, so their laptops never enter scope.

The control split is equally specific. Of the 110 CMMC Level Two controls, PreVeil states that 62 are inherited from its managed environment, 38 are shared between provider and customer, and 10 remain entirely the customer's. The inherited set covers categories that consume most contractor effort: endpoint hardening, encryption, patching, antivirus and EDR, application allowlisting, identity and MFA, logging and SIEM, network boundary, removable media and backups, and physical protection, since CUI resides in AWS GovCloud rather than on the customer's premises.

Evidence that it survives an assessment

The strongest proof point is that PreVeil VDI has been through multiple CMMC assessments by C3PAOs, including PreVeil's own assessment, which scored a perfect 110. The product ships with an assessment-ready documentation package: a System Security Plan, standard operating procedures and a shared responsibility matrix. PreVeil also publishes an interactive shared responsibility matrix showing which controls fall where and what the customer is responsible for in each.

Centralization also changes the maintenance burden. If CUI is spread across 20 laptops, every rule change means re-engineering 20 laptops and rewriting documentation. With the VDI model, configuration management is centralized: when a requirement changes, the provider updates the environment and its documentation, and customers inherit the update instead of rebuilding.

The AI angle

The article connects VDI to a threat trend rather than only a compliance one. 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. AI makes attacks cheaper and faster to run, so shrinking what you have to protect is the most dependable way to reduce risk.

Three locked-down virtual desktops are a much smaller target than twenty laptops in twenty places. CUI never reaches the laptop, so there is no local file for malware to grab, and nothing for AI assistants, copilots or browser extensions on the laptop to upload, sync or index. Ross listed virtual machines as one way to limit the damage after a breach: a compromised laptop does not hand over the CUI, because the CUI was never there.

VDI for CMMC: Why the Architecture, Not the Tool, Does the Work

It is tempting to read this as a product story, but the mechanism is architectural, and understanding it is what protects you from buying the wrong thing. VDI for CMMC works because of scope logic in the rule itself, not because any vendor waved a wand. The rule counts assets that store, process or transmit CUI. A KVM-only endpoint does none of those things, so it drops out of the boundary. The moment the configuration changes, so does the scope.

That is why the FAQ language is so precise: keyboard, video and mouse, nothing more. Local printing, local downloads, local file sync or a copy-paste path that lands CUI on the device would each put the endpoint back in scope. PreVeil blocks printing by default for exactly this reason. Any contractor evaluating this approach should ask a prospective provider to demonstrate, control by control, how the environment prevents CUI from escaping to the endpoint, because the scope reduction is only as durable as those technical guards.

There is also a scope trap on the other side. The virtual desktop environment itself stays in scope, and the provider becomes part of your assessment story. PreVeil addresses this with the documentation package and the C3PAO assessment history, but the general principle holds for any provider: you are inheriting controls from an organization whose evidence your assessor will examine.

For contractors already working through readiness, this connects to a broader principle our team applies in CMMC readiness consulting: enclaving CUI into a narrowly scoped boundary reduces audit surface, shortens timelines and lowers ongoing cost. A VDI is one form of enclave. A GCC High tenant or a dedicated cloud landing zone is another. The four common paths to CMMC compliance often blend, and VDI can be combined with any of the other three. The right question is not "VDI or not" but "what is the smallest boundary that contains our CUI, and who proves each control inside it."

Readers building their own program plan can see where this fits in our CMMC compliance services overview, or work through the requirements control by control in the 2026 CMMC Compliance Guide. The underlying requirements come from NIST SP 800-171 Revision 2, the authoritative source for the CUI security requirements that Level Two assesses, published by NIST (csrc.nist.gov), and the certification program itself is codified at 32 CFR Part 170 (law.cornell.edu).

What the Evidence Does and Does Not Show

The scope reduction is real and officially sanctioned, but the honest reading of the sources requires several caveats.

First, the out-of-scope treatment is conditional, not automatic. DoD's FAQ says the endpoint "can be considered" out of scope when configured for keyboard, video and mouse only. Configuration drift, a user workaround or a policy change could alter that. That verification burden exists somewhere, and the article does not quantify it.

Second, the numbers are vendor-reported. The 3-of-20 median licensing figure, the 62/38/10 control split and the perfect 110 assessment score all come from PreVeil's own article about its own product. They are specific and plausible, and the C3PAO assessment history lends credibility, but a regulated buyer should treat them as one provider's documented experience rather than an industry-wide benchmark. The sources do not say how many customers have passed assessments on the platform, only that it has been through multiple C3PAO assessments including PreVeil's own.

Third, VDI shrinks scope; it does not erase responsibility. Ten controls remain entirely the customer's, 38 are shared, and the customer still owns people, policy and evidence: training, personnel screening, access management, incident response, the annual affirmation and the triennial assessment. PreVeil packages much of the evidence, but the customer still has to show an assessor that controls work. The article is explicit that this "isn't magic": anything shown on a screen can still be seen, and a shoulder-surfing risk or a photographed screen is not solved by architecture.

Finally, the regulatory ground is still moving. The DoD CIO suspended the Phase Two deadline in July 2026, with later milestones paused until further notice. That suspension changes urgency, not requirements: DFARS obligations around adequate security and incident reporting remain in force, and DOJ Civil Cyber-Fraud Initiative settlements, including Raytheon's $8.4M in May 2025 and Georgia Tech's $875K in September 2025, show that misrepresenting security posture carries financial consequences. Architecture decisions made during the pause should assume certification pressure returns. What the sources do not tell us is whether DoD will issue further guidance on VDI scope treatment as the program matures, so contractors should verify the current FAQ language at decision time rather than relying on any single article, including this one.

What VDI Scope Reduction Means for Compliance and Risk

The compliance logic behind VDI is not a vendor interpretation. It rests on how CMMC Level 2 defines scope: every asset that stores, processes or transmits Controlled Unclassified Information is in scope, along with everything that secures those assets and anything not adequately separated from them. DoD's official CMMC FAQ addresses the architecture directly, stating that an endpoint used to reach a VDI can be considered out of scope when it is configured so that no CUI is processed, stored or transmitted beyond keyboard, video and mouse. The virtual desktop environment itself remains in scope and must still meet the 110 security requirements of NIST SP 800-171 Rev 2, assessed under 32 CFR Part 170 [1].

That distinction matters because scope drives cost in both directions. Every in-scope laptop must be hardened, and that hardening must be documented and proven to a C3PAO assessor. Under CMMC Level 2, most programs face a third-party assessment, triennial reassessment, and annual senior official affirmation. The DoD CIO FAQ has also clarified the boundary conditions: VDI endpoints are out of scope only in a KVM-only configuration, and encrypted CUI is still CUI. A laptop that merely displays a virtual desktop qualifies; a laptop where CUI lands locally does not [1].

The same scoping principle appears in the fact sheet guidance for defense contractors generally: enclaving CUI into a narrowly scoped boundary, such as a GCC High tenant or a dedicated cloud landing zone, keeps the 110 controls from applying across the entire enterprise network. VDI is one expression of that principle. It is also one of four common paths to CMMC compliance, and the other three can be blended with it [1].

There is a risk-management argument layered on top of the compliance argument. Dr. Ron Ross of NIST, speaking at the 2026 CMMC Summit on NIST and CMMC in the era of AI attacks, made the point that organizations should assume someone will get in and design so the damage stays small. He listed virtual machines as one way to limit post-breach damage. With VDI, a compromised laptop does not hand over CUI, because the CUI was never on it. There is no local file for malware to grab, and nothing for AI assistants, copilots or browser extensions on the laptop to upload, sync or index. AI lowers the cost of attacks, so the fewer places CUI lives, the smaller the attack surface [1].

One caution belongs in every planning conversation: VDI is not magic. Anything shown on a screen can still be seen, photographed or transcribed. Keeping the data itself off the device removes the easiest paths out, not every path. And the architecture does not erase responsibilities. People, policy, incident response, evidence, and the shared and company-owned controls remain the contractor's job. Setup discipline is what keeps laptops out of scope: if CUI ever lands on an endpoint, it is back in your assessment boundary. That is why managed VDI offerings such as PreVeil's block printing by default [1].

HIPAA's Security Rule at 45 CFR Part 164 requires a risk analysis and safeguards across administrative, physical and technical families, and shrinking the footprint of systems that touch electronic protected health information reduces what must be safeguarded and evidenced. PCI DSS v4.0.1 covers 12 control areas across cardholder data environments, and the same scoping discipline applies: fewer systems that handle cardholder data means fewer controls to operate and audit. The sources here speak directly to CMMC; the broader principle is ours to apply with judgment, not a claim any regulation endorses VDI by name.

What This Means for Regulated Industries

Defense Contractors

This story is aimed squarely at the defense industrial base. If your contracts carry DFARS 252.204-7021, you must hold a valid CMMC certificate at the specified level before award, and Level 2 requires all 110 practices of NIST SP 800-171 Rev 2 across 14 domains, assessed by a C3PAO. If your CUI is spread across a fleet of laptops, every one of them is in scope, every one must be hardened and documented, and every rule change means re-engineering the fleet and rewriting documentation. With VDI, configuration management is centralized: the provider updates the environment and its documentation, and you inherit the update [1].

The economics follow the scope. PreVeil's median VDI customer licensed 3 users out of a median company size of 20, because only the people who touch CUI need a seat. Sales, HR, accounting and the front office do not open drawings or handle test data, so their laptops need not be part of your assessment. Physical protection controls are also inherited when CUI lives in AWS GovCloud rather than on your premises, so there is no CUI in your office to lock up [1].

Two timing notes for planning. First, on 2026-07-13 the DoD CIO suspended the 2026-11-10 Phase II deadline; Phase I self-assessments remain in force and later milestones are paused until further notice. A deadline pause is not a compliance pause: DFARS 252.204-7019 still requires a current NIST SP 800-171 self-assessment score in SPRS when an offer is submitted, and DOJ Civil Cyber-Fraud Initiative settlements, including Raytheon at $8.4M in May 2025 and Georgia Tech at $875K in September 2025, show what misrepresentation costs. Second, DFARS 252.204-7012 must be flowed down to subcontractors when performance involves covered defense information, so if you are a subcontractor, expect primes to ask about your CUI architecture.

Before selecting any VDI provider, ask three questions: What documentation comes with it? What do I have left to do? Have customers passed assessments on it? PreVeil VDI ships with an SSP, standard operating procedures and a shared responsibility matrix, and has been through multiple C3PAO assessments, including PreVeil's own, which scored a perfect 110 [1].

Healthcare

CMMC does not apply to most healthcare organizations, but the architecture lesson does. The HIPAA Security Rule requires a risk analysis under 45 CFR 164.308(a)(1)(ii)(A) plus 18 standards across administrative, physical and technical safeguards, and there is no HHS-issued HIPAA certification, so your evidence is your compliance. IBM's 2026 figure puts the average healthcare breach at $6.64M, and Change Healthcare's breach ultimately reached 192.7M individuals in the final HHS filing of 2025-07-31. Business associates accounted for about 66% of breached healthcare records in 2024, which is a scoping problem in its own right: the more vendors and endpoints that touch PHI, the larger the breach surface [see fact sheet statistics].

The VDI pattern, keeping sensitive data in a controlled environment and treating user devices as windows into it, maps naturally onto PHI workflows for practices, billing companies and business associates. It reduces the endpoints where PHI can land, the removable media you must control, and the local files an AI tool or browser extension could sync or index. HHS OCR enforcement actions in 2024 through 2026, including a Children's Hospital Colorado civil money penalty of $548,265 where MFA was disabled, show that identity and access failures on endpoints carry real penalties. If you adopt the pattern, document it: your risk analysis must reflect the actual architecture.

Legal

Law firms handling government contracts work, or serving defense contractors as clients, can encounter CUI and FCI obligations through their engagements, and firms handling client secrets of any kind face the same structural problem: sensitive material scattered across partner laptops, home offices and personal devices. The VDI pattern offers a way to concentrate client-sensitive work in one controlled environment rather than hardening every machine a lawyer touches. It also addresses a modern exposure the sources highlight: AI assistants, copilots and browser extensions on a laptop can upload, sync or index whatever local files exist. If privileged or controlled material never lands on the device, those tools have nothing to reach.

Financial Services

Financial institutions face their own control regimes, and PCI DSS v4.0.1's 12 control areas across cardholder data environments reward exactly the discipline VDI embodies: reduce the systems that touch sensitive data and the assessment shrinks with them. The AI-driven threat picture is the sharpest reason to act: IBM's 2025 Cost of a Data Breach found 16% of breaches involved attacker use of AI and 20% involved shadow AI, and the FBI's IC3 2025 report tallied more than $20B in reported losses, up 26%. Keeping sensitive data off endpoints removes the local files that shadow AI tools and attackers both look for.

An Action Plan for This Month

  1. Inventory where CUI actually lives. Walk through every contract, mailbox, shared drive and laptop. You cannot shrink scope until you know its current shape, and DFARS 252.204-7019 requires a current self-assessment score in SPRS when an offer is submitted.
  2. Identify who genuinely touches CUI. Most of a company never does. PreVeil's median VDI customer licensed 3 users out of a median company size of 20, which shows how much of a typical fleet may be reducible [1].
  3. Map your current scope honestly. List every asset that stores, processes or transmits CUI, everything securing those assets, and anything not separated from them. That list is your assessment boundary today.
  4. Read DoD's CMMC FAQ language on VDI yourself. The out-of-scope position is conditional: no CUI processed, stored or transmitted beyond keyboard, video and mouse. Understand the condition before you rely on it [1].
  5. Score your SPRS self-assessment if it is stale. The score ranges from minus 203 to 110, with controls weighted 1, 3 or 5 points. An outdated score is a proposal risk even under the current Phase I posture.
  6. Evaluate VDI against the three provider questions. What documentation comes with it? What do I have left to do? Have customers passed assessments on it? Ask for the shared responsibility matrix in writing [1].
  7. Compare all four paths, not just one. VDI is one of four common routes to CMMC compliance and they often blend. Price the internal hours each path consumes, not just the tooling [1].
  8. Check your cloud baselines. DoD CIO FAQ clarifications state that encrypted CUI is still CUI and encrypted CUI in a cloud still needs FedRAMP Moderate or equivalency. A commercial tenant that was never assessed against that baseline does not satisfy DFARS 252.204-7012.
  9. Fix the endpoint discipline that keeps laptops out of scope. Block printing and local downloads for VDI users, and train staff that saving CUI locally puts the device back in scope.
  10. Get a professional gap analysis on the calendar. A typical CMMC Level 2 readiness engagement runs 12 to 14 weeks for a mid-size contractor, and the path from gap assessment to C3PAO-ready typically takes 6 to 18 months depending on starting posture.

How Petronella Technology Group, Inc. Helps

Petronella Technology Group, Inc. is a Cyber AB Registered Provider Organization, RPO #1449, and every engineer assigned to a defense client holds the CMMC Registered Practitioner credential. As an RPO, we prepare organizations for assessment; only a C3PAO can issue a CMMC Level 2 certificate, and we do not perform certification assessments for any organization. We do not promise guaranteed pass outcomes, because no honest preparer can.

Our CMMC readiness consulting delivers the artifacts this story turns on: an SSP covering all 110 NIST SP 800-171 controls with owners and evidence pointers, 14 control-family policies plus incident response and media protection plans, a live POA&M, a mock assessment using the Cyber AB CMMC Assessment Process, a baselined SPRS score, and a C3PAO shortlist with warm introductions. A typical Level 2 readiness engagement runs 12 to 14 weeks for a mid-size contractor, and our vCISO practice can serve as your security officer of record for CMMC senior official authorization.

Because scoping is the lever this whole story pulls, our guidance on CMMC compliance emphasizes enclaving CUI into a narrowly scoped boundary, typically a GCC High tenant or a dedicated cloud landing zone, which reduces audit surface, shortens timelines and lowers ongoing cost. For teams that want to go deeper before engaging, our 2026 CMMC Compliance Guide and CMMC Compliance Checklist 2026 lay out the requirements in plain English, and our broader compliance practice covers HIPAA, SOC 2 and other frameworks for organizations whose obligations do not stop at CUI. ComplianceArmor, our compliance documentation platform, automates SSP authoring, POA&M tracking and evidence repository organization, which is the ongoing burden VDI reduces but does not eliminate.

Related reading

Sources

Frequently Asked Questions

Does DoD actually allow VDI to keep laptops out of CMMC scope?

Yes, when the configuration is right. DoD's CMMC FAQ says an endpoint used to reach a VDI can be considered out of scope if it is configured so no CUI is processed, stored or transmitted beyond keyboard, video and mouse. The virtual desktop environment itself stays in scope [1].

Does VDI make my company CMMC compliant by itself?

No. VDI shrinks what you have to protect; it does not erase your responsibilities. With PreVeil VDI, 62 of the 110 controls are inherited, 38 are shared and 10 are entirely yours. People, policy, incident response and evidence remain your job, and you still affirm compliance annually and face reassessment every three years [1].

How many VDI licenses does a company typically need?

Only the people who handle CUI need a seat. PreVeil's median VDI customer licensed 3 users out of a median company size of 20, because sales, HR, accounting and front-office staff generally never touch CUI [1].

Does the DoD deadline suspension make VDI unnecessary right now?

No. On 2026-07-13 the DoD CIO suspended the 2026-11-10 Phase II deadline, with Phase I self-assessments remaining in force and later milestones paused until further notice. But DFARS 252.204-7019 still requires a current SPRS score when an offer is submitted, contracts still flow down 252.204-7012, and DOJ settlements show the enforcement risk of falling short. Architecture decisions made now determine your cost when milestones resume.

How does VDI help against AI-driven attacks?

AI lowers the cost of running attacks, so the fewer places CUI lives, the better. With VDI, CUI never lands on the laptop, leaving no local file for malware to grab and nothing for AI assistants, copilots or browser extensions to upload, sync or index. Dr. Ron Ross of NIST listed virtual machines among the ways to limit damage after a breach [1].

What should I verify before choosing a VDI provider?

Ask three questions: What documentation comes with it? What do I have left to do? Have customers passed assessments on it? PreVeil VDI ships an SSP, standard operating procedures and a shared responsibility matrix, and has been through multiple C3PAO assessments, including PreVeil's own, which scored a perfect 110 [1].

If you want a practical read on whether VDI fits your CUI environment, call Penny, our AI assistant, at 919-348-4912 to book a consultation, or reach Petronella Technology Group, Inc. through our contact form. The first call is a free 30-minute scoping consultation run by a CMMC Registered Practitioner.

Related reading: On-Premises AI Coding Assistants Now Rival the Cloud | Petronella Technology Group.

Related reading: On-Premises AI Coding Assistants Now Rival the Cloud | Petronella Technology Group.

Related reading: On-Premises AI Coding Assistants Now Rival the Cloud | Petronella Technology Group.

Online course from the Petronella Technology Group, Inc. Training Academy

CMMC Level 2 Security Awareness: Common Core

Foundational CMMC Level 2 awareness for all roles: CUI, insider threat, phishing, passwords and MFA, physical security, and incident reporting.

Price: $49

View the course Team packs

Get the CMMC Compliance Guide

Free, practical, and specific to regulated environments. We will email it to you.

No spam. Unsubscribe anytime.

Need help implementing these strategies? Our cybersecurity experts can assess your environment and build a tailored plan. Prefer to write? Send us a message.
Call Penny 919-348-4912

About the Author

Craig Petronella, CEO and Founder of Petronella Technology Group
CEO, Founder & AI Architect, Petronella Technology Group

Craig Petronella founded Petronella Technology Group in 2002 and has spent 30+ years professionally at the intersection of cybersecurity, AI, compliance, and digital forensics. He holds the CMMC Registered Practitioner credential issued by the Cyber AB and leads Petronella as a Cyber AB Registered Provider Organization (RPO #1449). Craig is an NC Licensed Digital Forensics Examiner (License #604180-DFE) and completed MIT Professional Education programs in AI, Blockchain, and Cybersecurity. He also holds CompTIA Security+, CCNA, and Hyperledger certifications.

He is an Amazon #1 Best-Selling Author of 15+ books on cybersecurity and compliance, host of the Encrypted Ambition podcast (95+ episodes on Apple Podcasts, Spotify, and Amazon), and a cybersecurity keynote speaker with 200+ engagements at conferences, law firms, and corporate boardrooms. Craig serves as Contributing Editor for Cybersecurity at NC Triangle Attorney at Law Magazine and is a guest lecturer at NCCU School of Law. He serves as a digital forensics expert witness for law firms on matters involving cybercrime, cryptocurrency fraud, SIM-swap attacks, and data breaches.

Under his leadership, Petronella Technology Group has served hundreds of regulated SMB clients across NC and the southeast since 2002, earned a BBB A+ rating every year since 2003, and been featured as a cybersecurity authority on CBS, ABC, NBC, FOX, and WRAL. The company leverages SOC 2 Type II certified platforms and specializes in AI implementation, managed cybersecurity, CMMC/HIPAA/SOC 2 compliance, and digital forensics for businesses across the United States.

CMMC-RP NC Licensed DFE MIT Certified CompTIA Security+ Expert Witness 15+ Books
Related Service
Achieve Compliance with Expert Guidance

CMMC, HIPAA, NIST, PCI-DSS - we have 80% of documentation pre-written to accelerate your timeline.

Learn About Compliance Services
Previous All Posts Next
Questions about this topic? Talk to our team. Call Penny 919-348-4912 Message us