💻 computer science

FIDEM: A Standard-Compliant Framework for Secure Binding of MUD Profiles to IoT Devices

This paper presents FIDEM, a standard-compliant framework that secures the binding of IoT devices to their Manufacturer Usage Description (MUD) profiles via Zero-Knowledge-Proof authentication over DHCP, eliminating the need for PKI while minimizing manufacturer involvement and demonstrating minimal overhead in real-world constrained devices.

Original authors: Alessandro Lotto, Savio Sciancalepore, Alessandro Brighente, Mauro Conti

Published 2026-05-29

📖 4 min read☕ Coffee break read

CC BY 4.0

Original authors: Alessandro Lotto, Savio Sciancalepore, Alessandro Brighente, Mauro Conti

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). ✨ This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine your home is full of smart devices: a thermostat, a security camera, a smart bulb. Each of these devices has a specific "job" and needs to talk to specific other things to do that job. For example, your security camera needs to talk to your phone and a cloud server, but it has no business talking to your smart fridge or your neighbor's Wi-Fi.

To keep things safe, there's a rulebook called MUD (Manufacturer Usage Description). Think of MUD as a "diet plan" for your devices. The manufacturer writes down exactly what the device is allowed to eat (send) and drink (receive) on the network. If a device tries to eat something off the menu, the network blocks it.

The Problem: The "Fake ID" Scam

Here is the catch: When a new device plugs into your network, it has to show the network controller its "diet plan" (the MUD file). It does this by shouting out a web address (a URL).

Currently, the system is like a bouncer at a club who only checks if the paper you handed him looks real, but doesn't check if you are the person who owns that paper.

The Flaw: A hacker can steal a real diet plan from a harmless device (like a smart lamp) and paste it onto a dangerous device (like a hacked camera).
The Result: The network thinks the dangerous camera is just a harmless lamp. It lets the camera do whatever it wants, thinking it's following the lamp's strict rules. The camera then starts attacking your network, and the network has no idea because it's looking at the wrong "ID card."

Existing solutions try to fix this by using heavy, complex digital certificates (like a massive, heavy passport), but most cheap IoT devices are too small and weak to carry that kind of weight.

The Solution: FIDEM (The "Secret Handshake")

The authors of this paper created a new system called FIDEM. Instead of using heavy passports, FIDEM uses a clever "Secret Handshake" based on math called a Zero-Knowledge Proof (ZKP).

Here is how it works, using an analogy:

The Setup: Imagine every device is born with a secret password (a key) that only it knows. The manufacturer also publishes a "lock" (a public code) that matches that password.
The Challenge: When the device connects to the network, the network controller (the bouncer) says, "Okay, show me you own that diet plan, but don't tell me the password."
The Handshake:
- The device does a quick math trick using its secret password and a random number the controller just gave it.
- It sends the result back.
- The controller does the same math trick using the "lock" (the public code) from the diet plan.
- If the results match, the controller knows: "This device definitely has the secret password that matches this specific diet plan."

The Magic: The device proved it owns the plan without ever revealing the password. Even if a hacker is watching the whole conversation, they can't steal the password or fake the handshake.

Why This is a Big Deal

The paper claims FIDEM solves three major headaches:

No Heavy Backpacks (No PKI): It doesn't require the heavy, complex digital certificate systems that slow down cheap devices. It's light and fast.
No Phone Calls to the Factory: The network controller doesn't need to call the manufacturer to ask, "Is this device real?" It can verify it all by itself using the math handshake. This makes it easy for manufacturers to adopt.
It's Standard: It works with the existing rules (DHCP) that devices already use to get an internet connection. You don't need to replace your router or your devices.

The Real-World Test

The researchers tested this on two common, low-cost chips (ESP32-S3 and ESP32-C6), which are the brains behind many cheap smart home gadgets.

Speed: It was incredibly fast. It took about 5 milliseconds (0.005 seconds) to verify the device. That's about 20 times faster than the heavy certificate method.
Battery: It used very little energy. It saved about 35% of the battery life compared to the heavy certificate method.
Safety: They proved mathematically (using a tool called ProVerif) that even if a hacker has a "super-device" that can help them cheat, they still can't break the system.

Summary

FIDEM is a lightweight, super-fast way to make sure your smart devices are actually who they say they are, and that they are following their specific safety rules. It stops hackers from swapping "ID cards" between devices, all without slowing down your network or draining your device's battery. It's like giving every device a unique, unforgeable secret handshake that proves it belongs to its specific rulebook.

Technical Summary: FIDEM Framework for Secure MUD Binding

Problem Statement
The Manufacturer Usage Description (MUD) standard (RFC 8520) allows manufacturers to define network behavior profiles for IoT devices, enabling network controllers to enforce restrictions based on expected traffic. However, a critical vulnerability exists in the Device-to-MUD Profile Binding (MUD-Binding) process. While the standard defines a secure X.509 certificate-based issuance method, current deployments predominantly rely on the insecure Dynamic Host Configuration Protocol (DHCP) extension due to its simplicity and plug-and-play nature.

In the insecure DHCP extension, a device simply advertises a URL pointing to its MUD profile. The network controller retrieves the file and enforces policies based on the file's authenticity, not the requesting device's entitlement. This decoupling allows malicious or compromised devices to advertise valid URLs referencing genuine MUD profiles intended for other devices. Consequently, attackers can induce the enforcement of incorrect, overly permissive network policies, facilitating lateral movement and privilege escalation. Existing solutions to secure this binding often fail to meet practical constraints: they rely on Public Key Infrastructure (PKI) which is rarely supported in constrained IoT devices, require excessive active involvement from manufacturers during runtime, break standard compliance, or lack mechanisms for secure profile updates.

Methodology: The FIDEM Framework
To address these gaps, the authors propose FIDEM, a standard-compliant framework that secures DHCP-based MUD URL issuance without relying on PKI or active manufacturer involvement during verification.

Threat Model: FIDEM operates under a stronger, realistic threat model than prior work. It assumes devices may be compromised at any lifecycle stage (including supply chain compromise) and considers adversaries who can use legitimate devices as cryptographic oracles to perform operations on behalf of compromised devices.
MUD Management Model (MMM): To ensure scalability, FIDEM introduces a class-based management model. Instead of assigning unique profiles to every individual device, manufacturers group devices with identical network requirements into "MUD Classes." Each class is associated with a single MUD profile and a shared secret key ( $K_c$ ). This reduces the management overhead for manufacturers and the storage requirements for devices.
Cryptographic Binding via Zero-Knowledge Proofs (ZKP):
- Key Management: Each MUD Class $C$ has a secret key $K_c$ stored in the device's secure hardware and a corresponding public point $X_c = K_c \cdot G$ on an Elliptic Curve. The MUD file is extended to include these public parameters ( $X_c$ , curve parameters, etc.).
- Verification Protocol: During the DHCP handshake, the device proves possession of $K_c$ $K_{c}$ without revealing it. The protocol uses a Schnorr-based interactive ZKP:
  - The device sends a commitment $R = r \cdot G$ (where $r$ is a random nonce) along with the MUD URL.
  - The Controller issues a random challenge $C$ .
  - The device computes a response $Z = r + H \cdot K_c$ , where $H$ is a hash of the commitment, public key, challenge, and URL.
  - The Controller verifies the equality $Z \cdot G \stackrel{?}{=} R + H \cdot X_c$ .
- Embedding: To maintain backward compatibility with the standard, the ZKP parameters (commitment $R$ ) are embedded into the reserved field of the DHCP option 161 (MUDstring) or a separate DHCP option if space is insufficient.
Secure Updates: FIDEM supports secure profile updates via a publish-subscribe model. The Controller periodically checks MUD file signatures. If a device reboots with a new URL, the Controller verifies that the new profile belongs to the same manufacturer, preventing cross-manufacturer impersonation.

Key Contributions

Formal Threat Model: The paper formalizes a threat model that explicitly accounts for supply chain compromises and adversaries using legitimate devices as cryptographic oracles, a scenario often overlooked in prior literature.
Standard-Compliant Framework: FIDEM is the first solution to secure the DHCP-based MUD URL issuance while remaining fully compliant with RFC 8520, avoiding the need for non-standard extensions or PKI.
Lightweight ZKP Authentication: By leveraging Schnorr-based ZKP, FIDEM eliminates the need for PKI and minimizes manufacturer involvement to the initial provisioning of class keys and file hosting.
MUD Management Model (MMM): The introduction of a class-based model for profile association enables scalable key management and lifecycle support.
Real-World Implementation: The authors implemented FIDEM on commercial constrained devices (ESP32-S3 and ESP32-C6) and released the source code.

Experimental Results
The authors evaluated FIDEM against standard DHCP, X.509 over HTTP, and X.509 over TLS using ESP32-S3 and ESP32-C6 devices.

Performance: FIDEM introduces minimal overhead compared to the insecure standard DHCP. On the ESP32-S3, the median verification time was 9.06ms (approx. 30% slower than standard DHCP's 6.99ms). On the ESP32-C6 (with hardware TEE), the overhead was reduced to approximately 7% (5ms).
Comparison to PKI: FIDEM significantly outperforms certificate-based approaches. It is approximately 20 times faster than X.509 over TLS and consumes ~35% less energy.
Energy Efficiency: The energy consumption for FIDEM on the ESP32-S3 was 385mJ, a negligible increase (~8%) over standard DHCP (354mJ) and significantly lower than X.509 over TLS (574mJ).

Significance and Claims
The paper claims that FIDEM successfully bridges the gap between security and deployability in IoT networks. By securing the widely used DHCP extension without requiring complex PKI infrastructure or active manufacturer runtime support, FIDEM makes secure MUD adoption feasible for resource-constrained environments. The framework withstands stronger adversaries than previous works, including those capable of exploiting legitimate devices as oracles, while maintaining standard compliance and supporting secure profile updates. The authors conclude that FIDEM offers a practical, low-overhead solution to the MUD-Binding vulnerability, enabling the enforcement of correct network policies without compromising the operational efficiency of IoT devices.