2 Reasons Not To Build New Cloud Security Infrastructure
Last week I talked about the challenges of managing privileged identities in the cloud. As I have highlighted in an earlier post the recent report by the Ponemon Institute on the Security of Cloud Computing Providers shows that when it comes to security cloud providers are “least confident in their ability to restrict privileged user access to sensitive data”.
Today , we are helping our customers extend their existing insider security infrastructure, policies and compliance reporting to their private, public and hybrid clouds. Why extend what they have and not build a new cloud security infrastructure? Well I hear 2 primary reasons from customers.
First, It just works. Our primary datacenter infrastructure products PowerBroker for Servers, PowerBroker Database Monitor and Audit and PowerBroker Identity Services all have flexible architectures that allow them to be readily deployed in public, private and hybrid cloud environments. It’s all a matter of proper configuration of the networking to fit the difference in the clouds and to assure secure connections between the components and the infrastructure they are monitoring.
But the real benefit of extending their existing insider security infrastructure, policies and compliance reporting is it’s a tool that know . The systems engineering and admin teams know how to operate and maintain it. And perhaps more importantly the audit and compliance people have built their processes around it. Both groups have enough new things to learn in a move to the cloud, so why not reduce the barriers. Call us – we have helped many customers with cloud deployments and want to help more.