IoT Security for Business Owners: Ten Controls That Stop the Common Attacks
November 11, 2026 · 6 min read · Etzal Group Team
A mid-sized cold drinks distributor installs cameras, a few temperature sensors and a remote-access box so that the equipment supplier can service the chillers. Everything is plugged into the office switch. Two years later, the accounting server is encrypted by ransomware. The investigation finds the way in: the remote-access box, still on its factory password and reachable from the internet. Nobody had thought of it as a computer. IoT security fails less often through clever attacks than through devices that were never treated as part of the network.
Why devices are easy targets
- Default credentials. Shipped with a known username and password that nobody changes.
- Old software. Firmware is rarely updated, so published weaknesses stay open for years.
- Flat networks. A camera sits on the same network as the finance server.
- Direct exposure. Devices are made reachable from the internet for convenience.
- Shared and forgotten accounts. The installer's login still works.
- No monitoring. Nobody would notice a device behaving oddly.
- Long life. A controller may run for fifteen years, far longer than its maker supports it.
Attackers find exposed devices with automated scanning. Being small or obscure is no protection.
What can go wrong
- Operations disrupted: equipment stopped, setpoints changed, alarms silenced.
- A route into business systems, leading to data theft or ransomware.
- Privacy: camera feeds and occupancy data exposed.
- False data: decisions made on readings someone has altered.
- Your devices used to attack others, with your connection and reputation.
- Safety, where devices control physical processes.
Ten controls
1. Keep an inventory
List every connected device: what it is, where, its network address, firmware version, who supplied it, who is responsible. You cannot protect what you have not listed. Most organisations find devices they did not know about.
2. Change every default credential
Before a device goes live. Unique, strong passwords per device or per site, stored in a password manager. Remove or disable default accounts.
3. Separate the networks
Put devices on their own segments, by function: cameras, building systems, production equipment. Allow only the specific connections that are needed, such as a sensor gateway talking to its server. Office computers and guest Wi-Fi should not be able to reach devices, and devices should not reach office systems.
This single measure would have contained the incident in the opening story.
4. Do not expose devices to the internet
No port forwarding to cameras, recorders or controllers. Remote access goes through a secure gateway or virtual private network, with individual accounts and multi-factor authentication.
5. Control remote access by suppliers
- Named individual accounts, never a shared login.
- Access enabled when needed and closed afterwards, or strictly limited to the supplier's equipment.
- Logged and reviewable.
- Removed when the contract ends.
6. Keep firmware updated
- Know the current version of each device.
- Subscribe to the supplier's security notices.
- Schedule updates, tested on one device first for anything critical.
- Plan replacement for devices the maker no longer supports.
7. Encrypt and authenticate communication
Devices should talk to their servers over encrypted connections, and each device should prove its identity with its own credential or certificate. A system where any device with the shared key can send data as any other is easy to abuse.
8. Limit what each device and user can do
- Least privilege. A sensor sends readings. It does not need to receive commands.
- Role-based access on the platform: viewing, acknowledging alarms and changing setpoints are different rights.
- Confirmation and limits for commands that affect physical equipment.
9. Secure the devices physically
Gateways and controllers in locked cabinets. Unused ports disabled. A device that can be reset to factory settings by anyone walking past is not secure.
10. Watch and be ready
- Log access and configuration changes.
- Alert on devices that go offline, new devices appearing, and unusual traffic.
- Back up device configurations.
- Have a plan: who is called, how a device is isolated, how operations continue by hand.
What to demand from suppliers
Put these in the purchase requirements.
- No shared default passwords. Unique credentials or forced change at setup.
- A stated support period during which security updates are provided.
- A way to report and receive notice of vulnerabilities.
- Encrypted communication and individual device identity.
- Documentation of every network connection the device makes, and to where.
- A secure update mechanism.
- Where the cloud service stores data, and who can access it.
- Evidence: independent testing or conformity with a recognised baseline for connected device security, such as ETSI EN 303 645 for consumer devices or the IEC 62443 series for industrial systems.
- A handover: all credentials and configuration given to you at the end of installation.
A supplier who cannot answer these is telling you how the device will behave in year three.
Industrial systems need extra care
Controllers and plant networks were often designed with no security, on the assumption of isolation.
- Separate plant networks from office networks, with a controlled zone between them.
- Read-only data paths for monitoring, where possible, so the monitoring system cannot send commands.
- Change control for any modification to control logic.
- Updates planned around production, with testing.
- Safety systems kept independent.
Availability and safety come first in a plant. Security measures must be designed with the people who run the process.
A one-day review
- Walk the site and list every connected device.
- Scan the network for devices you did not list.
- Check from outside: is anything reachable from the internet?
- Test default passwords on a sample.
- Draw the network: which devices share a segment with business systems?
- List remote access routes and who holds them.
- Note firmware versions against the supplier's latest.
- Rank the findings and fix the top five within a month.
Common mistakes
- Devices on the office network.
- Port forwarding for convenience.
- Factory passwords.
- The installer's account never removed.
- A shared login for all supplier engineers.
- Firmware never updated.
- No inventory.
- Buying on price alone with no security requirements.
- Assuming the supplier secures it.
- No plan for running by hand if systems must be isolated.
We design IoT and control systems with segmented networks, device identity, controlled remote access and documented handover, as part of IoT and Control Systems. If you are not sure what is connected at your site, contact us.
Summary
Connected devices are attacked because they are left on default passwords, old firmware and flat networks, often exposed to the internet. Keep an inventory, change every default, separate device networks from business systems, remove direct exposure, control supplier access, update firmware, encrypt and authenticate, limit privileges, lock cabinets and monitor. Write security requirements into purchases, take extra care with industrial systems, and run a one-day review to find the gaps.
Frequently asked questions
Why are IoT devices a security risk?
Many are installed with default passwords, rarely updated, connected to the same network as office computers and reachable from the internet for remote support. They run for years without anyone checking them. An attacker who takes over one device can disrupt operations, spy through cameras or use it as a route into the rest of the network.
What is the single most important IoT security measure?
Separation. Put devices on their own network segment that cannot reach office systems, and do not expose them directly to the internet. Even if a device is compromised, the damage is contained. Changing default passwords and keeping firmware updated come immediately after.
Do small companies need to worry about IoT security?
Yes. Most attacks on connected devices are automated and do not select targets by size. A small company with an exposed camera recorder or controller on a default password will be found by scanners within hours. The basic controls are inexpensive and mostly a matter of setup and discipline.
Related service
WhatsApp AI Chatbot
We build, train, and run a WhatsApp AI agent that answers customers 24/7, qualifies leads, and follows up.
