TL;DR: Device identity and provenance are the weak points in Industrial IoT security, according to DigiCert. Industrial systems need certificate-backed trust and lifecycle controls to make onboarding, revocation, and replacement governable at scale.
Editorial analysis by NHI Mgmt Group, based on content published by DigiCert: “Three Challenges for the Industrial IoT”.
Key questions
Q: Why do legacy protocols create more risk for identity attacks?
A: Legacy protocols create risk because they often cannot enforce modern MFA consistently, which gives attackers alternate authentication paths to abuse.
Q: What breaks when IoT security is built without a PKI-based trust model?
A: Without a PKI-based trust model, organisations often end up with weak device verification, inconsistent certificate handling, and brittle trust assumptions across connected devices.
A: Security teams should treat industrial IoT as an identity problem, not just a connectivity problem.
Practitioner guidance
- Map industrial device identity coverage Inventory which machines, sensors, and controllers can authenticate with certificates, and document where proprietary protocols still depend on implicit trust.
- Segment devices that cannot prove identity Place legacy or non-compliant controllers in constrained network zones until they can support stronger authentication or are replaced.
- Harden certificate lifecycle for IIoT endpoints Treat issuance, renewal, revocation, and replacement of device certificates as part of the industrial operations process, not a background PKI task.
Bottom line: Industrial IoT risk in this article is not connectivity by itself, but the weak identity and provenance model around connected machines and controllers.
Glossary terms: Industrial IoT, Device Identity, Supply Chain Integrity, Public Key Infrastructure
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Device identity is the trust boundary Industrial IoT never fully escaped. Industrial connectivity often gets discussed as a networking problem, but the article shows that the real boundary is identity proofing for machines, sensors, and controllers. Without a reliable way to authenticate the thing itself, every downstream control inherits ambiguity. The practitioner conclusion is that IIoT governance starts with machine identity, not after deployment.
A question worth separating out:
Q: What should IAM and OT teams verify before admitting a connected device?
A: They should verify whether the device can authenticate strongly, whether its certificate lifecycle can be managed, and whether the hardware, software, and firmware provenance is documented. If any of those checks fail, the device should not be treated as trustworthy simply because it is operationally useful.
👉 Read our full editorial: Industrial IoT security hinges on device identity and supply chain trust