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

7/26/2017
10:00 AM
50%
50%

Majority of Consumers Believe IoT Needs Security Built In

Respondents to a global survey say Internet of Things security is a shared responsibility between consumers and manufacturers.

While 90% of consumers across six different countries expect security to be built into their Internet of Things devices, the question about who should be responsible for implementing IoT security is divided, according to a survey released today by Irdeto.

The Irdeto Global Consumer IoT Security Survey, which queried 7,882 consumers in the US, Brazil, China, Germany, India, and the UK, reports that 15% of respondents believe consumers are responsible for implementing the security, while 20% say manufacturers should play that role. Overall, however, 56% believe it is the responsibility of both the consumer and manufacturer.

“While consumers across the globe believe that IoT devices need to have security manufactured into the product in order to prevent against cyberattacks, it’s encouraging that they also recognize the important role they play in IoT security,” says Mark Hearn, director of IoT security at Irdeto, in a statement.

The survey reports that 89% of respondents have at least one connected device in their home and of this group 81% have more than one IoT device. Among the six countries included in the survey, India has the most IoT users with 97% of residents having at least one IoT device in their home. The US has the fewest, with only 80%. 

Read more about the survey here

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
rwsmarine
50%
50%
rwsmarine,
User Rank: Apprentice
8/15/2017 | 3:23:54 PM
nomenclature
wht couldn't the nomenclature of the device be its temp password?  As soon as it comes online or booted the first time a mandatory password change is required.  Quick easy not great but at least its something.  Every device has a sn# to it and their all different
mikeroch
50%
50%
mikeroch,
User Rank: Apprentice
7/27/2017 | 11:40:39 AM
Re: Consumer vs manufacturers 192.168.1.1?
Absolutely agree with Dr. T, the responsibility should majorly be upon the manufacturer, it's simple, I buy some product of some brand, I trust them but due to their mistake I suffer the loss. So, even, knowing that it was good company, they failed to stand on it as they did wrong with the product. So, the 56% should be on the manufacturer side. So, IoT should be much cared by the manufacturer.
Nry2137
100%
0%
Nry2137,
User Rank: Apprentice
7/26/2017 | 12:29:05 PM
Re: Consumer vs manufacturer?
I believe the responsibility resides with both parties. However, in order to understand the responsibilities involved with security, I also believe that both parties, users specifically, need to be educated on their expected responsibilities. 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
7/26/2017 | 10:40:54 AM
Consumer vs manufacturer?
 

"Overall, however, 56% believe it is the responsibility of both the consumer and manufacturer."

I think it should be manufacturer responsibility to secure the device, most customers would not even know how to use the device forget about the security.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
7/26/2017 | 10:38:42 AM
IoT Security
If the device is doing more than one thing and connected to other devices security should be mandatory. If not and simply ringing the door bell and not connected to other things, why go so much trouble and make it expenses, basic security should be ok.
Attackers Leave Stolen Credentials Searchable on Google
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2021
How to Better Secure Your Microsoft 365 Environment
Kelly Sheridan, Staff Editor, Dark Reading,  1/25/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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-23359
PUBLISHED: 2021-01-27
WeBid 1.2.2 admin/newuser.php has an issue with password rechecking during registration because it uses a loose comparison to check the identicalness of two passwords. Two non-identical passwords can still bypass the check.
CVE-2020-23360
PUBLISHED: 2021-01-27
oscommerce v2.3.4.1 has a functional problem in user registration and password rechecking, where a non-identical password can bypass the checks in /catalog/admin/administrators.php and /catalog/password_reset.php
CVE-2020-23361
PUBLISHED: 2021-01-27
phpList 3.5.3 allows type juggling for login bypass because == is used instead of === for password hashes, which mishandles hashes that begin with 0e followed by exclusively numerical characters.
CVE-2021-25311
PUBLISHED: 2021-01-27
condor_credd in HTCondor before 8.9.11 allows Directory Traversal outside the SEC_CREDENTIAL_DIRECTORY_OAUTH directory, as demonstrated by creating a file under /etc that will later be executed by root.
CVE-2021-25312
PUBLISHED: 2021-01-27
HTCondor before 8.9.11 allows a user to submit a job as another user on the system, because of a flaw in the IDTOKENS authentication method.