Every device that runs critical infrastructure — from industrial controllers to individual sensors — emits a unique electromagnetic signature. Until now, no one read them. EDO does. We make hardware identity verifiable, continuous, and impossible to forge in software. Starting with the factories, grids and facilities that the physical world already depends on.
You spent millions on PLCs, RTUs and IIoT sensors. They run your line, your grid, your treatment plant. But here's the question nothing in your stack can answer: are they still the same units the integrator installed? If a service tech, contractor, or someone in your supply chain swapped one — you would not know.
Same firmware version. Same Modbus replies. Same network behavior. The only thing different is the silicon — and nothing in your SOC stack looks at silicon. We do.
Modern hardware authentication assumes secure boot, attestation chips, signed firmware. Most installed industrial gear has none of that, and ripping it out means stopping production. EDO works on what you already have.
"We trust the asset register" doesn't pass an Article 21 review. Auditors want a verifiable chain of custody — something you can hold up that says this exact device is the one that was installed. EDO is that something.
State-sponsored campaigns plant compromised hardware months before activation. By the time anomalous traffic shows up, the asset has been working against you for a year. The signature changes the day the swap happens — not the day the attack starts.
Every chip is built from real-world components — quartz crystals, power regulators, PCB traces. Each one is slightly imperfect in a way that's unique to that exact unit and stable for years. Together, those imperfections form a fingerprint that radiates out as part of the device's normal RF emissions.
EDO captures that fingerprint with a software-defined radio, places it in a sealed database, and compares every future reading against it. Swap the device and the fingerprint changes — even if the firmware, IP address, and Modbus replies stay identical.
What we don't do: touch your network, install agents, modify firmware, or stop your line. The sensor is passive. We listen, we don't transmit.
No agents on your devices. No taps on your network. No change windows. We bring a sensor cart, walk the line, and listen. Your operations team does not need to do anything.
Half-day visit. We map your devices, identify scope, agree on the asset list with your team. NDAs and security clearance handled here.
Our engineer captures the EM signature of every device in scope. Passive listening only. Your line keeps running. Average: 80–150 devices per shift.
We process the captures, build your Digital Twin, flag any anomalies. You get a draft report and a 90-minute walkthrough call.
Sealed PDF with per-device verdict, NIS2 / IEC 62443 evidence pack, and a recommendation on continuous monitoring. Auditor-ready.
The right question isn't "is it talking correctly?"
It's "is it the right device?"
Most customers begin with a one-time audit to satisfy NIS2, find what's already wrong, and put a baseline in place. From there, continuous monitoring runs against that baseline — and flags every drift, swap or anomaly going forward.
A one-time, full-line baseline. Audit-ready in 8 weeks.
For when your auditor is asking, when you suspect something's off, or when you simply want to know what's actually in your facility.
Continuous verification. Every drift, every swap, every time.
After the audit, the sensor stays. Your Digital Twin gets compared against live readings — and you get an alert the moment a signature changes.
Hardened deployments for critical and classified sites.
For air-gapped facilities, defence procurement, and sites where the stakes don't allow third-party SaaS. Custom signature library, ruggedized sensors, on-prem control plane.
The physics doesn't care whether the device is bolted to a chassis in Munich or a Pelican case in the field. If it has silicon, it has a signature. We read it.
If your operation runs on PLCs and you have an NIS2 obligation — or a CISO who lost sleep over Volt Typhoon — this is for you.
When the supply chain itself is the threat surface, you need a way to verify hardware integrity before it goes downrange — and again after it comes back.
Every other vendor told us to put more agents on the network. EDO was the first one that asked whether the devices on the network were the right devices in the first place. That question changed how we think about OT security.
CISO · European industrial operator
Pilot engagement · 2026
A 30-minute briefing, no slide deck. We bring the SDR, walk through a redacted result from a comparable facility, and tell you straight whether EDO makes sense for your environment. If it doesn't, we'll say so.
// No deck. No demo. Just the answer.