Configuration protection and OT security

Surya Fabric

Every configuration we cover is backed up on a schedule and kept by version. You see what changed and when. You get an inventory of what is on the operational network, and an engineer who reads the alerts and sends each one to the person who owns it.

Lost settings should not mean starting from scratch.

Capabilities

  • Scheduled backup of supported operational configurations
  • Version history and change visibility
  • Approved configurations available for authorized recovery
  • OT asset visibility
  • Platform alerts reviewed and findings routed to named owners under agreed procedures
  • Supported platform policy and security capabilities within the agreed license

Where it applies

Production continuity

Manufacturing

Supported PLC, HMI and industrial configurations backed up and versioned, changes made visible, and plant OT assets and security alerts monitored within the agreed scope.

Manufacturing continuity

Care-delivery continuity

Healthcare

Supported care-delivery and edge configurations protected and versioned, operational assets visible and platform alerts routed to named owners within the agreed scope.

Healthcare continuity

Qualification

What it takes to work with us.

One site to start. Equipment we support. A named owner who can approve changes. A network owner who has separated the floor from the office. We do not start until all four are in place.

  • Supported device families and software versions, confirmed at qualification
  • Qualified licensed capabilities, deployment method and integrations
  • Agreed separation and connectivity provided by the named network owner
  • Approved access and a qualified connected or air-gapped profile
  • An agreed alert-response procedure, coverage and named escalation owner

Delivery

How it is delivered

Field engineers deploy the tools on site, and remote engineers monitor only through connections you have approved; air-gapped sites are worked locally. Your engineers and OEMs approve return to service.

Where one platform's capabilities are included in another platform's scope, they are not sold or charged a second time.

Scope boundaries
  • A successful backup or an available version is not a tested restore or a return to production. Surya restores a configuration only where that work is expressly assigned, with an approved procedure, permissions and verification steps; engineering or OEM validation and return to service stay with those owners.
  • Surya does not author PLC logic or carry out process engineering or clinical validation; recovery to a running plant or care process stays with engineering and OEM owners.
  • Platform detection is not a full SOC, a general security assessment, incident investigation, forensics, specialist consulting or remediation of every threat. Findings do not authorize production changes.
  • Fabric includes no network setup, architecture, ongoing operation, network-as-a-service, WAN, NOC or performance management. Network-equipment replacement belongs only to qualified Standby scope.
  • Visibility alone is not enforcement. The designated network owner implements and owns network controls and approved IT/OT interfaces, except assigned Standby replacement work.
  • Only qualified supported configurations and licensed capabilities are included, not every module, integration, device family or disconnected feature.

Start with one site and a defined equipment scope. Before accepting work we confirm supported equipment and software versions, licensed capabilities, dependencies, permitted changes, an approved procedure with verification and a safe stop or rollback where it applies, coverage and escalation, recovery, stock and access arrangements, and responsible owners including the designated network owner. If any of these is missing, the work is not accepted until it is in place. Additional sites are qualified individually. Equipment or tasks outside supported configurations are not part of the offer and stay with your IT team or MSP, your engineering team, the OEM or a specialist you retain.

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.

The OT boundary

OT separated by default. Air-gapped where required. Connected only through controlled interfaces.

This is the condition of entry. Your network owner builds and runs the separation. We work inside it, connected or fully offline.

Minimum standard

The baseline at every site

  • OT in its own zone, apart from corporate IT
  • No flat network and no shared trust between office and floor
  • Nothing crosses unless it is documented and approved

Secure IT/OT convergence

Segmented and connected

Traffic crosses only where your network owner has opened a path. Our remote engineers use those paths and no others.

Where the site requires it

Air-gapped

No live path to corporate IT, the internet or the cloud. Work happens on site. Updates arrive by an offline transfer you approve.

What each profile does and does not mean
  • Segmented and connected: Explicitly authorized network traffic and vendor access.
  • Segmented and connected: Remote engineers configure and monitor only through approved access paths within the agreed boundary.
  • Segmented and connected: The designated network owner controls approved interfaces; application integration stays with system owners.
  • Air-gapped: Operation, administration and approved automation run locally.
  • Air-gapped: Information and packages move through customer-approved offline transfers.
  • Air-gapped: Changes and monitoring execute locally, with no live remote connection.
  • Air-gapped: Qualification names a local execution and monitoring owner, who carries out offline transfers, the review schedule and the exception handoff.
  • Blocked internet access alone is not an air gap, and an air-gapped site does not also have live IT/OT connectivity. Remote access paths are not part of the air-gapped profile.
  • Air-gapped equipment has no remote real-time monitoring; local checks are reviewed on the agreed schedule. Working through an internet outage is not the same as an air gap.
  • Disconnected operation is confirmed only after supported components, versions, local administration, application and identity dependencies, and offline transfers are qualified. On-premises deployment alone does not establish air-gap capability.

Working 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.

How it works

From site scope to supported operation.

  1. 01

    Define the site scope

    Choose Standby, Endpoint or Fabric around the equipment that supports production or care delivery.

  2. 02

    Confirm the boundary

    Confirm supported equipment, licensed capabilities, permitted changes and the connected or air-gapped profile with your network owner. Agree coverage and escalation before work starts.

  3. 03

    Prepare and configure

    RTP prepares compatible replacements. Field engineers deploy and configure supported tools and endpoints and perform assigned replacement work. Your network owner provides the agreed connectivity and separation.

  4. 04

    Operate and recover

    Remote engineers configure and monitor supported tools and endpoints where approved connectivity permits. Standby supports assigned equipment recovery; network, engineering and OEM owners approve return to service within their responsibilities.

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.

Keep my site running