When the Cloud was invented, many of us thought it could be the “be-all and end-all” secure data center. However, as the cold reality of data breaches has taught us, moving your company’s assets, processing power and storage to a third-party cloud environment doesn’t relieve you of your responsibility to understand where and how your data is secured.
Bonobos, a Walmart subsidiary, is the latest example. The company recently reported a data breach at a third-party cloud service provider (CSP) that resulted in customer PII exposure. This breach is another illustration of the pitfalls of shared responsibility. Is it on the customer, the third party, or the CSP?
Understanding the differences between cloud service levels can help you determine which control standards to embed into your cloud computing service models. There are four basic cloud service provider (CSP) levels:
Each level of support reflects whether risk responsibility lies with the customer or the provider. Under the Enterprise IT structure, the provider has controls in place for all ten responsibility zones (see table below). However, if you engage in any flavor of “as a Service,” then the responsibility can vary between the customer, the provider, or both.
When you assess supply chain security, beware of blanket responses from your vendors indicating that they are “protected” in the cloud. If they use the cloud, then determine which level of service they have and what controls are in place to support what’s covered in their CSP contract.
Microsoft’s Shared Responsibility Model*
Breaches like the one affecting Bonobos serve as a reminder to implement best practices, embed control standards to protect your data, and continuously assess third parties that store and manage your data. Whether you are using cloud services for backup data or active data, be sure to consider the following best practices:
Prevalent can assist with security evaluations of IaaS, PaaS, SaaS and other CSPs by using the built-in Cloud Security Alliance (CSA) Consensus Assessments Initiative Questionnaire (CAIQ) questionnaire in the Prevalent Platform. This questionnaire is an industry standard for documenting cloud security controls and CSP security capabilities using standardized, best-practice terminology. With comprehensive reporting against the standard, you gain a clear picture of your CSP’s security controls and can make better-informed decisions.
To complement the regular controls assessment, Prevalent Vendor Threat Monitor can deliver continuous cybersecurity, reputation and financial insights into your CSPs. This includes monitoring for hacker chatter on dark web forums, which provides a window into real and potentially unseen risks, while also validating the presence of certain controls.
Handing control and management of your data to a CSP does not necessarily mean that you are free of responsibility for regulatory governance and accountability. So, when a supplier or vendor indicates they are using cloud services, do not stop your assessment there. Find out what CSP level your third party is using and how controls are governed on both the vendor and the provider sides of the house. Also, be sure to consider active, backed-up, and terminated databases where applicable. It might save you from a world of heartache!
For more on how Prevalent can help address the regulatory and governance aspects of third-party risk management for CSPs, check out our best practices white paper, Satisfying Compliance with Third-Party Risk Management Requirements. Or contact us for a strategy session today.
*Source: Lanfear, Terry. “Shared Responsibility in the Cloud” Microsoft Azure Documentation, 16 Oct. 2019