Cloud Security Basics
Top 3 platform risks in Cloud Security
Shared responsibility, identity, data, platform, logging, and audit foundations
Ten 2020–2021 episodes explaining how provider protections and customer controls fit together: identity, data access, hardware, service accounts, security logging, and audit trails.
Google Cloud Tech 4 of 10
In this collection Browse 10 summaries 4 of 10
Google secures the infrastructure it provides; customers still secure their applications. This 2020 episode explains the provider's side through defense in depth: multiple layers of protection across physical facilities, hardware, and software.
Key Points Covered
- Platform risk spans physical and virtual systems: The video traces the platform from user devices and networks through servers and disks, while assigning Google operation of the infrastructure it provides 01:03–02:06(opens in a new tab).
- Each layer has access controls: The account covers data centers, hardware origins, secure startup, communication between services, stored data, and internet-facing services. It describes strict controls on access and privileges at each layer 01:03–03:08(opens in a new tab).
- Security requires ongoing testing and response: The episode describes round-the-clock incident investigation, exercises to improve detection and response, and programs that find vulnerabilities. It also names development frameworks intended to prevent classes of bugs, such as cross-site scripting, alongside automated testing tools 02:06–04:13(opens in a new tab).
- Provider protection does not replace application security: The episode closes by distinguishing the customer's application-security responsibility from Google's infrastructure-security responsibility 03:08–04:13(opens in a new tab).
Full video: https://www.youtube.com/watch?v=N83Ru1c77U4(opens in a new tab)