TroutTrout
Back to Blog
CMMCCUIIndustrial DMZOT Security

The industrial DMZ in a CMMC enclave: where the shop floor meets CUI

Trout TeamÚltima actualización: 7 min read

The short version

A CMMC enclave that includes OT and production equipment needs an industrial DMZ between the IT side of the enclave and the machines. The IT enclave holds CUI where people work on it: email, files and engineering workstations. An industrial DMZ appliance, such as Trout Access Gate CMMC for OT, carries the same boundary down to the CNC controllers, PLCs and CMMs that receive drawings and programs, with nothing installed on the machines.

If your enclave covers email and files but CUI ends up on the machine controllers, the enclave stops too early. You do not need a new enclave. Bring the machines into the same scope, document them as specialized assets, and put an industrial DMZ in front of them so every connection is authenticated and logged.

Part of the enclaveWhat it protectsTypical tool
IT enclaveEmail, files, CAD and collaboration on CUIGCC High, an encrypted file service, or an on-premise file server
Industrial DMZThe path from the IT side to the machines, and every session that crosses itAccess Gate CMMC for OT (Trout), beside the existing network
Machines (specialized assets)CNC controllers, PLCs, HMIs, CMMs that load CUINothing is installed on them. They are documented in the SSP

Why does CUI end up on the machine controllers?

To make a part, the drawing has to reach the machine. A CAM station turns a CUI drawing into a toolpath. A DNC server or file share sends the program to the CNC controller. A CMM loads the model to inspect the part, and the inspection report comes back. Each of these steps stores or transmits CUI.

Most enclave projects start with email and file storage, because that is where CUI arrives. The shop floor gets left out because its machines cannot run agents, take patches or ask for MFA. The drawing still reaches those machines, so CUI sits on systems the enclave does not cover.

32 CFR 170.19 sorts every asset into a category. A machine that receives CUI is in scope. CMMC lets you treat OT as a specialized asset: at Level 2 you document it in the inventory, the SSP and the network diagram, and the assessor does not test it against each requirement. The full breakdown, machine by machine, is in are manufacturing machines in scope for CMMC.

What does the industrial DMZ do inside a CMMC enclave?

The industrial DMZ is the controlled boundary between the IT systems and the machines. In a classic design it sits at Level 3.5 of the Purdue model, between the office network and the control network. No traffic goes straight from IT to a controller. Each flow that has to cross goes through a service in the DMZ.

Inside a CMMC enclave, the IDMZ does four jobs that the IT tools cannot do on the floor:

JobNIST SP 800-171 familyWhat it means on the floor
Keep the CUI machines apart from the rest of the plant3.13 System and Communications ProtectionOnly approved flows reach a CNC or a PLC
Authenticate people before a session reaches a machine3.1 Access Control, 3.5 Identification and AuthenticationMFA at the boundary, for machines that cannot ask for it
Log every connection3.3 Audit and AccountabilityUser, time, source and target, for every session
Give vendors a time-bound session to one machine3.1 Access ControlNo standing account and no open path into the segment

This is the compensating control an assessor expects to see for machines that cannot meet a control on their own. Where a machine can never meet a requirement, record it as an Enduring Exception and point to the boundary as the compensating control.

How is an industrial DMZ different from the IT enclave?

The IT enclave protects CUI where people handle it. The industrial DMZ protects the path to the machines that use it. GCC High, an encrypted file service or a hardened workstation all stop at the person. None of them can enforce anything on a CNC controller or a PLC, because there is nothing on the controller to enforce it with.

The two are parts of one enclave, with one System Security Plan. The CUI enclave architecture shows how a GCC High tenant and an on-premise enclave on the shop floor fit together. With CUI Vault, Access Gate receives jobs from the GCC High enclave over a site-to-site tunnel that uses FIPS 140-3 validated modules (CMVP #5441 and #5031), so a job reaches the machine without landing on a workstation.

How is an industrial DMZ different from firewall segmentation?

A firewall decides which networks can talk. An industrial DMZ also decides who, on which machine, and records it. VLANs and firewall rules separate the plant into zones, which is the first step and a good one. They do not authenticate the person behind a connection, they do not ask for MFA in front of a controller, and their logs show addresses rather than named users.

A classic IDMZ adds those services on top of the firewalls: a jump server, a directory with MFA, protocol gateways and a log collector. That is a network project. The side-by-side comparison is in industrial DMZ, firewall segmentation or CMMC enclave.

How do you add the shop floor to an existing enclave?

Five steps cover it.

  1. Trace the path of one drawing. Follow it from the inbox or file share to the CAM station, the DNC server, the controller and the CMM. Every system on that path is in scope.
  2. List the machines. Record type, firmware, network address and owner for each one. This is also the baseline inventory NIST SP 800-171 control 3.4.1 asks for.
  3. Classify them. CAM stations and DNC servers are usually CUI assets. Controllers and CMMs are usually specialized assets.
  4. Put the industrial DMZ in front of them. Connect Access Gate to your existing firewall or router and add one rule that forwards the machine traffic to it. Nothing is installed on the machines, and production keeps running.
  5. Update the SSP and the network diagram. Show the boundary, the machines behind it and the evidence it produces.

Access Gate is installed in a day, and a single-plant enclave is complete in a week. Elna Magnetics used it to secure 100% of its CUI flows for CMMC Level 2, including engineering workstations, file servers and the production floor.

Which Access Gate fits a CMMC shop floor?

Access Gate CMMC for OT is the product for this job. It comes in two sizes: Access Gate CMMC for a small plant or a single shop floor, and Access Gate CMMC Performance for a main plant with more machines. Both include the VPN for remote and vendor access, which uses FIPS 140-3 validated modules. For a plant that needs an industrial DMZ outside of CMMC, Access Gate IDMZ does the same jobs.

Does the Phase II suspension change any of this?

CMMC Phase II third-party assessments were suspended in July 2026. The controls still apply. NIST SP 800-171 binds you through DFARS 252.204-7012, and the score you post and affirm in SPRS covers the machines that receive CUI.


For the whole picture, see CMMC compliance for defense manufacturers. For the cloud side of the enclave, see the CUI enclave architecture.

FAQ

Frequently Asked Questions

How do you build a CMMC enclave that includes OT and production equipment?
Keep the IT enclave for the people who handle CUI, and add the shop floor to the same boundary. List the CNC controllers, PLCs, HMIs and CMMs that receive CUI as specialized assets in the inventory, the SSP and the network diagram. Then put an industrial DMZ between the IT side and the machines, so every connection is authenticated and logged. Trout Access Gate is an industrial DMZ appliance that does this beside your existing network, with nothing installed on the machines.
Our enclave covers email and files, but CUI ends up on the machine controllers. What do we do?
Extend the enclave to the machines instead of starting over. Trace the path a drawing takes from the file share to the CAM station, the DNC server and the controller, and bring every system on that path into scope. Put the controllers behind an industrial DMZ such as Trout Access Gate, which enforces MFA and per-machine access in front of them and logs every session. Document the controllers as specialized assets in the SSP.
What is an industrial DMZ?
An industrial DMZ (IDMZ) is a buffer zone between the office IT network and the OT network, at Level 3.5 of the Purdue model. No traffic goes straight from IT to the machines. Each flow that has to cross, such as a program download or a vendor session, goes through a service in the DMZ where it is authenticated and logged.
Is an industrial DMZ the same as the CMMC enclave?
No. The enclave is the scope: every system that stores, processes or transmits CUI. The industrial DMZ is the controlled boundary inside that scope, between the IT systems and the machines. A plant can have an enclave with no IDMZ, and then the machines usually sit on a flat network with the rest of the plant.
Do we have to install anything on the CNC controllers or PLCs?
No. Trout Access Gate sits beside your network and enforces access in front of the machines. You connect it to your existing firewall or router and add one rule that forwards the machine traffic to it. Removing that rule is the rollback.
Does the CMMC Phase II suspension change this?
Phase II third-party assessments are paused, but the controls still apply. NIST SP 800-171 binds you through DFARS 252.204-7012, and the score you affirm in SPRS covers the machines that receive CUI.