Google Distributed Cloud (GDC) air-gapped uses a Zero Trust architecture to help protect your infrastructure, platform services, and application workloads in disconnected environments without requiring connectivity to public Google Cloud or the internet.
The security documentation in GDC is organized across this overview and two dedicated documents:
- Security overview: covers security strategy (Zero Trust pillars and shared responsibility), cryptography, Identity and Access Management (IAM), and compliance.
- Infrastructure, network, and workload security: covers facility security, hardware security, host and node security, multi-tenant isolation, application supply chain security, and network segmentation.
- Security operations: covers infrastructure and tenant security monitoring, vulnerability management, incident response, external security information and event management (SIEM) log export, audit logging, emergency access, disaster recovery, and rolling upgrades.
Security strategy
GDC is built on a Zero Trust architecture that assumes no implicit trust based on network location, device ownership, or user identity. Every request across the hardware, control plane, and workload layers must be authenticated, authorized, and encrypted. For architectural details on how Zero Trust principles apply to disconnected deployments, see the GDC Zero Trust Strategy Whitepaper and Google Distributed Cloud's air-gapped approach to Zero Trust.
The GDC security model aligns with the following seven Zero Trust pillars:

- Identity and users: authenticates human and service identities through your enterprise identity provider (IdP) and enforces least-privilege access across organizations and projects.
- Devices and endpoints: verifies hardware and boot integrity, hardens host and node operating systems against defense benchmarks, and continuously monitors hosts for unauthorized changes.
- Applications and workloads: protects software integrity from build to runtime using verified software supply chains, local container registries with vulnerability scanning, and cluster admission policies.
- Data and cryptography: protects data at rest and in transit by default using hardware-backed cryptographic keys, customer-managed encryption keys (CMEK), and automated public key infrastructure (PKI).
- Network and environment: isolates management planes, tenant organizations, and project workloads using multi-layered network segmentation, perimeter inspection, and default-deny network policies.
- Automation and orchestration: enforces consistent configuration, non-disruptive rolling upgrades, and audited emergency access through declarative change management.
- Visibility and analytics: collects and correlates audit, operational, and security telemetry across the platform and supports exporting tenant logs to external security monitoring systems.
Shared responsibility model
Security in GDC is a shared responsibility across the infrastructure, platform, and workload layers. Depending on whether you consume infrastructure as a service (IaaS), platform as a service (PaaS), or software as a service (SaaS), operational responsibilities are divided as shown in the following diagram:

- Infrastructure layer: covers the underlying system infrastructure, including hardware appliances, switches, storage arrays, the root admin cluster, and infrastructure security monitoring. System upgrades, hardware lifecycle management, and infrastructure security operations are performed without accessing sensitive customer workload data.
- Organization and platform layer: covers tenant organization administration, including organization-level IdP connections, role bindings, Key Management System (KMS) keys, PKI certificates, project network policies, shared Kubernetes clusters, and organization observability and log export.
- Workload and application layer: covers developing, deploying, and monitoring containerized and virtual machine (VM) workloads within isolated project namespaces according to organization security policies.
For more information, see the following documentation:
| Topic | Documentation and configuration guides |
|---|---|
| Architecture and audiences | Documentation audiences and Resource hierarchy |
| Isolation and shared responsibility | Design access boundaries, Design workload separation, and Marketplace shared responsibility model |
Cryptography
GDC provides an integrated Key Management System (KMS), Certificate Authority Service (CAS), and public key infrastructure (PKI) backed by FIPS-validated hardware security modules (HSMs) to protect data at rest and in transit:
- PKI and CAS: automates certificate issuance, renewal, and trust bundle distribution across control planes and ingress endpoints, with support for internal root certificate authorities (CAs), external intermediate CAs, custom web TLS certificates, and workload CAs.
- KMS and HSM: uses an HSM-backed envelope encryption hierarchy per organization that lets you manage symmetric encryption keys and asymmetric signing keys, and use customer-managed encryption keys (CMEK) for cryptographic erasure.
- Default encryption at rest and in transit: encrypts all block, file, object, and server disk storage at rest by default using multi-layer FIPS-validated AES-256 encryption, and secures all traffic in transit using TLS, mutual TLS (mTLS), IPsec, or MACsec.
For more information, see the following documentation:
| Topic | Documentation and configuration guides |
|---|---|
| PKI and certificates | Fetch trust bundles, Web TLS certificate configs, Transition PKI modes, and Certificate Authority Service |
| Key management (KMS, CMEK, and HSM) | Key management system, Customer-managed encryption keys, and Control HSM keys |
| Data and storage encryption | Encryption at rest, Encryption in transit, Manage encrypted storage buckets, and Encrypt metrics |
Identity and Access Management
Identity and Access Management (IAM) in GDC authenticates
human users and workload service identities (ProjectServiceAccount) and
enforces least-privilege access and separation of duties across global and zonal
resources. You connect GDC to your enterprise identity
provider (IdP) using OpenID Connect (OIDC) or SAML 2.0 with multi-factor
authentication (MFA). You then grant access by binding users or groups to
predefined or custom roles scoped to your organization, project, or Kubernetes
cluster.
For more information, see the following documentation:
| Topic | Documentation and configuration guides |
|---|---|
| Identity providers and authentication | Authorization and access control, Connect to an identity provider, and Service identities |
| Role bindings and access control | Grant and revoke access, Manage access to standard clusters, and Predefined role permissions |
Compliance
GDC is engineered to help sovereign customers meet stringent compliance requirements through continuous inventory tracking, vulnerability scanning, penetration testing, and disaster recovery validation. Because GDC operates in your accredited facility, achieving final system accreditation (such as an Authority to Operate) follows the shared responsibility model.
Security Technical Implementation Guide (STIG) compliance
Under STIG rule RHEL-08-040320, the xorg-x11-server-common package is an
approved system dependency required for NVIDIA GPU drivers and hardware
acceleration libraries (such as Vulkan and Mesa). The graphical display manager
service is disabled and inactive on node operating system images.
For more information, see the following documentation:
| Topic | Documentation and configuration guides |
|---|---|
| Benchmarks and policies | CIS Kubernetes Benchmark and Configure organization policies |
| Audit logging and retention | Audit logs overview, Secure and restore audit logs, and Create WORM buckets |