Skip to content
Solutions › Energy and critical infrastructure
Energy and critical infrastructure

No agent touches operational technology without a person saying yes.

The oil and gas OT pack holds every agent write to PLCs, SCADA and setpoints for an engineer, keeps safety systems out of every agent's reach and keeps test agents on simulators.

The problem

In OT, a wrong action is a safety event, not a bug.

Writes to live plant

An agent that can change a setpoint or open a valve acts on physical equipment, not on data.

Safety systems

Shutdown systems and interlocks must never be bypassed or reset by software that guesses.

Remote access

Agents that open VPN, RDP or vendor sessions into OT create new paths across your perimeter.

Controls

Controls in the oil and gas OT pack

6 controls, each a policy you install from the Policy Hub. Every one starts in monitor mode and changes nothing until you promote it after a simulation on your own traffic.

Oil and gas (OT)

Five policies for operators of OT, used with the action governance pack for tool access.

  • A person approves

    Approve every OT write

    Any write to PLCs, SCADA, setpoints, valves or pumps needs an approver; only clear reads go through.

    Oil and gas (OT) pack · mapped to CISA AI in OT, principle 4
  • Blocked

    Only designated agents write

    Agents without the ot:write permission cannot write to OT at all, even with an approval.

    Oil and gas (OT) pack · mapped to ISA/IEC 62443-3-3, FR 2
  • Blocked

    Never change safety systems

    No agent can change, bypass, reset or trip safety instrumented systems, shutdowns or interlocks.

    Oil and gas (OT) pack · mapped to CISA AI in OT, principle 4.2
  • A person approves

    Approve remote access

    A person approves before an agent opens VPN, RDP, SSH or vendor remote access into OT.

    Oil and gas (OT) pack · mapped to NERC CIP-005-7, R2
  • Blocked

    Test agents off live OT

    Agents that are not in production can use only simulator, digital twin or lab OT tools.

    Oil and gas (OT) pack · mapped to ISA/IEC 62443-3-2, zones
  • Blocked

    Tools only for their teams

    An agent can use an MCP server only when it is registered and open to the agent's team; others are denied.

    Agent action governance pack
How it works for energy and critical infrastructure

How an agent's write to OT is governed.

CallerOperations agentproposes a setpoint changeClovie gatewayIdentify agentot:write permissionSafety systemsalways out of reachApprove OT writesheld for an engineerOutcomeApproved, then writtenthe identical call, onceBlockedsafety system or no permissionWaitingfor a control room engineerRecordAudit logagent, policy, approverEvidence packfor your OT security teamCallerOperations agentproposes a setpoint changeClovie gatewayIdentify agentot:write permissionSafety systemsalways out of reachApprove OT writesheld for an engineerOutcomeApproved, then writtenthe identical call, onceBlockedsafety system or no permissionWaitingfor a control room engineerRecordAudit logagent, policy, approverEvidence packfor your OT security team
Deployment

On site, next to the plant

Install Clovie on premises or air-gapped, inside the zones your OT security team defines. Nothing calls home.

  • SaaS
  • Customer VPC
  • On-premises
  • Air-gapped

Inside your zones

Run the gateway in the zone and conduit your architecture allows, close to the agents it governs.

Safe by default

An unknown tool verb counts as a write, so a naming mistake falls on the side of asking a person.

Simulators first

Tag simulators and digital twins, and let test agents learn there long before they see live plant.

Frameworks

Controls mapped to the frameworks you answer to

  • NIST AI RMF: NIST AI Risk Management Framework
  • ISO/IEC 42001: ISO/IEC 42001 AI management system
  • OWASP Top 10: OWASP Top 10 for LLM applications and agentic AI
  • EU AI Act: EU Artificial Intelligence Act
Questions

Questions

Do the OT policies block anything when installed?

No. Every policy installs in monitor mode, records what it would have done, and changes nothing until you promote it. Promote these policies to enforce before any agent can reach live OT.

How does Clovie know a tool call is a write?

Any OT tool call whose verb is not a clear read, such as get, read, list or monitor, counts as a write. Tag read-only tools whose names don't start with a read verb so they pass without approval.

Does this apply to electric utilities?

The controls work for any operator of OT. The NERC CIP references apply only to Bulk Electric System cyber systems, and the TSA directive only to designated pipelines; check which apply to you.

Can we run it with no connection to the internet?

Yes. On-premises and air-gapped installs check the licence offline, use models you host and keep the audit log on site.

See the OT pack on your own agents.

We'll run the controls on your own agents in monitor mode and show what they would have held and blocked.