Endpoint

7/30/2018
10:30 AM
Louis Creager
Louis Creager
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

MUD: The Solution to Our Messy Enterprise IoT Security Problems?

The 'Manufacturer Usage Description' proposal from IETF offers a promising route for bolstering security across the industry.

While Internet of Things (IoT) devices offer plenty of impressive capabilities that improve efficiency through industrial and workplace applications, they unequivocally continue to pose major security liabilities. Many IoT devices feature little or zero built-in security measures, making them enticing targets for hackers. At the same time, many companies plan to add a large number of IoT devices to their networks, increasing the challenge of identifying which devices are actually legitimate and limiting each device to only the access it requires.

While experienced network administrators might mitigate these shortcomings with access rules tailored to each IoT device or device category, this work is painstakingly cumbersome, offers no guarantees of security, and creates more work in an area where greater efficiency is the goal. In short, enterprises could certainly benefit from fundamental IoT security improvements at the device level.

The Proposed MUD Industry Standard
The Manufacturer Usage Description (MUD) specification, proposed and described in an Internet Engineering Task Force (IETF) draft document, offers a promising route for bolstering security across the IoT industry. MUD functions by enabling IoT devices to communicate with the networks they connect with and detailing the specific access and network functionality they require.

The MUD workflow is as follows. First, when the IoT device joins a network, it sends a MUD URL to the router. The router then functions as a MUD manager and visits the specified URL to retrieve a MUD file. The MUD manager then uses the information within the MUD file to put access rules in place that are recommended by the device's manufacturer.

In this way, enterprises can simply connect their IoT devices and the access and capabilities of those devices will be automatically limited to what is appropriate. Hackers may succeed in hijacking those devices but will be unable to corrupt the MUD file accessed online from the manufacturer. If an attacker attempts to direct a device to participate in a distributed denial-of-service attack, wreak havoc in an industrial environment, or collect and transfer sensitive information to an unfamiliar destination, MUD will not allow that activity to happen. Manufacturers still will need to address vulnerabilities and update firmware going forward, but MUD drastically reduces the harm that a compromised IoT device can actually inflict.

Can the MUD URL to which the Device Points Be Corrupted?
Hackers who understand this workflow could attempt to change the MUD URL to target their own false MUD file, one that allows the access needed to perform malicious activities. As drafted, MUD offers three choices for sending the MUD URL (and allows for others to be added in the future): the DHCP option, the X.509 extension, and the LLDP extension. Of these, the DHCP option and LLDP extension potentially could allow the MUD URL to be corrupted in scenarios where the IoT device becomes compromised. The X.509 extension distinguishes itself as more secure because the MUD URL is added to an identity certificate, either by the manufacturers when the device's IDevID is created or by another party in the supply chain with the creation of the LDevID.

How the 802.1AR Standard and DICE Support MUD Security
The IEEE 802.1AR standard specifies secure device identifiers, IDevIDs or LDevIDs, that are unique and cryptographically bound to individual devices. It also provides the capability to authenticate the identity of these devices. Devices utilizing this standard most often include a Trusted Platform Module (TPM) that stores cryptographic keys. Because the X.509 extension is added to the certificate for the IDevID or LDevID and stored on the TPM, the correct MUD URL is safeguarded through this verification. The IDevID can't be changed, and so neither can the MUD URL.

However, the size, cost, and power requirements of TPMs create severe limitations, making it impossible to rely on this method for securing all IoT devices. Thankfully, the Device Identifier Composition Engine (DICE) Architecture, offered by Trusted Computing Group, is up to the task of providing security to devices with these resource limits. Using DICE, even smaller IoT devices can store cryptographic keys and use the 802.1AR standard without the need for a TPM. Thus, they can use the X.509 extension and ensure the MUD URL is secure.

Looking forward, the promising MUD standard must be finalized as a draft document, and manufacturers of IoT devices and routers must then embrace the standard. If that happens, though issues will always remain, enterprises will have all the advantages of an IoT that is significantly safer and more secure.

Related Content:

Learn from the industry's most knowledgeable CISOs and IT security experts in a setting that is conducive to interaction and conversation. Register before July 27 and save $700! Click for more info

Louis Creager is an IoT security analyst at  * zvelo* , a provider of cybersecurity solutions for web content, network traffic, and connected/IoT devices. Prior to joining zvelo, Louis held security analyst and engineering roles at Trustwave, an information security ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
12 Free, Ready-to-Use Security Tools
Steve Zurier, Freelance Writer,  10/12/2018
Most IT Security Pros Want to Change Jobs
Dark Reading Staff 10/12/2018
6 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.