You can't govern
what you can't see.
OT Asset Inventory is where every other module starts. Model each PLC, RTU, HMI and historian the way your plant is actually built, mapped to its zone and conduit, so risk, compliance and remediation all have something real to attach to.
Most plants inventory OT in a spreadsheet that's wrong the day it's saved.
A device gets swapped, firmware gets patched, a new zone comes online, and the spreadsheet doesn't know. When the asset record is stale, every risk score, every control mapping and every audit built on top of it is stale too.
From discovered to governed, and kept that way.
{{ ph.title }}
{{ ph.body }}
A living model, not a list.
Zone & conduit aware
Every asset knows the zone it sits in and the conduits that reach it, the way IEC 62443 expects, so segmentation isn't a diagram in a drawer.
Integration-fed, not hand-typed
Pull discovered assets from Nozomi, Dragos, Claroty and Tenable OT through the API, then govern them here. Cynable complements detection, it doesn't replace it.
Criticality & ownership
Tag each asset with its consequence rating and the team that answers for it.
Full change history
Every firmware bump and swap is recorded, so the record is audit evidence in itself.
Rolls up the hierarchy
One asset's status flows up to its zone, site, operating company and the group.
Every device type, one taxonomy.
Cynable classifies OT assets by their role in the control system, from Level 0 field devices to Level 3 operations servers. Pick a class to see what it covers and what Cynable tracks on it.
Controllers
The devices that run the process logic. When one changes, the plant behaves differently, so this is where governance matters most.
One device knows exactly where it lives.
Every asset carries its full address in the org hierarchy. That address is what makes roll-ups, access control and reporting work the same way across all 250+ sites.
A clean inventory is where risk scoring begins.
Once your assets are modeled, Risk Management turns them into a live OT Risk Score, the IEC 62443 way. See how the next module builds on this one.