Firevault, offline secure storage, physically disconnected from the internet
Pricing

Control for utilities

Physical isolation for power grid and utility SCADA.

Utility networks bridge physical infrastructure and digital control. When those control paths are compromised, the consequences extend far beyond data loss.

  • IT/OT convergence
  • Legacy SCADA systems
  • Smart meter attack surface

As featured in

  • TechRadar Pro logo
  • Yahoo Finance logo
  • Channel Insider logo
  • Security Buyer logo
  • SecurityBrief logo

The challenge

Utility control systems face converging threats.

When utility control systems are reachable from corporate networks or the internet, every compromise upstream is a route towards the grid.

  1. Utility control data held in secured Firevault Bunkers.

  2. Critical operations require authorisation from both control room operators and security teams.

  3. Automated compliance logging that can help support NIS2, NERC CIP and Ofgem security expectations.

Challenge 3

Smart meter attack surface.

Advanced metering infrastructure creates millions of network endpoints that expand the attack surface.

Answered byRegulatory evidence

The scenario

Scenario: smart grid supply chain attack.

From a compromised smart meter head-end, only a few hops separated the attacker from SCADA. Step through it, or play it through.

Step 1 of 2

The attack path

Attackers compromise a firmware update server for smart meter head-end systems. The malicious update propagates to distribution management systems through the AMI network.

Operators lose visibility into distribution grid status across an entire region, and restoration takes nine days because backup SCADA configurations were stored on the same network.

The path
Always there
What the attacker needs
A foothold and time

An illustrative scenario.

Layer 1
Separation of SCADA from corporate IT
Time-bound
Remote access to control systems
6
Control modules deployed per utility zone
Logged
Evidence for NIS2 and NERC CIP

Where each module sits

Where each Control module is deployed across a utility network.

Utility estates run along the Purdue model, cloud and corporate at the top and field devices at the bottom. Control puts a real boundary at every level.

  1. Every Purdue boundaryIsolateEach level sits on its own physical fabric.
  2. L5 to L4 and L4 to L3.5 linksFirebreakA physical cut for operations on the public and office boundaries.
  3. L5 to L4 link and inside the L3.5 DMZValidateValidate checks origin, integrity and authority.
  4. Inside the L3.5 DMZRelayData flows from L4 into L3 inside scheduled, defined routes.
  5. L3.5 DMZ and L2 to L1 linkExecuteFirmware, configuration and control actions hold until the right approval is in place.
  6. L3 to L2 and L1 to L0 linksLockThe closer you get to the physical plant, the tighter the named access.

Explore the Control Blueprints

Capabilities

What you get with every deployment.

Six things Control gives the team, from the first boundary to the audit afterwards.

Utilities

Grid data in Firevault Bunkers

Utility control data held in secured Firevault Bunkers.

Utilities

Multi-party control

Critical operations require authorisation from both control room operators and security teams.

Utilities

Regulatory evidence

Automated compliance logging that can help support NIS2, NERC CIP and Ofgem security expectations.

Utilities

Cellular failover

Out-of-band management keeps control plane access available when primary utility communications are down.

Utilities

Tamper-evident logging

Every access, configuration change and control command is recorded.

Utilities

Verified configuration baselines

Verified baselines of grid configuration support restoration of control-plane state after an incident.

Adoption guide

From first boundary to routine operation.

Four steps, piloted on one site before it extends across the estate.

  1. 1

    Utility network assessment

    Map all network paths between corporate IT, SCADA, AMI and distribution management systems.

  2. 2

    Zone architecture design

    Design physically separated zones aligned to your utility operations, with Control modules at each boundary.

  3. 3

    Non-production pilot

    Deploy in a test environment mirroring your SCADA architecture, with full zone separation.

  4. 4

    Operational deployment

    Full deployment across utility infrastructure, with verified configuration baselines and continuous evidence.

Questions

What teams ask first

It sits on the paths between them rather than inside them. Isolate keeps each Purdue level on its own fabric, and Relay carries data between levels on scheduled, defined routes.

Yes, through governed routes. Data moves inside scheduled, defined routes, while the AMI network stays physically separated from SCADA.

In milliseconds, over an out-of-band command, zone by zone.

Monitoring continues over governed routes, and out-of-band management keeps control plane access available when primary communications fail.

All questions

Speak to the team to organise a PoC.

Walk through your blueprint with the Firevault team and scope a proof of concept on your estate. 30 minutes, no sales pitch.