CUI Enclave Patterns for Small Manufacturers and CMMC Scoping
How a small defense supplier can shrink its CMMC Level 2 scope with a CUI enclave: asset categories under 32 CFR 170.19, four enclave patterns and the mistakes that break them.
- PUBLISHED
- November 15, 2026
- READ TIME
- 7 MIN
- AUTHOR
- ONE FREQUENCY
- Topic
- cmmc, cui, nist-800-171
- Published
- November 15, 2026
- Read time
- 7 min
- Word count
- 1,293
Short answer: A CUI enclave is a small, separately managed environment where a company keeps controlled unclassified information (CUI) so that the rest of its business stays out of the compliance boundary. For a small manufacturer or software supplier, an enclave usually cuts the number of assets that must meet the 110 requirements of NIST SP 800-171 Revision 2, which is the basis for CMMC Level 2. It only works if the boundary is real: CUI must never leave it, and the scope must be documented in the system security plan.
This article describes design patterns. It is not legal advice, and One Frequency Inc claims no CMMC certification and is not a certified third-party assessor organization (C3PAO). It extends our guide to CMMC and NIST 800-171 for small defense suppliers.
What is CUI, and who decides what counts?
CUI is information that the government creates or possesses, or that an entity creates or possesses for the government, that a law, regulation or government-wide policy says must be safeguarded or dispersed with controls. The National Archives (NARA) runs the CUI program under 32 CFR Part 2002 and publishes the CUI Registry of categories. For a defense supplier, your contract and the markings on drawings, specifications and data tell you what is CUI. If you are unsure, ask your contracting officer or prime in writing before you design the boundary.
What does the CMMC scoping rule say about assets?
32 CFR 170.19 sets the CMMC assessment scope before an assessment. For Level 2 it defines asset categories:
- CUI assets: assets that process, store or transmit CUI. They are assessed against all Level 2 requirements.
- Security protection assets: assets that provide security functions to the scope. They are assessed against the Level 2 requirements relevant to what they do.
- Contractor risk managed assets: assets that can, but are not intended to, process CUI because of policy and procedure. They are documented in the inventory, the SSP and the network diagram, and an assessor reviews the SSP and may run a limited check.
- Specialized assets: assets such as IoT, IIoT and operational technology, government furnished equipment, restricted information systems and test equipment. They are documented and managed with risk-based practices, and are not assessed against the other requirements.
- Out-of-scope assets: assets that cannot process, store or transmit CUI and provide no security protection to CUI assets. You must be prepared to justify that.
The rule gives an example worth designing around: an endpoint hosting a VDI client configured to allow no processing, storage or transmission of CUI beyond keyboard, video and mouse is considered out of scope. That is the core idea of a virtual desktop enclave.
What are the common enclave patterns?
- Virtual desktop enclave. CUI lives in a hosted desktop environment. Staff connect from ordinary laptops with a client that blocks copy, paste, file transfer and printing. Under 170.19 the endpoint can be out of scope if the client really allows only keyboard, video and mouse, while the hosted desktop and its supporting services are in scope.
- Dedicated CUI workstations. A few hardened, separately managed computers on a segmented network, used only for CUI work. Simple and good for very small teams, but every such machine is fully in scope.
- Cloud collaboration enclave. CUI is kept in a government-community cloud tenant or equivalent. Under DFARS 252.204-7012 a cloud service provider that stores, processes or transmits covered defense information must meet the FedRAMP Moderate baseline or an equivalent, and 170.19 says the CSP must meet the FedRAMP requirements in that clause. Obtain the provider's customer responsibility matrix, because you stay responsible for what the provider does not cover.
- Managed enclave from a service provider. An external service provider runs the enclave for you. Under 170.19 the provider's services that handle CUI fall in your assessment scope, and the use must be documented in your SSP with the provider's service description and responsibility matrix.
How do you keep CUI inside the boundary?
- Identity first. Use phishing-resistant multi-factor authentication for enclave access and limit it to named people with a need.
- Data flow control. Block email, chat, personal cloud storage and removable media paths from the enclave. Define the single approved way to move data in and out, and log it.
- Segmentation. Keep enclave systems on a separate network or tenant, with deny-by-default rules and no shared admin accounts with the rest of the business.
- Security protection assets. Logging, vulnerability scanning, endpoint protection and identity services that protect the enclave are in scope. List them.
- Documentation. The inventory, network diagram and SSP must describe the enclave, the asset categories and each data flow. An assessor tests what the paper says.
- Training and rules. Tell staff what CUI looks like and what they must not do outside the enclave. A policy that nobody follows will fail in practice.
What mistakes break an enclave?
The common failures are CUI that arrives by email and is forwarded outside the boundary, shared accounts, engineers who download files "just for a moment," unmanaged backups, and a provider that does not meet the FedRAMP requirement. Map every place CUI can arrive, including supplier portals and customer file shares, before you declare the boundary.
How should small manufacturers think about shop-floor equipment?
CNC machines, test stands and other operational technology often cannot be fully secured. 170.19 lets you treat them as specialized assets if you document them in the inventory, SSP and network diagram and manage them with risk-based practices. Do not rely on that category as a loophole: if a machine receives CUI files, the rule treats it by what it does, so isolate it or route files through the enclave.
How One Frequency approaches this
One Frequency provides cybersecurity and compliance engineering and AI systems work. Our founder led SOC 2 at a Series A cybersecurity company and led engineering and the FedRAMP High effort for a zero-trust secure remote access platform for operational technology and industrial control systems. We apply that experience to scoping, enclave architecture, evidence collection and policy-as-code. We are a service-disabled veteran-owned small business; we hold no CMMC certification and are not a C3PAO. See our cybersecurity and compliance and government contracting pages, the CMMC Level 2 guide, or contact us.
FAQ
Q: What is a CUI enclave? A: A separately managed environment that holds CUI so the rest of a company stays outside the compliance boundary. It reduces the number of assets that must meet NIST SP 800-171, if CUI never leaves it and the boundary is documented in the system security plan.
Q: Does an enclave make my laptops out of CMMC scope? A: Possibly. 32 CFR 170.19 says an endpoint hosting a VDI client configured to allow no processing, storage or transmission of CUI beyond keyboard, video and mouse is considered out of scope. The configuration must really enforce that, and an assessor can test it.
Q: Can I put CUI in a commercial cloud? A: Only if the provider meets the FedRAMP requirements in DFARS 252.204-7012, which means the FedRAMP Moderate baseline or an equivalent. Get the provider's customer responsibility matrix and document the relationship in your SSP.
Q: Are CNC machines and other shop equipment in scope? A: If they can process, store or transmit CUI but cannot be fully secured, they can be treated as specialized assets, which you must document and manage with risk-based practices. Isolating them from CUI file flows is safer.
Q: Does One Frequency hold a CMMC certification? A: No. One Frequency Inc claims no CMMC certification and is not a C3PAO. We describe approaches and provide engineering support for suppliers preparing for assessment.
Cited and consulted.
- 0132 CFR 170.19: CMMC scoping (asset categories, ESP and CSP requirements)ecfr.gov · accessed Nov 15, 2026
- 0232 CFR Part 2002: Controlled Unclassified Information (NARA)ecfr.gov · accessed Nov 15, 2026
- 03National Archives: Controlled Unclassified Information program and CUI Registryarchives.gov · accessed Nov 15, 2026
- 04DFARS 252.204-7012: Safeguarding Covered Defense Information and Cyber Incident Reportingacquisition.gov · accessed Nov 15, 2026
- 05NIST SP 800-171 Revision 2: Protecting CUI in Nonfederal Systemscsrc.nist.gov · accessed Nov 15, 2026
- 0632 CFR Part 170: CMMC Program (eCFR)ecfr.gov · accessed Nov 15, 2026
- 07SBA: Release on the suspension of CMMC Phase II (July 13, 2026)legacy.sba.gov · accessed Nov 15, 2026
Ready to ship the next outcome?
One Frequency Consulting brings 25+ years of technology leadership and military discipline to every engagement. First call is operator-grade scoping — sixty minutes, no charge.