theDocumentId => 1330040 10 Steps for Writing a Secure Mobile App

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.

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
 

Recommended Reading:

Previous
1 of 11
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
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-37457
PUBLISHED: 2021-07-25
Cross Site Scripting (XSS) exists in NCH Axon PBX v2.22 and earlier via the SipRule field (stored).
CVE-2021-37458
PUBLISHED: 2021-07-25
Cross Site Scripting (XSS) exists in NCH Axon PBX v2.22 and earlier via the primary phone field (stored).
CVE-2021-37459
PUBLISHED: 2021-07-25
Cross Site Scripting (XSS) exists in NCH Axon PBX v2.22 and earlier via the customer name field (stored).
CVE-2021-37460
PUBLISHED: 2021-07-25
Cross Site Scripting (XSS) exists in NCH Axon PBX v2.22 and earlier via /planprop?id= (reflected).
CVE-2021-37461
PUBLISHED: 2021-07-25
Cross Site Scripting (XSS) exists in NCH Axon PBX v2.22 and earlier via /extensionsinstruction?id= (reflected).