EP203 Cloud Shared Responsibility: Beyond the Blame Game with Rich Mogull
Dec 16, 2024
auto_awesome
Rich Mogull, SVP of Cloud Security at FireMon and CEO at Securosis, dives into the intricacies of cloud security responsibility. He introduces the Cloud Shared Irresponsibilities Model, suggesting that cloud providers bear some blame in breaches due to customer misconfigurations. The discussion includes insights on what 'using the cloud securely' really means today and how to effectively teach cloud security. Rich also touches on balancing free and paid security features in the cloud and shares his top lesson for safer cloud practices.
The Cloud Shared Irresponsibilities Model emphasizes the blurred lines of accountability between cloud providers and customers in addressing security breaches.
Continuous learning and adaptation are essential for organizations to effectively navigate the complexities and evolving threats of cloud security.
Deep dives
The Cloud Transformation Timeline
Cloud transformation is often misunderstood in terms of its timeline and implementation. While some industry professionals envision a swift transition to cloud computing, the reality is that many organizations are only beginning their journey, even years after cloud technology has been established. The speaker suggests that the original projection of a 20-year transition might actually extend to 30 years, given that a significant number of companies still rely on traditional data centers. This highlights the disparity between those who have fully adopted cloud technologies and those just beginning to explore their potential.
Shared Responsibility and Its Complexities
The topic of shared responsibility in cloud security reveals significant misunderstandings among users. Many believe that the responsibility of security and compliance is clearly divided between cloud providers and clients, resembling the original models created years ago. In practice, this division is much murkier, with overlapping responsibilities that complicate accountability when issues arise. Real-world scenarios, like the Capital One breach and the Snowflake incident, demonstrate that both providers and clients may share blame, revealing the reality of a shared irresponsibility model rather than a straightforward division of duties.
Essential Learning for Cloud Security
To successfully navigate cloud security, understanding the complexities of various cloud platforms is crucial. The speaker emphasizes that organizations need to educate themselves on the nuances of their chosen platforms, rather than treating cloud as merely another data center. The analogy of encountering alien technology emphasizes the difference between familiar concepts and their implementation in the cloud. Therefore, working with subject matter experts and investing in training is essential for any organization looking to secure their cloud environments effectively.
The Ongoing Need for Learning and Adaptation
The fast-evolving nature of cloud technologies demands continuous learning and adaptation from security professionals. With new services and solutions consistently being introduced, staying informed is vital to maintaining effective cloud security practices. The speaker points out that static approaches to cloud security are likely to lead to vulnerabilities, as technology and threats will continue to evolve. Therefore, professionals in the field must embrace the challenge of ongoing education and adaptation to maximize the benefits of cloud computing.
Let’s talk about cloud security shared responsibility. How to separate the blame? Is there a good framework for apportioning blame?
You've introduced the Cloud Shared Irresponsibilities Model, stating cloud providers will be considered partially responsible for breaches even if due to customer misconfigurations. How do you see this impacting the relationship between cloud providers and their customers? Will it lead to more collaboration or more friction?
We both know the Jay Heiser 2015 classic “cloud is secure, but you not using it securely.” In your view, what does “use cloud securely” mean for various organizations today?
Here is a very painful question: how to decide what cloud security should be free with cloud and what security can be paid?
You dealt with cloud security for a long time, what is your #1 lesson so far on how to make the cloud more secure or use the cloud more securely?
What is the best way to learn how to cloud? What is this CloudSLAW thing?