Control for oil and gas

Physical control of every path into DCS, SCADA and safety systems.

Control physically governs every network path into safety instrumented systems and DCS/SCADA environments, so access exists only when it is authorised. In oil and gas, a compromised control system is a potential safety incident, not just a data breach.

• Safety system tampering
• Ransomware on the DCS
• Persistent vendor and remote access

The scenario

Scenario: a contractor VPN reaches the refinery DCS.

A contractor VPN left active between maintenance visits is a standing route to the DCS. Step through it, or play it through.

1. 01The attack path
2. 02With Control

Step 1 of 2

The attack path

An attacker uses a contractor’s VPN, left active between maintenance visits, to reach a refinery DCS network.

They alter controller logic, with the safety instrumented system next in line.

The path

Always there

What the attacker needs

A foothold and time

Play it through

An illustrative scenario.

Layer 1

Separation of DCS and SIS

Windowed

Contractor and vendor access

Offline

DCS baselines, PLC programs and SIS logic

Logged

Evidence for IEC 62443 and NIS2

Where each Control module is deployed from the internet to the safety system.

A Purdue stack from the internet (L5) down to field devices and safety systems (L0 and SIS), with Control at each boundary. Referenced standards include IEC 62443, API Standard 1164 and the TSA Pipeline Security Directives.

1. Every Purdue boundaryIsolateEnterprise, DMZ, DCS and safety each sit on their own physical fabric.
2. L5 to L4 and vendor linksFirebreakA physical cut on the internet and contractor boundaries.
3. Into the industrial DMZValidateRequests and updates are checked for origin, integrity and authority.
4. Industrial DMZ and contractor linkRelayContractor access opens for the maintenance window only.
5. DCS to controllersExecuteLogic changes hold until operations and HSE approval is in place.
6. L1 to L0 and SIS linksLockSafety is the last layer anything reaches, with named access only.

Explore the Control Blueprints

From first boundary to routine operation.

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

1. 1

   Process network assessment

   Map every path into the DCS, SCADA and safety systems, including contractor and remote links.

2. 2

   Zone and conduit design

   Design zones and conduits with Control modules at each boundary.

3. 3

   Single-facility pilot

   Deploy at one facility with contractor windows, dual sign-off and offline recovery sets.

4. 4

   Enterprise rollout

   Extend across facilities and remote sites.

Explore more

Where to go next.

• Control for OT environments
• Control for energy
• OT recovery
• Control Blueprints
• Control by industry

• Isolate
• Firebreak
• Validate
• Relay
• Execute

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.