TroutTrout
AI OT security · Firewall rule automation

Let your LLM turn a pcap into OT firewall rules in minutes.

Trout Access Gate lets your LLM write the firewall rules of your OT network from a pcap. You dry-run them, and one route switches traffic over. A large OT deployment is secured in 2 minutes.

Last updated:

00:44Not protected→Protected
Real take, pcap to deployed
Your LLM · hall-d-line-3.pcap

Here is hall-d-line-3.pcap. Build the Secure Operation Twin for these machines.

● Reading the capture: 18 machines, 23 flows.

  • Engineering station → L3 Filler PLCModbus
  • SCADA server → L3 Packer HMIOPC UA
  • Vendor laptop → L3 Filler PLCModbus
  • L3 Office PC → L3 Labeler PLCModbus

● Twin ready: 4 zones, 15 machines, 3 people, 4 enclaves. Dry run ready.

Existing router · 1 ruleip route 10.46.1.0/24 → Access Gate
Production hall with orange steel columns

Why plant networks stay flat

Securing a running plant usually means new VLANs and re-addressed machines. The firewall gets rebuilt rule by rule. That work needs a production shutdown. The network stays flat, and anyone on it can reach every machine.

Three steps, one route change

How firewall rule automation works for OT.

Your LLM prepares the configuration through admin access to the appliance. Nothing goes live until a person switches the route.

01

Load a pcap.

Capture traffic on your existing OT network and load the file. The file lists which machines talk to which, and over which protocol.

02

Build the twin with your LLM.

Your LLM turns the capture into a Secure Operation Twin configuration. Refine it in plain words, then dry-run it.

03

Switch with one route.

Add one route on your router, and the subnet passes through Access Gate. Nothing is rewired or re-addressed, and the plant keeps running.

Source-based routing
Secured in minutes

What your OT network gets on day one.

Access Gate first builds a copy of your OT network, called the Secure Operation Twin. One routing rule then switches traffic to it. Inventory, access control and logs all apply at once.

2 min

To secure a large OT deployment once traffic passes through Access Gate.

01

OT asset inventory.

Access Gate lists and names every machine on the network.

OT asset inventory
02

OT network segmentation and access control.

Each machine sits behind its own boundary. Only named users can reach it.

OT network segmentation
03

Access logs.

The logs show who reached which machine and when. They also record every configuration change.

Change history
Watch it on a real line

Video: from a pcap to a protected line

A packaging line secured in two minutes

The video starts from a flat packaging line and a pcap of its traffic. Your LLM builds the configuration. One route on the existing router switches the line over. It goes from not protected to protected while the clock runs.

FAQ

Questions about securing OT with your LLM.

AI OT security uses an AI model to help secure operational technology and industrial networks. With Access Gate, your LLM writes the security configuration from your real traffic. Access Gate enforces it on the wire, in front of each machine. A person dry-runs and applies every change.

It is an industrial proxy in front of your machines. Traffic passes through it. Each machine gets access control, encryption and logs, and nothing on the machine changes. Read more on the Secure Operation Twin.

A capture of your existing traffic shows which machines exist and which connections they need. Your LLM builds the twin configuration from that capture. You do not start from a blank page.

You add one route on your router. Traffic from that subnet then passes through Access Gate. No machine is re-addressed or rewired. Every change lands in the change history and can be rolled back.

By hand, you start from a blank policy and review it manually. You re-address machines to switch over, and you retype the old rules to undo. With Access Gate, your LLM starts from a capture of your existing traffic. You check the result with a dry run. One route on your router switches traffic over. A rollback from the change history undoes it.

Yes. Any LLM agent tool that can use admin access to the appliance works. Claude Code and ChatGPT are two examples. Your team keeps the tool it already uses.

No. Your LLM works through admin access to the appliance and database access. An administrator uses the same access. There is no MCP server or API to install.

Nothing goes live until a person applies it. Every change runs as a dry run first. It lands in the enclave change history and can be rolled back.

Run it as a dry run. You see what would change, and nothing is applied until a person pushes it. Every change lands in the enclave change history and can be rolled back.

All of them. LLM management works on every Access Gate appliance, in Access Gate IDMZ and Access Gate Fleet.

See it on your network

Bring a pcap to a demo

In a demo, we load a capture, build the twin with an LLM and switch it with one route.