DCS Labs · Programme 04 · IoT / OT

Plants run for decades. Their cryptography won’t.

Post-quantum migration for industrial control, utilities, telecom edges and device fleets, with signed evidence at every step and no rip-and-replace.

Read the full IoT / OT brief Talk about a pilot

EngineR-Series

ApproachGateway, not re-flash

StatusIn development

01 The problem

A controller installed today will still be running when today’s keys can be broken.

Harvest now, decrypt later

Telemetry and remote sessions recorded today can be read later. The exposure starts now, not on the day a quantum computer arrives.

Firmware keys outlive algorithms

A firmware-signing key issued today is trusted by devices that will be in service for ten to twenty years.

Many devices can’t change

Plenty of controllers can’t be patched at all. Migration has to work around them, and prove what it did.

02 How it works

Estate → gateway → control plane → backbone.

01 · ESTATE

Devices keep the protocols they speak.

PLCs, RTUs, sensors and historians stay as they are. What cannot change is not changed.

02 · GATEWAY

A gateway carries identity and signed firmware.

It relays signed firmware and device identity through the engine’s custody path. It holds no cryptography of its own.

03 · CONTROL PLANE

Discover, plan, migrate, dual-run, verify.

The same migration state machine used for IT estates runs for each device class, and every step leaves a receipt.

04 · BACKBONE

Evidence that lasts as long as the plant.

Receipts, key history and long-horizon archives keep the record verifiable after today’s algorithms are retired.

03 Honest status

What exists today.

The R-Series backbone and its migration evidence are built. The gateway agent, OT adapters, firmware-signing workflow and test bench are in development. We are looking for a first field pilot.

Read the full IoT / OT brief Firmware signing Back to DCS Labs