Manufacturer Usage Description (MUD) is an IETF Standards Track mechanism, defined in RFC 8520, that lets a single-purpose network device — an IoT sensor, a camera, an industrial controller — tell the network what access it actually needs, so the network can restrict it to exactly that and nothing more. Published in March 2019 as a Proposed Standard by Eliot Lear (Cisco Systems), Ralph Droms (Google) and Dan Romascanu, its Abstract states the goal plainly: "to provide a means for end devices to signal to the network what sort of access and network functionality they require to properly function." MUD replaces the manual, per-device firewall rule-writing that most networks either skip entirely or get wrong, with a manufacturer-authored, machine-readable policy that any compliant network can fetch and enforce.
Key takeaways
- RFC 8520 is explicit about the class of device it targets: not laptops or phones, but "Things" — devices built to do one job, whose legitimate network behavior is therefore narrow and predictable by design.
- Whichever path carries it, the MUD URL must use the https scheme and points to a MUD file (registered IANA media type application/mud+json).
- The example in Section 9 describes "The BMS Example Light Bulb" with cache-validity set to 48 hours and two IPv6 access lists that allow only outbound TCP 443 to a single cloud hostname.
- MUD rules can name hosts by DNS name, but their real strength is classes that the local network fills in, so a maker can write policy without knowing any customer's addressing.
Why does MUD exist for "Things," not general-purpose computers?
RFC 8520 is explicit about the class of device it targets: not laptops or phones, but "Things" — devices built to do one job, whose legitimate network behavior is therefore narrow and predictable by design. A smart light bulb has no business reason to talk to an arbitrary IP address on the internet; a building-access controller has no reason to accept inbound connections from the guest Wi-Fi. MUD gives the manufacturer of such a device a standard way to say so, up front, rather than leaving every network operator to guess or every device to run wide open by default. A device's actual network behavior is often undocumented until someone watches it, which is why passive traffic analysis (see OT Snapshot) and declared-intent mechanisms like MUD are complementary: one records what a device did, the other states what it should do.
How does the MUD URL reach the network?
A device signals where to find its policy by emitting a MUD URL through one of three mechanisms RFC 8520 defines:
| Mechanism | How it carries the MUD URL |
|---|---|
| DHCP | A DHCPv4 option (161, OPTION_MUD_URL_V4 in the IANA DHCP registry) or DHCPv6 option (112, OPTION_MUD_URL_V6), sent during normal address configuration |
| X.509 certificate | A non-critical certificate extension, id-pe-mud-url (OID 1.3.6.1.5.5.7.1.25), typically embedded in an IEEE 802.1AR manufacturer-installed certificate |
| LLDP | A vendor-specific TLV frame, using IANA's Organizationally Unique Identifier registry, for devices on a wired LAN that use Link Layer Discovery Protocol |
Whichever path carries it, the MUD URL must use the https scheme and points to a MUD file (registered IANA media type application/mud+json). The certificate route ties the URL to the device's identity (see our IEEE 802.1AR DevID guide), but a URL inside a factory certificate cannot change with firmware; DHCP and LLDP can carry a versioned URL such as the RFC's own example https://things.example.org/product_abc123/v5.
What is inside a MUD file?
A MUD file is a YANG model instance serialized as JSON, in two parts: an ietf-mud:mud container that describes the device and names its policies, and an ietf-access-control-list:acls block, using the ACL model from RFC 8519, that holds the rules. The device fields, per Section 3 of RFC 8520:
| Field | What it says |
|---|---|
mud-version, mud-url |
Format version (1) and the file's own URL |
last-update |
When the file was generated; the RFC calls it "akin to a version number" |
mud-signature |
Where the detached signature file lives |
cache-validity |
Hours a MUD manager waits before checking for an update: recommended no less than 24, never more than 168 for a supported Thing |
is-supported |
false when the maker intends never to issue another firmware or software update, or never to update the MUD file |
systeminfo |
Short description for administrators, no more than 60 characters of display space |
mfg-name, model-name, firmware-rev, software-rev |
Optional identity fields; the two revision fields must stay empty if the device can be upgraded but its MUD URL cannot |
documentation |
Link to documentation for the device and its MUD file |
extensions |
Names of the MUD extensions the file uses; undeclared extensions must not appear |
from-device-policy, to-device-policy |
References to the access lists for each direction of traffic |
The example in Section 9 describes "The BMS Example Light Bulb" with cache-validity set to 48 hours and two IPv6 access lists that allow only outbound TCP 443 to a single cloud hostname. The is-supported flag deserves attention: it is an end-of-support signal every MUD manager can read, so setting it to false when updates stop tells operators the device is now their risk to carry.
Which abstractions can a MUD policy use?
MUD rules can name hosts by DNS name, but their real strength is classes that the local network fills in, so a maker can write policy without knowing any customer's addressing. Section 4 of RFC 8520 adds these match types to the ACL model:
| Class | What it expands to |
|---|---|
manufacturer |
Devices whose MUD URL has a given authority (hostname) |
same-manufacturer |
Devices whose MUD URL authority matches this device's |
model |
Devices with exactly the same MUD URL |
local-networks |
Local networks; by default, traffic that does not head toward the default route |
controller |
Hosts registered locally for a named class, or a well-known service URN such as DNS or NTP |
my-controller |
Hosts the administrator registers as controllers for this specific model |
direction-initiated |
Which side may open a TCP connection: from-device or to-device |
direction-initiated matters more than it looks. It lets a profile say "the device may call the cloud on port 443" without also letting anyone on the internet open a connection to the device on that port.
What does the MUD manager do, step by step?
The MUD manager (RFC 8520 also notes "MUD controller" as a legacy synonym for the same role) is the network-side component that retrieves a device's MUD file, validates it, and converts the manufacturer's recommended policy into real network controls — typically access-control lists scoped to that device. The split of responsibility is the point: the manufacturer authors what "normal" looks like for its own product, once; the network operator's MUD manager enforces it, continuously, without out-of-band knowledge of what the device is supposed to do. Section 1.9 gives one intended order of operations:
- The Thing emits its MUD URL.
- The nearest switch forwards the URL to the MUD manager.
- The manager retrieves the MUD file and its signature (unless it has copies), validates the signature, and may check the URL and the hosts in the file against reputation services.
- The manager may ask the administrator to approve the Thing and its policy; it may skip this for known Things or Thing types.
- It turns the abstractions into local configuration.
- It configures the switch nearest the Thing, and possibly other systems.
- When the Thing disconnects, the policy is removed.
The RFC says a MUD manager may be a component of an AAA system or a network management system, and leaves communication within those systems out of scope, so how a given switch vendor carries out step 6 is product-specific.
How is a MUD file signed and checked?
A MUD file "MUST be signed using CMS as an opaque binary object" (Section 13.1). The signature is served as application/pkcs7-signature from the location in mud-signature, and the RFC shows an openssl cms -sign command that produces a .p7s file. Before processing anything else, the MUD manager must fetch that signature and validate it. The signing certificate needs the digitalSignature key-usage bit, and when the device certificate carries an id-pe-mudsigner extension, the signer's subject must match it. If a check fails or the chain does not reach a known trust anchor, the manager "MUST cease processing the MUD file until an administrator has given approval."
For makers. The RFC says the signature exists "to assign accountability" for the recommendation; the signer does not have to be the manufacturer, and integrators may use their own certificates. It also warns that a file "may need to be re-signed if the signature expires", so put the signing certificate's expiry on the same calendar as the product's support period.
What does RFC 8520 itself warn about (Section 16)?
The specification is unusually direct about its own limits:
- Spoofing the manufacturer claim: "Things claiming to be of a certain manufacturer SHOULD NOT be included in that manufacturer grouping without additional validation of some form."
- Certificate/domain trust drift: "MUD managers SHOULD cache certificates used by the MUD file server. When a new certificate is retrieved for whatever reason, the MUD manager should check to see if ownership of the domain has changed."
- Rogue CA risk: a certificate authority could sign a certificate "that contains the same subject name as is listed in the MUDsigner field in the manufacturer certificate, thus seemingly permitting a substitute MUD file for a device."
- Weak identity binding: "Implementations SHOULD NOT grant elevated permissions... to devices that do not strongly bind their identity to their L2/L3 transmissions."
The throughline across all four: MUD constrains a device to its declared profile — it does not, on its own, prove the device presenting a given MUD URL is the genuine article. A device maker relying on MUD as a security control still needs a real identity mechanism (such as the 802.1AR certificate the URL can ride inside) behind it.
Where is MUD used and referenced today?
- NIST NCCoE build. NIST SP 1800-15 (May 2021) demonstrated that when an IoT device joins a home or small-business network, MUD "can automatically permit the device to send and receive only the traffic it requires to perform its intended function." Its authors come from NIST, CableLabs, Cisco, DigiCert, ForeScout, MITRE and others.
- OT segmentation guidance. NIST SP 800-82 Rev. 3 lists SP 1800-15 as supplemental guidance in §6.2.1.3, Network Segmentation and Isolation, next to firewall and zero trust guidance; see our SP 800-82 guide.
- Extensions. RFC 9761 (April 2025, Standards Track) lets manufacturers add TLS and DTLS profile parameters, so a network security service can "identify unexpected (D)TLS usage."
- Tooling. MUD Maker is a public web tool for building MUD files; it advises starting from the UDP and TCP ports a device will use.
Worked example: what would a MUD profile for a gateway look like?
Synthetic example: "GW-200", its maker and every hostname below are invented; .example domains are reserved for documentation. GW-200 is a cellular gateway that polls energy meters over Modbus TCP on a plant floor and forwards readings to the maker's cloud over MQTT with TLS.
| Flow the device needs | Direction initiated | MUD match |
|---|---|---|
Publish telemetry to telemetry.gw.example, TCP 8883 |
from-device | DNS name |
Check for firmware at updates.gw.example, TCP 443 |
from-device | DNS name |
| Poll meters, Modbus TCP 502 | from-device | local-networks |
| Accept configuration from the site engineering station | to-device | my-controller |
| Time and name resolution | from-device | controller URNs for NTP and DNS |
Steps the maker takes:
List intended flows from the design, then confirm them by capturing the gateway's traffic in a lab and comparing the two lists. Build the filewith cache-validity48,is-supportedtrue, a shortsysteminfo, and adocumentationpage that tells operators what to register asmy-controller.Leave `firmware-rev` emptyif the MUD URL ships in an 802.1AR certificate that firmware updates cannot change. Sign and publishthe file and its .p7sunder an HTTPS URL that will outlive the product, and emit the URL by DHCP option 161 or 112.Re-issue on changeWhen a release adds a flow, such as a remote-diagnostics endpoint, publish an updated file with a new last-updatebefore the release ships, or enforcing networks will block the new feature.
In a plant that follows IEC 62443-3-2, the same flow table is useful input when the integrator defines the conduit between the meter zone and the external network, whether or not the site runs a MUD manager.
Why does this matter for device and firmware makers?
For a manufacturer, publishing a MUD file is a concrete, low-cost way to document — in a machine-readable, standardized format — exactly what a device is supposed to do on a network, which doubles as evidence for a secure-development narrative alongside a firmware SBOM: an SBOM says what's inside the image, a MUD file says what the image is allowed to do once it's running. No regulation known to us at the time of writing names MUD as a required control for any device class; where it is useful is as an optional, standards-based way to narrow a device's attack surface and to give downstream buyers (and assessors) a precise, manufacturer-authored baseline to check observed behavior against. Confirm any specific regulatory or buyer-specific mapping before relying on it; this guide makes no such claim.
What are the common pitfalls?
- Profile drift. A firmware release adds a cloud endpoint but the MUD file stays the same, so the feature fails on enforcing networks, or an operator loosens the policy by hand.
- Rules that are too broad. Allowing any destination on port 443 defeats the purpose; name hosts or use classes.
- No direction on TCP rules. Leaving out
direction-initiatedcan permit inbound connections the maker never intended. - Short-lived hosting. A MUD URL on a campaign domain that later lapses leaves fielded devices without a policy, and a new domain owner could serve a different file.
- Treating MUD as identity. MUD narrows traffic; it does not prove a device is genuine.
- Silent end of support. Set
is-supportedtofalsewhen updates stop, so operators can plan.
SoftWSP does not generate, read or enforce MUD files. Its OT Snapshot works from Zeek logs of a site's own traffic capture and lists, for each host, the ports and services it was seen serving, which ICS protocols it speaks, and any interactive remote-access sessions crossing the network boundary, so an engineer can hold that list against a device's MUD profile by hand. For the firmware itself, Device & Firmware Security extracts an SBOM as CycloneDX JSON, matches its components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report for engineer review.
This guide summarises the public IETF RFC 8520 specification; it does not constitute legal or compliance advice.
Put this guide to work
Frequently asked questions
What is MUD (Manufacturer Usage Description)?
MUD is an IETF Standards Track specification, RFC 8520, authored by Eliot Lear (Cisco Systems), Ralph Droms (Google) and Dan Romascanu, published in March 2019 as a Proposed Standard. Its own Abstract states the goal directly: "to provide a means for end devices to signal to the network what sort of access and network functionality they require to properly function." RFC 8520 targets single-purpose network endpoints — the specification calls them "Things" rather than general-purpose computers — so a network can automatically restrict a device's traffic to only the access its own manufacturer says it needs, instead of relying on a human to hand-write a firewall rule.
How does a device emit its MUD URL, and what is in the MUD file?
RFC 8520 defines three carrier mechanisms for the MUD URL: DHCP options (DHCPv4 option 161 or DHCPv6 option 112, registered with IANA in Section 17), a non-critical X.509 certificate extension (id-pe-mud-url, OID 1.3.6.1.5.5.7.1.25), typically carried in an IEEE 802.1AR manufacturer certificate, and a vendor-specific LLDP TLV. Whichever mechanism carries it, the MUD URL points to a **MUD file**: a YANG-modeled JSON document (media type application/mud+json, also IANA-registered) describing the device and the access-control policy the manufacturer recommends for it — for example, which specific domains or local services the device is allowed to talk to.
What does a MUD manager (controller) do with that information?
The network-side component — called a MUD manager, with "MUD controller" used as a legacy synonym for the same role — retrieves the MUD file from the URL the device emitted, validates it, and translates its recommended policy into actual network configuration (such as access-control lists) for that device. The device's manufacturer, not the network operator, authors the baseline policy; the network operator's MUD manager is what enforces it, which is the core of MUD's value: a small IoT vendor can ship a usage profile without that vendor needing to run or manage any network infrastructure itself.
What are MUD's biggest security caveats, per RFC 8520 Section 16?
The specification itself names several caveats directly. On spoofing: "Things claiming to be of a certain manufacturer SHOULD NOT be included in that manufacturer grouping without additional validation of some form." On certificate trust: "MUD managers SHOULD cache certificates used by the MUD file server. When a new certificate is retrieved for whatever reason, the MUD manager should check to see if ownership of the domain has changed," and the RFC separately flags the risk that "a rogue certification authority (CA) may sign a certificate that contains the same subject name as is listed in the MUDsigner field." On device identity: "Implementations SHOULD NOT grant elevated permissions... to devices that do not strongly bind their identity to their L2/L3 transmissions." In short, MUD only restricts a device to its declared profile — it does not, by itself, prove the device presenting a given MUD URL is authentic.
Sources
- IETF RFC 8520: Manufacturer Usage Description Specification (Lear, Droms, Romascanu), March 2019
- RFC Editor: Status information for RFC 8520
- IANA: Internet Assigned Numbers Authority — official site
- IETF RFC 8519: YANG Data Model for Network Access Control Lists (ACLs), March 2019
- IETF RFC 9761: Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for IoT Devices, April 2025
- IANA: BOOTP and DHCP parameters (option 161, OPTION_MUD_URL_V4)
- IANA: DHCPv6 parameters (option 112, OPTION_MUD_URL_V6)
- IANA: media type application/mud+json
- NIST SP 1800-15: Securing Small-Business and Home IoT Devices: Mitigating Network-Based Attacks Using MUD (May 2021)
- NIST SP 800-82 Rev. 3: Guide to Operational Technology (OT) Security, §6.2.1.3 (PDF, September 2023)
- MUD Maker: a tool to build MUD files
About this guide
SoftWSP Firmware Security Desk
Covers the Firmware vulnerabilities & fixes cluster: 131 guides.

In this cluster
Questions about this page?
