Claroty counted roughly 65,000 consumer devices sitting on critical-infrastructure OT networks. Smartwatches, streaming sticks, personal phones — the flotsam of modern life, plugged into the systems that run water plants and power grids. Every CISO I know read that number as attack surface. I read it as something worse: 65,000 uncontrolled process inputs that walked through the gate in someone's pocket. No change ticket. No PFMEA row. No entry in any register that matters. In my years running quality in automotive plants, if a gauge had entered the process stream the way these devices did — unmarked, unverified, owned by nobody on the org chart — we would have stopped the line. Rightly.
You cannot control what you have not listed
I built a QA/QC department from zero at a 900-person greenfield plant. Before the first part was measured, before the first auditor walked the floor, there was a spreadsheet with three columns: device, owner, next calibration date. That ledger — the measuring-device register required by ISO 9001 clause 7.1.5 and drilled into anyone who has lived under IATF 16949 — was the founding discipline of the department. Not the CMM machine. Not the torque analysers. The list.
An OT network deserves exactly the same ledger and almost never gets one. Owner. Purpose. Firmware version. Review date. A device without an entry is a gauge without a calibration sticker: physically present, functionally invisible, quietly shifting your process capability in ways no control plan anticipated. Claroty's researchers did not find exotic malware. They found that the register doesn't exist. Every one of those 65,000 devices is evidence of an asset nobody listed, which means nobody risk-assessed, which means nobody controls.
A network you have not inventoried is not a network — it is a rumour with routers.
The phone is a measuring device now
Here is where the quality argument gets uncomfortable. The personal phone is not a visitor to the process. It is a participant. I have watched technicians photograph non-conforming parts on their own phones for the QRQC board, scan supplier travellers, message the shift leader a picture of a crack straight from the line. That is data capture. That is record creation. The device entered the Man/Machine columns of the 4M matrix without a single signature, carrying traceability obligations — and, in aerospace contexts, export-control exposure — in the same pocket as someone's family photos.
The QRQC instinct applies directly. When something leaks, when a defect escapes, when a network gets compromised, the first question is always the same: what changed? In process terms, these devices are an undocumented change to the measurement system — introduced by the hundreds, daily, by the very people the change-control process was designed to include. The hospital cyberattacks documented in recent industry reporting, the twenty Australian industrial ransomware incidents Dragos logged in a single quarter — the entry point is rarely the hardened server. It is the seam. The thing nobody listed.
Segregation by segmentation
Zoning a network is the same engineering judgement as quarantining suspect stock. You do not negotiate with a suspect batch; you fence it, label it, decide its fate from a position of containment. Network segmentation is poka-yoke applied to electronics — not a rule people must remember, but an arrangement that makes the mistake physically difficult.
The practical moves are unglamorous and proven. A guest VLAN that exists in practice, not just in the architecture diagram, with personal devices herded onto it by default. Camera and phone rules enforced at the line — where the operator can see the fence — rather than in a policy document nobody re-reads after induction. A quarterly device sweep audited with the rigour of a gauge audit: physical walk, network scan, reconciliation against the register, deviations raised as non-conformities.
I hold a CEH certification and thirty-plus security credentials, and I spent enough time in bug-bounty work — including a clickjacking disclosure that landed me on T-Mobile's public Hall of Fame — to learn one durable lesson: flaws live in the seams nobody inspects. That vulnerability was not exotic logic. It was a mundane frame boundary two teams each assumed the other owned. IT/OT is the largest unaudited seam in manufacturing today. Both sides have valid assumptions. Neither is written down, and the smartwatch sits in the gap.
Key takeaways
- Treat the network device register as the gauge register: owner, purpose, firmware, review date. An unlisted device is an uncalibrated instrument in the process stream.
- Recognise that personal phones now perform measurement and traceability functions — bring them under change control, or provide controlled alternatives at the line.
- Build segmentation as poka-yoke: guest VLANs, enforced zoning, and quarterly device sweeps reconciled like calibration audits, with deviations raised as non-conformities.
- When investigating any breach or escape, apply the QRQC first question — what changed — to hardware entering the network, not just to process parameters.
So flip the auditor's question. Not "show me your firewall rules" but "show me the list." The rules describe a network as designed; the list describes a network as lived. If the maintenance technician's smartwatch is not on it — and at 65,000 uncounted devices across critical infrastructure, it is not — then the list is fiction, and the certificate in the lobby describes a network that stopped existing the day someone charged their watch at a plant-floor socket. The smartwatch counted his steps. Nobody counted the smartwatch.