CyberSentienOT compliance evidence from the tools you already run.
Export from Nozomi Networks Guardian, Claroty, Dragos Platform or Tenable OT Security. The engine reads assets with firmware and zone, vulnerabilities, alerts and connections, and works out five checks per zone. Each result says met, not met or not measured, and names the reason, down to the row and file hash it came from.
The five checks
| Check | Credits | What it reads |
|---|---|---|
| Asset inventory completeness | IEC 62443-3-3 SR 7.8 | the asset export against the zone model |
| Connections against the conduit rules | SR 5.1, SR 5.2 | observed flows against the allowed conduits (finds Telnet and unapproved SSH) |
| Monitoring coverage | SR 6.2 | alert exports per zone; a file missing a severity column is refused and says so |
| Firmware currency | none, by design | firmware against the engineer-maintained baseline (patch management is IEC 62443-2-3) |
| Vulnerabilities against each zone's target security level | none, by design | open findings against the level set under IEC 62443-3-2 |
What the console gives you
Zones and conduits
Screenshot pending.
Requirements traceability matrix, with a telemetry column and Excel export
Screenshot pending.
Decks for the safety board
Screenshot pending.
Catalogues on the engine:
What it does not do yet
CSV import today; no API connector yet.
Column maps are confirmed against your real export during the demo week.
Telemetry-backed credits appear in the Rail & OT console. Document evidence stays candidate evidence for assessor review.
Credits are per zone, and a check is met only when every zone it covers is met.
Start with one export
Send one export and get your zone report inside the demo week. The rest of the rail console opens on the gated demo.