EP193 Inherited a Cloud? Now What? How Do I Secure It?
Guests:
• Taylor Lehmann (https://www.linkedin.com/in/tlehmanncyber/) , Director at Office of the CISO, Google Cloud
• Luis Urena (https://www.linkedin.com/in/urena-luis/) , Cloud Security Architect, Google Cloud
Topics
• There is a common scenario where security teams are brought in after a cloud environment is already established (https://cloud.google.com/blog/transform/how-to-secure-cloud-surprises/) . From your experience, how does this late involvement typically impact the organization's security posture and what are the immediate risks they face?
• Upon hearing this, many experts suggest that “burn the environment with fire” or “nuke it from orbit” are the only feasible approaches? What is your take on that suggestion?
• On the opposite side, what if business demands you don't touch anything but “make it secure” regardless?
• Could you walk us through (https://cloud.google.com/blog/transform/how-to-secure-cloud-surprises/) some of the first critical steps you do after “inheriting a cloud” and why they are prioritized in this way?
• Why not just say “add MFA everywhere”? What may or will blow up?
• We also say “address overly permissive users and roles” and this sounds valuable, but also tricky. How do we go about it?
• What are the chances that the environment is in fact compromised already? When is Compromise Assessment the right call, it does cost money, right?
• How do you balance your team’s current priorities when you’ve just adopted an insecure cloud environment. How do you make tradeoffs among your existing stack and this new one?
Resources:
• “Confetti cannons or fire extinguishers? Here’s how to secure cloud surprises” (https://cloud.google.com/blog/transform/how-to-secure-cloud-surprises/)
• EP179 Teamwork Under Stress: Expedition Behavior in Cybersecurity Incident Response (https://cloud.withgoogle.com/cloudsecurity/podcast/ep179-teamwork-under-stress-expedition-behavior-in-cybersecurity-incident-response/)
• IAM Recommender (https://cloud.google.com/policy-intelligence/docs/role-recommendations-overview)
• “TM" book by Adam Shostack (https://shostack.org/books/threat-modeling-book)
• “Checklist Manifesto” (https://www.amazon.com/Checklist-Manifesto-How-Things-Right/dp/0312430000) book
• “Moving shields into position: How you can organize security to boost digital transformation” (https://cloud.google.com/transform/moving-shields-into-position-organizing-security-for-digital-transformation) (with a new paper!)
Видео EP193 Inherited a Cloud? Now What? How Do I Secure It? канала Anton Chuvakin
Cloud Security Podcast by Google
• Taylor Lehmann (https://www.linkedin.com/in/tlehmanncyber/) , Director at Office of the CISO, Google Cloud
• Luis Urena (https://www.linkedin.com/in/urena-luis/) , Cloud Security Architect, Google Cloud
Topics
• There is a common scenario where security teams are brought in after a cloud environment is already established (https://cloud.google.com/blog/transform/how-to-secure-cloud-surprises/) . From your experience, how does this late involvement typically impact the organization's security posture and what are the immediate risks they face?
• Upon hearing this, many experts suggest that “burn the environment with fire” or “nuke it from orbit” are the only feasible approaches? What is your take on that suggestion?
• On the opposite side, what if business demands you don't touch anything but “make it secure” regardless?
• Could you walk us through (https://cloud.google.com/blog/transform/how-to-secure-cloud-surprises/) some of the first critical steps you do after “inheriting a cloud” and why they are prioritized in this way?
• Why not just say “add MFA everywhere”? What may or will blow up?
• We also say “address overly permissive users and roles” and this sounds valuable, but also tricky. How do we go about it?
• What are the chances that the environment is in fact compromised already? When is Compromise Assessment the right call, it does cost money, right?
• How do you balance your team’s current priorities when you’ve just adopted an insecure cloud environment. How do you make tradeoffs among your existing stack and this new one?
Resources:
• “Confetti cannons or fire extinguishers? Here’s how to secure cloud surprises” (https://cloud.google.com/blog/transform/how-to-secure-cloud-surprises/)
• EP179 Teamwork Under Stress: Expedition Behavior in Cybersecurity Incident Response (https://cloud.withgoogle.com/cloudsecurity/podcast/ep179-teamwork-under-stress-expedition-behavior-in-cybersecurity-incident-response/)
• IAM Recommender (https://cloud.google.com/policy-intelligence/docs/role-recommendations-overview)
• “TM" book by Adam Shostack (https://shostack.org/books/threat-modeling-book)
• “Checklist Manifesto” (https://www.amazon.com/Checklist-Manifesto-How-Things-Right/dp/0312430000) book
• “Moving shields into position: How you can organize security to boost digital transformation” (https://cloud.google.com/transform/moving-shields-into-position-organizing-security-for-digital-transformation) (with a new paper!)
Видео EP193 Inherited a Cloud? Now What? How Do I Secure It? канала Anton Chuvakin
Cloud Security Podcast by Google
Показать
Комментарии отсутствуют
Информация о видео
7 октября 2024 г. 20:10:40
00:30:41
Другие видео канала




















