PLCs, SCADA, substations, factories, building automation
Attested OT and industrial control
The plant runs for thirty years. Trust was checked once, on the first day.
A plant or a building runs for thirty years. Its controllers were trusted on the day they were wired in, and mostly still are. Since then they took firmware updates, vendor laptops, spare parts and remote access. Nobody can show what each controller runs today. Attestation gives the plant that answer without stopping production.
Who this is for
- Asset owners, utilities, factories, water, pharma, food
- Machine builders and automation vendors, selling into IEC 62443 tenders
- System integrators, who commission and maintain plants
- Building operators and integrators, hospitals, airports, data centres, campuses
- OT security and compliance leads, answering NIS2 and insurers
When trust has to be proved again
Firmware is updated during a shutdownThe window is short and the next one is a year away. Each controller should prove the new version before the line starts again.
A controller is replaced from the spare shelfThe spare has old firmware and an identity the plant has never seen. It should be enrolled with evidence.
A vendor connects for remote maintenanceThe plant should know what the vendor changed, from the device itself.
A device moves between zonesIEC 62443 separates zones and conduits. A device that changes zone should earn its place in the new one.
A building controller is changedHeating, access doors, lifts and fire systems hang off the same building management system. A changed controller should prove itself before it can open a door.
An advisory names a firmware versionThe question is which of four hundred controllers run it. The answer should take an hour and come from the devices.
What we deliver
- An identity and attestation design that fits long-lived equipment: factory identity, onboarding, and proof of firmware state where the hardware supports it.
- Rules for shutdown windows, spares, vendor access and zone changes: what a device must prove, and what it may do until then.
- A path for old equipment that cannot attest: gateways that vouch for what they front, and a plan for replacement.
- Evidence mapped to IEC 62443, NIS2 and the Cyber Resilience Act, in the form your assessor and your insurer ask for.
Questions worth answering
- Can you list the firmware version of every controller today, from evidence?
- After a shutdown, how do you know every update arrived?
- What does a spare part prove before it controls a process?
- Which of your devices could attest if you asked them?
Across the life cycle
DesignBuildMake or deployOperateUpdateRetire
The stage that decides here: operate. Equipment runs for decades between short shutdowns. Operation is almost the whole life cycle. See attestation in the product life cycle.
Rules and standards your buyers cite
IEC 62443NIS2Cyber Resilience ActEU Machinery Regulation
Industries that use this
Pharma and life sciencesEnergy and smart grids
Go deeper
Not quite your case? An energy company? Energy and smart grids. Pharma production? Pharma and life sciences. Small connected products? Attested devices.
Working on Attested OT and industrial control? A first call takes 30 minutes and commits you to nothing. Bring your product and the one question that worries you.
Next fixed date: EU Digital Identity Wallets are due in every member state on 24 December 2026, 42 days from now.
Concepts: Re-attestation · Continuous attestation · Remote attestation · IETF RATS architecture