IoT Device Security: The NIST and ETSI Baselines You Should Meet
IoT devices often become an entry point for attacks because of default passwords and firmware that is never updated. NIST IR 8259 and ETSI EN 303 645 provide minimum standards.
Agricultural sensors, cameras, industrial gateways and smart-home devices are now connected to the internet. The problem is that many devices ship with the same default password, no update mechanism, and no way to report vulnerabilities. Devices like these are easily hijacked into botnets.
The NIST baseline
NIST IR 8259 describes foundational security activities that IoT device manufacturers should carry out before and after a product is sold. Its companion, NIST IR 8259A, defines the core technical capabilities of a device, including:
- Device identification that is logically and physically unique.
- Device configuration that can only be changed by authorised parties.
- Data protection for stored and transmitted data.
- Restricted logical access to interfaces.
- Secure software updates.
- Cybersecurity state awareness — the ability to report the device's security status.
The ETSI EN 303 645 standard
The European standard ETSI EN 303 645 for consumer IoT devices contains provisions now widely used as a global reference, including:
- No universal default passwords.
- A clear vulnerability disclosure policy.
- Keep software updated for the stated support period.
- Secure storage of credentials and encrypted communication.
- Minimise the attack surface and protect personal data.
Applying this to IoT projects
- Provide unique credentials per device from production.
- Use TLS between devices, gateways and the cloud platform.
- Deliver over-the-air firmware updates that are digitally signed.
- Separate IoT networks from office networks.
- Monitor telemetry to detect unusual device behaviour.
IoT security must be designed in from the start, because fixing thousands of devices already installed in the field is far more expensive.
Sources & references
This article is a summary and interpretation by the Oemah Solution team of the sources below. Refer to the original sources for full details and context.



