TroutTrout

DoD Zero-Trust for OT.

Point-by-point alignment to DTM 25-003 — how Access Gate delivers Target Level Zero Trust across all 7 DoD OT pillars without replacing a single device.

The DoD Is Mandating Zero Trust Across All OT Systems

Under DTM 25-003, all DoD Components must reach Target Level Zero Trust across OT environments — including PLCs, SCADA, sensors, and legacy systems that cannot be patched or moved to the cloud.

Traditional IT Security Cannot Be Applied to OT

The DoD guidance explicitly states that standard IT tools can be 'ineffective and potentially dangerous' in OT. Agents, scanners, and cloud enclaves disrupt safety-critical operations.

Legacy Equipment Must Be Protected in Place

OT environments prioritize availability and safety above all. Security must wrap existing assets without touching wiring, controllers, PLCs, or HMIs — no updates, no agents, no downtime.

One Appliance Per Site Is the Right Architecture

TAG deploys a single appliance per site, inserting a software-defined proxy in front of each OT asset. No network redesign. No downtime. Full Target Level coverage from day one.

Why Trout

Built for OT Zero Trust. Not Adapted from IT.

Every DoD OT-ZT pillar assumes the underlying infrastructure will remain unchanged. Trout's proxy-based architecture was designed from the ground up for exactly this constraint.

Proxy + SDN Overlay

A software-defined overlay inserts a lightweight, identity-aware proxy in front of each OT asset. Zero changes to PLCs, HMIs, controllers, or switches.

No Agents. No Downtime.

TAG attaches logically, not physically. All access — local, remote, contractor, OEM — passes through a Zero-Trust boundary without altering OT behavior.

Battle-Tested in the DIB

Proven in real production environments with unpatchable, safety-critical systems. Used by defense contractors working toward CMMC Level 2 and NIST 800-171.

DoD OT-ZT Pillars

Seven Pillars. Full Coverage. One Appliance.

Users

1. Users — Activities 1.1–1.9TAG ✓
DoD OT-ZT MandateTrout Capability
Identify all OT user accounts (1.1.1.OT)Identity gateway creates authoritative OT user and asset inventory
Enforce RBAC / least-privilege (1.2.2.OT)RBAC/ABAC enforced at the asset boundary, per task and port
Require MFA for OT access (1.3.1.OT)MFA enforced before any session initiation with OT assets
Control privileged accounts (1.4.x.OT)Privileged session broker with full recording and authorization
Manage contractor access (1.2.2.OT)Time-bound, identity-verified, fully audited contractor access
UNCLASSIFIED — PUBLIC RELEASE
Alignment Guide

Download the Full DoD OT-ZT Alignment Guide.

Full point-by-point mapping of DTM 25-003 requirements to Trout Access Gate capabilities across all 7 Zero-Trust pillars. Unclassified — Public Release.

Done

What You'll Find Inside

Executive summary of DTM 25-003. Architecture overview of Trout Access Gate. Activity-by-activity mapping for all 7 pillars: Users, Devices, Applications, Data, Networks, Automation, and Visibility.

11 pages — Unclassified

Ready to Assess Your Site?

Request a live demo to see how the Access Gate maps to your specific OT environment and accelerates your path to Target Level Zero Trust.

Request a Demo
FAQ

Common Questions About DoD OT Zero Trust.

7

DoD OT-ZT pillars, each with specific activities mandated by DTM 25-003 — all covered by Trout Access Gate without disrupting operations.

DTM 25-003 is a DoD Directive-Type Memorandum issued in July 2025 that mandates all DoD Components reach Target Level Zero Trust across all unclassified and classified systems, including Operational Technology (OT) environments. It defines 7 pillars and specific activities that must be addressed.

The DoD guidance explicitly states that traditional IT security approaches can be 'ineffective and potentially dangerous' in OT environments. OT systems prioritize availability and safety — they rely on legacy industrial protocols, cannot tolerate downtime, and often cannot run agents, be patched, or be moved to cloud enclaves.

TAG uses a software-defined networking (SDN) overlay to transparently insert a lightweight, identity-aware proxy in front of each OT asset. The underlying network remains unchanged — no rewiring, no recabling, no changes to PLCs, HMIs, or switches. All access now passes through a Zero-Trust enforcement boundary.

Yes. Trout Access Gate is fully on-premise and has no cloud dependency. Its policy engine runs locally, making it suitable for air-gapped, intermittently connected, and classified environments. No data leaves the site.

Deployment typically takes hours, not weeks. Once installed, TAG immediately begins building an asset inventory and enforcing access policies. The alignment guide documents which specific DoD activities are addressed out-of-the-box and which require policy configuration.

DTM 25-003 directly mandates DoD Components. However, the same NIST 800-171 controls underpin CMMC Level 2, which defense contractors must meet to handle CUI. The 7-pillar framework provides a useful architecture reference for contractors preparing for CMMC assessments on OT environments.

Target Level is the baseline required by DTM 25-003. It covers the core activities within each pillar: identity verification, device inventory, network segmentation, data classification, and continuous monitoring. Advanced Level adds deeper capabilities like dynamic policy automation and behavioral analytics. Access Gate addresses Target Level across all 7 pillars.

Access Gate performs passive asset discovery to build a real-time inventory of every device on the network, including OT assets that cannot run agents or respond to active scans. This addresses Activities 2.1 through 2.7 without touching the devices. The overlay network then enforces deny-by-default access per device.

Yes. Access Gate generates session logs, policy configurations, segmentation baselines, and access control records that map directly to DTM 25-003 activities. Assessors can review who accessed what, when, through which protocol, and whether the session was authorized. All evidence is stored on-premise.

Access Gate runs a local policy engine that automates access decisions, alert generation, and configuration enforcement. Policies are version-controlled and can be deployed across multiple sites through the management plane. No cloud orchestration or external API calls are required.

The alignment guide is UNCLASSIFIED and publicly available. Access Gate itself operates in air-gapped, classified, and SCIF environments with no cloud dependency. Specific deployment guidance for classified networks is available through direct engagement with the Trout team.

Related Hub

Zero Trust for OT Networks

Architecture guides, protocol security whitepapers, comparison pages, and implementation resources for Zero Trust in OT environments.

Visit hub