Connected devices in business: five rules to avoid opening a door to attackers
A connected sensor or camera is a small computer plugged into your network, often with no screen and no alerts. Badly configured, it becomes the easiest way in. Five rules cut the risk sharply.
Start from the use case
Before buying, define what you want to measure or automate, how often, and for which decision. The choice of connectivity (Wi-Fi, 4G, LoRa, cable) follows from range, power consumption and data volume, not fashion.
The five rules
- Change factory credentials at installation. Default passwords are public.
- Isolate devices on a separate network (VLAN or guest network), so a compromised sensor cannot reach your computers and data.
- Keep an inventory: model, location, version, owner. You cannot protect what you do not know.
- Apply manufacturer updates, and prefer vendors that still publish them.
- Disable what you do not need (remote access, open ports) and watch for abnormal traffic.
Think about the life cycle
Plan from the start who replaces batteries, who receives failure alerts and what happens when a device is retired: its access and data must be wiped before it is thrown away or resold.
Choosing connectivity
- Wi-Fi: simple inside a building, but power-hungry and short range.
- 4G or 5G: for mobile or remote devices, with a subscription per device.
- LoRa: long range and very low power for sensors sending little data, such as in a field or large site.
- Cable: the most reliable for fixed critical equipment.
These rules are general security good practice. Auditing a real deployment depends on its architecture.
Frequently asked questions
How many sensors for a first project?
Start with a pilot of a few sensors on one specific use case, measure the gain, then extend.
How do I power remote sensors?
Long-life batteries or a small solar panel, depending on consumption and measurement frequency.
Are connected devices a security risk?
Yes if they keep factory credentials, stay unpatched or share the company network.
What happens if the connection drops?
Design the device to store measurements locally and send them when the network returns.
