Endpoint

10/5/2017
11:40 AM
Dawn Kawamoto
Dawn Kawamoto
Slideshows
50%
50%

10 Steps for Writing a Secure Mobile App

Best practices to avoid the dangers of developing vulnerability-ridden apps.
Previous
1 of 11
Next

Image Source: Pedrosek via Shutterstock

Image Source: Pedrosek via Shutterstock

More than 4 million mobile apps are currently in production, but only 29% on average are tested for bugs, and nearly a third of these contain significant vulnerabilities, according to a recent Ponemon Institute survey.

Enterprises, meanwhile, are expected to accelerate their mobile app development in the coming months, according to a recent Gartner survey. On average, enterprises deployed eight mobile apps from the start of the year, with nearly nine more on tap or planned through June, the survey found.

"Developers are less careful when developing apps for internal use because they want to develop it fast, so it can achieve some purpose," says Vivien Raoul, chief technical officer and co-founder of Pradeo, which recently published the Mobile Application Security Guide.

Whether enterprises are developing mobile apps for internal use or to aid customers in using their service, they face consequences if a mobile app is vulnerable security-wise. In addition, organizations whose apps are for customers stand the risk of getting hit with a civil complaint if the apps aren't up to snuff security-wise.

The Federal Trade Commission, for example, has been slapping companies with civil lawsuits over the way enterprises have handled the security of their mobile app development efforts. Enterprises that have felt the FTC's wrath include Upromise, Credit Karma, and Fandango.

Here are key steps for creating a secure enterprise mobile app:

 

Dawn Kawamoto is an Associate Editor for Dark Reading, where she covers cybersecurity news and trends. She is an award-winning journalist who has written and edited technology, management, leadership, career, finance, and innovation stories for such publications as CNET's ... View Full Bio

Previous
1 of 11
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Russia Hacked Clinton's Computers Five Hours After Trump's Call
Robert Lemos, Technology Journalist/Data Researcher,  4/19/2019
Tips for the Aftermath of a Cyberattack
Kelly Sheridan, Staff Editor, Dark Reading,  4/17/2019
Why We Need a 'Cleaner Internet'
Darren Anstee, Chief Technology Officer at Arbor Networks,  4/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-11486
PUBLISHED: 2019-04-23
The Siemens R3964 line discipline driver in drivers/tty/n_r3964.c in the Linux kernel before 5.0.8 has multiple race conditions.
CVE-2019-11487
PUBLISHED: 2019-04-23
The Linux kernel before 5.1-rc5 allows page->_refcount reference count overflow, with resultant use-after-free issues, if about 140 GiB of RAM exists. This is related to fs/fuse/dev.c, fs/pipe.c, fs/splice.c, include/linux/mm.h, include/linux/pipe_fs_i.h, kernel/trace/trace.c, mm/gup.c, and mm/hu...
CVE-2018-7576
PUBLISHED: 2019-04-23
Google TensorFlow 1.6.x and earlier is affected by: Null Pointer Dereference. The type of exploitation is: context-dependent.
CVE-2018-8825
PUBLISHED: 2019-04-23
Google TensorFlow 1.7 and below is affected by: Buffer Overflow. The impact is: execute arbitrary code (local).
CVE-2019-10688
PUBLISHED: 2019-04-23
VVX products using UCS software version 5.8.0 and earlier with Better Together over Ethernet Connector (BToE) application version 3.8.0 and earlier uses hard-coded credentials to establish a connection between the host application and device.