Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

9/24/2013
02:42 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Why A Hardware Root Of Trust Matters For Mobile

Even with mobile device management, enterprises still lack control over devices

As the IT industry grapples with the security implications of mobile devices, some experts believe one of the most important first steps it can take is to stop getting caught up in irrelevancies.

"We are lost in a conversation of mobile versus PC or phones versus tablets or whatever else, but that's not what's important," says Steven Sprague, CEO of Wave Systems, explaining that the really important piece is, "How are we going to manage multiple tenant trusted devices, and what are the basic foundation principles for that? Then you've got to stick to your guns. I don't care if they have the slickest marketing program under the sun -- we've got to continue putting on our glasses and calling out when the emperor has no clothes."

And one of the most important duds that mobile is missing, according to Sprague, is a standards-based hardware root of trust. Together with Dave Challener, security architect for Johns Hopkins University Applied Physics Laboratory, and Dan Griffin, president of JW Secure, Sprague discussed the deficiencies of mobile device technology in a panel earlier this month at the first annual Trusted Computing Conference in Orlando, Fla. The running theme in their discussion was the enterprise relinquishment of on-device control.

"Mobile is a step backward from a couple of perspectives," says Griffin, explaining that, first and foremost, the major mobile device vendors have not baked enough security features into their operating systems or provided the kind of development platforms that encourage developers to build security into their applications.

"Finally, the carriers and the implementers of these operating systems are super-nervous about providing system-level access to the device, but you can't do antivirus or other security without system-level access," he says. "So we're just in this weird state right now where, OK, we have all this fun stuff we could do to make a PC really locked down -- you just can't do that on a mobile device."

Challener views the state of things even more dimly.

"You look at mobile devices, and you see that you don't control the network, you don't control the hardware, you can't select hardware subsystems that are in it, you don't get to control when firmware is updated, you don't get to select the OS, and the app selection in an app store is uncontrolled," he says. "Boy, if I were an IT guy, I would be panicking."

However, mobile has done one very good thing for IT security: bringing the discussion squarely back around to the importance of device security.

"A device-centric view of the network is really useful," Sprague says. "The enterprise has been trying to ignore the device because devices are complicated and messy. And so we have control in the network, and hope and prayer in the device."

But control is the key word in device security; as things stand, there's no real control on the mobile device, whether it is owned by the employee or the enterprise. Take MDM, for example.

"You don't buy mobile device control software -- you buy mobile device management software," he says.

One of the biggest impediments today is the fact that at the hardware level, the device is either controlled by the carrier or the vendor itself. This is most visibly seen in the transition from iPhone to iPad as Apple got out of its single-carrier relationship with AT&T.

"As a carrier, AT&T controlled the iPhone with absolute power. They could shut it off at will, terminate service, and change the OS," Sprague says. "The brilliant maneuver by Apple was to take control of the initial hardware root of identity of the subscriber."

Nowadays, the only way to get full use out of the iPad is through that connection with iTunes, with Apple having ultimate control over the device and the ability to shut down its functionality remotely.

"The reason why a standards-based, independent hardware root of trust is important is that it allows someone else to take control of the device before the carrier," he says. "If you look at almost every use case and application out there, this is the fundamental capability that's being requested, even if it is being requested in a language that is not as clear as that."

Unfortunately, the real difficulty is convincing carriers or vendors to loosen their grasp of control. It is an issue of leverage and one that Sprague believes only one entity exists capable of wresting control away for the betterment of the industry.

"The only way we can wrestle control back from Verizon is through a requirement placed on the environment by a player strong enough to do that," he says. "The only player -- emphasis on the word 'only' -- is the U.S. federal space."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3349
PUBLISHED: 2019-11-19
lightdm before 0.9.6 writes in .dmrc and Xauthority files using root permissions while the files are in user controlled folders. A local user can overwrite root-owned files via a symlink, which can allow possible privilege escalation.
CVE-2019-10080
PUBLISHED: 2019-11-19
The XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI ...
CVE-2019-10083
PUBLISHED: 2019-11-19
When updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.
CVE-2019-12421
PUBLISHED: 2019-11-19
When using an authentication mechanism other than PKI, when the user clicks Log Out in NiFi versions 1.0.0 to 1.9.2, NiFi invalidates the authentication token on the client side but not on the server side. This permits the user's client-side token to be used for up to 12 hours after logging out to m...
CVE-2019-19126
PUBLISHED: 2019-11-19
On the x86-64 architecture, the GNU C Library (aka glibc) before 2.31 fails to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable during program execution after a security transition, allowing local attackers to restrict the possible mapping addresses for loaded libraries and thus bypass ASLR ...