Cloud Security Basics
Top 3 access 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 2 of 10
In this collection Browse 10 summaries 2 of 10
Access security is more than checking a password: it also limits which resources a user can reach and which devices they can use. This 2020 episode explains how network protection, sign-in checks, and application policies work together.
Key Points Covered
- Access risk is broader than stolen passwords: The examples include phishing, man-in-the-middle interception, denial-of-service attacks, and accidental or malicious use of excessive permissions 01:04–02:10(opens in a new tab).
- Protect the connection and service: The episode explains that TLS encrypts traffic and requires a server to prove its identity, making interception harder. Load balancers report traffic to a central denial-of-service detection service, which can tell them to drop or slow attack traffic 02:10–03:13(opens in a new tab).
- Require more than a stolen password: Sign-in checks consider whether a device or location is familiar. A hardware security key adds something the user must physically possess, rather than another secret an attacker could obtain through phishing 03:13–04:15(opens in a new tab).
- Control what an authenticated user can reach: The example puts Identity-Aware Proxy in front of a legacy application to require membership in an approved group or domain with little application-code change. Endpoint policies add device requirements, so a valid identity alone need not be enough for access 04:15–06:22(opens in a new tab).
Full video: https://www.youtube.com/watch?v=IHBoUADMrHc(opens in a new tab)