IoT Security by Design: Device Identity, Encryption and Updates

Security for a connected product is no longer a matter of judgement alone. Published baselines describe what a reasonable product does, regulators in several markets now require parts of them, and retailers and enterprise buyers ask about them. Details differ by region, but the common core is consistent: every device has its own identity, everything it sends is encrypted and authenticated, and it receives security updates for a stated period.

At a glance

13
Provision categories in ETSI EN 303 645, the European consumer IoT baseline.
No defaults
Universal default passwords are banned under the UK PSTI product security regime.
mTLS
Mutual TLS, where device and server each present a certificate, is the usual device-to-cloud pattern.
Support
Baselines expect a stated minimum period during which security updates are provided.

The problem

Many weaknesses in connected products are architectural rather than coding errors: a password shared by every unit, a service that trusts any device on the right network, or a product with no way to be patched. None is a quick fix after launch.

Requirements are also moving. The UK product security regime has applied since April 2024, the EU Cyber Resilience Act phases in obligations to December 2027, and the US has a voluntary Cyber Trust Mark for consumer devices. Products designed today will be sold under rules still being finalised.

Security designed into identity, transport and updates costs little. Security added after launch rarely works.

The three foundations

Identity means each device holds a unique credential, ideally a private key that cannot be read out, and the cloud can revoke one device without touching the rest. Encryption means TLS 1.2 or 1.3 for TCP links and DTLS for UDP, with server certificates validated properly and no fallback to plain text.

Updates mean signed firmware, delivery that reaches the whole fleet, and a published policy stating how long the product will receive fixes. ETSI EN 303 645 and the UK regime also require a way for researchers to report vulnerabilities.

What good looks like

Pick the baselines that apply to your markets and map each provision to a design decision, an owner and a piece of evidence.

Design identity, transport security and update signing together, since they share keys, certificates and a root of trust.

Publish the support period and disclosure policy before launch, and set up the internal process to triage reports and ship fixes.

Security baselines and where they apply
BaselineScopeStatus
ETSI EN 303 645Consumer IoT, European standardWidely referenced; basis for several schemes
UK PSTI product security regimeConsumer connectable products sold in the UKMandatory since April 2024
EU RED delegated actInternet-connected radio equipment sold in the EUApplies since August 2025; supported by EN 18031
EU Cyber Resilience ActProducts with digital elements sold in the EUObligations phase in to December 2027
NIST IR 8259ACore device cybersecurity capabilitiesUS guidance used by federal and labelling schemes
US Cyber Trust MarkConsumer wireless IoT productsVoluntary FCC labelling programme
Summary only. Check the current text and status of each for your product and market.
Shared secret and per-device identity
Shared secretPer-device certificate
Effect of one leakWhole fleet exposedOne device exposed
RevocationRotate every deviceRevoke one certificate
Factory processTrivialNeeds a signing step
Fits current baselinesGenerally notYes
Why every baseline pushes towards unique credentials.

What it changes

Market Access

Products meet the baselines buyers and regulators now ask about.

Contained Risk

One compromised device does not expose the fleet or its cloud service.

Patchability

Vulnerabilities found after launch can be fixed for the stated support period.

Evidence

Each requirement maps to a design decision that can be shown to an assessor.

Where to go next

Device-level protections such as secure boot, debug port locking and key storage sit beneath this architecture and need the same early attention.

Threat-model the whole system, including the app and cloud APIs. The easiest route for an attacker is often not the device at all.

Problems this prevents

  • Default passwords shared across units
  • Links that fall back to plain text
  • No route for researchers to report flaws
  • An unstated or unrealistic support period

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.