While living in the cloud has become a popular option, companies remain skeptical. No matter how many security precautions are provided, when services like SaaS, IaaS (Infrastructure as a Service) and PaaS (Platform as a Service) are offered in the cloud, companies are tentative to employ them.

Game. Set. Match.

A recent Aberdeensurvey may put some fears to rest, while turning apprehension on its head. The survey, which compared companies using onpremise web security solutions to those using cloud-based solutionsfound that by NOT storing information via the cloud, companies may beputting themelves at greater risk for more malware incidents and data loss.

During its 12- month analysis, Abderdeen recorded the following:

36 Companies Using On-Premise Solutions

  • 26 Malware infections
  • 9 Website compromises
  • 11 Data Loss/Data Exposure incidents*
  • 11 security related downtime incidents
  • 30 audit deficiencies

22 Organizations Using Cloud-Based Services

Learning Opportunities

  • 11 Malware infections
  • 2 Website Compromises
  • 6 Data Loss/Data Exposure
  • 6 Security-Related Downtime incidents
  • 2 Audit Deficiencies

Advantage: Cloud

The analysis shows that cloud-based solutions incur fewer security risks. While the numbers between the two platforms may not seem drastic, let’s take a moment to put it in a language that companies understand: money.

Assume for a moment, as Aberdeen did, that each data loss incident or exposure costs US$ 640,000. Having had 5 fewer Data loss incidents translates into US$ 3 million in cost avoidance. Or consider that for every audit deficiency, a company loses US$ 7,000. Would you rather have 30 of them or two? We thought so.

There are several great reasons to operate within the cloud, like efficiency, collaboration and convenience. Until now, those didn’t mean much to the C-suite. Yet, when coupled with a strong security track analysis, it will be much harder for executives to ignore the benefits of cloud, or all the money they’ll be saving as a result.

*This number was incorrectly listed when it first published and has been updated to reflect the correct number of data loss incidents incurred using on-premise solutions.