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.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3673
PUBLISHED: 2021-08-02
A vulnerability was found in Radare2 in version 5.3.1. Improper input validation when reading a crafted LE binary can lead to resource exhaustion and DoS.
CVE-2021-32806
PUBLISHED: 2021-08-02
Products.isurlinportal is a replacement for isURLInPortal method in Plone. Versions of Products.isurlinportal prior to 1.2.0 have an Open Redirect vulnerability. Various parts of Plone use the 'is url in portal' check for security, mostly to see if it is safe to redirect to a url. A url like `https:...
CVE-2021-32810
PUBLISHED: 2021-08-02
crossbeam-deque is a package of work-stealing deques for building task schedulers when programming in Rust. In versions prior to 0.7.4 and 0.8.0, the result of the race condition is that one or more tasks in the worker queue can be popped twice instead of other tasks that are forgotten and never pop...
CVE-2021-33195
PUBLISHED: 2021-08-02
Go before 1.15.12 and 1.16.x before 1.16.5 allows injection.
CVE-2021-33196
PUBLISHED: 2021-08-02
Go before 1.15.12 and 1.16.x before 1.16.5 attempts to allocate excessive memory (issue 1 of 2).