<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[🛡️ Identity, secure boot and updates]]></title><description><![CDATA[<p dir="auto">Knowing your threat model is half the job. This companion post is the other half: the concrete mechanisms that keep a deployed fleet trustworthy for years — identity, storage, boot integrity, and updates that can't brick everything at once.</p>
<h3>One device, one credential</h3>
<p dir="auto">Fleet-wide passwords and hardcoded API keys are a supply-chain vulnerability — one leak compromises every unit ever shipped. Each device gets unique credentials issued at provisioning, with expiry and rotation planned from day one. Certificates beat passwords where the hardware allows it: a client certificate in protected storage is harder to phish, share, or guess than any string a human invents.<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-4-3" rel="nofollow ugc">Certificate-based auth and device tokens</a></p>
<h3>Secrets live in protected storage, not source code</h3>
<p dir="auto">On-device credentials belong in NVS with proper access control plus a provisioning flow — never as string literals in firmware. Assume anyone can dump your flash; design so a dump alone isn't enough. Work through what happens when a unit is returned, resold, or stolen: wipe procedures and revocation lists are part of the design, not an afterthought. The general principle — shrink what the device exposes — applies far beyond storage:<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-4-4" rel="nofollow ugc">Credential storage on the device</a><br />
→ <a href="https://embiq.grapesiot.com/foundation/12-iot-security-fundamentals/02-device-security" rel="nofollow ugc">Device security: shrinking the attack surface</a></p>
<h3>Trust the code you run</h3>
<p dir="auto">Secure boot stops modified firmware from executing on your hardware.<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-4-2" rel="nofollow ugc">The secure boot concept</a><br />
Signed OTA with hash verification stops tampered images from installing. Automatic rollback on failure stops one bad release from becoming a fleet-wide outage — an update path without rollback is a disaster waiting for a trigger. The full identity-to-update story, end to end:<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-4-5" rel="nofollow ugc">Secure OTA with signed firmware</a><br />
→ <a href="https://embiq.grapesiot.com/foundation/12-iot-security-fundamentals/04-identity-authorization-and-secure-updates" rel="nofollow ugc">Identity, authorisation and secure updates</a></p>
<h3>What "passing review" looks like</h3>
<p dir="auto">Unique per-device credentials (never hardcoded), TLS with proper certificate validation and clock sync, secure boot plus signed OTA with rollback, and a tested incident routine. That's the bar that separates professional firmware from hobbyist firmware.</p>
<hr />
<p dir="auto"><em>Finish with <a href="https://embiq.grapesiot.com/bonus/53-iot-security-engineering/" rel="nofollow ugc">IoT security engineering</a> — threat modelling to incident response in one track. Post what you've hardened, your provisioning flow, or your OTA rollback story. Tag with <code>security</code>.</em></p>
]]></description><link>https://forum.grapesiot.com/topic/77/identity-secure-boot-and-updates</link><generator>RSS for Node</generator><lastBuildDate>Thu, 19 Nov 2026 13:02:46 GMT</lastBuildDate><atom:link href="https://forum.grapesiot.com/topic/77.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 03 Oct 2026 11:29:42 GMT</pubDate><ttl>60</ttl></channel></rss>