Autonomous trucks, mining haulage, ports, agriculture, construction
Attested autonomous vehicles and machines
Three companies share one vehicle. None of them can see what the others installed.
An autonomous truck is built by one company, driven by another company's software and run by a third. Each of them answers for a 40-tonne machine, and none of them can see what the others installed last night. Attestation gives all three the same verifiable answer. Re-attestation keeps it true after every update, repair and handover.
Who this is for
- Truck and machine makers, on the road and off it
- Autonomy suppliers, whose software runs on someone else's vehicle
- Fleet and site operators, mines, ports, farms, logistics
When trust has to be proved again
An over-the-air update changes approved softwareOn the road, UN Regulation 156 ties type approval to identified software versions. A vehicle can report any version. It should prove the one it runs. The autonomy kit is serviced or swappedComputers, sensors and controllers from different suppliers must be enrolled again with evidence. A technician's signature is too little.
A remote operator takes controlVehicle and control room should each verify the other before a single command is accepted.
A machine moves between sites or ownersA haul truck entering a mine network, or a resold machine, should earn its access again.
A vulnerability is announced in a componentThe operator needs to know within hours which units run it. A spreadsheet of intended versions is not that answer.
What we deliver
- One attestation model shared by manufacturer, autonomy supplier and operator: who attests what, who verifies, who is told.
- Re-attestation rules for updates, repairs, remote operation and site entry, including what a machine may do until it has passed.
- Evidence mapped to what your approval authority or customer asks for. On the road: UN R155 and R156. Off the road: the EU Machinery Regulation, the Cyber Resilience Act and IEC 62443.
Questions worth answering
- Can the operator verify the autonomy software version without asking the supplier?
- After a repair, who proves the machine is back in an approved state?
- Does the control room know it talks to the real machine, and the machine to the real control room?
Across the life cycle
DesignBuildMake or deployOperateUpdateRetire
The stage that decides here: make or deploy. Three companies assemble one vehicle. Whoever owns deployment owns the first proof, so settle it in the contract. See attestation in the product life cycle.
Rules and standards your buyers cite
UN Regulations 155 and 156EU Machinery RegulationCyber Resilience ActIEC 62443
Use case
Autonomous haul trucks at a mine
Go deeper
Who builds in this area
From our public landscape: Aurora, Kodiak AI, Waabi, PlusAI, Torc Robotics, Bot Auto, Stack AV, Gatik, Einride, Volvo Autonomous Solutions, Scania, Cat MineStar Command for hauling, Komatsu FrontRunner, Hitachi Construction Machinery AHS, Epiroc, Sandvik AutoMine, Pronto, Outrider, Embotech, Fernride, Oxa, Forterra, Kalmar, John Deere autonomous tractor, Applied Intuition, Gravis Robotics.
Not quite your case? Robots and drones? Attested robots. Mine or port control systems? Attested OT.
Working on Attested autonomous vehicles and machines? 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