IoT security is the set of technologies, practices and controls used to protect Internet of Things devices, networks, data, applications and associated services from unauthorised access, misuse, disruption, manipulation and compromise. IoT security applies to connected devices ranging from smart home equipment and cameras to industrial sensors and medical or automotive systems. Because IoT environments combine physical devices, embedded software, communications and cloud services, security must cover the complete system rather than focusing only on the device itself. Weak security in one component can affect other components if the device has network access or trusted credentials.
IoT devices often have constrained processors, memory and battery capacity, which can make conventional security mechanisms more difficult to implement. Some devices also remain deployed for many years, sometimes longer than their software-support periods. Secure design can include hardware-backed key storage, secure boot, signed firmware, encrypted communications, strong device identity, access control and mechanisms for secure updates. Security should ideally be considered during product design rather than added after deployment. A device with insufficient processing capacity for modern cryptographic or update mechanisms can be difficult to secure effectively once it is already deployed.
Device identity is a fundamental IoT security concern. Systems need to distinguish one device from another and determine which devices are authorised to communicate or perform particular actions. Shared default passwords are particularly problematic because a compromise of one device can expose many others if credentials are identical. Strong device-specific credentials, certificates, cryptographic keys or hardware-backed identities can establish stronger authentication. Authorisation should then determine what an authenticated device or user is permitted to do. Authentication answers who or what is connecting, while authorisation determines which operations that entity may perform.
Secure communications protect information while it travels between devices, gateways, applications and cloud services. Encryption protocols such as TLS can protect network communications against interception or modification when implemented correctly. However, encryption alone does not establish that the communicating device is legitimate or authorised. Certificate validation, key management, endpoint authentication and secure protocol configuration are also important. IoT systems may use a variety of communication technologies, including Wi-Fi, cellular networks, Bluetooth, Zigbee, Thread, Ethernet and specialised industrial protocols, each with different security characteristics and deployment considerations.
Firmware security is particularly important because embedded software controls device behaviour. Secure boot can help ensure that only authorised software is executed, while signed firmware can allow a device to verify that an update originated from a trusted source and has not been modified. Vulnerability management requires a way to identify affected device models and distribute fixes. If a manufacturer provides no secure update mechanism, vulnerabilities can remain permanently exposed. Organisations purchasing IoT equipment should therefore consider software-support policies, update mechanisms and expected device lifespan as part of procurement rather than treating hardware specifications as the only important criteria.
Network architecture can reduce the consequences of a compromised IoT device. Network segmentation can isolate devices from sensitive systems and restrict unnecessary communication. Firewalls, access-control lists and zero-trust principles can further limit what a device can reach. For example, a smart sensor that only needs to communicate with a particular gateway should not necessarily have unrestricted access to internal servers. Monitoring can identify unusual traffic, repeated authentication failures or communication with unexpected destinations. These controls provide defence in depth because a vulnerability in an individual device does not automatically grant unrestricted access to the entire network.
Physical security is also relevant because IoT devices are often deployed in locations accessible to users, customers, contractors or the public. An attacker with physical access may attempt to extract storage, manipulate interfaces, reset a device or interfere with sensors. The appropriate protections depend on the threat model. Tamper resistance, secure enclosures, disabled debug interfaces, encrypted storage and secure hardware can reduce some risks. Physical compromise may be particularly significant for devices deployed outdoors, in vehicles, industrial facilities or other locations where defenders cannot continuously control physical access.
IoT security is therefore a lifecycle discipline covering design, procurement, deployment, configuration, operation, monitoring, patching and retirement. Common security failures include default credentials, unnecessary services, insecure communications, unsupported firmware, excessive network privileges and inadequate logging. Security also needs to account for the broader ecosystem because a device may depend on a mobile application, gateway, cloud service and vendor account. When an IoT device reaches end of life, organisations should have a process for securely removing credentials, deleting stored information and decommissioning associated cloud resources.
