Usually, the way we define and implement security is driven by compliance. But despite a wide number of frameworks from the Information Systems Audit and Control Association‘s (ISACA) Control Objectives for Information and related Technology (COBIT) to Payment Card Industry Data Security Standards (PCI DSS), those compliance standards aren’t very clear, leaving ample room for every auditor to interpret them differently.
When you dive deeper into the Ponemon study data, it shows that “cloud providers are most confident about their ability to ensure recovery from significant IT failures and ensure the physical location of data assets are in secure environments.” These are two areas where best practices and the compliance standards are well-defined.
On the other hand, cloud providers are “least confident in their ability to restrict privileged user access to sensitive data.” At least part of that lack of confidence can surely be attributed to the lack of a clear definition of privileged access and what the appropriate controls are.
Since many of the privileged users of a cloud system are the customer’s employees, it makes sense that cloud security has got to be an area of shared responsibility between the cloud vendor and the customer. But who should do what and, ultimately, who’s in charge?
Scott Lang, Sr. Director, Product Marketing at BeyondTrust
Scott Lang has nearly 20 years of experience in technology product marketing, currently guiding the product marketing strategy for BeyondTrust’s privileged account management solutions and vulnerability management solutions. Prior to joining BeyondTrust, Scott was director of security solution marketing at Dell, formerly Quest Software, where he was responsible for global security campaigns, product marketing for identity and access management and Windows server management.