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
HackerOne Drops Mobile Voting App Vendor Voatz
Dark Reading Staff 3/30/2020
Limited-Time Free Offers to Secure the Enterprise Amid COVID-19
Curtis Franklin Jr., Senior Editor at Dark Reading,  3/31/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11558
PUBLISHED: 2020-04-05
An issue was discovered in libgpac.a in GPAC 0.8.0, as demonstrated by MP4Box. audio_sample_entry_Read in isomedia/box_code_base.c does not properly decide when to make gf_isom_box_del calls. This leads to various use-after-free outcomes involving mdia_Read, gf_isom_delete_movie, and gf_isom_parse_m...
CVE-2020-11547
PUBLISHED: 2020-04-05
PRTG Network Monitor before 20.1.57.1745 allows remote unauthenticated attackers to obtain information about probes running or the server itself (CPU usage, memory, Windows version, and internal statistics) via an HTTP request, as demonstrated by type=probes to login.htm or index.htm.
CVE-2020-11548
PUBLISHED: 2020-04-05
The Search Meter plugin through 2.13.2 for WordPress allows user input introduced in the search bar to be any formula. The attacker could achieve remote code execution via CSV injection if a wp-admin/index.php?page=search-meter Export is performed.
CVE-2020-11542
PUBLISHED: 2020-04-04
3xLOGIC Infinias eIDC32 2.213 devices with Web 1.107 allow Authentication Bypass via CMD.HTM?CMD= because authentication depends on the client side's interpretation of the <KEY>MYKEY</KEY> substring.
CVE-2020-11533
PUBLISHED: 2020-04-04
Ivanti Workspace Control before 10.4.30.0, when SCCM integration is enabled, allows local users to obtain sensitive information (keying material).