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.

Vulnerabilities / Threats

4/20/2015
07:20 PM
Connect Directly
Google+
Twitter
RSS
E-Mail

White House's Daniel 'Intrigued' By UL-Type Model For IoT Security

Michael Daniel, the national cybersecurity coordinator and assistant to the President, talks Internet of Things security and recent Executive Orders on intel-sharing and sanctions.

Image Source: RSA Conference
Image Source: RSA Conference

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Some Guy
100%
0%
Some Guy,
User Rank: Moderator
4/21/2015 | 10:21:46 AM
Simplistic & Shows Ignorance of How UL Works
Way too simplistic! UL is built on 100+ years of experience in a fairly static environment that changes on decade timescales. Can you imagine taking years to respond to a new attack? And even if you gave a device a cyber-UL sticker today, howwould it be protected from future, emerging, new threats? There is a nugget underneath it all that is key -- UL is really driven by the insurance industry. If you install a non-UL device and there is a fire, the insurance company does not have to pay.

To be effective two things will have to happen for IoT cyber-security. First, we need IoT security to be driven as a first-order requirement. It can't be an afterthought in the current IoT gold-rush just to get products working and to market, regardless of the security. Perhaps insurance is the economic vehicle to drive that; strict product liability and lawsuits certainly can be the way, but that takes too long. Legislation to require minimum security features such as immutable HW ID, secure boot, signed code, and application whitelisting would be a great step forward. It's incumbent on all of us in our practices and purchases to insist that IoT have security from the outset and not added 30 years after the fact like the Internet.

Second, cyber-criminals are going to have to be hunted to extinction in the real world, not cyber-space -- think Pinkertons  and what it took to end train robberies in the 19th century (e.g., vs. Butch Cassidy, the Sundance Kid and the Hole-in-the-Wall Gang). Like Yakov Smirnov used to say about old Soviet Russian warning shots: they shoot you and that's warning for the next guy.
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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-2019-19642
PUBLISHED: 2019-12-08
On SuperMicro X8STi-F motherboards with IPMI firmware 2.06 and BIOS 02.68, the Virtual Media feature allows OS Command Injection by authenticated attackers who can send HTTP requests to the IPMI IP address. This requires a POST to /rpc/setvmdrive.asp with shell metacharacters in ShareHost or ShareNa...
CVE-2019-19637
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is an integer overflow in the function sixel_decode_raw_impl at fromsixel.c.
CVE-2019-19638
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer overflow in the function load_pnm at frompnm.c, due to an integer overflow.
CVE-2019-19635
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer overflow in the function sixel_decode_raw_impl at fromsixel.c.
CVE-2019-19636
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is an integer overflow in the function sixel_encode_body at tosixel.c.