Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Embiq Community

  1. Home
  2. Course Q&A
  3. Block 3 — IoT & Connectivity
  4. šŸ” Securing and extending connected devices

šŸ” Securing and extending connected devices

Scheduled Pinned Locked Moved Block 3 — IoT & Connectivity
securitytlsble
1 Posts 1 Posters 208 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    admin
    wrote on last edited by
    #1

    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.

    Lock it down

    Mutual TLS, done right. 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.
    → Why security matters — real attacks
    → Certificate-based auth and device tokens

    Trust the code you run. 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.
    → The secure boot concept
    → Credential storage on the device
    → Secure OTA with signed firmware

    Reach beyond MQTT

    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.
    → HTTP and REST from the device
    → WebSocket basics for local dashboards
    → Modbus RTU for industrial devices
    → BLE provisioning of WiFi credentials

    šŸ Capstone
    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.


    Post questions here and tag with security, tls or ble. For the device-to-cloud path (networking, MQTT, patterns), see the companion post above.

    1 Reply Last reply
    0

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better šŸ’—

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    Powered by NodeBB Contributors
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups