Devices that are not computers, until they are
The Internet of Things is a loose label for everyday objects and equipment that have sensors, a small computer and a network connection. Examples in workplaces include security cameras, badge readers, thermostats and lighting controls, printers, door locks, environmental sensors, point-of-sale terminals, medical equipment, vehicle trackers and production machinery. At home, similar devices include speakers, doorbells and appliances.
For an IT team, the important point is that these things behave like small computers on the network, even when nobody thinks of them that way. They have software, addresses, credentials and flaws, and someone ends up supporting them. Often it is IT, even if another department bought the device.
Who owns it?
A frequent early problem is ownership. Facilities may purchase the building controls, a clinic may buy equipment from a supplier, and a manager may plug in a convenient sensor. IT then discovers the device when it appears on the network or when it fails. A few questions are worth settling early:
- Who approves a new connected device before purchase?
- Who is responsible for updates, passwords and replacement?
- What does the supplier support, and for how long?
- Who responds when it stops working at night?
Agreeing on this before devices arrive prevents many awkward discussions later. Including IT in purchasing for anything that connects to the network is a simple and effective rule.
Knowing what you have
You cannot secure or support what you do not know about. Connected devices are easy to lose track of because they are small, numerous and often installed out of sight. Good asset management for these devices usually records the type, location, owner, network address, software version, purchase date and support end date. Network scanning can help find unknown devices, but it should supplement a purchasing process, not replace it.
The network side
Large numbers of small devices put load on network infrastructure in several ways.
Addressing and capacity. Each device needs an address, and some need wired ports or power. Wireless coverage must cope with many simultaneous low-traffic clients, and crowded wireless bands can cause unreliable behavior, so planning Wi-Fi channels matters in dense environments.
Segmentation. Many connected devices cannot be fully secured. A common approach is to place them on separate network segments with tight firewall rules, allowing only the connections they need. If a camera is compromised, the aim is for it not to provide a route to file servers or finance systems.
Latency and reliability. Some uses, such as safety systems or production control, are sensitive to delays and outages. Others tolerate delays. Knowing which category a device falls into guides how the network is built and monitored.
Where the data goes. Many devices send data to a supplier’s cloud service. That raises questions about what is collected, where it is stored, and who can see it. Some processing happens locally, near the devices, to reduce traffic or delay, which adds another layer to a hybrid cloud design.
Security concerns
Connected devices have a mixed security record. Common problems include default or shared passwords, services left open that are never needed, no way to update, and suppliers that stop providing fixes after a few years. Some devices cannot support modern sign-in methods at all.
Practical measures, though never a guarantee of protection, include:
- Changing default credentials immediately and using unique ones.
- Disabling features and ports that are not needed.
- Applying vendor updates through a regular patch management routine, and recording devices that cannot be updated.
- Applying least privilege to what the device can reach and to accounts that manage it.
- Using vulnerability scanning to look for known weaknesses, with care, since some fragile equipment reacts badly to scans.
- Isolating unsupported devices, or replacing them.
If a device is compromised, incident response steps should be ready: how to find it, disconnect it and restore normal service. Staff awareness helps too, since people sometimes bring in personal gadgets that connect to the office network.
Privacy considerations
Cameras, microphones, location trackers and badge systems can record information about people. That may be personal data, and rules about notice, purpose and retention can apply. IT teams do not decide the legal position alone, but they are often asked to configure retention periods, restrict access to footage or readings, and answer questions about where data is held. Collecting only what is needed, a form of data minimization, reduces both risk and storage burdens.
Day-to-day operations
Support for connected devices looks like support for other equipment, with some twists.
Monitoring. System monitoring can check whether devices are online, reporting normally and running current software. With hundreds of devices, alerts must be tuned so that one routine glitch does not bury the team in noise.
Troubleshooting. A problem might lie with the device, power, the network, the supplier’s cloud service or the app that controls it. A methodical approach helps separate them.
Remote management. Devices spread across sites may need remote updates and resets. Without those, someone has to travel to each one.
Supplier relationships. When a device depends on a supplier’s service, an outage or a change of plan on their side can affect you. This echoes concerns about vendor lock-in in other areas of IT.
Documentation. Wiring, settings and recovery steps are easy to forget. A short record for each type of device saves time when staff change.
Lifecycle and replacement
Connected devices often last longer than the software support behind them. A sensor that works physically may be unsafe to keep if updates have ended. Hardware lifecycle planning should include the expected support period, a budget for replacement, and a safe way to wipe stored data before disposal, since devices can hold network passwords or recordings.
Where this leads
The number of connected devices in organizations is likely to keep growing, and smarter functions will increasingly run on the devices themselves. For IT teams, the most reliable preparation is not predicting each gadget but building habits: involve IT in purchases, keep an accurate inventory, segment the network, update what can be updated, and plan for retirement. These steps turn a scattered set of gadgets into something that can be managed.