Skip to content

IoT Security Concepts

2 Topics 2 Posts

Threat models, certificate management, secure boot, real attack case studies

This category can be followed from the open social web via the handle iot-security-concepts@forum.grapesiot.com

  • šŸ›”ļø Identity, secure boot and updates

    security certificates ota
    1
    0 Votes
    1 Posts
    99 Views
    A
    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. One device, one credential 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. → Certificate-based auth and device tokens Secrets live in protected storage, not source code 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: → Credential storage on the device → Device security: shrinking the attack surface Trust the code you run Secure boot stops modified firmware from executing on your hardware. → The secure boot concept 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: → Secure OTA with signed firmware → Identity, authorisation and secure updates What "passing review" looks like 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. Finish with IoT security engineering — threat modelling to incident response in one track. Post what you've hardened, your provisioning flow, or your OTA rollback story. Tag with security.
  • šŸ”’ How IoT devices get owned

    security tls firmware
    1
    0 Votes
    1 Posts
    82 Views
    A
    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. Think like an attacker first 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. → Threat modelling and security foundations The transport layer: where most devices fail open TLS with both sides proving identity. 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. → Device-side practice: TLS auth and secure boot Network posture. 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. → Network and communication security Continue with the IoT security deep track — identity, firmware and incident response. Post your device, your threat model, and where you think you're exposed. Tag with security or tls. For identity, secure boot and updates, see the companion post below.