Key Points
- Manufacturing is now the most targeted industry for cyberattacks, and connected devices on the plant floor are a big part of the reason. Industrial IoT security has to be treated as an operational priority, not an IT afterthought.
- The biggest risks are not exotic. Flat networks, unpatched legacy equipment, weak vendor practices, and unmanaged devices cause most incidents. Fixing the fundamentals gets you most of the way there.
- You do not have to choose between connectivity and security. With the right architecture, the right standards (IEC 62443), and the right vendor requirements, you can run a fully connected plant without expanding your attack surface.
Every sensor, gateway, and connected controller on your plant floor does two things at once. It gives you data you never had before, and it gives attackers a potential way in. That is the tradeoff at the center of industrial IoT security, and it is why the topic has moved from IT conference rooms to plant manager offices.
The good news: this tradeoff is manageable. Getting industrial IoT security right doesn't take the biggest budget. The manufacturers doing it well know where the real risks live, work from a proven framework, and hold their vendors to a clear standard.
This guide covers all three.
What Makes Industrial IoT Security Different
If you already have an IT security program, you might assume it covers your connected plant equipment. It does not, and the reason comes down to three differences between IT and OT environments.
The priorities are inverted. IT security protects confidentiality first. OT security protects availability first. When a laptop gets compromised, you wipe it and move on. When a PLC controlling a production line gets compromised, you cannot just take it offline. Downtime is the damage. Any security approach that treats plant equipment like office equipment will either get bypassed by operations or shut down production on its own.
The equipment lives longer. Your laptops refresh every three or four years. Industrial control systems routinely run for 20 years or more. That means your network almost certainly includes devices running operating systems and firmware that stopped receiving security patches a decade ago. You cannot patch your way out of this. You have to architect around it.
The consequences are physical. A breached ERP system leaks data. A breached control system can stop lines, damage equipment, and put people at risk. The stakes are different, so the discipline has to be different, too.
Industrial IoT sits right at the intersection of these two worlds. Sensors and gateways are modern, connected, internet-facing devices installed directly on legacy operational equipment. That is exactly why they deserve their own security conversation.
The Threat Landscape Is Not Theoretical
Manufacturers sometimes assume attackers only care about banks and hospitals. The data says otherwise.
According to Dragos, 119 ransomware groups targeted industrial organizations in 2025, up from 80 the year before, and manufacturing accounted for more than two-thirds of the victims. Across the industrial ransomware cases Dragos observed in 2024, 75% disrupted operations to some degree, and 25% caused a full shutdown of an OT site.
The entry points are just as instructive as the volume. The Verizon Data Breach Investigations Report found that 38 percent of manufacturing breaches started with an exploited vulnerability, and 61 percent involved a third party.
Read those numbers together and a picture forms. Attackers are not breaking through hardened defenses with sophisticated zero-days. They are walking through doors that were left open: an unpatched internet-facing system, a vendor with weak credentials, a remote access tool nobody was tracking. Manufacturing is targeted because attackers know downtime is expensive and plants are under pressure to pay quickly to restore production.
That is the threat model industrial IoT security has to answer.
Where Manufacturers Are Actually Exposed
Before you can secure a connected plant, you need an honest inventory of where the exposure comes from. In most facilities, it comes from five places.
1. Flat networks
Many plants still run everything on one network. The HMI, the historian, the office printers, the maintenance sensors, and the guest WiFi can all reach each other. In that environment, a single compromised device becomes a launchpad to everything else. Dragos reports that 88 percent of OT networks struggle with detection and response, which means once an attacker is inside a flat network, they usually have time to move.
2. Legacy equipment that cannot defend itself
That 20-year-old controller was designed for an era when the plant network was physically isolated. No encryption, no authentication, no way to patch it. And it's not going anywhere. It runs your process, and replacing it would cost more than the entire security budget. Legacy equipment is a constraint you design around, not a problem you solve.
3. Unmanaged and unknown devices
You cannot protect what you do not know you have. Plants accumulate connected devices over years: a sensor pilot from a vendor that left, a cellular modem installed by a contractor, a smart HVAC system nobody told IT about. Every unknown device is unmonitored attack surface.
4. Third-party and vendor access
Integrators, OEMs, and service providers all need remote access to your equipment at some point. Each connection is a potential path in, and the Verizon data shows third parties are involved in a majority of manufacturing breaches. The access itself is rarely
5. IoT devices with weak security fundamentals
Not all industrial IoT hardware is built to the same standard. Devices that ship with default passwords, shared keys instead of certificates, unencrypted traffic, or no mechanism for firmware updates import risk directly onto your machines. This is the exposure you have the most control over, because you choose what you buy.
The Framework That Works: IEC 62443
You do not need to invent an industrial IoT security strategy from scratch. IEC 62443 is the international standard for securing industrial automation and control systems, and it was built for exactly this environment: long equipment lifecycles, availability-first priorities, and mixed generations of technology.
The core concept is zones and conduits. You group assets with similar security requirements into zones, and you strictly control the conduits, meaning the communication paths, between them. Your safety systems sit in one zone. Your control systems sit in another. Your monitoring sensors sit in a third. Traffic between zones passes through defined, monitored, restricted paths, and nothing else gets through.
This structure does something powerful: it contains failure. When a device in one zone is compromised, the attacker hits a wall instead of a highway. Recent updates to the standard push this even further, emphasizing microsegmentation and identity-based controls over simple network location, which aligns industrial practice with the zero trust direction the rest of the security world is moving in.
IEC 62443 also defines security levels, from SL1 (protection against casual misuse) up to SL4 (protection against nation-state level attackers), so you can match the strength of your controls to the criticality of each zone rather than applying one blanket policy to the entire plant. Your changeover documentation does not need the same protection as your safety instrumented systems, and the standard gives you a defensible way to make that call.
If you take one action from this guide, make it this: map your plant into zones and conduits, even roughly, even on a whiteboard. The exercise alone will show you where your real exposure is.
A Practical 7-Step Industrial IoT Security Checklist
Frameworks set the direction. These seven practices are what implementation looks like on the ground.
Build and maintain a complete asset inventory. Every connected device, its firmware version, its network location, and its owner. This is the foundation everything else stands on. CISA and its partner agencies dedicated an entire joint guidance document to exactly this point. If a device is not in the inventory, it is not being monitored, patched, or defended.
Segment your network, starting with the highest-consequence assets. You do not have to segment the whole plant in one project. NIST's guide to OT security recommends the same phased approach: start by isolating safety systems and critical process controls, then work outward. Every zone boundary you add shrinks the blast radius of a future incident.
Require strong encryption and authentication on every new device. TLS 1.2 or higher for data in transit and AES 256 for data at rest is the baseline, not the gold standard. Certificate-based authentication should be standard. Shared keys and default passwords are disqualifying.
Demand over-the-air update capability. NIST's core baseline for IoT devices lists secure software updates as a required capability, and for good reason: a sensor fleet you cannot patch remotely is a liability that grows every year.
Control and audit third-party access. Scope every vendor connection to the specific systems it needs, set expiration dates, and review the list quarterly. Given that most manufacturing breaches involve a third party, this single habit closes one of the most common doors, and CISA, the NSA, and the FBI published joint guidance on exactly how to secure the remote access software behind it.
Monitor OT traffic for anomalies. Attackers who get in tend to stay quiet and move slowly. The SANS 2024 ICS/OT survey found OT-specific monitoring jumped from 33 to 52 percent of organizations in a single year. The plants investing here are pulling ahead. Baseline what normal communication looks like between your zones, and alert on deviations.
Plan for the incident before it happens. Decide now who has the authority to isolate a network segment, how production continues during containment, and how you communicate with customers. Only 34 percent of organizations rehearse incidents in ICS/OT-specific environments, which shows in the outcomes: plants with a rehearsed plan restore operations in days. Plants without one improvise for weeks.
Hold Your IoT Vendors to a Higher Standard
Here is the part of industrial IoT security that manufacturers control completely: what you allow onto your machines in the first place. Every vendor conversation should include these questions, and the answers should be specific, not reassuring.
How does data leave the device, and does it touch my plant network? This question matters more than most buyers realize. Sensors that communicate over independent cellular connections never touch your OT network at all, which means they add monitoring capability without adding a single node to your internal attack surface. Sensors that require WiFi or ethernet on your plant network need to justify that access and fit inside your zone architecture.
What encryption is used in transit and at rest? Expect TLS 1.2 or higher and AES 256, stated plainly.
How are devices authenticated? Certificate-based authentication is the acceptable answer.
How are firmware updates delivered, and how quickly are vulnerabilities patched? Ask for the actual process and the actual track record.
What certifications does the platform hold? SOC 2 Type II and ISO 27001 indicate a vendor that treats security as an ongoing discipline rather than a marketing claim.
Can I get SSO through my identity provider? Access to the platform should run through the same identity controls as the rest of your business.
A vendor that answers these questions crisply is a vendor that has been asked them before. A vendor that gets vague is telling you something important.
Security Is What Makes the Connected Plant Possible
It is tempting to frame industrial IoT security as a tax on progress, one more hurdle between your team and the data it needs. That framing gets it backwards.
The plants getting the most value from IoT, the ones catching bearing failures three weeks early and cutting unplanned downtime year after year, are the ones that solved security first. They can deploy sensors at scale because IT trusts the architecture. They can expand monitoring to new lines without a six-month review cycle, because the standards were set once and every new device meets them.
That is the real payoff. Industrial IoT security done right is not a barrier to the connected plant. It is the reason the connected plant gets built at all.
Start with the inventory. Map your zones. Raise the bar on your vendors. The threats targeting manufacturing are real, but so is the playbook for beating them.
Here at Tractian, we are dedicated to protecting your data through technical controls in compliance with regulatory and legal resources. Learn more here: https://trust.tractian.com/.