Risk
11/21/2011
05:50 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Develop Secure Mobile Applications

We share best practices to create safe mobile apps for users and customers.

InformationWeek Green - Nov. 28, 2011 InformationWeek Green
Download the November, 2011 InformationWeek secure mobile apps supplement, distributed in an all-digital format as part of our Green Initiative
(Registration required.)
We will plant a tree for each of the first 5,000 downloads.

Secure Mobile Apps The runaway success of mobile devices and apps like Angry Birds has touched off a frenzy of development, as companies rush to roll out apps for consumer and enterprise markets alike. These days, if your business isn't on a mobile platform, it's nowhere. But when developers are under pressure to release new applications, security is often an afterthought. That's bad news for consumer data, applications, and a company's infrastructure.

We've been here before, of course. It happened with client-server applications, then Web applications, and now mobile platforms. The more code that's written and the more platforms on which it runs, the more vulnerabilities will be present. It's safe to assume that all applications have security flaws, and those written to run on mobile devices are no exception.

What follows is a look at several challenges to securing mobile applications and guidance on what you can do about them.

Work Security In Early

Developers are pushing out code as fast as they can, and security concerns can easily get lost. In hypercompetitive markets, the business very likely isn't going to tolerate slowing the release rate to accommodate secure coding practices. To avoid being blamed for late releases, security pros must find ways to implement security without affecting timelines.

First, you must find low-impact ways to meet security requirements. Use automated code-analysis software during the build and test process, perform security testing during quality assurance, and work with developers to use standard preapproved libraries that have been reviewed for security. These steps go a long way toward reducing the effort required in the final security review, which typically occurs at the end of the development cycle and leaves little time for security testing and remediation.

Pay Attention To Web Links

Mobile applications typically connect to Web apps to send, retrieve, and process data, so the Web application layer presents significant risks. If you're performing code reviews, using standardized libraries, and applying other application development processes to protect Web applications, you're already doing a lot of what's needed to secure mobile applications.

Keeping Data Safe on the Move

Our full report on security and mobile applications is free with registration.

This report includes 14 pages of action-oriented analysis to help you secure mobile apps. What you'll find:
  • Best practices on secure app development
  • Advice for security teams on working with developers
Get This And All Our Reports


Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0485
Published: 2014-09-02
S3QL 1.18.1 and earlier uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object in (1) common.py or (2) local.py in backends/.

CVE-2014-3861
Published: 2014-09-02
Cross-site scripting (XSS) vulnerability in CDA.xsl in HL7 C-CDA 1.1 and earlier allows remote attackers to inject arbitrary web script or HTML via a crafted reference element within a nonXMLBody element.

CVE-2014-3862
Published: 2014-09-02
CDA.xsl in HL7 C-CDA 1.1 and earlier allows remote attackers to discover potentially sensitive URLs via a crafted reference element that triggers creation of an IMG element with an arbitrary URL in its SRC attribute, leading to information disclosure in a Referer log.

CVE-2014-5076
Published: 2014-09-02
The La Banque Postale application before 3.2.6 for Android does not prevent the launching of an activity by a component of another application, which allows attackers to obtain sensitive cached banking information via crafted intents, as demonstrated by the drozer framework.

CVE-2014-5136
Published: 2014-09-02
Cross-site scripting (XSS) vulnerability in Innovative Interfaces Sierra Library Services Platform 1.2_3 allows remote attackers to inject arbitrary web script or HTML via unspecified parameters.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.