So I spent the better part of this morning staring at a network scan. Not because I'm paranoid—though, to be fair, in my line of work a little paranoia is a feature. I was trying to answer a question that I get asked a lot by B2B partners: what is on my wifi that shouldn't be there?
If I remember correctly, the number of connected devices in the average industrial facility has nearly doubled in the last three years. And not all of them are officially sanctioned. In our Q1 2024 quality audit, we found 17% of devices on a client's production floor network were unaccounted for. That's a quality problem hiding as an IT annoyance.
The Surface Problem: 'What Is on My WiFi?'
When a plant manager asks me what's on their wifi, they're usually thinking about bandwidth hogs. Someone's streaming video. A contractor left a personal hotspot running. Maybe a rogue printer is broadcasting. They want to find it, lock it down, and move on.
Fair enough. That's the surface issue. But here's something vendors won't tell you: the real problem isn't the device itself—it's that the device got there without anyone noticing. That's a process failure, not just a network one.
To be fair, most network scans—like the kind you run from a smartphone app or a basic IoT gateway report—will tell you what's connected. They'll give you a list of MAC addresses and IPs. What they won't tell you is whether that device is supposed to be there, what it's doing, or whether it's affecting the performance of the equipment that actually matters.
The Deeper Cause: Why Unauthorized Devices Get Through
I get why people think this is just a security problem. 'Someone connected something they shouldn't have.' But that skips the real issue.
What most people don't realize is that modern production and logistics networks are designed for flexibility, not for lockdown. You've got contractors coming in with their own tablets. You've got temporary sensors for a new production line. You've got the occasional 'I'll just plug this in for a quick test' from an engineer who doesn't want to wait for IT clearance. And the network, as designed, lets them.
That's not necessarily bad design—it's pragmatic. But it creates a blind spot. If you're running a facility with, say, 50,000 connected devices (a number we're seeing more often in smart factories), you can't manually check each one. You need a system that categorizes devices by role, by trust level, and by whether they're expected.
That's where the quality angle comes in. In my world, we don't just ask 'is this device connected?' We ask: 'Does this device meet the spec for being on this network?'
Here's an example. I reviewed a supplier's IoT gateway deployment where their 'standard' configuration allowed any device with a valid DHCP request to connect. No whitelist. No device fingerprinting. The vendor claimed this was 'within industry standard' for their product category. Normal tolerance for manufacturing networks, they said. But that's a specification, not a standard—and it's a lazy one. We rejected their setup and required a hardware-level trust check, similar to how LoRa modules authenticate endpoints via unique device identifiers and encryption keys. The fix cost them about $18,000 in rework—but it saved us from a potential production outage down the line.
The Real Cost of an Unmanaged Network
I still kick myself for not catching a similar issue earlier in my career. We had a line where machine downtime was creeping up week over week. Everyone pointed fingers: the machine vendor said it was the network; the network team said it was the machine. Turned out there was a contractor's wireless camera streaming HD video on the same 2.4 GHz band as our critical equipment. Uptime was degraded by about 8% over a month. That 8% cost us a production deadline and a $22,000 penalty.
Now, that's an extreme case. But the principle holds: unmanaged devices degrade quality. Not always in a catastrophic way. Sometimes it's just a sensor reading that takes a few milliseconds longer to arrive. Sometimes it's a packet of dropped data from a blood pressure monitor in a connected health setup that logs 'no reading' instead of the actual value. In a batch of 100,000 units, that 0.5% error rate turns into 500 heads you can't account for.
So when I ask 'what is on my wifi,' I'm not asking about intruders. I'm asking about compliance. About consistency. About whether the devices that should be talking are talking clearly, and the ones that shouldn't be aren't.
The Short Answer: A Quality-First Approach to Network Visibility
Here's my rule: treat every device on your network like a component in a supply chain. You wouldn't accept a part without a spec sheet. Don't accept a device without a network role and a trust classification.
Practically, that means:
- Device enrollment at hardware level, not just IP assignment. If your LoRa modules or wireless gateways don't have a hardware-level identity that the network can verify, you're relying on 'trust but verify'—which is just 'trust' with extra steps.
- Role-based traffic rules. A contractor's tablet does not need to talk to the production line control server. A production sensor does not need to ping the internet.
- Regular audits with a purpose. Not just 'find all devices.' Ask: 'For each device found, is it authorized? Is it behaving as expected?'
You don't need a $100,000 solution for this. But you do need the right access control story from the silicon up. A transparent device identity model—one that shows you what's connected, what it's allowed to do, and whether it's supposed to be there—is worth more than any 'find intruders' tool. Because the intruder you should worry about isn't a hacker. It's the unvetted sensor that's quietly degrading your quality numbers.
I'll put it this way: the vendor who tells you upfront what's included in their network management—even if it costs more—usually costs less in the end. Because when you know exactly what's on your wifi, you can stop guessing and start controlling.
