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
Commercial IoT: Big Trouble in Small Devices
Newest First  |  Oldest First  |  Threaded View
TimTonne
50%
50%
TimTonne,
User Rank: Apprentice
9/11/2017 | 10:25:27 AM
Re: IoT Secuity
Excellent post, very informative. I wonder why the opposite specialists of this sector don't understand this. You must continue your writing. I am confident, you've a great readers' base already
alex143
50%
50%
alex143,
User Rank: Apprentice
4/2/2017 | 7:11:12 AM
IoT Secuity.
The scenario is looking dangerous. What Should be the best solution then?
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
4/1/2017 | 5:16:41 PM
Re: Will get worse
In many cases, this has already happened -- by both white-hat researchers and black-hat malfeasors.

IIoT security (esp. in the public sector) has a record of being pretty pitiful.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
3/31/2017 | 3:29:28 PM
IoT forecasts/predictions
re: "By 2020, the Internet of Things (IoT) is projected to include somewhere  between 20 billion and 50 billion connected things"

First off, the observations/insights in that article that you link to are fantastic.  Thank you.  I've been beating that drum for quite some time (although the article posits that that range is more realistically capped at 17.6 billion connected devices -- inclusive of computers, mobile devices, and IoT "things").

Secondly, it's worth noting that -- one year after its notorious "50 billion connected devices by 2020" prediction made in 2010, Cisco predicted 25 billion connected devices by 2015.

Obviously, we fell far short of that (Cisco even conceded as much, reporting 15 billion connected devices two years ago -- which may or may not have been an overly liberal assessment), which you'd think would impact both Cisco's and others' predictions.  Not so much.   This hasn't stopped the forecasters and professional prognosticators predicting similarly big numbers for 2020 (and, for the hedgers who want to forecast even further out such that we'll forget what they said by then, 2021, 2025, and 2030).

(Even more hilariously, IBM projected 1 TRILLION connected devices by 2015.)
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/29/2017 | 5:14:03 PM
Will get worse
"... Imagine the impact of a successful attack on the energy grid, chemical plants, medical equipment, oil fields or even traffic lights or ATMs...." Good points , so this means it will get worse unless we act soon.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/29/2017 | 5:10:26 PM
Re: IoT requires out-of-the-box solution
"... bind an identity to its public key ..." I would say any identifier in the device should be working but not having enough knowledge to comment actually.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/29/2017 | 5:08:54 PM
HIP?
HIP may work but are we thinking the IP is the problem for IoT deceives ?
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/29/2017 | 5:07:25 PM
Re: IoT requires out-of-the-box solution
"... PKI solutio ..." It would work in my view, IoT deceives will be elective which other devices that they should be talking.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/29/2017 | 5:03:08 PM
Offline IoT
How about making those devices offline? They connect internet when they need updates but rest of the time they stay offline.
shimritd
50%
50%
shimritd,
User Rank: Author
3/29/2017 | 12:43:48 PM
IoT requires out-of-the-box solution
I believe any PKI solution will not hold for the IoT environment. First of all, there is the problem of how to bind an identity to its public key in an open environment and second, i believe that that kind of solution cannot scale.


More SolarWinds Attack Details Emerge
Kelly Jackson Higgins, Executive Editor at Dark Reading,  1/12/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-36192
PUBLISHED: 2021-01-18
An issue was discovered in the Source Integration plugin before 2.4.1 for MantisBT. An attacker can gain access to the Summary field of private Issues (either marked as Private, or part of a private Project), if they are attached to an existing Changeset. The information is visible on the view.php p...
CVE-2020-36193
PUBLISHED: 2021-01-18
Tar.php in Archive_Tar through 1.4.11 allows write operations with Directory Traversal due to inadequate checking of symbolic links, a related issue to CVE-2020-28948.
CVE-2020-7343
PUBLISHED: 2021-01-18
Missing Authorization vulnerability in McAfee Agent (MA) for Windows prior to 5.7.1 allows local users to block McAfee product updates by manipulating a directory used by MA for temporary files. The product would continue to function with out-of-date detection files.
CVE-2020-28476
PUBLISHED: 2021-01-18
All versions of package tornado are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configura...
CVE-2020-28473
PUBLISHED: 2021-01-18
The package bottle from 0 and before 0.12.19 are vulnerable to Web Cache Poisoning by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with defa...