GCP Security & Identity Hub 🔐

Google Cloud is architected around the BeyondProd and BeyondCorp zero-trust security models. Trust is never granted based on physical network perimeter; instead, every access request, container execution, RPC invocation, and storage access is cryptographically authenticated, authorized, and audited at the hypervisor, kernel, and software-defined network boundary.


Service Catalog & Security Architecture Map

ServiceCategoryCore Architecture & Protection ScopeReference Guide
IAM & Resource HierarchyIdentity & AccessOrg Folder Project resource hierarchy, Service Accounts, Short-lived STS Tokens, CEL Conditions.IAM & Access Deep Dive
Workload Identity FederationKeyless AuthOIDC/SAML token exchange eliminating static JSON service account keys for GitHub Actions, AWS, and GKE.Workload Identity Federation
Cloud KMS & Cloud HSMCryptographic KeysFIPS 140-2 Level 3 HSM, Envelope Encryption, CMEK, automated key rotation, and External Key Manager (EKM).Cloud KMS & Envelope Encryption
Security Command Center (SCC)CSPM & Threat DetectionCentralized CSPM/CWPP, agentless hypervisor-level VM Threat Detection (VMTD), Container Threat Detection.Security Command Center (SCC)
Cloud ArmorWAF & DDoS DefenseGlobal Anycast edge DDoS defense, OWASP ModSecurity CRS, ML-based Adaptive Protection, and rate-based throttling.Cloud Armor Deep Dive
Identity-Aware Proxy (IAP)Zero Trust AccessContext-aware zero-trust HTTPS/TCP proxying, eliminating VPNs for SSH/RDP and internal web apps via BeyondCorp.IAP & BeyondCorp Deep Dive
Sensitive Data Protection (Cloud DLP)Data Privacy & MaskingAutomated discovery, classification, and cryptographic tokenization/masking of PII/PHI in BigQuery, GCS, and streams.Cloud DLP Deep Dive
Certificate Authority Service (CAS)Enterprise PKI & TLSFully managed, highly scalable private CA hierarchy (Root/Subordinate CAs) and Certificate Manager automated renewal.Certificate Authority Service
Binary AuthorizationSupply Chain GatekeeperCryptographic deploy-time container image admission control enforcing SLSA provenance before execution in GKE.Binary Authorization

The BeyondCorp & Defense-in-Depth Architecture

flowchart TD
    subgraph ExternalClients ["External Untrusted Perimeter"]
        User["Remote Employee / Corporate Device"]
        Attacker["Malicious DDoS / Web Scraping Bot"]
    end

    subgraph EdgeDefense ["Google Global Edge (100+ PoPs)"]
        Anycast["Global Anycast IP Frontend"]
        Armor["Cloud Armor (DDoS Mitigation, OWASP Top 10, Adaptive ML)"]
        Anycast --- Armor
    end

    subgraph ZeroTrustIdentity ["Zero Trust Access Boundary"]
        IAP["Identity-Aware Proxy (Context-Aware Access, Device Health)"]
        CloudID["Cloud Identity / Google Workspace IdP"]
        IAP <--> CloudID
    end

    subgraph InternalVPC ["Customer Private Cloud Foundation"]
        VPC["Private VPC (No Public IPs)"]
        GKE["GKE Workloads (Workload Identity, Shielded Nodes)"]
        KMS["Cloud KMS (CMEK Envelope Encryption)"]
        DLP["Sensitive Data Protection (Cloud DLP Inspection)"]
        SCC["Security Command Center (Hypervisor Threat Detection)"]

        VPC --> GKE
        GKE <--> KMS
        GKE <--> DLP
        SCC -.->|"Hypervisor VMTD"| GKE
    end

    User --> Anycast
    Attacker -.->|"Blocked at Edge"| Armor
    Armor --> IAP
    IAP -->|"Encrypted Tunnel"| VPC