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.

Risk

9/15/2015
05:15 PM
Sara Peters
Sara Peters
Commentary
Connect Directly
Twitter
RSS
E-Mail vvv
50%
50%

Fixing IoT Security: Dark Reading Radio Wednesday at 1 P.M. ET

Join us for a conversation about what is being done and what needs to be done to secure the Internet of Things.

Last week, the FBI was inspired to issue a public service announcement warning that the Internet of Things poses opportunities for cybercrime. The PSA included practical advice about passwords, and querulous philosophical challenges like "Consider whether IoT devices are ideal for their intended purpose."

Who can blame the Feds for being nervous? There are already 3.9 billion Internet of Things (IoT) devices in the world today, and Gartner estimates that by 2020 there will be 25 billion of them -- inside our public infrastructure, our homes, our cars, even our bodies… and all full of vulnerabilities.

Today, the IoT Village, which debuted last month at DEF CON, announced that through its hacking contest and workshops, 60 zero-day vulnerabilities have already been discovered in a variety of IoT devices. The list includes bugs in satellite receivers, motion sensors, and baby monitors, a remote code execution attack that can bring a Parrot drone crashing to the ground, and even a man-in-the-middle attack on a Samsung Smart Refrigerator that could jeopardize a hungry fridge owner's email account and any account associated with that email address.

Industrial manufacturing behemoth GE is using a new ad campaign to convince us that it's a "digital company" now too, but the truth is, manufacturers of IoT devices are relatively new to the business of writing code and unprepared for the brave new world they’re creating.

What can the infosec community do to help solve the problem, other than just find fault? We're devoting the next episode of Dark Reading Radio to that question.

Join us for "Fixing IoT Security," next Wednesday, Sep. 23, at 1:00 p.m. ET, conveniently coinciding with the world's first conference dedicated to IoT security and privacy. The show also coincides with the launch of the Internet of Things Security Foundation (IoTSF), a group established to curate and develop best practices, with associates from a variety of telecom and IoT companies, including Vodafone, British Telecom, and Imagination Technologies.

We'll tackle the topic from both sides -- with guests who approach the topic from an IT security background and guests who approach it from the device manufacturer / embedded systems background.

I'll be your host. Joining me will be:

  • Haydn Povey, CEO and founder of Secure Thingz, a start-up that spun out of microprocessor technology giant ARM, and member of the executive steering board for the new IoTSF.
  • Jeff Wilbur, chairman of the Online Trust Alliance, which recently released a framework for IoT security and privacy.
  • Ruben Santamarta, principal security consultant for IOActive, who's been a leader in research on vulnerabilities in satellite technology. IOActive has been at the forefront of research into car hacking, smart cities security, cyber-physical hacking, and other IoT-related security issues.
  • Dark Reading's own Marilyn Cohodas, reporting from Boston at the inaugural IoT Security event.

Have questions you want us to address? Let us know in the comments below or hop into the live chat during our radio broadcast of "Fixing IoT Security," next Wednesday at 1 p.m. Eastern Time. Register now.

 

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
lynnbr2
50%
50%
lynnbr2,
User Rank: Strategist
9/23/2015 | 9:41:39 AM
Why consumers should own the software on products they buy
Sharing the editorial at the link below:

www dot designworldonline dot com/the-real-reason-manufacturers-dont-want-consumers-to-own-software/ 

 
Austin Milbarge
100%
0%
Austin Milbarge,
User Rank: Apprentice
9/23/2015 | 9:35:16 AM
couple of questions
It's awesome that folks in IT security are making such a great effort to work with the various IoT companies etc as it's a Pandora's Box that needs to be addressed.

That said....

Q1 - I'm curious though if there are any initiatives in the works to work with these IoT companies when it comes to interacting with security researchers (outside said company/ies), their response and reaction to bugs, exploits, zero days etc that are brought to their attention especially in good faith. 

And

Q2 - Once informed, how to categorize and address the disclosed issue within the company. Is it a "stop everything and get this fixed asap" issue because said company may have early beta equipment in-use in the wild (customers) and may feel the issue is enough of a threat to apply most of their resources to fixing said issue (at least those resources necessary to address the issue) even if it means taking those resources away from their current work (perhaps in the midst of meeting a deadline?) I realize it's all contextual and we could all come up with 100 different scenarios but it should be noted that a lot of start-ups are going to be riding a fine line with deadlines, money, perception etc and likely won't be able to weather a misstep quite as well as the larger more established companies.
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: What Virtual Reality phishing attacks will look like in 2030.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-21652
PUBLISHED: 2021-05-11
A cross-site request forgery (CSRF) vulnerability in Jenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
CVE-2021-21653
PUBLISHED: 2021-05-11
Jenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier does not perform a permission check in an HTTP endpoint, allowing with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
CVE-2021-21654
PUBLISHED: 2021-05-11
Jenkins P4 Plugin 1.11.4 and earlier does not perform permission checks in multiple HTTP endpoints, allowing attackers with Overall/Read permission to connect to an attacker-specified Perforce server using attacker-specified username and password.
CVE-2021-21655
PUBLISHED: 2021-05-11
A cross-site request forgery (CSRF) vulnerability in Jenkins P4 Plugin 1.11.4 and earlier allows attackers to connect to an attacker-specified Perforce server using attacker-specified username and password.
CVE-2021-21656
PUBLISHED: 2021-05-11
Jenkins Xcode integration Plugin 2.0.14 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.