Asia's Source for Enterprise Network Knowledge

Monday, November 24th, 2014

Information security management

5 mistakes a security vendor made in the cloud

When security experts sound the alarm about enterprises embracing cloud computing with little understanding of the risks, it's usually a case where the expert -- working for a vendor -- is making a pitch for their employer's products. That's all well and good, but here's the problem -- some of them have trouble keeping their own side of the cloud clean.
 
That, according to Nils Puhlmann, co-founder of the Cloud Security Alliance and previously CISO for such entities as Electronic Arts and Robert Half International.
 
Puhlmann recently contacted us about one example where a sizable security vendor made multiple mistakes in the cloud. He spoke on the condition that the vendor's name is kept anonymous, as he is working with the company to help address its problems.
 
"This major security vendor basically did everything you can possibly do wrong when rolling out the latest version of its SaaS (software as a service) product, leading to users uninstalling their solution in large numbers," he said.
 
In listing the following five mistakes (most of which are rooted in a lack of communication with customers), his goal is to show other security vendors how NOT to do things, and to arm IT security practitioners with a list of questions they should ask of those they pay to give them secure cloud-based services.
 
MISTAKE 1: Updating the SaaS product without telling customers or letting them opt out
Customers using a particular version of the SaaS product were caught unaware when the vendor decided to roll out a new version through the cloud. It was done in a way where, at the moment of the upgrade, any new endpoint that was added to be managed automatically got the new version. Customers were not asked or notified, and were forced into a mixed-version environment as a result. "In the past, I as a customer was able to choose if I wanted to do this, and I could choose the timing," he said. "Here, there was no control, no timing or notification."
 
MISTAKE 2: Not offering a rollback to the last prior version
The problem with the first mistake is that customers are now faced with compatibility issues in their environment that can cause a freeze-up of essential IT functions, including those related to security. The natural course for the IT security practitioner is to uninstall the new but incompatible version, dust off the CD with the last version of the product, and re-install the version that has proven itself stable in that environment. But in the cloud it's not always so simple, especially in this case, where the vendor offered no rollback option. "You get forced into a mixed environment and have no way to react," Puhlmann said.
 
MISTAKE 3: Not offering customers a choice to select timing of an upgrade
For IT security practitioners, dealing with new versions of a software or service that prove incompatible is nothing new. It happens just about every month when Microsoft releases its security updates. But in most cases, IT shops have control over when an update is pushed out in their environments. In the case of Microsoft's monthly Patch Tuesday updates, most IT admins run the updates through a roughly week-long gauntlet of testing and tweaking before deploying company-wide. But in this case, customers had no control over the timing of upgrades in their environments, Puhlmann said.