<?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[🔒 How IoT devices get owned]]></title><description><![CDATA[<p dir="auto">Insecure firmware has taken down chunks of the internet — hundreds of thousands of cameras, routers and DVRs running default credentials, herded into a botnet overnight. Similar flaws have reached into industrial plants. Your device ships into an adversarial network, so security is a set of decisions from the first line of firmware, not a feature added at the end.</p>
<h3>Think like an attacker first</h3>
<p dir="auto">Ask four questions about your own device: what is valuable here (data? compute? a foothold into the LAN?), who wants it, how do they reach it (open ports? UART header? cloud API?), and what happens if they succeed? That threat model decides everything else — a soil sensor and a door lock do not deserve the same budget, and the model tells you where the budget goes.<br />
→ <a href="https://embiq.grapesiot.com/foundation/12-iot-security-fundamentals/01-iot-threat-model-and-security-foundations" rel="nofollow ugc">Threat modelling and security foundations</a></p>
<h3>The transport layer: where most devices fail open</h3>
<p dir="auto"><strong>TLS with both sides proving identity.</strong> Server-only TLS leaves devices talking to impostors; mutual auth means the device verifies the server and 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">Device-side practice: TLS auth and secure boot</a></p>
<p dir="auto"><strong>Network posture.</strong> Close what you don't use, assume the local network is hostile, and treat every byte arriving over the air as untrusted input until validated. Most Mirai-class compromises weren't exotic crypto breaks — they were default passwords on open remote-access ports.<br />
→ <a href="https://embiq.grapesiot.com/foundation/12-iot-security-fundamentals/03-network-and-communication-security" rel="nofollow ugc">Network and communication security</a></p>
<hr />
<p dir="auto"><em>Continue with <a href="https://embiq.grapesiot.com/communication-iot/19-iot-security-fundamentals/" rel="nofollow ugc">the IoT security deep track</a> — identity, firmware and incident response. Post your device, your threat model, and where you think you're exposed. Tag with <code>security</code> or <code>tls</code>. For identity, secure boot and updates, see the companion post below.</em></p>
]]></description><link>https://forum.grapesiot.com/topic/76/how-iot-devices-get-owned</link><generator>RSS for Node</generator><lastBuildDate>Thu, 19 Nov 2026 13:02:45 GMT</lastBuildDate><atom:link href="https://forum.grapesiot.com/topic/76.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 03 Oct 2026 11:29:41 GMT</pubDate><ttl>60</ttl></channel></rss>