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

Control for energy

Physical isolation for electricity network control.

Electricity networks are converging: corporate trading, control centres, substations and distributed energy resources now share paths. An intrusion on the IT side can reach grid switching and protection.

  • Converging estates
  • Persistent OEM and vendor access
  • Protection settings at risk

As featured in

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

The challenge

Converging electricity networks open new routes to the grid.

When the corporate estate and the control centre share paths, an IT compromise is a route towards switching and protection.

  1. Protection settings and recovery sets held in secured Firevault Bunkers.

  2. Critical changes need sign-off from more than one authorised role.

  3. Compliance logging that can help support NIS2, NERC CIP and Ofgem expectations.

Challenge 2

Persistent OEM and vendor access.

Equipment vendors and OEMs hold standing VPN access into control environments for support.

Answered byMulti-party sign-off

Challenge 3

Protection settings at risk.

Substation protection settings and recovery sets often sit on the same networks they are meant to restore.

Answered byRegulatory evidence

The scenario

Scenario: a vendor laptop pivots into the control room.

A vendor connection needed for support was open between visits, and became the route in. Step through it, or play it through.

Step 1 of 2

The attack path

A vendor laptop with persistent VPN access is compromised.

The attacker pivots from the vendor connection into control room SCADA.

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

An illustrative scenario.

Layer 1
Substation and control room separation
Windowed
OEM and vendor access
Offline
Protection settings and recovery sets
Logged
Evidence for NIS2, NERC CIP and Ofgem

Where each module sits

Where each Control module is deployed across the electricity network.

From the internet and corporate estate, through the industrial DMZ and the control centre (EMS, DMS and DERMS), to SCADA, substation IEDs and primary plant. Control puts a real boundary at each step.

  1. Every Purdue boundaryIsolateCorporate, control centre, SCADA and substations sit on their own physical fabrics.
  2. Internet, corporate and vendor boundariesFirebreakA physical cut that takes the live path away on command.
  3. Into the industrial DMZValidateRequests are checked for origin, integrity and authority before they reach the control centre.
  4. Industrial DMZ and vendor linkRelayData and vendor access move on scheduled, time-bound routes.
  5. Control centre to SCADAExecuteSwitching and configuration actions hold until the right approval is in place.
  6. SCADA to substation IEDsLockAccess to protection and field devices ties to named engineers with the right authority.

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.

Energy

Data held in Firevault Bunkers

Protection settings and recovery sets held in secured Firevault Bunkers.

Energy

Multi-party sign-off

Critical changes need sign-off from more than one authorised role.

Energy

Regulatory evidence

Compliance logging that can help support NIS2, NERC CIP and Ofgem expectations.

Energy

Out-of-band management

Control plane access that does not depend on the operational network.

Energy

Tamper-evident logging

Every access, change and command is recorded.

Energy

Verified configuration baselines

Verified baselines of protection settings and configuration support restoration 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

    Network assessment

    Map every path between corporate IT, the control centre, SCADA, substations and vendors.

  2. 2

    Zone architecture design

    Design physically separated zones with Control modules at each boundary.

  3. 3

    Non-production pilot

    Deploy in a test environment mirroring your control architecture.

  4. 4

    Operational deployment

    Roll out across the network, with verified baselines and continuous evidence.

Questions

What teams ask first

Control acts on the paths between zones, not inside the control systems. Data moves on governed routes, so operations continue.

Vendor access opens in scheduled windows with the right approval, and closes again afterwards.

Offline, in Offline Secure Storage® in a secured Firevault Bunker, as verified baselines ready for recovery.

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.