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
The Economics Fueling IoT (In)security
Newest First  |  Oldest First  |  Threaded View
arielkriger
50%
50%
arielkriger,
User Rank: Author
12/19/2018 | 2:59:10 AM
Re: Profitability is Key
PxMx, thank you for sharing insights. I definitely agree with your assessment of the challenges given IoT devices' sheer volume. However, I don't believe the onus for providing security can or should be on the regulators and enterprises alone. For example, even if stricter regulations were to exist, even today, many of the manufacturers of IoT devices find it challenging to level up due to a lack of in-house knowledge and understanding of which regulations to favor/follow. And as you mention, organizations that use these devices are very limited in their ability to control the devices' security; because it is simply not enabled by design.

I strongly believe that the device manufacturers are best situated in the supply chain to own a large portion of the responsibility to solve this security challenge, and need to find the support (including through third parties) to develop more secure devices as well as look into ways to continue to protect them once deployed.
PxMx
50%
50%
PxMx,
User Rank: Apprentice
12/18/2018 | 8:03:14 AM
Profitability is Key
Great summary of this problem space. Reducing profitability truly is key. However, given the size of IoT, and IoT is only just getting started, it will be a great challenge. I'm not one for more regulation, but given the size and potential impact of IoT, regulation may be appropriate. Specifically, regulation that requires products to meet secure design requirements before going to market. In addition, while enterprises may not be able to change the design of IoT solutions, in their environments they can take steps to increase the cost to attackers by effectively making their security programs more agile. Some examples, real-time monitoring for active defense, security instrumentation, and deception.


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.