<?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[🔐 Securing and extending connected devices]]></title><description><![CDATA[<p dir="auto">A connected device without security is a loaded gun pointed at your own network — and MQTT isn't the answer to every device-side problem either. This companion post covers the two things that turn a working prototype into shippable firmware: locking it down, and reaching beyond MQTT where it fits.</p>
<h3>Lock it down</h3>
<p dir="auto"><strong>Mutual TLS, done right.</strong> Server-only TLS leaves devices talking to impostors. Both sides prove identity — the device verifies the server, the server verifies the device. Two field gotchas: actually validate the CA chain (skipping verification "temporarily" becomes permanent), and sync the clock first — certificates look invalid on a device that thinks it's 1970.<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-4-1" rel="nofollow ugc">Why security matters — real attacks</a><br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-4-3" rel="nofollow ugc">Certificate-based auth and device tokens</a></p>
<p dir="auto"><strong>Trust the code you run.</strong> Secure boot stops modified firmware from executing; signed OTA with hash verification plus automatic rollback stops a bad or malicious update from bricking the fleet. Credentials live in protected on-device storage with a provisioning flow — never as string literals in source. Assume anyone can dump your flash; design so a dump alone isn't enough.<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-4-2" rel="nofollow ugc">The secure boot concept</a><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/embedded-iot/block3/3-4-5" rel="nofollow ugc">Secure OTA with signed firmware</a></p>
<h3>Reach beyond MQTT</h3>
<p dir="auto">HTTP/REST for on-device APIs and cloud calls, WebSocket for local dashboards, Modbus RTU for industrial sensors on RS-485 that isn't going away, and BLE provisioning so users can configure WiFi credentials without hardcoding them.<br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-5-1" rel="nofollow ugc">HTTP and REST from the device</a><br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-5-2" rel="nofollow ugc">WebSocket basics for local dashboards</a><br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-5-3" rel="nofollow ugc">Modbus RTU for industrial devices</a><br />
→ <a href="https://embiq.grapesiot.com/embedded-iot/block3/3-5-4" rel="nofollow ugc">BLE provisioning of WiFi credentials</a></p>
<p dir="auto"><strong><img src="https://forum.grapesiot.com/assets/plugins/nodebb-plugin-emoji/emoji/android/1f3c1.png?v=abd5690c300" class="not-responsive emoji emoji-android emoji--checkered_flag" style="height:23px;width:auto;vertical-align:middle" title="🏁" alt="🏁" /> Capstone</strong><br />
A fully connected, secure IoT device — TLS-authenticated MQTT link to GrapesIoT, a clean topic schema, LWT-based presence detection, and offline buffering that survives a broker outage. Share your build in the lab submissions area when it's done.</p>
<hr />
<p dir="auto"><em>Post questions here and tag with security, tls or ble. For the device-to-cloud path (networking, MQTT, patterns), see the companion post above.</em></p>
]]></description><link>https://forum.grapesiot.com/topic/69/securing-and-extending-connected-devices</link><generator>RSS for Node</generator><lastBuildDate>Thu, 19 Nov 2026 12:48:09 GMT</lastBuildDate><atom:link href="https://forum.grapesiot.com/topic/69.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 03 Oct 2026 11:29:35 GMT</pubDate><ttl>60</ttl></channel></rss>