Secure remote access for machine vendors under CMMC means ending every vendor session in the industrial DMZ. The vendor signs in with a named account and MFA, reaches the one machine they service, for a set time, and the session is recorded. A shop-floor access gateway such as Trout Access Gate CMMC for OT is where those sessions end. The vendor's laptop never joins your plant network, and the CNC or PLC needs no software installed.
This post explains why the end point of the session decides whether you pass. For the step-by-step setup, every NIST SP 800-171 control and the evidence list, see the guide to secure remote access for machine vendors under CMMC.
Where does a vendor session end today?
Machine builders and service vendors reach your CNCs, PLCs, HMIs and CMMs for support. Every method in use today ends the session somewhere. That end point decides what the vendor can reach and what you can show an assessor.
| Where the session ends | Typical method | What the vendor can reach | What you can show the assessor |
|---|---|---|---|
| On the machine | Remote desktop software on an HMI or PC | That machine, plus whatever it can reach | The tool's own log, held in its cloud |
| On the plant network | Client or site-to-site VPN | Every machine on the segment | The VPN connection time only, with no machine or action |
| In the IT enclave | Virtual desktop in GCC High | The enclave, then the floor through whatever path exists | Enclave logs. The path to the machine needs its own record |
| On the firewall | A rule that allows the vendor's address | The ports the rule opens | Allowed and blocked packets, with no person attached |
| In the industrial DMZ | Access Gate CMMC for OT (Trout) | One machine, for a set time | The named user, the MFA event, the machine, the time and a session recording |
With the first four methods, nothing you control sits between the vendor and the machine. In the industrial DMZ, the session ends at a gateway you control, and the gateway opens a separate connection to one machine.
Which CMMC controls point to the industrial DMZ?
NIST SP 800-171 Rev. 2 is what CMMC Level 2 assesses. Five controls decide where a vendor session should end:
| Control | What it asks | What the industrial DMZ does |
|---|---|---|
| AC.L2-3.1.14 | Route remote access through managed access control points | Every vendor session ends at the gate. There is no other path to the machines |
| AC.L2-3.1.12 | Monitor and control remote access sessions | Sessions are time-limited, can be ended at any time, and are recorded |
| IA.L2-3.5.3 | MFA for network access | The vendor passes MFA at the gate before any traffic reaches a machine |
| MA.L2-3.7.5 | MFA for nonlocal maintenance, and end the session when maintenance is done | Maintenance sessions need MFA and close when the window ends |
| AU.L2-3.3.1, AU.L2-3.3.2 | Audit records traceable to each user | Each session is logged with the person, the time, the source and the machine |
Control 3.1.14 is the core of the argument. A managed access control point is a place you own, where every remote session is checked. On the shop floor, that place is the industrial DMZ. A CNC controller cannot ask for MFA or keep an audit log, so the gate in front of it does both. The guide lists the remaining controls, including least privilege (3.1.5), external connections (3.1.20) and FIPS-validated encryption (3.1.13, 3.13.11).
How is the industrial DMZ different from the IT enclave and the firewall?
Plants with a CUI enclave often ask why the enclave or the firewall cannot handle vendors. Each one covers a different part of the path.
The IT enclave covers the desk. A GCC High enclave or a hosted virtual desktop holds the drawings and the people who handle them. It ends at the plant boundary. A vendor who works from a virtual desktop in the enclave still needs a controlled path from that desktop to the machine on your floor.
The firewall covers the perimeter. Your Fortinet, Meraki or Palo Alto firewall decides which addresses can reach which ports. A firewall rule does not know which person is behind an address. It does not ask for MFA per session, and it does not record what was done on a PLC. You keep the firewall as the perimeter.
The industrial DMZ covers the boundary between the enclave and the shop floor. It identifies each person, applies MFA, limits each session to one machine and one time window, and records it. Access Gate IDMZ puts these jobs in one appliance: zone filtering, an authenticating proxy, a bastion for remote access, MFA and the audit log.
What does a vendor session look like at the gate?
- The vendor signs in. They use a named account and MFA. Their own VPN or 4G link only carries the connection, and they get no address on your plant network.
- The rule names one machine and a time window. A rule for a grinder service call opens the grinder's controller from 2 pm to 4 pm. The rest of the line stays out of reach, and at 4 pm the session drops.
- Commands are checked. Access Gate reads the industrial protocol, so you can let a vendor read a PLC and block writes or program downloads.
- The session is recorded. You can replay it. The recording is the evidence the assessor asks for under 3.1.12 and 3.3.2.
The tunnel built into Access Gate CMMC for OT uses FIPS 140-3 validated modules, CMVP certificates #5441 and #5031. Access Gate connects beside your existing firewall or router. You add one rule that forwards the machine traffic to it, and nothing is installed on the machines.
What does a C3PAO see when vendor access ends in the DMZ?
The assessor asks for the remote access policy, the list of vendor accounts, proof that MFA ran on a real vendor session, a sample session log and the SSP entry. When every vendor session ends at one gate, each of those comes from one place. Access Gate exports the vendor accounts and the enforced rules, and the session logs carry the person, the time and the machine.
The machines themselves are usually specialized assets. Access Gate is a security protection asset, so it is assessed against the controls it provides. For how the gate fits into the overall scope, see how to keep CMMC scope to the people and machines that touch CUI.
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. Vendor remote access, MFA and audit logging still apply through DFARS 252.204-7012 to every contract with CUI, and your SPRS score covers them.
List your vendors first.
Write down every vendor who reaches a machine today, how they get in and which machines they touch. Each line that ends on the machine, on the plant network or on a firewall rule is a session to move into the industrial DMZ.
For the full control mapping and the access methods compared, read secure remote access for machine vendors under CMMC. The CMMC compliance hub covers the rest of the shop floor.