# Contractors Validate CAC-Enabled AVD Enclaves

A discussion about CAC-authenticated Azure Virtual Desktop (AVD) environments examines whether endpoints accessing controlled unclassified information (CUI) can remain outside an enclave’s assessment scope. Commenters distinguish smart-card authentication from unrestricted USB passthrough: a narrowly restricted smart-card channel may be compatible with that boundary, but the specific configuration should be reviewed by a C3PAO. They also caution that device identifiers alone may not prevent USB spoofing.

- Contractors configuring AVD for CUI should document that smart-card authentication is the only exposed USB channel and that other channels—such as storage, clipboard, and printing—are unavailable, as relevant to their environment.
- Assessment teams should validate the actual configuration, including controls against USB-device spoofing, and retain test results as assessment evidence.
- The discussion cites a DoD FAQ regarding hardware PKI tokens, but does not establish that every CAC-enabled setup keeps endpoints out of scope; organizations should have their specific configuration reviewed by their C3PAO.

**Jurisdictions:** federal
**Industries:** Defense & Military, Information Technology
**Topics:** Cybersecurity
**Published:** November 19, 2026

### Government Entities
- U.S. Department of Defense (DoD)

### Key Quotes
> I wouldn't treat CAC as generic USB passthrough. The DoD FAQ allows a hardware PKI token while the endpoint stays out of scope, but you need to show the session exposes only the smart-card channel, not arbitrary USB, storage, clipboard or printing; put those negative tests in the assessment evidence.
> — Community commenter

### Sources
- [VDI enclave but needs CAC authentication...](https://www.reddit.com/r/CMMC/comments/1y0lxul/vdi_enclave_but_needs_cac_authentication) - reddit-cmmc