Discover PerformanceHP Software's community for IT leaders // November 2013
5 questions for real mobile security
In the fast-changing mobile ecosystem, you’ll need the answer to these questions to inspire a security strategy that fits your business.
Threats and vulnerabilities targeted toward mobile devices are on the rise. Today’s security-conscious users will hold someone accountable for every security misstep they encounter—even if that accountability is ultimately misplaced.
The repercussions of a real or perceived security blunder can be devastating. To avoid landing in the crosshairs of angry mobile device users, your organization needs to plan ahead, creating a mobile app strategy that offers the best protection for the business and for users.
Jacob West, CTO of HP Enterprise Security and head of HP Security Research, has written an ebook on the primary considerations of mobile security, in which he sets a foundation for a robust, cost-effective mobile applications security strategy. The key, he writes, is for the enterprise to ask—and answer—the following five questions:
1. Why is mobile security an imperative?
The global shift from traditional desktop computers to mobile devices has made mobile the major area of growth for IT and development investment. Organizations that fail to properly consider mobile security requirements are taking a tremendous risk.
2. Who will users hold accountable?
As mobile breaches increase, users will surely look for someone to hold accountable. Who will pay the price?
- App owners: While not the only choice for blame, it is the most obvious.
- App developers: Savvy users may figure out that the logo on the app is not necessarily who’s at fault for the offending security errors.
- Network service providers, device manufacturers, and OS authors: Not all users understand the mobile marketplace and, as a result, may place the blame for security oversights in unlikely places.
3. What platform strategy makes sense?
- Native vs. hybrid: In the early days of smartphones, a lot of companies jumped straight into native app development, and faced a corresponding multitude of security challenges as a result. Companies are wising up and choosing non-native app development instead.
- Delivery: Increasingly, the app store is going to be the control point for mobile security. This differentiator will impact not only commercial app stores, but also enterprises that want to provide secure apps for their workforce.
- Programming language: While security issues won’t be the only factor in your platform decisions, complications with mobile development languages are a major driver pushing enterprises back to mobile-optimized web applications.
4. Where should you develop your mobile apps?
Few companies today write all their own code, but the outsourcing vs. in-house development question is growing more complex. You’ll need to weigh the pros and cons of each option to know which will provide the best tradeoff between cost, control, speed, and security.
5. How do we build secure mobile apps?
Building securely in the mobile world isn’t terribly different from security for traditional application development. Organizations with a high level of security maturity can easily transfer their expertise and assurances to mobile app development. The trick is knowing where you fall on the maturity continuum.
- Level 1—Reactive: A small central team assesses and remediates code.
- Level 2—In place: Security practices are applied to code before production.
- Level 3—Proactive: Security best practices are instilled into software methodology now and in the future.
To dive deeper into mobile security, download the free, original ebook “Mobile software security done right” (reg. req’d).