TroutTrout
Back to Blog
CMMCSegmentationIndustrial DMZOT Security

Industrial DMZ, firewall segmentation or CMMC enclave: what each one does

Trout TeamLast updated: 6 min read

The short version

To segment CNC and CMM machines for CMMC Level 2, put them in their own zone and control every path into that zone with an industrial DMZ. Firewall segmentation keeps the zone apart from the office and the rest of the plant. An industrial DMZ appliance, such as Trout Access Gate CMMC for OT, authenticates each person before a session reaches a machine, applies per-machine rules and logs every session. The IT enclave keeps its own job: protecting CUI on email, files and workstations.

The three are often confused because all three draw a boundary. They draw it in different places, for different reasons. This post compares them job by job, so you can see which one covers which NIST SP 800-171 requirement on the shop floor.

What each one does, job by job

JobFirewall segmentationIT enclaveIndustrial DMZ with Access Gate CMMC for OT (Trout)
Where it draws the boundaryBetween networks or VLANsAround the people and systems that handle CUIBetween the IT side and the machines
Keeps CNCs and CMMs apart from the office networkYes, by network and portNo, it does not reach the floorYes, every flow to a machine is filtered
Knows who is behind a connectionNo, it sees IP addressesYes, for its own users and appsYes, each session is tied to a named user
MFA in front of a controllerNoNo, MFA stops at the deskYes, before any traffic reaches the machine
Vendor access to one machineA rule that opens a pathNot in scopeA time-bound session to one machine, recorded
Logs an assessor can readAddresses and portsUsers, files and mailUser, time, source and target for every session
What changes on the networkNew VLANs, rules and often new IP addressesA tenant or a new file serviceOne rule on your existing firewall or router

What does firewall segmentation cover for CMMC?

Firewall segmentation separates networks. It is the first step every plant should take. A CNC on the same flat network as the office PCs is reachable from every one of them. Putting the machines in their own VLAN, with rules that allow only the flows they need, serves 3.13 System and Communications Protection.

A firewall does not cover the rest. A firewall rule allows traffic from an address. It does not know whether the person at that address is the programmer, a vendor or an attacker on a stolen laptop. It cannot ask for MFA in front of a controller. Its logs record addresses and ports, which an assessor cannot match to a named user. Segmenting by VLAN also usually means switch changes, new IP addresses on machines and a downtime window, which is why many plants put it off.

What does an IT enclave cover?

An IT enclave protects CUI where people work on it. It can be Microsoft GCC High, an encrypted email and file service, a single hardened PC or a hosted virtual desktop. Those are good answers for the drawings in your inbox and on your file share.

None of them reaches the shop floor. A CNC controller cannot join a GCC High tenant. A CMM cannot run an endpoint agent. When the drawing becomes a program and goes to the machine, it leaves the IT enclave. For that boundary, see the industrial DMZ in a CMMC enclave.

What does an industrial DMZ add?

An industrial DMZ controls who reaches which machine, and records it. In the Purdue model it sits at Level 3.5, between the office network and the control network. In a classic design it is built from two firewalls, a jump server, a directory with MFA, protocol gateways and a log collector. That is a network project of several months.

Access Gate IDMZ does those jobs in one appliance that sits beside your existing network. For CMMC, Access Gate CMMC for OT adds the VPN for remote and vendor access, which uses FIPS 140-3 validated modules. In front of the CNCs and CMMs it does four things:

  1. It filters every flow between the zones. Only the program downloads and reports you approve go through.
  2. It asks each person for MFA on a login page before traffic reaches a machine.
  3. It gives a vendor a time-bound session to one machine and records it.
  4. It writes one tamper-evident log with the user, the time, the source and the target.

For the machines that cannot meet a control on their own, that is the compensating control you document in the SSP. The CMMC requirements for OT and specialized assets explain how CNCs and CMMs are categorized.

How do the three fit together in one plant?

Use all three, each for its own job. The firewall stays at the perimeter and keeps the zones apart. The IT enclave holds CUI for the people who handle it. The industrial DMZ sits between the IT side and the machines.

A typical defense machine shop looks like this:

ZoneWhat sits in itWhat protects it
OfficeCommercial Microsoft 365 users who never touch CUIThe perimeter firewall
IT enclaveCAD and CAM stations, the CUI file share, the people who handle drawingsGCC High or another IT enclave
Machine zoneCNC controllers, CMMs, the DNC server, PLCs on the same lineAccess Gate CMMC for OT (Trout) as the industrial DMZ

Only the IT enclave and the machine zone are in your CMMC assessment scope. The office stays out, as long as it cannot reach CUI and is separated from the enclave. The CUI enclave architecture covers the scoping rules in 32 CFR 170.19.

How long does it take?

Access Gate is installed in a day. You connect it to your existing firewall or router and add one rule that forwards the machine traffic to it. The machines keep their IP addresses, and nothing is installed on them. Removing the rule is the rollback. A single-plant enclave, with scope, policies and evidence, is complete in a week.

CMMC Phase II assessments have been paused since July 2026, but the controls still apply through DFARS 252.204-7012. Segmenting the machines now keeps your SPRS affirmation accurate for the shop floor.


For the full approach, see CMMC compliance for defense manufacturers. For machines that cannot meet a control at all, see CMMC exceptions and compensating controls for OT.

FAQ

Frequently Asked Questions

How do you segment CNC and CMM machines for CMMC Level 2?
Put the CNC controllers, CMMs and the DNC server that feeds them in their own zone, separate from the office network and the rest of the plant. Allow only the flows the work needs, such as program downloads and inspection reports. Then require every person and vendor to authenticate before a session reaches a machine, and log each session. An industrial DMZ appliance such as Trout Access Gate does the authentication, the per-machine rules and the logging beside your existing firewall.
Is firewall segmentation enough for CMMC on the shop floor?
It covers part of 3.13 System and Communications Protection: it keeps zones apart. It does not authenticate the person behind a connection, ask for MFA in front of a controller, or log sessions by named user. Those controls sit in 3.1, 3.3 and 3.5. Trout Access Gate adds them in front of the machines, and your firewall keeps its job at the perimeter.
Do we need VLANs to segment machines for CMMC?
Not necessarily. VLANs are one way to separate zones, and they usually mean switch changes, new IP addresses and a downtime window. Trout Access Gate separates the machines at the network layer without re-addressing them. You add one rule on your existing firewall or router that forwards the machine traffic to it.
Does the IT enclave cover the machines?
No. GCC High, an encrypted file service or a hardened workstation protects CUI where people work on it. None of them can enforce anything on a CNC controller or a CMM. The machines need their own boundary inside the same enclave and the same SSP. Trout Access Gate provides that boundary in front of the machines.
Does Access Gate replace our firewall?
No. Your Fortinet, Meraki or Palo Alto firewall stays at the edge. Trout Access Gate sits beside it and handles the machines: per-machine access, vendor sessions and audit evidence. On a Meraki MX the change is one VLAN, one static route and one source-based route.
Which NIST SP 800-171 families does each layer cover?
Firewall segmentation mainly serves 3.13 System and Communications Protection. The IT enclave covers most families for the systems people use. The industrial DMZ covers 3.1 Access Control, 3.3 Audit and Accountability, 3.5 Identification and Authentication and part of 3.13 for the machines that cannot meet them on their own.