Most machine shops do not need CMMC Level 2 for the whole company. Level 2 applies to the assets that process, store or transmit CUI, and to the assets that protect them. Put CUI in an enclave, give enclave access only to the people who handle it, and keep everyone else's systems out of reach. On the shop floor, the boundary between that enclave and the machines is an industrial DMZ, and a shop-floor access gateway such as Trout Access Gate CMMC for OT is one in a box: it keeps the CNCs and PLCs that receive CUI inside the boundary without pulling the whole plant network into scope.
The answer flips when CUI is everywhere. If CUI drawings sit on the shared file server, arrive in every inbox and print on every printer, then every one of those systems is in scope, and so is most of the company. Scoping means moving CUI into a smaller set of systems before the assessment.
This post walks through the five asset categories, how an enclave limits scope to the people who handle CUI, where the machines land, and what the industrial DMZ does at the boundary.
Who is in CMMC scope at a 150-person machine shop?
CMMC scopes assets. A person is in scope through the systems they use. Take a typical 150-person shop with a DoD contract:
| Group | Uses CUI? | In scope? |
|---|---|---|
| Program managers, buyers and quality engineers on the DoD job | Yes, they open the drawings and the purchase order | Yes, through the enclave systems they use |
| CAM programmers | Yes, they build toolpaths from CUI drawings | Yes, with their CAD/CAM workstations |
| Machinists and inspectors on DoD parts | They run the program and inspect the part | Through the machines, which are in scope |
| Office staff, sales, HR, finance | No | No, if their systems cannot reach CUI |
| Machinists on commercial work only | No | No, if their machines have no path to CUI |
The people who never touch CUI stay out of scope only if their laptops and their machines have no path to it. You show this with the network diagram and the firewall rules. An org chart does not prove it.
What are the five CMMC asset categories?
32 CFR 170.19 sorts every asset in a Level 2 scope into one of five categories. Each one asks for something different:
| Category | What it is | What Level 2 asks | Shop-floor example |
|---|---|---|---|
| CUI asset | Processes, stores or transmits CUI | Assessed against the NIST SP 800-171 requirements | CAD/CAM workstation, DNC server, enclave file share |
| Security protection asset | Provides security functions to the scope | Assessed against the requirements it supports | Firewall, identity provider, Access Gate CMMC for OT (Trout) in front of the machines |
| Contractor risk managed asset | Can handle CUI, but your policies and practices keep CUI off it | Documented in the inventory, SSP and network diagram | An MES or ERP server that tracks DoD jobs by part number only |
| Specialized asset | OT, IoT and Industrial IoT, test equipment, government-furnished equipment, restricted information systems | Documented in the inventory, SSP and network diagram, and managed under your risk-based policies | CNC controller, PLC, CMM, test stand |
| Out-of-scope asset | Cannot process, store or transmit CUI, and provides no security protection to CUI assets | Nothing, but the separation must hold | Office laptops and commercial-only machines with no path to CUI |
Two details trip up machine shops. A contractor risk managed asset is still in scope: the assessor can check it if the SSP does not show how your practices keep CUI off it. And a security protection asset is assessed even if it never holds CUI. The gateway that controls who reaches the machines is one of them.
How does an enclave limit scope to the employees who handle CUI?
An enclave is the part of your environment where CUI lives. Only the enclave systems, the machines that receive CUI and the systems that protect them are in your assessment scope. Four steps build it:
- Find every copy of CUI. Follow one DoD drawing from the prime's portal to the desk, the CAM station, the DNC server, the CNC, the CMM and the printer. Each stop holds a copy.
- Move the desk side into an IT enclave. That can be Microsoft GCC High through a managed provider, a hosted virtual desktop or an encrypted email and file service. Give enclave accounts only to the people on the DoD work.
- Put the machines behind a boundary you control. The CNCs, CMMs and printers that receive CUI stay on the floor. Their access, MFA and logging happen at the industrial DMZ in front of them.
- Document the boundary. The SSP, the asset inventory and the network diagram show the enclave, the machines inside it and the assets left outside.
The CMMC enclaves for small manufacturers guide compares the enclave types for step 2. The rest of this post covers step 3.
Where do the machines land?
A machine that receives CUI programs, drawings or files is in scope. Most CNC controllers, PLCs, HMIs and CMMs are operational technology, so you can categorize them as specialized assets. A machine on commercial work stays out of scope only if it has no path to CUI assets. On a flat plant network where every machine can reach the DNC server, that test fails for all of them.
The machine-by-machine sort is in Are manufacturing machines in scope for CMMC?. On the shop floor, network paths decide scope. A machine is out of scope when nothing connects it to CUI. It is a manageable specialized asset when something in front of it controls who reaches it and records what happens.
What does the industrial DMZ do at the boundary of the CUI enclave?
The industrial DMZ (IDMZ) is the zone between the CUI enclave and the shop floor. Every flow that crosses it is named, checked and logged: a toolpath from the CAM station to a CNC, an inspection report from a CMM back to the enclave, a vendor session to one machine. Nothing goes straight from the office network to a machine.
Plants already have two things that look like this boundary. Neither does the same job:
| IT enclave | Firewall segmentation (VLANs and rules) | Industrial DMZ (Access Gate CMMC for OT (Trout)) | |
|---|---|---|---|
| Where it sits | The desk: email, files, engineering workstations | Between network segments | Between the CUI enclave and the shop floor |
| What it controls | Who uses CUI at a workstation | Which address can reach which port | Which named person or system reaches which machine, for how long |
| MFA before a machine session | No, it stops at the desk | No | Yes, at the gate |
| Session record for the assessor | Enclave logs only | Allowed and blocked packets | Every session, with the user, the time and the machine |
| Effect on scope | Holds the desk side of CUI | Separates segments but does not identify people | Keeps the CUI machines in the boundary and the rest of the plant out |
Trout Access Gate is the industrial DMZ in one appliance. It connects beside your existing firewall, which stays the perimeter. You add one rule on your firewall or router that forwards the machine traffic to Access Gate, and nothing is installed on the machines. Access Gate is installed in a day, and the enclave is complete in a week. See Access Gate IDMZ for how the IDMZ jobs fit in one system.
Because the gateway provides security functions to the scope, it is a security protection asset and it is assessed. That is why it produces its own evidence: the machine inventory, the enforced access rules and the session logs.
How do you write the scope into the SSP?
The assessor reads the scope from three documents. Keep them consistent:
- The asset inventory lists every asset in scope with its category, including each CNC, PLC and CMM that receives CUI.
- The network diagram shows the enclave, the industrial DMZ and the machines behind it, and the paths that cross the boundary.
- The System Security Plan explains why each asset sits in its category and how the specialized assets are managed.
For a machine that cannot meet a control and cannot be changed, write an enduring exception and pair it with a compensating control. The guide to CMMC exceptions and compensating controls for OT lists what each entry needs.
What changed with the Phase II suspension?
CMMC Phase II third-party assessments have been suspended since 13 July 2026. The audits are paused, but the controls are still required. NIST SP 800-171 still applies through DFARS 252.204-7012, and the score you post in SPRS covers the scope you declare. A smaller scope is fewer systems to protect, document and affirm.
Start by following one drawing.
Pick one DoD part. Follow its drawing from the prime's portal to the printer on the floor, and write down every system it touches. That list is the first draft of your scope. Everything not on it is a candidate to stay out.
Machine vendors reach the same machines from outside. See why vendor remote access under CMMC belongs in the industrial DMZ, and the CMMC compliance hub for the full on-premise approach.