Break-glass access and IAM auditing
A sanctioned emergency access path is only legitimate if its use is heavily alerted — and three tools close the loop on every IAM decision this chapter made.
Speaker notes
- Break-glass access is a deliberately-provisioned emergency path for when following the normal process would make an active incident worse — it must be a dedicated group (never a personal account), time-boxed membership, and tested via drills, or it's theoretical, not working.
- The requirement that actually makes break-glass safe: heavily alerted on USE, not just logged. A break-glass mechanism with no usage alerting is worse than not having one — it's a standing, unmonitored privilege-escalation route disguised as a safety control.
- Three audit tools answer three different questions: IAM Policy Analyzer answers who can currently do X accounting for all inheritance, IAM Recommender answers which grants a principal holds but never uses, and Cloud Audit Logs answers who did what and when in the past — run Recommender as a standing quarterly review, not just reactively after an incident.
Deck map
01
GCP foundations in one line
02
How the ACE exam maps to this course
03
GCP's geography and the project as the unit of isolation
04
Organization, folders, and projects
05
Org policies and how inheritance works
06
Labels, network tags, and resource manager tags
07
Billing accounts, budgets, and cost control
08
gcloud CLI, Cloud Shell, and client libraries
09
Terraform on GCP and the end of Deployment Manager
10
Gemini CLI, Cloud Assist, and Application Design Center
11
Principals, roles, bindings, and policies
12
Primitive, predefined, custom roles, and IAM conditions
13
Service accounts, keys, and impersonation
14
Workload Identity Federation
15
Break-glass access and IAM auditing
16
Choosing a machine family: E2, N4, C4
17
Disks, OS Login, and VM Manager
18
Spot VMs and managed instance groups
19
Autoscaling policies, health checks, GPUs and TPUs
20
GKE Autopilot vs Standard vs the 2026 hybrid option
21
Node pools and pod autoscaling
22
Cloud Run revisions, traffic splitting, and functions
23
Choosing between GKE, Cloud Run, and Compute Engine
24
Cloud Storage classes and lifecycle management
25
Choosing a managed database
26
The managed database lineup
27
Connection pooling, read replicas, and Pub/Sub
28
Backup, regional failover, and CMEK
29
VPC networks, subnets, and Shared VPC
30
Firewall rules, tags, and Cloud NAT
31
Load balancers, Cloud DNS, and Cloud CDN
32
VPN, Interconnect, and private access
33
How a request actually reaches shipment-api
34
Cloud Monitoring: metrics, dashboards, alerts
35
Cloud Logging: router, buckets, and audit logs
36
Trace, Profiler, Error Reporting, and Managed Prometheus
37
How the five Cloud Operations products fit together
38
Readiness checklist