This document serves as a consolidated knowledge base for GCP PCD preparation and reference.
It includes concepts, best practices, and architectural details relevant to professional cloud developers.
- Security Design in Google Cloud
- (Future sections go here – e.g., IAM, Networking, CI/CD, App Development, etc.)
Google’s security infrastructure is designed with multiple progressive layers to protect customer data, from the physical hardware level up to operational practices.
Key Features:
- Hardware design & provenance
- Server boards & networking equipment custom-designed by Google.
- Custom chips, including a hardware security chip for servers & peripherals.
- Secure boot stack
- Cryptographic signatures over BIOS, bootloader, kernel, and base OS image to ensure correct boot software.
- Premises security
- Google-owned data centers with multiple layers of physical security.
- Limited access to a small number of employees.
- For third-party data centers: Google-controlled physical security in addition to provider’s measures.
Key Feature:
- Encryption of inter-service communication
- Cryptographic privacy & integrity for RPC network traffic.
- Automatic encryption of RPC traffic between data centers.
- Deployment of hardware cryptographic accelerators to extend encryption to all internal data center RPC traffic.
Key Features:
- Central identity service (Google login page) with risk-based authentication:
- Challenges for extra info based on device/location history.
- Multi-factor authentication support
- Secondary factors like U2F-based devices (Universal 2nd Factor).
Key Feature:
- Encryption at rest
- Centrally managed keys used by storage services (indirect access to file storage).
- Hardware encryption support in HDDs and SSDs.
Key Features:
- Google Front End (GFE) TLS termination
- Uses CA-issued X.509 certificates & public-private key pairs.
- Perfect forward secrecy supported.
- DoS attack protection.
- Denial of Service (DoS) protection
- Large-scale infrastructure absorbs attacks.
- Multi-tier, multi-layer DoS protections.
Key Features:
- Intrusion detection
- Rules + machine intelligence for incident alerts.
- Red Team exercises for testing response mechanisms.
- Reducing insider risk
- Strictly limited & monitored admin access.
- Employee U2F requirement
- All employees use U2F-compatible Security Keys to prevent phishing.
- Secure software development practices
- Centralized source control.
- Two-party code review.
- Developer libraries to prevent certain security bugs.
- Vulnerability Rewards Program to incentivize external bug discovery.
- Google Cloud Security Design
- GCP PCD Exam Guide
- Official Google Cloud Documentation