OT visibility & security / part of Surya Fabric
Claroty
Supported Claroty OT visibility and platform security capabilities within an agreed licensed deployment and response scope, coordinated with controls, security and the designated network owner. Visibility is distinct from industrial configuration backup.
Understand the environment behind the line.
- An agreed OT asset-visibility scope
- Review platform alerts and route findings to named owners under agreed procedures
- No general security assessment or open-ended remediation
Defined scope
Qualify the licensed capabilities, supported assets, deployment method and access with the designated network owner and the owners who review findings. Network separation must be in place; Surya does not design or operate the plant network. Octoplant configuration protection is another Fabric component; Standby replacements can be scoped separately.
Visibility alone does not enforce separation. The designated network owner implements and owns network controls and approved interfaces, except expressly assigned Standby replacement work. Surya operates only the supported licensed Claroty capabilities and reviews and routes platform alerts through an agreed response scope and coverage arrangement; this is not a full SOC, incident investigation or forensics service. Security findings do not authorize production changes.
Delivered as part of Surya Fabric
Every operational configuration we cover, backed up and versioned. You see what changed and when. You see every device on the operational network.
Claroty is one component Surya can use inside Surya Fabric. Surya configures and operates only the supported components and licensed capabilities agreed for each platform. Modules, device families, integrations and disconnected features are qualified, not automatically included.
Explore Surya FabricWorking alongside IT
Who owns what.
Surya
The replacements and the supply chain behind them. The configuration backups. The OT inventory. The operating PCs.
Your IT team or MSP
Email, identity, business applications, employee laptops, and the network. Not our business, and we will not quote it.
Plant engineering, clinical engineering and your OEMs
The process, the logic, the calibration, and the call on return to service. Always.
How an asset comes into scope
An asset comes into scope when it supports the site's production or care delivery and matches a supported Surya configuration. Changes to running equipment follow the designated owner's approvals and the agreed maintenance and change process. Network ownership is named at qualification; platform visibility does not transfer network enforcement or operation to Surya.
Your next step
We do not take every site.
Tell us what yours runs on. If we can stand behind it, you get a scope and a clear line on who owns what. If we cannot, we will say so.