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.

Comments
White House's Daniel 'Intrigued' By UL-Type Model For IoT Security
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.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/14/2020
Omdia Research Launches Page on Dark Reading
Tim Wilson, Editor in Chief, Dark Reading 7/9/2020
Russian Cyber Gang 'Cosmic Lynx' Focuses on Email Fraud
Kelly Sheridan, Staff Editor, Dark Reading,  7/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-6287
PUBLISHED: 2020-07-14
SAP NetWeaver AS JAVA (LM Configuration Wizard), versions - 7.30, 7.31, 7.40, 7.50, does not perform an authentication check which allows an attacker without prior authentication to execute configuration tasks to perform critical actions against the SAP Java system, including the ability to create a...
CVE-2020-6289
PUBLISHED: 2020-07-14
SAP Disclosure Management, version 10.1, had insufficient protection against Cross-Site Request Forgery, which could be used to trick user in to browsing malicious site.
CVE-2020-6290
PUBLISHED: 2020-07-14
SAP Disclosure Management, version 10.1, is vulnerable to Session Fixation attacks wherein the attacker tricks the user into using a specific session ID.
CVE-2020-6291
PUBLISHED: 2020-07-14
SAP Disclosure Management, version 10.1, session mechanism does not have expiration data set therefore allows unlimited access after authenticating once, leading to Insufficient Session Expiration
CVE-2020-6292
PUBLISHED: 2020-07-14
Logout mechanism in SAP Disclosure Management, version 10.1, does not invalidate one of the session cookies, leading to Insufficient Session Expiration.