Print CUI from CUI Vault to the plant floor, CMMC ready

A CUI drawing sits safely in the CUI Vault enclave — then someone has to print it on the plant floor. This demo shows that last hop to an on-premise printer, protected by Trout Access Gate: blocked by default, opened by a named admin, logged, and locked back down.

Watch on YouTube

What you see

  • Asset inventory. Every on-premise IT and OT machine that handles CUI (CM.L2-3.4.1).
  • Blocked by default. The print job is denied until allowed by exception (SC.L2-3.13.6).
  • Human activation. A named admin opens one path, to one printer (AC.L2-3.1.1, 3.1.2).
  • Authenticated and logged. The job is tied to a named user and sent through a FIPS 140-3 validated VPN tunnel (IA.L2-3.5.1, 3.5.2, AU.L2-3.3.1, 3.3.2, SC.L2-3.13.11).
  • Back to baseline. The printer locks down again once the job is done.

Nothing is installed on the printer. CUI Vault runs the managed GCC High enclave; Access Gate sits in the plant, in front of the machines. Together they give one controlled path from the cloud to the physical part.

Chapters

  • 0:00 — CUI Vault VDI, the plant printer
  • 0:15 — Asset inventory, IT and OT
  • 0:32 — Job blocked by default
  • 0:43 — Human activation and the FIPS 140-3 tunnel
  • 1:01 — Locked back to baseline
Talk to us about CUI Vault Subscribe on YouTube All videos

More demos