Raja Hamza, Contributing Writer EDITORIAL
IT & Engineering

IoT on the Corporate Network: Discovering and Securing Unmanaged Devices

IoT on the Corporate Network: Discovering and Securing Unmanaged Devices

The corporate network was once home mainly to computers, servers and printers. Today it hosts an astonishing variety of devices: security cameras, badge readers, smart thermostats, conference room displays, medical equipment, manufacturing sensors and much more. These Internet of Things devices often outnumber traditional endpoints. I have walked through facilities where IT teams believed they had a few hundred connected devices, only to discover several thousand once proper discovery tools were deployed. That gap between perception and reality is where much IoT risk lies.

Why IoT Devices Are Risky

Many IoT devices were designed for function and cost rather than security. They may run outdated software that cannot be patched, use default passwords or communicate with external services in ways IT does not understand. They typically cannot run endpoint security agents. Attackers have exploited these weaknesses to gain network footholds, launch attacks and build networks of compromised devices.

Discovery Comes First

Organizations cannot secure what they cannot see. Discovery tools identify devices on the network, often by analyzing their traffic patterns and characteristics to determine what they are. Machine learning helps classify unfamiliar devices accurately. A complete, current inventory is the foundation for every other IoT security measure.

Segmentation and Least Privilege

IoT devices should have only the network access they genuinely need. A security camera needs to reach its video recording system, not the finance department’s file server. Placing IoT devices in segmented networks with restricted access limits the damage if one is compromised. Policies can be applied automatically based on device type once devices are identified.

Behavioral Monitoring

Because IoT devices typically behave predictably, unusual behavior is a strong indicator of compromise. Monitoring traffic for anomalies, such as a thermostat attempting to reach unfamiliar internet addresses, enables rapid detection.

Procurement and Lifecycle

Security should be considered before devices are purchased. Organizations can require vendors to support secure configuration, regular updates and documented communication requirements. Devices that reach end of support should be replaced or further isolated.

Collaboration Across Teams

IoT devices are often purchased by facilities, operations or clinical teams rather than IT. Effective security requires collaboration between these groups.

Working With Vendors

IoT manufacturers vary enormously in their security maturity. Some provide regular updates, clear documentation of network requirements and secure default settings. Others provide almost nothing. Building security requirements into purchasing contracts, and favoring vendors that publish vulnerability disclosure policies, gradually raises the standard of devices entering the network. Over time, this reduces the burden of compensating for insecure products after installation. Periodic reassessment of the device inventory, ideally quarterly, ensures that newly connected equipment is classified and secured before it becomes a forgotten weak point.

The Bottom Line

IoT devices now make up a large and often invisible part of the corporate network. Discovery, segmentation, behavioral monitoring and lifecycle management together reduce their risk. Collaboration with the teams that purchase and use these devices is essential. Organizations that address IoT security systematically close one of the most common gaps attackers exploit. In my view, the first step, simply finding out what is connected, is often the most revealing.