CMMC
How to Scope a CUI Enclave: GCC High, AVD, Boundary
A well scoped CUI enclave is the one decision that most cuts the cost, time and risk of CMMC Level 2. Here is how to draw it.
Cybersecurity Consulting, a Capital Cyber practice in Leesburg, Virginia, provides CISO level leadership for CMMC, NIST SP 800-171 and federal authorization, with a program for ITAR technical data.
What is a CUI enclave?
It is a small, walled off part of your setup where Controlled Unclassified Information, or CUI, may live. NIST SP 800-171 then applies to it, not the whole company.
It is a set of people, systems and data flows, the only places CUI is stored, processed or sent. Everything inside must meet all 110 requirements.
Everything outside must be kept from CUI, and an assessor checks how.
It can be a separate cloud tenant, virtual desktops, a walled off network with its own servers, or a mix. The design follows the data, not the org chart.
The engineers who read drawings need to be inside. The receptionist who books deliveries usually does not.
Why scope before buying any tools?
The scope decides what each tool must cover. Buy first, and the tool sets the scope.
Buy an endpoint product for every laptop, and every laptop is now in the talk, needed or not.
List your data flows. Where does CUI arrive, from whom, and in what form? Who opens it, on what devices?
Where is it saved, printed, emailed or sent to a shop floor machine? Where does it leave, and to whom?
The answers usually show CUI touches far fewer people and systems than you thought. An enclave uses that.
How do you draw the boundary?
Draw it around every asset that stores, processes or sends CUI, plus every asset that protects them. Then prove the line holds.
The line goes on a network diagram and in the System Security Plan, or SSP. The two must agree.
Every path in and out should be known, filtered and logged: identity, email, file transfer, remote access, printing and any link to production gear.
An assessor will ask how CUI could escape. If a user can copy a drawing to a personal laptop, the diagram is wrong.
Where does Microsoft GCC High fit?
GCC High is Microsoft's government cloud for email, files and teamwork. It often suits an enclave when CUI arrives by email and lives in documents.
It is built for contractors with DFARS 252.204-7012 and export control duties. Microsoft backs those duties in its contract. That is a big reason firms pick it.
But it is not a compliance program, only a platform where the rules can be met. The setup, sign in rules, logging, data loss controls and procedures are still yours.
It has real costs: licenses, migration and fewer third party tools. Choose it when your data flows call for it. Do not choose it by default.
When does Azure Virtual Desktop make sense?
Use it, in a government region, when a small group works with CUI inside apps, not just email and files. Users log in to a virtual desktop that holds the CUI and the apps.
Only screen, keyboard and mouse traffic goes back to the device in front of them. The CMMC scoping rule covers this. A device whose desktop client is set so CUI cannot go beyond that traffic is out of scope.
The settings earn that. Set clipboard, drive mapping, printing and file transfer controls on purpose, and show an assessor.
How do the CMMC asset categories work?
CMMC scoping puts every asset in a category with its own duties.
CUI Assets handle the information directly.
Security Protection Assets protect the enclave. Think identity provider, logging platform or a managed security provider's tools.
Contractor Risk Managed Assets can handle CUI but are kept from it by policy and procedure.
Specialized Assets include operational technology, test equipment, Internet of Things devices and government property. Many cannot be fully set to the rules.
Out of Scope Assets cannot handle CUI at all, because they are cut off in hardware or network terms.
Placing each asset, and writing down why, is much of a scope review.
What about machines on the shop floor?
They are often the hardest part. A CNC controller that gets a program made from a controlled drawing may be handling CUI. It may run a system that cannot be patched or given modern controls.
Treat them as Specialized Assets. Put them on their own network segment. Control how programs reach them, and describe it all in the SSP.
You need not make a twenty year old controller meet every rule. Show the risk is understood, contained and managed.
What does a scope document contain?
The CUI data flow diagram.
The network diagram with the boundary marked.
The asset list, with a category and a reason for each asset.
The outside service providers and what each one does.
The cloud services in use, and how each meets the cloud rules of DFARS 252.204-7012.
It also records each decision and why, so an assessor can follow it. A scope is done when an outsider reads it and agrees CUI is nowhere else.
Next step: book a 30 minute call with the practice to test your CUI enclave boundary before you buy tools.