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.

IoT
3/1/2018
04:45 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Securing the Web of Wearables, Smartphones & Cloud

Why security for the Internet of Things demands that businesses revamp their software development lifecycle.

Wearables are only a small part of the Internet of Things (IoT), a complicated mesh of smart devices, mobile phones, and several applications working together in a digital ecosystem.

The IoT "user experience" is a product of interactions between wearables, smartphones, and applications and analytics software hosted in the cloud. Securing this web of hardware and software is a tricky challenge for companies accelerating into the IoT, an environment that didn't exist until a few years ago, says Deep Armor founder and CEO Sumanth Naropanth.

"What we're seeing industry-wide is that this class of products is somewhat initiating a paradigm shift in the entire security development lifecycle," he explains. "[Businesses] are now responsible for changing the old security development lifecycle (SDL) frameworks and best practices into something more agile."

At this year's Black Hat Asia, taking place March 23–26 in Singapore, Naropanth will discuss security and privacy research related to the development of IoT devices, including a custom SDL designed to incorporate wearables, phones, and the cloud. The session will elaborate on flaws and privacy issues related to IoT, and best practices for building new connected products.

[Learn more about the IoT security shift in Black Hat Asia session "Securing Your In-Ear Fitness Coach: Challenges in Hardening Next Generation Wearables," in which Naropanth will discuss gaps in IoT security and necessary changes to the software development lifecycle.]

Sumanth says it's time for businesses to think about the bigger picture and secure the broader IoT ecosystem rather than getting bogged down with ingredient-level IoT security. This means not only securing individual devices but the software and services connecting them.

"Looking at a fitness tracker or IoT device, what you see is really not everything that exists," he explains. "It's like the tip of the iceberg." Behind the small activity monitor on your wrist is an array of APIs, Web portals, cloud services, and more often than not, a mobile application.

Speed vs. Security
Businesses in the IoT market are learning how to be more agile, Naropanth explains. This is especially relevant to startups, which often view security as an "expense without returns."

This isn't true when in wearables and IoT. Now companies are worried about things like securing the hardware, doing secure boot, updating mobile phones securely, and doing crypto on a very limited IoT software stack — all before launching their products before anyone else. Most enterprises working on IoT and wearables are actually taking it seriously, he adds.

"The challenge for them is more about how to balance their time to market with adequate enough security so the product is at least reasonably secure when it goes out the door," Naropanth says.

A key component of this updated SDL is evaluating the ecosystem. Your company may be building a fitness tracker that has to work with Wi-Fi, Bluetooth, or a cloud-based component someone else has developed. It's your job to navigate the interoperability challenges related to the hardware and software connecting to the wearable.

Developing for the IoT: What to Keep in Mind
Sumanth explains two best practices for IoT businesses to prioritize as they create and connect new products. The first: getting the security and product teams on the same page.

"Catching security weaknesses earlier and earlier in the product lifecycle — it helps everyone," he says. "For the company and for the enterprise, it saves a lot of money." It's better to catch security weaknesses early than when code is about to ship. If errors are found later on, a larger team is needed to address the problem," he adds.

"We strongly encourage product teams to engage with the security team early in the process. It helps us find the weaknesses early on and reduce the number of bugs that get caught later."

Naropanth also recommends IoT developers to look at existing vulnerabilities from an IoT point of view. Often, old flaws can have a "butterfly effect" in the IoT and lead to wearable devices getting bricked. Furthermore, vulnerabilities in some parts of the IoT — for example, a smartphone — can affect other connected devices.

Related Content:

 

 

 

Black Hat Asia returns to Singapore with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier solutions and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3154
PUBLISHED: 2020-01-27
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
CVE-2019-17190
PUBLISHED: 2020-01-27
A Local Privilege Escalation issue was discovered in Avast Secure Browser 76.0.1659.101. The vulnerability is due to an insecure ACL set by the AvastBrowserUpdate.exe (which is running as NT AUTHORITY\SYSTEM) when AvastSecureBrowser.exe checks for new updates. When the update check is triggered, the...
CVE-2014-8161
PUBLISHED: 2020-01-27
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
CVE-2014-9481
PUBLISHED: 2020-01-27
The Scribunto extension for MediaWiki allows remote attackers to obtain the rollback token and possibly other sensitive information via a crafted module, related to unstripping special page HTML.
CVE-2015-0241
PUBLISHED: 2020-01-27
The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a denial of service (crash) or possibly execute arbitrary code via a (1) large number of digits when processing a numeric ...