Recent Breaches
Breaches
View All →
Utilities - Renewables and BESS

Physical isolation for wind, solar and battery storage sites

Renewable generators run a fleet of remote sites with heavy OEM remote access into turbines, inverters and battery management. Firevault Control puts a real boundary between the office, the OEM zone, the fleet operations centre and the controllers behind them.

Back to Utilities
Control

Utilities - Renewables and BESS

When OEM access, fleet operations and site control share the same paths, every vendor incident becomes a candidate for a fleet-wide outage.

100%

Site SCADA isolation from corporate IT

Zero

Persistent OEM access to inverter or BMS controllers

6

Control modules deployed per renewable site

Full

Evidence for NIS2 and Grid Code expectations

The Challenge

Renewables carry vendor risk that other operators have spent decades trying to avoid.

OEM remote access by default

Turbine, inverter and BESS vendors expect persistent remote access into their kit for monitoring and firmware. That is a standing connection into operations.

Fleet operations across many sites

Remote operations centres run dozens of sites at once. A compromise in the ROC can cascade to every site it manages.

Grid Code and curtailment control

Curtailment, setpoint and Grid Code response commands flow into inverter-based resources from the fleet operations centre. Those commands have to be trustworthy.

The Scenario

Scenario: OEM portal compromise across a wind fleet

Attackers compromise the OEM remote support portal used to monitor a wind fleet. From there they pivot through the persistent VPN into the fleet operations centre and push a malicious firmware payload to turbine controllers across multiple sites. Several sites curtail to zero output for the rest of the day. With Firevault Control, OEM access opens only on scheduled, brokered windows. Firmware updates that cross into a site require named, multi-party approval. The fleet operations centre and the per-site SCADA sit on separate fabrics, so a ROC compromise cannot walk straight into every site. Verified baselines for turbine and inverter configuration are held on infrastructure that has no live network path to production and require multi-party authorisation to release.

"Our biggest standing connection was never an attacker. It was a vendor. That is the gap to close."

Module deployment · renewables and BESS site

Where each Control module is deployed across wind, solar and battery storage.

Renewable generators run a fleet of remote sites with heavy OEM remote access into wind turbines, inverters and battery management. Control puts a real boundary between the office, the OEM zone, the site SCADA and the inverter and battery controllers behind it.

Grounded in NIST SP 800-82 Rev. 3, IEC 62443-3-2, IEC 61400-25 and Grid Code requirements for inverter-based resources.

L5

Cloud / Internet

External

Market interfaces
Cloud analytics
FirebreakValidate

Market and cloud traffic terminates at the perimeter.

L4

Enterprise

IT

SOC
SIEM
Identity
Asset management

Office and trading systems.

Office and trading systems.

IsolateRelayUnlink

OEM paths exist on a schedule and not a minute more.

OEM

OEM / vendor zone

DMZ · trust boundary

OEM remote access
Vendor jump
Firmware broker

Turbine and inverter OEM access opens on a schedule only.

Turbine and inverter OEM access opens on a schedule only.

ValidateLockExecute

OEM activity into fleet operations is named, checked and approved.

L3

Fleet operations

OT

ROC SCADA
DERMS
Historian

Remote operations centre across the fleet.

Remote operations centre across the fleet.

Isolate

Fleet ROC and site SCADA on separate fabrics.

L2

Site supervisory

OT

Site SCADA
BESS EMS
HMI

Per-site control view.

Per-site control view.

Execute

Curtailment, setpoints and firmware need approval before they move.

L1

Basic control

Field

Turbine controllers
Inverter controllers
BMS

Wind, solar and battery controllers.

Wind, solar and battery controllers.

Lock

Turbine, inverter and battery devices tie to named engineers.

L0

Physical

Field

Turbines
Inverters
Battery racks
OSS

Crown jewels

Off-network

Detail callout · A

Offline Secure Storage

Turbine and inverter configurations, BESS baselines, grid code settings and the recovery sets you need after a vendor incident.

Offline by design · secure by default

Modules & symbols

FirebreakPhysical sever
ValidateIntegrity check
IsolateZone boundary
RelayTime-bound path
UnlinkRemove trust
LockNamed access
ExecuteApproved action
DMZ boundaryTrust transition
OSS calloutOff-network detail

Where each module is deployed, and what it does there.

One row per module. Placement on the network, then plain-English purpose at that point.

  1. Isolate

    At every zone boundary on the diagram

    Office, OEM, fleet ROC and site SCADA all sit on separate physical fabrics. An OEM compromise cannot walk into the fleet.

  2. Firebreak

    On the L5 to L4 link

    A real off switch on the public boundary when an incident is in flight.

  3. Relay

    On the OEM link

    OEM connections exist for the window of work and not a minute more.

  4. Unlink

    On the OEM link

    When an OEM engagement or maintenance window ends, Unlink removes the persistent connection and the inherited trust.

  5. Validate

    On the L5 to L4 link and the OEM link

    Firmware and engineering traffic is checked for origin, integrity and authority before it reaches fleet operations.

  6. Execute

    Inside the OEM link and on the L2 to L1 link

    Firmware, curtailment and setpoint changes hold until the right authority signs them off.

  7. Lock

    On the OEM link and the L1 to L0 link

    Access to turbines, inverters and batteries ties to named engineers. Standing access is the exception.

Featured In

TechRadar ProSecurity BuyerYahoo FinanceSecurityBriefChannel Insider

Key Capabilities

Sovereign generation data

Operational and Grid Code data remains within the agreed jurisdiction in carefully selected Firevault Bunkers.

Multi-party control

Curtailment, setpoint and firmware actions require sign-off from both fleet operations and security teams.

Regulatory evidence

Continuous compliance evidence for NIS2 and Grid Code cyber expectations for inverter-based resources.

Out-of-band management

Cellular and dedicated paths keep the control plane reachable when primary networks are compromised.

Tamper-proof logging

Every access, configuration change and curtailment command lands in immutable logs on physically separate infrastructure.

Verified configuration baselines

Verified baselines of turbine, inverter and BESS configuration enable a known-good restore of control-plane state.

Demo to Live

Adoption Guide

Step 1

Network assessment

Map every path between corporate IT, OEM portals, the fleet operations centre and per-site SCADA to identify standing vendor connections.

Step 2

Zone architecture design

Design physically separated zones aligned to OEM, fleet and per-site boundaries, with Control modules at each one.

Step 3

Non-production pilot

Deploy in a test environment mirroring a single site and the ROC with full zone separation, multi-party authorisation and compliance logging.

Step 4

Operational deployment

Full deployment across the renewables and BESS estate with verified configuration baselines, continuous compliance evidence and 24/7 out-of-band management.

Step 1

Network assessment

Map every path between corporate IT, OEM portals, the fleet operations centre and per-site SCADA to identify standing vendor connections.

Step 2

Zone architecture design

Design physically separated zones aligned to OEM, fleet and per-site boundaries, with Control modules at each one.

Step 3

Non-production pilot

Deploy in a test environment mirroring a single site and the ROC with full zone separation, multi-party authorisation and compliance logging.

Step 4

Operational deployment

Full deployment across the renewables and BESS estate with verified configuration baselines, continuous compliance evidence and 24/7 out-of-band management.

Questions

Frequently Asked

Renewables blueprint - PoC

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.

    Firevault

    Firevault is Offline Secure Storage. Hardware you own, physically disconnected by default, with KYC-verified access. Ransomware-proof by design, not by patch.

    © 2026 Firevault Limited. Disconnect to Protect®