<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=339036&amp;fmt=gif">

Blue Cedar Blog

Mar 2, 2018 | Author: Blue Cedar

Which Comes First?  Device or App Security?


If you were rolling out a mobility initiative even just 18 months ago, it's quite possible that the cost and complexity of trying to secure data associated with mobile apps—especially at scale—was just too overwhelming. Depending on the intended user, you had (expensive) choices to make. If your organization owned the physical devices that the apps would run on, you had a little more control. But this approach meant purchasing devices, configuring them with an MDM application, adding a vendor-specific device configurator, creating a custom application, and ensuring support for replacements, software, and application updates. If users had their own devices, it eliminated the cost of hardware but significantly increased data security risk because the devices were unmanaged and untrusted.

 

Neither corporate ownership or BYOD completely solved the security problem.

 

Blue Cedar's approach of securing the app instead of the device recently created a "Eureka!" moment for analysts at Blue Hill Research, a division of AOTMP. You'd think that building security into mobile apps in development would more difficult and costly than simply applying device controls. That's backwards. Isn't it? Not according to Tony Rizzo, chief research officer, and Andrew Hartwyk, senior research director at Blue Hill Research. Blue Cedar enterprise mobile app security technology neatly and completely solves the very real mobility problems that organizations are trying to solve. And it's more than just solving a mobile security issue.

 

"Theoretical?" asks Hartwyk in a recent blog entry. "No. Blue Cedar has simplified the mobile application security management questions that enterprises are boiling water over today."

 

He guesses that more than 80% of global users could be BYOD users if organizations started by securing their mobile apps first. It would save millions of dollars in deployment, licensing, and hardware costs.

 

As an example, Hartwyk cites the story of a pharmaceutical client that was trying to introduce mobility to their clinical trial process. "Among the variables that we were trying to solve for was the fact that each clinical trial required different apps and connectivity features to third-party software, external devices, or other systems," he said. "Blue Cedar would have solved them all."

 

Read more about the client that could have benefitted from Blue Cedar and see why Rizzo and Hartwyck believe that starting with app security and working "backwards" might be the most efficient and cost-effective way to move mobility forward in your organization.

 

 

Please Leave A Comment