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-9710
Published: 2015-05-27
The Btrfs implementation in the Linux kernel before 3.19 does not ensure that the visible xattr state is consistent with a requested replacement, which allows local users to bypass intended ACL settings and gain privileges via standard filesystem operations (1) during an xattr-replacement time windo...

CVE-2014-9715
Published: 2015-05-27
include/net/netfilter/nf_conntrack_extend.h in the netfilter subsystem in the Linux kernel before 3.14.5 uses an insufficiently large data type for certain extension data, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via outbound network traffic that trig...

CVE-2015-2666
Published: 2015-05-27
Stack-based buffer overflow in the get_matching_model_microcode function in arch/x86/kernel/cpu/microcode/intel_early.c in the Linux kernel before 4.0 allows context-dependent attackers to gain privileges by constructing a crafted microcode header and leveraging root privileges for write access to t...

CVE-2015-2830
Published: 2015-05-27
arch/x86/kernel/entry_64.S in the Linux kernel before 3.19.2 does not prevent the TS_COMPAT flag from reaching a user-mode task, which might allow local users to bypass the seccomp or audit protection mechanism via a crafted application that uses the (1) fork or (2) close system call, as demonstrate...

CVE-2015-2922
Published: 2015-05-27
The ndisc_router_discovery function in net/ipv6/ndisc.c in the Neighbor Discovery (ND) protocol implementation in the IPv6 stack in the Linux kernel before 3.19.6 allows remote attackers to reconfigure a hop-limit setting via a small hop_limit value in a Router Advertisement (RA) message.

Dark Reading Radio
Archived Dark Reading Radio
After a serious cybersecurity incident, everyone will be looking to you for answers -- but you’ll never have complete information and you’ll never have enough time. So in those heated moments, when a business is on the brink of collapse, how will you and the rest of the board room executives respond?