The shared fate model
1. The shared fate model
Let’s pretend you’ve been assigned a school project with a partner. Naturally, you want to do well on the project. And you hope your partner does too, right? You want them to work just as hard as you so you can share the work fairly and get the best grade possible. Things work similarly in the world of cloud security. As organizations make the decision to migrate to the cloud, one of the factors they have to consider is the trust they have in the cloud service provider to secure their data and resources. This trust is one of the main reasons for the shared responsibility model with a CSP, which has recently been elevated to a model known as shared fate. The shared fate model emphasizes the CSP’s involvement in the customer’s entire security journey and offers resources to securely manage their environment at each stage. The shared fate model was created to respond to gaps in the shared responsibility model, with the CSP offering more extensive guidance in how to secure a customer’s cloud-based resources. This addresses the challenges that customers face when using the shared responsibility model. Some of these challenges include navigating changing regulations, determining how security controls overlap, and approaching security as an ongoing process. The primary purpose of the shared fate model is to increase the level of trust between the users of cloud services and the cloud service provider. In shared fate, the cloud service provider invests more time to develop resources to help the customer design, deploy, and operate their cloud environment. This means there is a stronger partnership between the customer and the cloud service provider. There are several ways the shared fate model can increase the level of trust with the customer. Three examples we’ll cover are security foundations for users, landing zones, and mitigating risk. Security foundations for users are used by Google Cloud. Google’s security foundations are a list of best practices, or blueprints, for configuring and deploying Google services. They deploy and maintain secure solutions using infrastructure as code. The second way the shared fate model increases trust is with landing zones. A landing zone is a modular and scalable configuration that enables organizations to adopt Google Cloud for their business needs. Google offers guidance on configuring landing zones. For a user that's new to the cloud, using a landing zone provides a starting point for adding identity provisioning, a resource hierarchy, and network and security controls. Finally, the shared fate model focuses on mitigating risk with the Risk Protection Program. Part of the program includes Google’s tool, Risk Manager. Risk Manager is a Google Cloud security tool that offers insight into your organization's technical risk posture. It lets you generate reports to evaluate risk across your organization. Throughout this video, you learned about how the shared fate model strengthens the relationship between customers and the CSP, and how it distinguishes itself from the shared responsibility model. Building trust and understanding common vulnerabilities are huge assets to security analysts.2. Let's practice!
Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.