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.
The Security of Cloud Applications
Hillel Solow, CTO and Co-founder, Protego,  7/11/2019
Where Businesses Waste Endpoint Security Budgets
Kelly Sheridan, Staff Editor, Dark Reading,  7/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-13643
PUBLISHED: 2019-07-18
Stored XSS in EspoCRM before 5.6.4 allows remote attackers to execute malicious JavaScript and inject arbitrary source code into the target pages. The attack begins by storing a new stream message containing an XSS payload. The stored payload can then be triggered by clicking a malicious link on the...
CVE-2019-13644
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.1 is vulnerable to stored XSS due to lack of filtration of user-supplied data in a budget name. The JavaScript code is contained in a transaction, and is executed on the tags/show/$tag_number$ tag summary page.
CVE-2019-13645
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.3 is vulnerable to stored XSS due to lack of filtration of user-supplied data in image file names. The JavaScript code is executed during attachments/edit/$file_id$ attachment editing.
CVE-2019-13646
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.3 is vulnerable to reflected XSS due to lack of filtration of user-supplied data in a search query.
CVE-2019-13647
PUBLISHED: 2019-07-18
Firefly III before 4.7.17.3 is vulnerable to stored XSS due to lack of filtration of user-supplied data in image file content. The JavaScript code is executed during attachments/view/$file_id$ attachment viewing.