Google’s Shared Responsibility model
Google secures the infrastructure; customers secure configurations, data, and access.
the encryption layers in GCP
Encryption at rest (automatic), in transit (TLS), CMEK/CSEK (customer-controlled), optional app-level encryption.
CMEK vs CSEK
CMEK = managed via Cloud KMS, audit-friendly; CSEK = you supply raw keys, not stored by Google, high risk.
VPC Service Controls
A data perimeter preventing API-level data exfiltration from managed services.
Private Google Access vs VPC-SC
PGA = private IP routing to Google APIs; VPC-SC = logical security perimeter for managed services.
IAP vs Cloud Armor
IAP authenticates user identity for internal apps; Cloud Armor protects external endpoints from DDoS/web attacks.
Binary Authorization
Verifies only signed container images are deployed (trust chain enforcement).
Security Command Center (SCC)
Central threat and vulnerability monitoring dashboard for GCP.
the 3 Cloud Audit Log types
Admin Activity, Data Access, System Events.
an aggregated sink
Centralized export that routes logs from multiple projects/org to one destination (BigQuery or Storage).
service securely stores API keys and passwords
Secret Manager.
BeyondCorp
Google’s zero-trust model: every request verified for user, device, and context.
service prevents data exfiltration
VPC Service Controls.
service ensures only signed containers deploy
Binary Authorization.
service provides DDoS protection
Cloud Armor.
service provides centralized vulnerability insights
Security Command Center.
enforce customer-controlled encryption keys
Enable CMEK for supported services and control via Cloud KMS IAM.
role for encryption key usage
roles/cloudkms.cryptoKeyEncrypterDecrypter.
Exam trap: “prevent insider copy of data from BigQuery.” — Correct answer?
Implement VPC Service Controls with Service Perimeter around BigQuery.
achieve centralized audit trail
Create aggregated log sinks sending all Admin/Data logs to a Security Project.