Segmenting IoT and OT Off Your Business Network

Walk through a typical business today and count the things connected to the network that aren't computers. Security cameras. The smart thermostat. Network printers. The badge-access system. A conference-room display. Maybe a TV in the lobby, a smart doorbell, a fleet of VoIP phones. In a warehouse, clinic, or shop floor, add the machinery, sensors, and controllers that keep operations running.

Every one of those is a computer of some kind, sitting on your network — and collectively they're the weakest, least-watched part of it. The industry buckets them as IoT (Internet of Things — the cameras, smart gadgets, printers) and OT (Operational Technology — the industrial and building-control systems). Leaving them on your main network is one of the most common and most dangerous mistakes we see. Here's why, and what to do instead.

Why these devices are the soft underbelly

Regular computers get attention: they're patched, they run security software, someone notices when they act up. IoT and OT devices get almost none of that, for reasons baked into what they are.

  • They rarely get updated. Many ship with security flaws and never receive a single firmware patch in their service life. Nobody's logging into the lobby camera to apply updates.
  • They run forgotten default passwords. Cheap cameras and gadgets famously ship with well-known logins that nobody changes — published online, scanned for automatically.
  • You can't run security tools on them. There's no antivirus for a thermostat. You can't see what's happening inside them the way you can on a PC.
  • They live for years. A camera or industrial controller installed once may run untouched for a decade, long after its software stopped being supported.
  • OT gear is fragile by design. Industrial systems often can't be patched or rebooted casually because doing so means stopping production — so known flaws sit open for a long time.

Put plainly: these are internet-connected computers you usually can't update, can't monitor, and can't fully secure. On a flat network, each one is a standing open door into everything else you own.

The riskiest device on most business networks isn't a laptop. It's the camera, the printer, or the smart gadget nobody thinks about — unpatched, unwatched, and trusted by default.

How a camera becomes a breach

This isn't theoretical. Internet-connected cameras and IoT devices have been hijacked at massive scale for years, conscripted into botnets or used as quiet footholds inside business networks. The pattern is grimly consistent: an attacker compromises a weak device — a camera with a default password, an unpatched printer — and from there, if the network is flat, they pivot toward the real targets. The thing they broke into wasn't valuable. It was just the easiest way in.

OT raises the stakes further. When industrial or building systems share a network with the office, an attacker who reaches them can disrupt physical operations, not just data. That's why keeping OT separated from IT is now treated as a baseline practice, not a nicety.

The fix: dedicated VLANs and a default of no trust

The solution is the same architectural move we've covered throughout this series — segmentation — applied specifically to these devices. The goal is simple to state: IoT and OT devices get their own VLANs, walled off from your business network, and they are trusted with nothing by default.

1. Give them their own segments

Put cameras and IoT gadgets on a dedicated VLAN. Put OT and industrial systems on another, separate from both IoT and the office. Don't lump them in with staff workstations, and don't lump unlike things together — a security camera and a factory controller have no reason to share a network.

2. Block them from initiating connections inward

This is the heart of it. With firewall rules between segments, deny IoT and OT devices the ability to start connections into your business network. A camera never needs to reach your file server. A thermostat has no business talking to your accounting system. Let them do their narrow job and nothing else. This is exactly the kind of rule-writing covered in our piece on inter-VLAN routing and ACLs — permit the specific traffic each device legitimately needs, deny everything else.

3. Control their internet access too

Many of these devices "phone home" to a manufacturer's cloud, and some have no business reaching the internet at all. Where a device doesn't need internet access, block it. Where it does, restrict it to only what it requires. An unsupervised camera with open internet access is a device you've handed the keys to.

4. Reach them through a controlled path, not a flat one

Your team still needs to view the cameras and manage the systems. The answer isn't to flatten the network — it's to permit that specific access from specific, trusted machines, through the controlled doors your firewall rules define. Convenience and isolation aren't in conflict if the rules are written with care.

OT deserves extra caution

For businesses with real operational technology — manufacturers, larger medical and dental practices, facilities with serious building automation — treat the OT network as its own world. The widely referenced guidance is to keep a hard boundary between OT and IT, allow only tightly defined traffic across it, and never let OT systems wander onto the general business network or the open internet. When physical processes and safety are on the line, the cost of a soft boundary is far higher than lost data. This kind of infrastructure planning is part of how we approach network and systems administration for the businesses we support.

A checklist for your own devices

Take an honest inventory and ask:

  • Are the cameras, printers, and smart devices on the same network as our computers and data? (If yes, that's the first thing to fix.)
  • Have the default passwords on every device been changed?
  • Can any of these devices reach our servers or sensitive systems today?
  • Do any of them have open internet access they don't actually need?
  • For any industrial or building-control systems — are they isolated from the office network?
  • Do we even have a full list of what's connected? (You can't protect what you haven't counted.)

That last point matters most. A lot of businesses are surprised by what's actually on their network once someone looks. The smart devices accumulate quietly — a camera here, a connected display there — until the "internet of things" footprint is larger than anyone realized, and none of it is segmented.

The bottom line

The devices most likely to get a business breached are rarely the computers everyone worries about — they're the cameras, printers, gadgets, and machines nobody's watching, the ones you can't patch and can't run security tools on. The defense isn't to secure each one perfectly; you can't. It's to box them off on their own VLANs, deny them trust by default, and let firewall rules permit only the narrow traffic they truly need. For businesses across Pinellas and Pasco County, getting these devices off the flat network is one of the highest-value, lowest-drama security upgrades available. If you're not sure what's connected or how it's separated, that's exactly the kind of review we're glad to run.

Need help with this?

Talk to a local IT team that has supported businesses across Pinellas & Pasco County since 2010.

Get a Free Consultation Free Security Assessment