OrchestrateOT Cybersecuritywith Asset Level Precision.

Nine modules, one engine. Every asset governed, assessed and proven, everyEvery finding driven to an action, every action taking risk down.

Request a demo
Assets
396assets
Governance
4apply
Compliance
…assessing
Evidence
1,284proofs
Mitigation
2open
Risk
14.0/ 25
Deviations
1active
TPRM
18vendor score
BCM
1 hRTO

Governance · 4 controls apply to PLC-07 · Compressor train B

The command view

Every site, every asset. One view, without touching the process.

Risk by site, cluster and asset class, with every figure traced to a real asset and a real piece of proof.

Command · Multi-site portfolio
OTMATIX: Command · Multi-site portfolio

Command. Every site on one board, ranked by risk and backed by proof.

0
agents on your controllers
1,400+
controls in one library
250+
frameworks, clause by clause
Level 4
office network, never the control network
ISA/IEC 62443NIST SP 800-82r3NERC CIPNIS2NCA OTCC-1:2022ISO/IEC 27001:2022Sector regulator cataloguesCustom frameworksOEM requirementsNational CI regulationISA/IEC 62443NIST SP 800-82r3NERC CIPNIS2NCA OTCC-1:2022ISO/IEC 27001:2022Sector regulator cataloguesCustom frameworksOEM requirementsNational CI regulation
Why OTMATIX

IT security tools were never built for a plant.

Controllers run for thirty years, patches wait for turnarounds and scanners can trip a process. OTMATIX was designed around eight realities of OT.

01 / 08
The reality
Obsolescence

Controllers outlive their vendor support.

How OTMATIX answers it

Every asset carries its lifecycle state and vendor support status. Anything that cannot be upgraded is covered by a formal deviation with compensating controls, and the deviation expires on schedule.

Lifecycle state per assetVendor support statusDeviations that expire
How it works · Micro Governance

Assurance, built up from a single controller.

OTMATIX starts at the individual asset and builds upward, so every figure on the command view traces back to a real asset and a real piece of proof.

Step 01 · Bind

Every controller carries only the controls that apply.

Each asset gets its own statement of applicability. A control for a PLC is not a control for a historian.

  • A statement of applicability per asset
  • Not applicable only with a recorded reason
  • Drawn from one library of 1,400+ controls
Statement of applicability
PLC-201
14 of 1,400+ controls
  • ✓SR 1.1 · Human user identification
  • ✓SR 2.8 · Auditable events
  • ✓SR 3.4 · Software and information integrity
  • ✓SR 5.1 · Network segmentation
  • ✓SR 7.3 · Control system backup
  • –SR 4.3 · Use of cryptography N/A · reason recorded
The platform

Twelve modules. One governed plant.

Assets · Asset register01 / 11
OTMATIX: Assets · Asset register
Know the plant

Asset Register

One OT-native register from SCADA servers to safety systems, with an accountable owner and a custodian for each.

Also in the platformChangePatchVulnerabilityAccess governance
Coverage · the Purdue model

From the enterprise down to the valve.

OTMATIX runs at Level 4 and governs what matters at every level below, in the language your engineers already use.

Enterprise ITIndustrial DMZOperational technologyNo agents below the DMZ
L5
Enterprise
ERP, email, corporate IT
Exposure

Risk decisions made without any view of plant-floor reality.

OTMATIX governs
  • ✓Risk appetite per site
  • ✓Board-level command view
  • ✓Policy ownership and review cycles
Level 1 of 7
Who it’s for

One orchestrator for everyone who answers for the plant.

For Plant managers

See which sites, areas and assets carry the risk.

  • Risk by site, cluster and asset class on one command view
  • Every figure traced to a real asset and a real piece of proof
  • Deviations that expire, so nothing stays excepted by default
Plant view · Risk by area01 / 05
OTMATIX: Plant view · Risk by area
Deployment and safety

Close to the plant. Never on the control network.

OTMATIX runs at Purdue Level 4, on the site office network your plant teams already use. It never reaches into the DMZ or the control network, so it cannot disturb a live process.

Where it sits
Level 4, beside the people who answer for the plant.
L5Enterprise
L4Office networkOTMATIX runs here
OTMATIX server⟵ browser ⟶EngineersOperatorsManagers
3.5Industrial DMZNo crossing
Control network · untouched0 agents · 0 scans · 0 connections
L3Site operationsHistorians, EWS, OT domain
L2SupervisorySCADA, HMI, alarm servers
L1Basic controlPLC, RTU, relays, SIS
L0ProcessSensors, actuators, valves
0
Connections into OT

No agents, no scans and no data pulled from Level 3 and below. Teams assess equipment where it is and record the result at Level 4.

L4
On the office network

Engineers, operators and managers on site use any browser on the Level 4 network. No new firewall rules toward the control network.

4096-bit
Isolated and offline-ready

A separate database for every tenant. RSA-4096 licence validated offline, so no internet connection is needed.

Opt-in
Optional AI layer

Agents draft findings and answer posture questions. Humans still decide.

Three Zone 2 assets have evidence lapsing. Accept drafts?
Why not spreadsheets

Built for OT. Not adapted to it.

Seven things an OT programme needs, and how each approach covers them.

Capability
Sheets
IT GRC
OTMATIX
Controls bound to each individual asset
OT standards built in, clause by clause
Evidence that expires and stops counting
Independent three-pass assessment
Deviations with compensating controls and an end date
Patching on OEM approvals and turnarounds
Runs at Level 4, never on the control network
Fully covered
1 / 7
0 / 7
7 / 7
CoveredPartly coveredNot covered
Watch

The case for OTMATIX, in under two minutes.

Then take the narrated briefing: fifteen stations, about eight minutes. Open any station on its own.

The reality
The method
Running it
THE OT REALITY · BUILT TO RUNBuilt to run for thirty years.● RUNNINGSECURITY · UNKNOWNTheir security was never designed to last that long.
1:56 · narrated · captions below
0:00 / 1:56

Built to run. Industrial control systems are built to run for thirty years. Their security was never designed to last that long.

FAQ · Technical specifications

Questions, answered.

Deployment4 questions
Q01Deployment

Does OTMATIX install anything on our controllers?

No.

Nothing is installed on controllers and nothing scans the network. Your teams assess where the equipment is, and OTMATIX records the result, the evidence and its expiry.

0 agentsNo scanningNo process traffic
Related
Ask an OT engineer

See your plant’s cybersecurity, orchestrated.

A walkthrough built around your sites, your asset classes and the standards you answer to.

  • Your asset classes, from SCADA servers to safety systems
  • IEC 62443, NERC CIP, NIS2 or your own framework, mapped live
  • Deviations, patches and vendor access on a real Purdue layout
  • A Level 4 deployment, kept clear of your control network
What happens next
  1. 1We reply within one business day
  2. 2We learn your sites, asset classes and standards
  3. 3You see OTMATIX on your own plant

Delivered by the OT security team at OT Associates, pure play OT security.

Request a demo

No obligation. Your details stay with OT Associates.