Files
tom_analysis_agent/eval/results/20261021T203623Z-handoff/solution_architecture/solution-architecture-guide.md
Jonathan Boniface 628b6ee170 docs: publish the runs of 2026-10-21
The evaluation (both cases three times: report, results, spread, each
run's Deliverables and lesson candidates) and the hand-off through the
Orchestration engine (report, the document of links, both agents' kept
files and records). Benchmark cases only, all fictional; no machine paths,
and the links carry no signatures. Other runs stay ignored.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 09:25:03 +01:00

104 KiB

Google Cloud solution architecture: UK-Regulated Payment Platform Foundation

1. Executive summary and workload overview

Scope baseline and design foundations

This solution architecture guide provides the definitive technical design and landing zone specification for an enterprise-grade Google Cloud platform foundation to support a UK-regulated payment platform's core payments engine.

The architecture rests on 44 facts stated directly by the customer, 0 answered in conversation, 11 catalogue and baseline facts assumed on their behalf, 4 unknown details, and 4 items determined to be not applicable. Because several architectural, networking, and operational parameters were established via assumptions rather than confirmed customer specifications, this document represents an indicative design rather than an agreed final implementation.

The foundational assumptions that most shape the architecture include:

  1. Scope and Acceptance Criteria (ASSUMP-01): The platform foundation is provisioned within a 10-week window, compliant with DORA and PCI-DSS v4.0, providing 10Gbps dedicated interconnect hybrid connectivity, centralised egress inspection, and customer-managed encryption keys.
  2. High Availability Target (ASSUMP-02): A platform foundation availability target of 99.9% across availability zones (europe-west2).
  3. Disaster Recovery Objectives (ASSUMP-03, ASSUMP-04): A warm standby resilience posture in europe-west1 achieving a Recovery Time Objective (RTO) of 4 hours and a Recovery Point Objective (RPO) of 1 hour.
  4. Appliance Vendor and Form Factor (ASSUMP-05): Deployment of scalable third-party Network Virtual Appliances (NVAs) on Compute Engine Managed Instance Groups behind an Internal Passthrough Network Load Balancer for centralised egress inspection.
  5. Private IP Allocation (ASSUMP-06): Allocation of non-overlapping private RFC 1918 address space across development, staging, production, and transit hub VPCs.
  6. Platform Observability and Tooling (ASSUMP-07, ASSUMP-08, ASSUMP-10, ASSUMP-11): Utilization of Google Cloud Operations Suite (Cloud Monitoring and Logging) for 24/7 observability, Terraform for Infrastructure as Code, and GitHub Actions with Workload Identity Federation for keyless CI/CD.
  7. Key Governance and Geographic Residency (ASSUMP-12, ASSUMP-13): Customer-Managed Encryption Keys (CMEK) configured with 90-day automatic rotation, and strict Organization Policies restricting platform resources exclusively to London (europe-west2) and Belgium (europe-west1).

Project timelines, milestone phases, and delivery resource scheduling are maintained independently within the dedicated Delivery Plan deliverable.

Workload overview and solution summary

The core payments engine requires an immutable, resilient, and highly secure cloud landing zone. The architecture establishes a multi-tier environment hierarchy separating development, staging, and a strictly isolated production Cardholder Data Environment (CDE). Connectivity between on-premises mainframes/ledgers and Google Cloud is established over dual 10Gbps Dedicated Cloud Interconnect circuits terminating in europe-west2, backed by standby routing in europe-west1. All direct public internet ingress is prohibited (networking.exposure: internal_only), and outbound egress traffic across all environments is statically routed through a centralized transit hub hosting auto-scaled, auto-healed inspection firewalls. Identity is federated from corporate Microsoft Entra ID via Cloud Identity for administrators, while deployment pipelines authenticate keylessly via Workload Identity Federation. All persistent storage is protected by Cloud KMS CMEK keys, and platform activity is archived in an immutable, locked Cloud Storage audit repository.


2. Requirements and current state

2.1. Functional requirements

  • FR-1: Multi-tier environment isolation (REQ-02): The platform foundation must provision distinct, isolated environment tiers for development, staging, and production to host payment workloads. Development and staging implement the corp_workload archetype, while production implements the pci_regulated_workload archetype with strict isolation between non-production and production scopes.
  • FR-2: Dedicated hybrid interconnect connectivity (REQ-03): The platform foundation must establish private, bidirectional hybrid network connectivity between on-premises payment systems and cloud environments over a dedicated interconnect using 10Gbps Dedicated Cloud Interconnect attachments, redundant Cloud Routers, and BGP dynamic routing.
  • FR-3: Centralised egress traffic inspection (REQ-03): The platform foundation must inspect and filter all outbound traffic from cloud environments to the public internet through centralised inspection appliances. Outbound traffic is routed to a central hub transit VPC where virtual firewall appliances perform deep packet inspection and URL filtering before egress.
  • FR-4: Corporate identity federation (REQ-04): The platform foundation must federate corporate identities from Microsoft Entra ID to authenticate administrative users for platform access, integrating single sign-on (SSO) and enterprise role-based access control (RBAC).
  • FR-5: Automated CI/CD pipeline authentication (REQ-01, REQ-04): The platform foundation must authenticate automated GitHub Actions delivery pipelines via Workload Identity Federation using OpenID Connect (OIDC), exchanging GitHub workflow execution tokens for short-lived Google Cloud credentials without static, long-lived service account keys.
  • FR-6: Customer-managed encryption key management (REQ-04): The platform foundation must provide customer-managed encryption key (CMEK) management to encrypt data across platform storage and compute resources, maintaining cryptographic custody over all confidential customer data.
  • FR-7: Centralised audit logging and retention (REQ-02): The platform foundation must aggregate audit logs from all environment tiers into a central log repository with an immutable retention policy, locking log objects to satisfy financial regulatory compliance.

2.2. Non-functional requirements

  • Security, privacy, and compliance:
    • NFR-1 (Regional deployment and data residency): Platform resources must reside in europe-west2 with a warm standby presence in europe-west1, ensuring all customer and payment data remains within the United Kingdom and European Union (REQ-02, estate.regions.primary, estate.regions.secondary, estate.regions.resiliency_tier, estate.data_residency).
    • NFR-2 (Multi-tier environment isolation and PCI perimeter): Separate Google Cloud projects/folders for development, staging, and production; no direct cross-environment VPC peering between production and non-production tiers (REQ-02, governance.environment_tiers).
    • NFR-3 (Hub-and-spoke network topology and private exposure): Shared VPC hub-and-spoke topology with internal-only exposure; external IPs disabled on subnets; default internet routes removed; public inbound traffic denied (REQ-02, REQ-03, networking.exposure, networking.topology).
    • NFR-5 (Centralised egress traffic inspection): Central egress inspection transit VPC; 0.0.0.0/0 traffic routed to inspection appliances; no direct route or NAT bypassing appliances (REQ-03, networking.egress_control.model).
    • NFR-7 (Identity federation and secretless pipeline authentication): Entra ID as single source of truth; Workload Identity Federation for GitHub Actions; service account keys disabled by policy (REQ-04, governance.identity_source_of_truth, governance.pipeline_authentication).
    • NFR-8 (Financial regulatory compliance alignment): Organization policies enforce mandatory guardrails (uniform bucket-level access, CMEK enforcement, public IP restrictions); Security Command Center configured organization-wide for DORA, PCI-DSS v4.0, and ISO 27001 (REQ-02, compliance.frameworks).
    • NFR-9 (Customer-managed key encryption and 90-day rotation): Cloud KMS key rings in europe-west2 and europe-west1; automated rotation period of 90 days (7,776,000 seconds); Org Policy enforcing CMEK (REQ-04, compliance.encryption.type, compliance.encryption.key_rotation_days, compliance.data_classification).
    • NFR-10 (Immutable audit logging and retention): Central log sink exports all administrative and data access logs to an audit bucket; retention policy set to 365 days (31,536,000 seconds) and locked immutably with Bucket Lock (REQ-02, compliance.audit_logging.retention_days, compliance.audit_logging.immutable_retention_policy).
  • Reliability:
    • NFR-4 (10Gbps Dedicated Cloud Interconnect): Redundant 10Gbps dedicated interconnect attachments in primary region across distinct edge availability domains; redundant Cloud Routers with BGP sessions (REQ-03, networking.hybrid_connectivity.enabled, networking.hybrid_connectivity.bandwidth_gbps).
    • NFR-6 (Warm standby disaster recovery objectives): Secondary network and infrastructure in europe-west1 configured for warm standby failover supporting an assumed RTO of 4 hours and RPO of 1 hour (REQ-02, estate.regions.secondary, estate.regions.resiliency_tier).
    • NFR-11 (Platform availability target): Shared networking, Cloud Routers, and transit inspection appliances support continuous 99.9% availability across availability zones (REQ-02).
  • Cost:
    • Infrastructure costs tracked via BigQuery billing exports; storage lifecycle management transitions aged audit logs to colder classes; warm standby operates in pilot-light mode to eliminate idle waste.
  • Operations:
    • NFR-13 (10-Week delivery and automated Infrastructure as Code): Modular Terraform code; remote state backend in Cloud Storage with object versioning and CMEK encryption; ready for workload ingestion within 10 weeks (REQ-01).
    • NFR-14 (24/7 Observability and PR-driven change management): 24/7 centralized monitoring via Google Cloud Operations Suite; alert policies for BGP sessions, load balancer health, and audit sinks; standard resource labeling taxonomy (governance.pipeline_authentication).
  • Performance:
    • Low-latency hybrid transit over 10Gbps dedicated circuits; gVNIC enabled on NVA instances for maximum throughput and high packet-per-second processing; customized, matched MTU sizing across Shared VPC and interconnect VLAN attachments.
  • Sustainability:
    • NFR-12 (Carbon footprint and regional sustainability): Placement restricted to europe-west2 and europe-west1 to balance latency, data residency, and high carbon-free energy (CFE) scores; pilot-light DR minimizes idle compute emissions.

2.3. Current state

  • Current infrastructure:
    • Greenfield deployment mode on Google Cloud (estate.mode: greenfield). No existing Google Cloud projects, VPCs, IAM policies, or infrastructure assets exist. Reading live cloud resources was disabled (cloud_read: false).
    • Core transactional payment processing systems currently operate in an on-premises UK data centre facility.
    • Corporate identity is managed centrally in Microsoft Entra ID with conditional access and multi-factor authentication.
    • Application development, source code, and deployment pipelines reside in GitHub Enterprise with GitHub Actions runners.
  • Pain points and drivers for migration/redesign:
    • Need for rapid, compliant expansion into cloud infrastructure within 10 weeks to support the core payments engine.
    • Regulatory obligations under DORA, PCI-DSS v4.0, and UK financial frameworks requiring multi-region operational resilience, strict perimeter isolation, and immutable audit trails.
    • Requirement for private, low-latency hybrid integration with existing on-premises core payment systems without public internet exposure.

2.4. Dependencies

  • Internal dependencies:
    • Application squads managing runtime payment microservices and containerized workloads.
    • Corporate security and network teams responsible for on-premises IP subnet allocations (RFC 1918) and BGP ASN assignments.
    • Platform operations team responsible for 24/7 incident response and monitoring.
  • External dependencies:
    • Microsoft Entra ID tenant administrators for OpenID Connect / SAML federation and group mapping.
    • GitHub Enterprise organization administrators for Workload Identity Federation trust policy definitions.
    • Telecommunications carriers and colocation data centre facilities for physical 10Gbps cross-connect provisioning to Google Cloud edge points of presence in London.
    • Google Cloud Organization setup and GBP-denominated billing account association.

3. Technical decomposition of the workload

The platform foundation is decomposed into eleven loosely coupled logical components spanning governance, networking, security, identity, and operational lifecycle domains:

+--------------------------------------------------------------------------------------------------+
|                               PLATFORM FOUNDATION ARCHITECTURE                                   |
+--------------------------------------------------------------------------------------------------+
|                                                                                                  |
|  +-------------------------------------+        +---------------------------------------------+  |
|  | C-1: Multi-Tier Environment         |        | C-9: Platform Compliance & Governance       |  |
|  |      Hierarchy & Isolation Boundary |<-------|      Guardrail Controller                   |  |
|  +-------------------------------------+        +---------------------------------------------+  |
|                 ^                                                                                |
|                 |                                                                                |
|  +--------------v----------------------+        +---------------------------------------------+  |
|  | C-4: Transit Network Fabric &       |<------>| C-2: Dedicated Hybrid Network Interconnect  |  |
|  |      Routing Controller             |        |      Gateway (10Gbps to On-Premises)        |  |
|  +-------------------------------------+        +---------------------------------------------+  |
|                 |                                                                                |
|                 v                                                                                |
|  +-------------------------------------+                                                         |
|  | C-3: Centralised Egress Traffic     |------> [ External Public Internet Endpoints ]           |  |
|  |      Inspection Gateway             |                                                         |  |
|  +-------------------------------------+                                                         |  |
|                                                                                                  |
|  +-------------------------------------+        +---------------------------------------------+  |
|  | C-5: Corporate Identity             |        | C-6: Automated Delivery Pipeline Identity   |  |
|  |      Federation Gateway             |        |      Broker                                 |  |
|  +-------------------------------------+        +---------------------------------------------+  |
|                                                                |                                 |
|                                                                v                                 |
|  +-------------------------------------+        +---------------------------------------------+  |
|  | C-7: Cryptographic Key Management & |        | C-10: Declarative Infrastructure            |  |
|  |      Rotation Service               |        |       Provisioning & State Engine           |  |
|  +-------------------------------------+        +---------------------------------------------+  |
|                                                                                                  |
|  +-------------------------------------+        +---------------------------------------------+  |
|  | C-8: Centralised Immutable Audit    |        | C-11: Centralised Operational Telemetry &   |  |
|  |      Log Repository                 |        |       Alerting Engine                       |  |
|  +-------------------------------------+        +---------------------------------------------+  |
+--------------------------------------------------------------------------------------------------+

Component specification

  1. C-1: Multi-Tier Environment Hierarchy & Isolation Boundary: Establishes logically separated structural containers for development, staging, and production tiers. Implements administrative boundaries separating corp_workload from pci_regulated_workload archetypes. Prevents non-production incidents from impacting live payment systems. Restricts resources to europe-west2 and europe-west1.
  2. C-2: Dedicated Hybrid Network Interconnect Gateway: Provides private, high-throughput (10Gbps), low-latency bidirectional hybrid transit between on-premises payment systems and Google Cloud. Terminates physical cross-connects and runs BGP dynamic routing across redundant Cloud Routers in europe-west2, with standby routing in europe-west1.
  3. C-3: Centralised Egress Traffic Inspection Gateway: Authoritative outbound checkpoint for all traffic destined for the public internet or external payment partners. Performs stateful deep packet inspection, threat detection, and URL/FQDN filtering using auto-scaled Network Virtual Appliances behind an internal load balancer.
  4. C-4: Transit Network Fabric & Routing Controller: Acts as the central hub-and-spoke transit backbone. Enforces network segmentation ensuring production PCI environments have zero lateral reachability to non-production tiers. Removes direct internet gateways and suppresses external IP allocation across all workload spokes.
  5. C-5: Corporate Identity Federation Gateway: Integrates corporate single sign-on (SSO) with Microsoft Entra ID as the single source of truth. Synchronizes directory groups to Cloud IAM roles, enforcing corporate MFA and conditional access.
  6. C-6: Automated Delivery Pipeline Identity Broker: Provides keyless Workload Identity Federation for GitHub Actions CI/CD workflows. Validates OIDC JWT tokens and exchanges them for short-lived Google Cloud credentials, eliminating static service account keys.
  7. C-7: Cryptographic Key Management & Rotation Service: Provides centralized custody and lifecycle governance of Customer-Managed Encryption Keys (CMEK) via Cloud KMS. Enforces automatic 90-day key rotation and dual-region availability across primary (europe-west2) and standby (europe-west1) regions.
  8. C-8: Centralised Immutable Audit Log Repository: Centralizes administrative, system, and data access audit logs organization-wide. Enforces an immutable retention lock (Bucket Lock) for 365 days, preventing modification or premature deletion by any administrator.
  9. C-9: Platform Compliance & Governance Guardrail Controller: Enforces declarative preventative and detective security guardrails via Organization Policy Service and Security Command Center. Blocks public IP assignment, enforces CMEK and uniform bucket-level access, and confines resource locations to approved regions.
  10. C-10: Declarative Infrastructure Provisioning & State Engine: Orchestrates automated, drift-free Terraform provisioning. Manages remote state in Cloud Storage with object versioning, CMEK encryption, and automated lifecycle cleanup.
  11. C-11: Centralised Operational Telemetry & Alerting Engine: Continuously tracks platform health, Interconnect BGP sessions, inspection appliance capacity, and log sink exports via Cloud Monitoring, alerting 24/7 operations upon anomaly or degradation.

Component Requirements Traceability Matrix

Component ID Component Name Functional Requirements Non-Functional Requirements Scope / Customer Intent Drivers
C-1 Multi-Tier Environment Hierarchy & Isolation Boundary FR-1 NFR-1, NFR-2, NFR-8 REQ-02, Environment isolation, PCI-DSS boundary
C-2 Dedicated Hybrid Network Interconnect Gateway FR-2 NFR-4, NFR-6, NFR-11 REQ-03, 10Gbps hybrid link, on-premises core payments
C-3 Centralised Egress Traffic Inspection Gateway FR-3 NFR-3, NFR-5 REQ-03, Outbound traffic inspection appliances
C-4 Transit Network Fabric & Routing Controller FR-1, FR-2, FR-3 NFR-3, NFR-6, NFR-11 REQ-02, REQ-03, Hub-and-spoke Shared VPC topology
C-5 Corporate Identity Federation Gateway FR-4 NFR-7 REQ-04, Microsoft Entra ID single sign-on
C-6 Automated Delivery Pipeline Identity Broker FR-5 NFR-7, NFR-13 REQ-01, REQ-04, GitHub Actions Workload Identity
C-7 Cryptographic Key Management & Rotation Service FR-6 NFR-1, NFR-9 REQ-04, Customer-managed keys, 90-day rotation
C-8 Centralised Immutable Audit Log Repository FR-7 NFR-10, NFR-14 REQ-02, Central audit logging, 365-day locked retention
C-9 Platform Compliance & Governance Guardrail Controller FR-1 NFR-1, NFR-2, NFR-8, NFR-12 REQ-02, Regional residency, DORA / PCI-DSS guardrails
C-10 Declarative Infrastructure Provisioning & State Engine FR-5 NFR-13, NFR-14 REQ-01, 10-week delivery, PR-driven Terraform IaC
C-11 Centralised Operational Telemetry & Alerting Engine — NFR-11, NFR-14 REQ-02, 99.9% platform availability, 24/7 observability

4. Proposed solution architecture

4.1. Google Cloud products and features mapping

Component Recommended Google Cloud product/feature Justification and citations Alternatives considered Pros and cons of alternatives
C-1: Multi-Tier Environment Hierarchy & Isolation Boundary Google Cloud Resource Manager Resource Manager provides hierarchical organization nodes (Folders) and trust boundaries (Projects) to isolate resources, enforce IAM, and apply Organization Policies at scale (Google Cloud Resource Hierarchy). None Pros: N/A
Cons: N/A - Resource Manager is the fundamental required service for structuring environments in Google Cloud.
C-2: Dedicated Hybrid Network Interconnect Gateway Cloud Interconnect (Dedicated) Provides a direct, physical 10Gbps connection from on-premises to Google Cloud, meeting the strict NFR-4 requirement for a dedicated 10Gbps link and low latency (Cloud Interconnect Overview). Partner Interconnect Pros: Easier to provision through a service provider; may not require physical colocation.
Cons: Throughput, SLAs, and routing depend on the partner. Given the requirement for a dedicated 10Gbps link, Dedicated Interconnect is required over Partner.
C-3: Centralised Egress Traffic Inspection Gateway Compute Engine (Network Virtual Appliances) Mandated by NFR-5 and FR-3 to deploy centralised "inspection appliances". Deploying third-party NVAs on Compute Engine in Managed Instance Groups behind an Internal Passthrough Load Balancer provides stateful packet inspection, URL filtering, and threat detection while allowing standard enterprise firewall policies (Advanced Network Security). Cloud NGFW Enterprise Pros: Fully managed, cloud-native intrusion prevention system (IPS) and URL filtering without the overhead of managing VMs or high availability clusters.
Cons: While a vendor was left to be decided, NVAs provide exact feature parity with on-premises hardware firewalls for a direct policy match. Cloud NGFW is the managed alternative.
C-4: Transit Network Fabric & Routing Controller Virtual Private Cloud (Shared VPC) NFR-3 explicitly mandates a "Shared VPC hub-and-spoke topology." Shared VPC allows a central host project to manage the network fabric while allowing spoke environments to deploy resources into isolated projects, maintaining centralized network control (Shared VPC Overview). VPC Network Peering Pros: Completely decentralized administration; no need for a central host project.
Cons: Lacks centralized IAM control for subnets and does not support transitive routing natively. NFR-3 mandates Shared VPC.
C-5: Corporate Identity Federation Gateway Cloud Identity NFR-7 explicitly permits Cloud Identity or Workforce Identity Federation. Cloud Identity acts as an identity proxy, synchronizing users and groups from Microsoft Entra ID via SAML 2.0 / SCIM, allowing Google Cloud IAM to leverage existing corporate identities for single sign-on and role-based access control mapped to groups (Federating Google Cloud with Active Directory). Workforce Identity Federation Pros: Sync-less architecture; requires only one account (Entra ID) and dynamically evaluates claims on login.
Cons: Relies entirely on Entra ID for group assertions and does not support post-SSO MFA within Google Cloud natively. Cloud Identity is preferred for deep RBAC group integration.
C-6: Automated Delivery Pipeline Identity Broker Workload Identity Federation FR-5 requires workload identity federation to authenticate GitHub Actions without persistent keys. Workload Identity Federation validates OIDC tokens from GitHub and exchanges them for short-lived Google Cloud credentials (Workload Identity Federation). Service Account Keys Pros: Simple to configure and widely supported by legacy tools.
Cons: Requires storing, managing, and rotating static credentials, which violates the requirement for deployment "without persistent keys".
C-7: Cryptographic Key Management & Rotation Service Cloud Key Management Service (Cloud KMS) FR-6 and NFR-9 mandate customer-managed encryption key (CMEK) management with 90-day automatic rotation. Cloud KMS provides the capability to create, automatically rotate, and manage encryption keys across Google Cloud services (Cloud KMS Documentation). Cloud HSM Pros: Provides hardware-backed keys (FIPS 140-2 Level 3) for the highest level of regulatory compliance.
Cons: Higher cost; requirements specify CMEK, which Cloud KMS software keys fulfil natively.
C-8: Centralised Immutable Audit Log Repository Cloud Storage To achieve an "immutable retention policy" (NFR-10), Cloud Storage with Bucket Lock provides SEC-compliant WORM (Write Once Read Many) immutability. Logs are routed here via Cloud Logging log sinks (Cloud Storage Bucket Lock). Cloud Logging (Log Buckets) Pros: Native log querying via Log Analytics and built-in retention configuration.
Cons: Cloud Logging retention policies can be configured, but Cloud Storage Bucket Lock provides a more stringent, compliance-grade immutability lock for long-term regulatory retention.
C-9: Platform Compliance & Governance Guardrail Controller Organization Policy Service NFR-8 mandates preventative security guardrails. Organization Policy Service allows centralized restrictions across the resource hierarchy, acting as a preventative gatekeeper to block non-compliant resource configurations such as public IP assignment or disabled CMEK (Organization Policy Overview). Security Command Center (SCC) Pros: Provides continuous detective controls, vulnerability scanning, and compliance monitoring mapping to PCI-DSS and ISO 27001.
Cons: Primarily a detective tool; it does not natively block resource creation. SCC is used alongside Organization Policy Service as a complement.
C-10: Declarative Infrastructure Provisioning & State Engine Cloud Storage NFR-13 requires automated Terraform provisioning with state stored in a dedicated remote backend with object versioning and encryption. Cloud Storage is the native Google Cloud service for hosting Terraform remote state securely with CMEK support (Terraform State in Cloud Storage). Terraform Cloud Pros: Managed state storage and execution environment providing remote execution and policy enforcement.
Cons: Requires an external SaaS subscription; Cloud Storage is native, highly durable, and easily supports CMEK.
C-11: Centralised Operational Telemetry & Alerting Engine Cloud Monitoring NFR-14 mandates 24/7 centralized monitoring, telemetry, and alerting. Cloud Monitoring (part of Google Cloud Operations Suite) is the native solution for tracking availability, creating dashboards, and triggering automated alerts upon threshold breaches (Cloud Monitoring Documentation). Third-party APM (e.g., Datadog) Pros: Feature-rich with broad enterprise adoption and extensive multi-cloud integrations.
Cons: Introduces an external dependency and additional licensing cost; Cloud Monitoring is built-in and tightly integrated with all Google Cloud resources.

All recommended Google Cloud products are verified as generally available, fully supported, and compliant with current platform standards.

4.2. Architecture diagram

flowchart LR
    n0["Dev Folder<br/>Resource Manager"]
    n1["Staging Folder<br/>Resource Manager"]
    n2["Production Folder<br/>Resource Manager"]
    n3["Host Project<br/>Virtual Private Cloud"]
    n4["Hub Network<br/>Virtual Private Cloud"]
    n5["Dev Network<br/>Virtual Private Cloud"]
    n6["Staging Network<br/>Virtual Private Cloud"]
    n7["Production Network<br/>Virtual Private Cloud"]
    n8["Dev Subnetwork<br/>Virtual Private Cloud"]
    n9["Staging Subnetwork<br/>Virtual Private Cloud"]
    n10["Production Subnetwork<br/>Virtual Private Cloud"]
    n11["Hub-Prod Peering<br/>Virtual Private Cloud"]
    n12["Hub-Dev Peering<br/>Virtual Private Cloud"]
    n13["Hub-Stg Peering<br/>Virtual Private Cloud"]
    n14["Interconnect Router 1<br/>Cloud Interconnect"]
    n15["Interconnect Router 2<br/>Cloud Interconnect"]
    n16["VLAN Attachment 1<br/>Cloud Interconnect"]
    n17["VLAN Attachment 2<br/>Cloud Interconnect"]
    n18["Standby Router<br/>Cloud Interconnect"]
    n19["Standby VLAN Attachment<br/>Cloud Interconnect"]
    n20["Standby Subnetwork<br/>Virtual Private Cloud"]
    n21["NVA Instance Template<br/>Compute Engine"]
    n22["NVA MIG<br/>Compute Engine"]
    n23["NVA Health Check<br/>Compute Engine"]
    n24["NVA Forwarding Rule<br/>Compute Engine"]
    n25["NVA Autoscaler<br/>Compute Engine"]
    n26["Inbound Deny Firewall<br/>Virtual Private Cloud"]
    n27["Cloud Identity Group<br/>Cloud Identity"]
    n28["Workload Identity Pool<br/>Workload Identity Federation"]
    n29["WIF Provider<br/>Workload Identity Federation"]
    n30["KMS Key Ring Primary<br/>Cloud KMS"]
    n31["KMS Crypto Key Primary<br/>Cloud KMS"]
    n32["KMS Key Ring Standby<br/>Cloud KMS"]
    n33["KMS Crypto Key Standby<br/>Cloud KMS"]
    n34["Audit Log Bucket<br/>Cloud Storage"]
    n35["Org Log Sink<br/>Cloud Storage"]
    n36["Org Policy Skip Default Network<br/>Organization Policy Service"]
    n37["Org Policy VM External IP<br/>Organization Policy Service"]
    n38["Org Policy Resource Locations<br/>Organization Policy Service"]
    n39["Org Policy Service Account Keys<br/>Organization Policy Service"]
    n40["SCC Config<br/>Organization Policy Service"]
    n41["Prod Org Policy<br/>Organization Policy Service"]
    n42["TF State Bucket<br/>Cloud Storage"]
    n43["Alert Policy Interconnect<br/>Cloud Monitoring"]
    n44["Alert Policy LB<br/>Cloud Monitoring"]
    n45["Dev Route to NVA<br/>Virtual Private Cloud"]
    n46["Staging Route to NVA<br/>Virtual Private Cloud"]
    n47["Production Route to NVA<br/>Virtual Private Cloud"]
    n48["Pipeline Service Account<br/>Workload Identity Federation"]
    n49["Pipeline SA IAM Member<br/>Workload Identity Federation"]
    n50["Org Policy UBLA<br/>Organization Policy Service"]
    n51["Org Policy CMEK Enforce<br/>Organization Policy Service"]
    n52["Alert Policy Audit Logs<br/>Cloud Monitoring"]
    n5 -->|peers with| n4
    n6 -->|peers with| n4
    n7 -->|peers with| n4
    n45 -->|routes to| n24
    n46 -->|routes to| n24
    n47 -->|routes to| n24
    n29 -->|authenticates via| n28
    n35 -->|exports to| n34
    n16 -->|attaches to| n14
    n17 -->|attaches to| n15
    n19 -->|attaches to| n18
    n22 -->|uses| n21
    n24 -->|forwards to| n22
    n22 -->|checked by| n23
    n25 -->|scales| n22
    n31 -->|belongs to| n30
    n33 -->|belongs to| n32
    n49 -->|grants access to| n48

4.3. Architecture description

The architecture comprises fifty-three infrastructure elements mapped across eleven logical subsystems, structured to deliver full regulatory compliance, network segmentation, and operational resilience.

Architectural Elements Inventory

Id Name Product Resource Type Component Description
E-1 Dev Folder Resource Manager google_folder C-1 Organizational folder isolating development tier workloads.
E-2 Staging Folder Resource Manager google_folder C-1 Organizational folder hosting pre-production staging workloads.
E-3 Production Folder Resource Manager google_folder C-1 Highest-security administrative folder hosting the PCI-DSS Cardholder Data Environment.
E-4 Host Project Virtual Private Cloud google_compute_shared_vpc_host_project C-4 Central administrative Shared VPC host project.
E-5 Hub Network Virtual Private Cloud google_compute_network C-4 Central transit VPC network in the host project with global routing and custom MTU.
E-40 Dev Network Virtual Private Cloud google_compute_network C-4 Spoke VPC network for development with default routes deleted at creation.
E-41 Staging Network Virtual Private Cloud google_compute_network C-4 Spoke VPC network for staging with default routes deleted at creation.
E-42 Production Network Virtual Private Cloud google_compute_network C-4 Spoke VPC network for production CDE with default routes deleted at creation.
E-6 Dev Subnetwork Virtual Private Cloud google_compute_subnetwork C-4 Regional subnetwork in europe-west2 with Private Google Access enabled.
E-7 Staging Subnetwork Virtual Private Cloud google_compute_subnetwork C-4 Regional subnetwork in europe-west2 with Private Google Access enabled.
E-8 Production Subnetwork Virtual Private Cloud google_compute_subnetwork C-4 Isolated regional subnetwork in europe-west2 hosting the core payments engine.
E-37 Standby Subnetwork Virtual Private Cloud google_compute_subnetwork C-4 Secondary regional subnetwork in europe-west1 supporting warm standby DR.
E-43 Hub-Prod Peering Virtual Private Cloud google_compute_network_peering C-4 Bi-directional VPC peering interconnecting Hub Network and Production Network (R-3).
E-44 Hub-Dev Peering Virtual Private Cloud google_compute_network_peering C-4 Bi-directional VPC peering interconnecting Hub Network and Dev Network (R-1).
E-45 Hub-Stg Peering Virtual Private Cloud google_compute_network_peering C-4 Bi-directional VPC peering interconnecting Hub Network and Staging Network (R-2).
E-9 Interconnect Router 1 Cloud Interconnect google_compute_router C-2 Primary Cloud Router in europe-west2 with BGP dynamic routing for hybrid connectivity.
E-10 Interconnect Router 2 Cloud Interconnect google_compute_router C-2 Redundant secondary Cloud Router in europe-west2 providing dual-zone control-plane redundancy.
E-11 VLAN Attachment 1 Cloud Interconnect google_compute_interconnect_attachment C-2 10Gbps Dedicated Interconnect attachment in Availability Domain 1 (R-9).
E-12 VLAN Attachment 2 Cloud Interconnect google_compute_interconnect_attachment C-2 10Gbps Dedicated Interconnect attachment in Availability Domain 2 (R-10).
E-35 Standby Router Cloud Interconnect google_compute_router C-2 Standby Cloud Router provisioned in europe-west1 for regional disaster recovery.
E-36 Standby VLAN Attachment Cloud Interconnect google_compute_interconnect_attachment C-2 Standby 10Gbps Dedicated Interconnect attachment in europe-west1 (R-11).
E-13 NVA Instance Template Compute Engine google_compute_instance_template C-3 VM template specifying next-generation firewall image and high-throughput gVNIC interfaces.
E-14 NVA MIG Compute Engine google_compute_region_instance_group_manager C-3 Regional Managed Instance Group across multiple zones in europe-west2 (R-12).
E-15 NVA Health Check Compute Engine google_compute_region_health_check C-3 Regional TCP health check with 5-second interval for rapid failure detection (R-14).
E-16 NVA Forwarding Rule Compute Engine google_compute_forwarding_rule C-3 Internal passthrough Network Load Balancer forwarding rule forwarding egress flows to NVAs (R-13).
E-17 NVA Autoscaler Compute Engine google_compute_region_autoscaler C-3 Regional autoscaler dynamically scaling the NVA MIG between 2 and 5 instances (R-15).
E-47 Inbound Deny Firewall Virtual Private Cloud google_compute_firewall C-4 Ingress deny-all firewall rule blocking direct public internet access (0.0.0.0/0).
E-18 Cloud Identity Group Cloud Identity google_cloud_identity_group C-5 Enterprise directory group synchronized from Microsoft Entra ID for platform RBAC.
E-19 Workload Identity Pool Workload Identity Federation google_iam_workload_identity_pool C-6 Central trust boundary for federating external CI/CD delivery pipelines.
E-20 WIF Provider Workload Identity Federation google_iam_workload_identity_pool_provider C-6 OIDC identity provider verifying GitHub Actions tokens with repo-level attribute constraints (R-7).
E-54 Pipeline Service Account Workload Identity Federation google_service_account C-6 Least-privilege IAM service account used by automated GitHub Actions workflows.
E-55 Pipeline SA IAM Member Workload Identity Federation google_service_account_iam_member C-6 IAM member binding granting roles/iam.workloadIdentityUser to the GitHub principal set (R-18).
E-21 KMS Key Ring Primary Cloud KMS google_kms_key_ring C-7 Regional cryptographic key ring located in europe-west2.
E-22 KMS Crypto Key Primary Cloud KMS google_kms_crypto_key C-7 Primary symmetric CMEK encryption key configured with 90-day rotation (R-16).
E-23 KMS Key Ring Standby Cloud KMS google_kms_key_ring C-7 Regional cryptographic key ring provisioned in europe-west1 for warm standby DR.
E-24 KMS Crypto Key Standby Cloud KMS google_kms_crypto_key C-7 Standby symmetric CMEK key in europe-west1 with 90-day rotation (R-17).
E-25 Audit Log Bucket Cloud Storage google_storage_bucket C-8 Central audit bucket with locked 365-day retention policy (Bucket Lock) and lifecycle tiering.
E-26 Org Log Sink Cloud Storage google_logging_organization_sink C-8 Organization-level log sink exporting administrative and data access logs to E-25 (R-8).
E-27 Org Policy Skip Default Network Organization Policy Service google_org_policy_policy C-9 Enforces compute.skipDefaultNetworkCreation globally across all projects.
E-28 Org Policy VM External IP Organization Policy Service google_org_policy_policy C-9 Enforces compute.vmExternalIpAccess with deny_all = true.
E-29 Org Policy Resource Locations Organization Policy Service google_org_policy_policy C-9 Enforces gcp.resourceLocations restricting resources to europe-west2 and europe-west1.
E-30 Org Policy Service Account Keys Organization Policy Service google_org_policy_policy C-9 Enforces iam.disableServiceAccountKeyCreation across the organization.
E-56 Org Policy UBLA Organization Policy Service google_org_policy_policy C-9 Enforces storage.uniformBucketLevelAccess on all Cloud Storage buckets.
E-57 Org Policy CMEK Enforce Organization Policy Service google_org_policy_policy C-9 Enforces gcp.restrictNonCmekServices requiring customer-managed keys.
E-46 Prod Org Policy Organization Policy Service google_org_policy_policy C-9 Dedicated policy enforcing compute.restrictXpnProjectLienRemoval on the Production folder.
E-38 SCC Config Organization Policy Service google_scc_organization_custom_module C-9 Organization Security Command Center custom module for continuous compliance monitoring.
E-31 TF State Bucket Cloud Storage google_storage_bucket C-10 Dedicated remote backend bucket with object versioning, CMEK encryption, and lifecycle rules.
E-32 Alert Policy Interconnect Cloud Monitoring google_monitoring_alert_policy C-11 Alert policy monitoring Cloud Interconnect BGP session availability (session_up).
E-33 Alert Policy LB Cloud Monitoring google_monitoring_alert_policy C-11 Alert policy tracking NVA Load Balancer backend health and latencies.
E-58 Alert Policy Audit Logs Cloud Monitoring google_monitoring_alert_policy C-11 Alert policy tracking Cloud Logging organization export sink error rates.
E-51 Dev Route to NVA Virtual Private Cloud google_compute_route C-4 Custom route in Dev Network directing 0.0.0.0/0 to NVA load balancer E-16 (R-4).
E-52 Staging Route to NVA Virtual Private Cloud google_compute_route C-4 Custom route in Staging Network directing 0.0.0.0/0 to NVA load balancer E-16 (R-5).
E-53 Production Route to NVA Virtual Private Cloud google_compute_route C-4 Custom route in Production Network directing 0.0.0.0/0 to NVA load balancer E-16 (R-6).

Task and Data Flows

On-Premises Core System
       │
       ▼ (10Gbps Dedicated Interconnect / BGP)
[VLAN Attachment 1 / 2] (E-11, E-12)
       │
       ▼
[Interconnect Router 1 / 2] (E-9, E-10)
       │
       ▼
[Hub Network] (E-5)
       │
       ├─────────────────────────────────┐
       ▼ (Hub-Prod Peering R-3)          ▼ (Routes R-4, R-5, R-6)
[Production Network] (E-42)       [NVA Forwarding Rule] (E-16)
       │                                 │
       ▼                                 ▼ (Forwards R-13)
[Production Subnet] (E-8)          [NVA MIG Backends] (E-14)
(Core Payments Engine)                   │ (Deep Packet Inspection)
       │                                 ▼
       └──────(Outbound Egress)──► Public Internet (0.0.0.0/0)
  1. Hybrid Payment Transaction Flow (On-Premises to Cloud Workload):
    • Ingress: Core on-premises payment systems initiate transactions over physical 10Gbps cross-connects terminating on VLAN Attachment 1 (E-11) and VLAN Attachment 2 (E-12) in europe-west2.
    • Routing: Dynamic BGP sessions on Interconnect Router 1 (E-9) and Interconnect Router 2 (E-10) advertise RFC 1918 CIDRs and route traffic into Hub Network (E-5).
    • Transit: Traffic crosses Hub-Prod Peering (E-43) directly into Production Network (E-42) and terminates on payment engine VMs in Production Subnetwork (E-8). Non-production tiers are completely bypassed.
    • Failover: If a regional outage occurs in europe-west2, BGP dynamically routes transactions to Standby VLAN Attachment (E-36) and Standby Router (E-35) in europe-west1 into Standby Subnetwork (E-37), satisfying the 4-hour RTO.
  2. Centralised Outbound Egress Inspection Flow (Cloud to Public Internet):
    • Initiation: Workloads in Production Subnetwork (E-8) (or dev/staging subnets) generate outbound requests destined for public endpoints.
    • Route Redirection: Spoke VPCs lack default internet gateways (delete_default_routes_on_create = true). Custom static routes (E-51, E-52, E-53) intercept 0.0.0.0/0 and point to NVA Forwarding Rule (E-16).
    • Load Balancing & Inspection: The Internal Passthrough Network Load Balancer routes traffic to healthy instances in NVA MIG (E-14). The appliances perform stateful deep packet inspection, threat scanning, and URL filtering.
    • Egress: Clean traffic is SNAT'd and egresses to the public internet via the hub's external interface; malicious or unauthorized flows are dropped.
  3. Administrative Authentication & Corporate SSO Flow:
    • Administrative personnel access the Google Cloud console or CLI.
    • Cloud Identity redirects authentication to Microsoft Entra ID, where conditional access policies and multi-factor authentication are verified.
    • Entra ID returns SAML/OIDC assertions mapping user memberships to Cloud Identity Group (E-18).
    • Google Cloud IAM grants short-lived, role-scoped administrative permissions across Dev Folder (E-1), Staging Folder (E-2), or Production Folder (E-3).
  4. Automated CI/CD Delivery Pipeline Flow (Keyless Workload Identity Federation):
    • An approved pull request is merged in the GitHub Enterprise repository.
    • The GitHub Actions workflow requests an OIDC token signed by GitHub's authority (token.actions.githubusercontent.com).
    • The runner presents the token to Google Cloud STS via Workload Identity Pool (E-19) and WIF Provider (E-20).
    • E-20 validates the token claims and repository attribute conditions (assertion.repository == 'org/repo').
    • Pipeline SA IAM Member (E-55) allows the pipeline principal to impersonate Pipeline Service Account (E-54).
    • The pipeline executes Terraform using short-lived credentials, reading and writing remote state in TF State Bucket (E-31) encrypted with KMS Crypto Key Primary (E-22). No static private keys exist.
  5. Cryptographic Key Management & Data Encryption Flow:
    • When a data volume, database, or storage bucket is provisioned in Production Folder (E-3), Org Policy CMEK Enforce (E-57) mandates CMEK.
    • The service requests envelope encryption keys from KMS Key Ring Primary (E-21) using KMS Crypto Key Primary (E-22).
    • Cloud KMS automatically rotates the key every 90 days (7,776,000 seconds). New data is encrypted with the newest version; existing data remains decryptable seamlessly.
    • Standby keys on KMS Key Ring Standby (E-23) in europe-west1 ensure localized cryptographic capability during DR.
  6. Centralised Immutable Audit Logging Flow:
    • Administrative activities, IAM changes, network routing modifications, and data access events across all folders and projects are intercepted by Org Log Sink (E-26).
    • E-26 exports audit streams in real time to Audit Log Bucket (E-25).
    • Audit Log Bucket enforces Bucket Lock with an immutable 365-day retention policy (31,536,000 seconds). The policy cannot be shortened or deleted by any administrative identity.
    • Lifecycle rules transition objects older than 90 days to Coldline storage to minimize retention costs.
  7. Telemetry, Health Monitoring & Operational Alerting Flow:
    • Google Cloud Operations Suite scrapes real-time telemetry across hybrid circuits and appliance tiers.
    • Alert Policy Interconnect (E-32) monitors BGP session state; Alert Policy LB (E-33) tracks NVA health check responses and backend latency; Alert Policy Audit Logs (E-58) monitors sink export errors.
    • Breaches of availability or error thresholds immediately notify 24/7 central platform operations for remediation.

5. Design and configuration recommendations

5.1. Security, privacy, and compliance

  • Organization Policy Guardrails: Enforce strict preventative constraints organization-wide: disable default VPC creation (compute.skipDefaultNetworkCreation), restrict public IP assignment (compute.vmExternalIpAccess), ban service account key generation (iam.disableServiceAccountKeyCreation), enforce uniform bucket access (storage.uniformBucketLevelAccess), restrict services without CMEK (gcp.restrictNonCmekServices), and restrict resource creation strictly to europe-west2 and europe-west1 (gcp.resourceLocations). Apply production-specific constraints on Production Folder (E-3).
  • Centralised Egress Inspection: Force all outbound traffic from spoke VPCs through an internal passthrough load balancer directing flows to Network Virtual Appliances (NVAs) in the transit hub. Enforce deep packet inspection, TLS inspection, and strict domain allowlisting.
  • Cryptographic Key Management: Deploy Cloud KMS key rings in both europe-west2 and europe-west1. Enforce automated 90-day rotation (7,776,000 seconds) on all symmetric keys to satisfy PCI-DSS v4.0 Requirement 3.6 and DORA cryptographic standards.
  • Workload Identity Federation: Restrict CI/CD delivery pipelines to specific GitHub Enterprise repositories using CEL attribute conditions (assertion.repository == 'org/repo'). Completely eliminate downloadable service account keys.
  • Audit Trail Immutability: Configure Cloud Storage Bucket Lock with an immutable 365-day retention period. Enforce uniform bucket-level access to prevent discretionary object-level tampering.

5.2. Reliability

  • High-Availability Hybrid Connectivity: Provision redundant 10Gbps Dedicated Interconnect VLAN attachments across two distinct Edge Availability Domains in europe-west2, paired with dual Cloud Routers running BGP dynamic routing with tuned keepalive (20s) and hold timers (60s). Provision standby Interconnect routing in europe-west1 for warm standby disaster recovery.
  • Resilient Inspection Tier: Deploy inspection NVAs in a regional Managed Instance Group (MIG) distributed across multiple zones (europe-west2-a, europe-west2-b). Implement auto-healing with aggressive regional health checks (5s check interval) and autoscaling (2 to 5 instances) to tolerate zone failures without traffic loss.
  • Disaster Recovery Posture: Maintain the secondary landing zone in europe-west1 in a warm standby pilot-light posture. Ensure automated Terraform scripts can rapidly scale networking and compute to meet the 4-hour RTO and 1-hour RPO.

5.3. Operational excellence

  • Infrastructure as Code Governance: Structure all landing zone components as modular Terraform configurations. Store Terraform state in a centralized Cloud Storage bucket configured with object versioning, CMEK encryption, and automated lifecycle rules to prune non-current versions.
  • GitOps CI/CD Delivery: Manage all infrastructure changes via GitHub pull requests requiring peer reviews, automated security linting, pre-flight dry runs (terraform plan), and Workload Identity Federation authentication.
  • Centralized Telemetry & Alerting: Configure Cloud Monitoring alert policies for Dedicated Interconnect BGP session health, NVA load balancer backend latencies, and organization log sink delivery metrics. Enforce standard metadata labeling (env, cost-centre, archetype) across 100% of resources.

5.4. Cost optimization

  • Audit Storage Lifecycle Management: Apply Cloud Storage Object Lifecycle Management to the centralized audit bucket (E-25), automatically transitioning log objects older than 90 days from Standard to Coldline storage, minimizing compliance retention expenses.
  • Pilot Light Standby Optimization: Keep standby compute resources in europe-west1 at minimal or zero footprint during baseline operations, scaling out only during failover testing or active disaster recovery events.
  • Committed Use Discounts (CUDs): After establishing baseline traffic and NVA appliance utilization in production, purchase 1-year or 3-year Compute Engine Committed Use Discounts for baseline VM instances, capturing Sustained Use Discounts (SUDs) on variable capacity.

5.5. Performance efficiency

  • gVNIC High-Throughput Networking: Configure NVA Compute Engine instances with Google Virtual NIC (GVNIC) network interfaces to ensure maximum throughput and low-latency packet handling.
  • MTU Alignment: Standardize maximum transmission unit (MTU) sizing across the Shared VPC hub network and Dedicated Interconnect VLAN attachments (e.g., 1460 or 1500 bytes) to prevent packet fragmentation and transmission latency overhead.
  • Internal Passthrough Load Balancing: Use Internal Passthrough Network Load Balancing to forward egress traffic to NVAs with zero proxy overhead, preserving client IP headers and achieving line-rate forwarding.

5.6. Sustainability

  • Regional Carbon Optimization: Confine primary workloads to europe-west2 and warm standby to europe-west1. Leverage europe-west1 (which boasts high Carbon-Free Energy / CFE% scores) for batch payment reconciliation and non-latency-sensitive processing.
  • Idle Infrastructure Minimization: Implement autoscaling on inspection tiers to ensure instances scale down during off-peak transaction hours. Utilize Cloud Storage lifecycle policies to eliminate orphaned state objects and decommission dark data.

Questions for the customer

The request does not say enough to settle these. They are not faults in the design: each is something to ask the customer, and the answer may change a recommendation.

Pillar About Question
security Are safe libraries and application frameworks used to prevent common vulnerabilities? What software frameworks, approved package repositories, and dependency security standards (e.g., Google Cloud Assured Open Source Software) are utilized across the payment engine codebase?
security Is a risk assessment performed using industry standards? Has your organization performed a formal risk assessment against industry standards (such as ISO/IEC 27005 or NIST SP 800-30) for this cloud payment platform migration?
security Are defenses validated through periodic testing or red-teaming? What cadence, tooling, and external testing frameworks (such as DORA Threat-Led Penetration Testing / TLPT) does your security organization execute to validate system defenses?
reliability User-focused SLIs and SLOs are explicitly defined and actively monitored. What specific Service Level Indicators (SLIs) and Service Level Objectives (SLOs)—such as transaction latency percentiles, error rate thresholds, and availability targets—are established for the core payment engine?
reliability Regular backup schedules are in place, and restoration processes are routinely tested. What are your target Recovery Point Objective (RPO) and Recovery Time Objective (RTO) for payment data and configuration, and what is your schedule for testing restoration processes?
reliability Game days or chaos engineering practices are regularly held to validate failure recovery. Does your organisation conduct regular game days or chaos engineering exercises to validate failure recovery and regional failover procedures between europe-west2 and europe-west1?
reliability A formalized, blameless postmortem process exists to ensure organizational learning from operational incidents. Does your organisation have an established, blameless postmortem process to review operational incidents, identify root causes, and track corrective reliability actions?
operational-excellence A formal framework or set of criteria exists to assess operational readiness before production deployment. How do you define and measure operational readiness for your cloud workloads, and what specific criteria or governance gates are required before production deployment?
operational-excellence Incident response roles and communication channels are clearly defined and documented. Describe your incident management process, including roles, responsibilities, and communication channels.
operational-excellence A structured, blameless post-mortem process is followed for all major incidents. How do you conduct post-incident reviews (PIRs) to identify root causes and implement preventive measures?
operational-excellence A documented strategy is in place for regularly reviewing and adapting cloud operations to industry advancements. How do you ensure that your cloud operations are continuously adapting to meet evolving business needs and technological advancements?
cost-optimization Managed Services: Serverless options are preferred for new workloads unless specific technical constraints exist. What are the runtime requirements and technical constraints of the core payments engine (for example, containerized workloads compatible with managed serverless services like Cloud Run or GKE Autopilot versus VM-based COTS software requiring dedicated Compute Engine instances)?
performance-optimization Initial provisioning is based on load testing or historical data rather than general estimates. What historical transaction throughput (average and peak TPS) and latency profiles from your on-premises payments engine will be used to baseline and size initial Google Cloud compute, interconnect, and inspection capacity?
performance-optimization Caching is implemented at multiple layers (CDN, in-memory, or browser) to offload backend systems. What caching strategies and data residency/PCI-DSS boundaries apply to your payment processing flows, and can non-sensitive reference or token validation data be cached in-memory using managed services such as Memorystore for Redis/Valkey?
performance-optimization The architecture uses microservices or decoupled components to allow independent scaling. Is the core payments engine architected as decoupled microservices or asynchronous processing pipelines (e.g., separating authorization, clearing, settlement, and fraud detection) that can scale independently?
performance-optimization Resource utilization is reviewed regularly to eliminate idle overhead and balance cost with performance. What operational process and review cadence does your infrastructure team follow to analyse capacity utilisation, right-size compute and storage tiers, and optimize warm standby resource overhead in europe-west1?
sustainability The organization embraces a shared responsibility and shared fate model for sustainability. How does your organization define its sustainability boundaries and targets with Google Cloud, and what formal shared responsibility commitments are in place?
sustainability Collaborations with sustainable partners are prioritized and multi-cloud data portability is leveraged, or internal practices align with recognized global standards like the Green Software Foundation. Does your organization align its software and cloud architecture practices with external sustainability frameworks such as the Green Software Foundation or Greenhouse Gas Protocol?
sustainability The download size of website products is measured and maintained against a strict budget, or CI/CD pipelines automate the minimization and compression of HTML, CSS, and JS files. Does the payment platform deployment encompass merchant- or consumer-facing web applications, and do delivery pipelines enforce web asset size budgets?
sustainability Static sites or Progressive Web Apps (PWAs) are preferred for faster loading, or DOM manipulation is minimized to reduce device power consumption. If client-facing web interfaces are included in scope, are they designed using static hosting or Progressive Web App principles to minimize client-side energy consumption?
sustainability A formal GreenOps function defines accountability for carbon reduction targets, or verified Carbon Footprint data from BigQuery supports formal ESG disclosures. Does your organization have an established GreenOps or sustainability function accountable for tracking and meeting cloud carbon reduction targets?
sustainability Abstract carbon metrics are transformed into tangible progress indicators in annual reports, or sustainability is treated as a first-class technical requirement (NFR) tied to KPIs and performance reviews. Are carbon efficiency metrics embedded into your technical KPIs, non-functional requirements (NFRs), and engineering performance reviews?
sustainability Training tailored to specific job roles (e.g., developers on code efficiency, FinOps on carbon unit economics) is provided, or teams are formally trained to access and interpret carbon footprint data. Do you provide role-specific training for engineers and operations staff on green cloud architectural patterns and interpreting Carbon Footprint data?

6. Deployment guidance

6.1. Deployment prerequisites

Before initiating the Terraform deployment, verify that the following toolchain and cloud prerequisites are in place:

  • Tooling and CLI:
    • Terraform CLI version >= 1.9.
    • Google Cloud CLI (gcloud) installed, authenticated, and configured with administrative credentials.
  • Permissions and IAM Privileges:
    • The executing deployment identity (or automated GitHub Actions service account) requires administrative bindings at the Organization and seed project levels:
      • roles/resourcemanager.organizationAdmin
      • roles/compute.networkAdmin
      • roles/compute.securityAdmin
      • roles/iam.securityAdmin
      • roles/orgpolicy.policyAdmin
      • roles/kms.admin
      • roles/storage.admin
      • roles/logging.configWriter
      • roles/monitoring.admin
  • Google Cloud APIs:
    • The following Google Cloud APIs must be enabled within the deployment project:
      • compute.googleapis.com (Compute Engine API)
      • cloudresourcemanager.googleapis.com (Cloud Resource Manager API)
      • iam.googleapis.com (Identity and Access Management API)
      • cloudidentity.googleapis.com (Cloud Identity API)
      • cloudkms.googleapis.com (Cloud Key Management Service API)
      • logging.googleapis.com (Cloud Logging API)
      • storage-component.googleapis.com (Cloud Storage API)
      • monitoring.googleapis.com (Cloud Monitoring API)

6.2. Step-by-step deployment instructions

  1. Prepare Workspace: Clone the repository and change directory into the Terraform root folder:

    cd terraform/
    
  2. Initialize Terraform: Download and initialize the HashiCorp Google provider plugins:

    terraform init
    
  3. Configure Environment Variables: Create a terraform.tfvars file and specify parameters matching your organization hierarchy:

    project_id       = "your-landing-zone-seed-project"
    region           = "europe-west2"
    primary_region   = "europe-west2"
    secondary_region = "europe-west1"
    org_id           = "123456789012"
    billing_account  = "012345-6789AB-CDEF01"
    
  4. Plan and Inspect Infrastructure Changes: Execute a speculative plan dry-run to verify resource graph construction and check for drift:

    terraform plan -out=tfplan
    
  5. Apply Configuration: Provision the landing zone resources:

    terraform apply tfplan
    
  6. Post-Deployment Hybrid Network & Appliance Verification:

    • Coordinate cross-connect provisioning with colocation facility engineers in London and associate customer VLANs with vlan-attachment-1 and vlan-attachment-2.
    • Validate BGP session establishment across interconnect-router-1 and interconnect-router-2 using:
      gcloud compute routers get-status interconnect-router-1 --region=europe-west2
      
    • Verify that advertised RFC 1918 prefixes (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) are learned by on-premises BGP peers.
    • Test symmetric outbound egress routing through the NVA forwarding rule (10.10.0.0/24, 10.20.0.0/24, 10.30.0.0/24 to 0.0.0.0/0).

Infrastructure as Code Artifacts

terraform/versions.tf

terraform {
  required_version = ">= 1.9"

  required_providers {
    google = {
      source  = "hashicorp/google"
      version = "8.6.0"
    }
  }
}

provider "google" {
  project = var.project_id
  region  = var.region
}

terraform/variables.tf

variable "project_id" {
  type        = string
  description = "The project ID"
}

variable "region" {
  type        = string
  description = "The default region"
}

variable "primary_region" {
  type        = string
  description = "The primary region (europe-west2)"
  default     = "europe-west2"
}

variable "secondary_region" {
  type        = string
  description = "The secondary region (europe-west1)"
  default     = "europe-west1"
}

variable "org_id" {
  type        = string
  description = "The organization ID"
}

variable "billing_account" {
  type        = string
  description = "The billing account ID"
}

terraform/main.tf

# Folders
resource "google_folder" "dev" {
  display_name = "Development"
  parent       = "organizations/${var.org_id}"
}

resource "google_folder" "staging" {
  display_name = "Staging"
  parent       = "organizations/${var.org_id}"
}

resource "google_folder" "production" {
  display_name = "Production"
  parent       = "organizations/${var.org_id}"
}

# Host Project
resource "google_compute_shared_vpc_host_project" "host" {
  project = var.project_id
}

# VPC Networks
resource "google_compute_network" "hub" {
  name                    = "hub-inspection-network"
  project                 = var.project_id
  auto_create_subnetworks = false
  routing_mode            = "GLOBAL"
  mtu                     = 1460
}

resource "google_compute_network" "dev" {
  name                            = "dev-network"
  project                         = var.project_id
  auto_create_subnetworks         = false
  delete_default_routes_on_create = true
}

resource "google_compute_network" "staging" {
  name                            = "staging-network"
  project                         = var.project_id
  auto_create_subnetworks         = false
  delete_default_routes_on_create = true
}

resource "google_compute_network" "production" {
  name                            = "production-network"
  project                         = var.project_id
  auto_create_subnetworks         = false
  delete_default_routes_on_create = true
}

# Subnetworks
resource "google_compute_subnetwork" "dev" {
  name                     = "dev-subnetwork"
  project                  = var.project_id
  region                   = var.primary_region
  network                  = google_compute_network.dev.id
  ip_cidr_range            = "10.10.0.0/24"
  private_ip_google_access = true
}

resource "google_compute_subnetwork" "staging" {
  name                     = "staging-subnetwork"
  project                  = var.project_id
  region                   = var.primary_region
  network                  = google_compute_network.staging.id
  ip_cidr_range            = "10.20.0.0/24"
  private_ip_google_access = true
}

resource "google_compute_subnetwork" "production" {
  name                     = "production-subnetwork"
  project                  = var.project_id
  region                   = var.primary_region
  network                  = google_compute_network.production.id
  ip_cidr_range            = "10.30.0.0/24"
  private_ip_google_access = true
}

resource "google_compute_subnetwork" "standby" {
  name          = "standby-subnetwork"
  project       = var.project_id
  region        = var.secondary_region
  network       = google_compute_network.hub.id
  ip_cidr_range = "10.40.0.0/24"
}

# Peerings
resource "google_compute_network_peering" "hub_prod" {
  name         = "hub-to-prod"
  network      = google_compute_network.hub.id
  peer_network = google_compute_network.production.id
}

resource "google_compute_network_peering" "hub_dev" {
  name         = "hub-to-dev"
  network      = google_compute_network.hub.id
  peer_network = google_compute_network.dev.id
}

resource "google_compute_network_peering" "hub_stg" {
  name         = "hub-to-stg"
  network      = google_compute_network.hub.id
  peer_network = google_compute_network.staging.id
}

# Cloud Interconnect
resource "google_compute_router" "interconnect_1" {
  name    = "interconnect-router-1"
  project = var.project_id
  region  = var.primary_region
  network = google_compute_network.hub.id
  bgp {
    asn                = 65001
    keepalive_interval = 20
    advertise_mode     = "CUSTOM"
    advertised_ip_ranges {
      range = "10.0.0.0/8"
    }
    advertised_ip_ranges {
      range = "172.16.0.0/12"
    }
    advertised_ip_ranges {
      range = "192.168.0.0/16"
    }
  }
}

resource "google_compute_router" "interconnect_2" {
  name    = "interconnect-router-2"
  project = var.project_id
  region  = var.primary_region
  network = google_compute_network.hub.id
  bgp {
    asn                = 65001
    keepalive_interval = 20
    advertise_mode     = "CUSTOM"
    advertised_ip_ranges {
      range = "10.0.0.0/8"
    }
    advertised_ip_ranges {
      range = "172.16.0.0/12"
    }
    advertised_ip_ranges {
      range = "192.168.0.0/16"
    }
  }
}

resource "google_compute_interconnect_attachment" "vlan_1" {
  name                     = "vlan-attachment-1"
  project                  = var.project_id
  region                   = var.primary_region
  router                   = google_compute_router.interconnect_1.id
  type                     = "DEDICATED"
  interconnect             = "my-interconnect-1" # Mock interconnect
  bandwidth                = "BPS_10G"
  edge_availability_domain = "AVAILABILITY_DOMAIN_1"
  mtu                      = 1460
  labels = {
    env         = "production"
    cost-centre = "platform"
    archetype   = "network"
  }
}

resource "google_compute_interconnect_attachment" "vlan_2" {
  name                     = "vlan-attachment-2"
  project                  = var.project_id
  region                   = var.primary_region
  router                   = google_compute_router.interconnect_2.id
  type                     = "DEDICATED"
  interconnect             = "my-interconnect-2" # Mock interconnect
  bandwidth                = "BPS_10G"
  edge_availability_domain = "AVAILABILITY_DOMAIN_2"
  mtu                      = 1460
  labels = {
    env         = "production"
    cost-centre = "platform"
    archetype   = "network"
  }
}

resource "google_compute_router" "standby" {
  name    = "standby-router"
  project = var.project_id
  region  = var.secondary_region
  network = google_compute_network.hub.id
  bgp {
    asn = 65002
  }
}

resource "google_compute_interconnect_attachment" "standby_vlan" {
  name         = "standby-vlan"
  project      = var.project_id
  region       = var.secondary_region
  router       = google_compute_router.standby.id
  type         = "DEDICATED"
  interconnect = "my-interconnect-3" # Mock interconnect
  labels = {
    env         = "production"
    cost-centre = "platform"
    archetype   = "network"
  }
}

# NVA (Compute Engine)
resource "google_compute_instance_template" "nva" {
  name         = "nva-template"
  project      = var.project_id
  machine_type = "e2-medium"
  network_interface {
    network  = google_compute_network.hub.id
    nic_type = "GVNIC"
  }
  disk {
    source_image = "debian-cloud/debian-11"
    auto_delete  = true
    boot         = true
  }
  labels = {
    env         = "production"
    cost-centre = "platform"
    archetype   = "security"
  }
}

resource "google_compute_region_health_check" "nva" {
  name               = "nva-health-check"
  project            = var.project_id
  region             = var.primary_region
  check_interval_sec = 5
  tcp_health_check {
    port = 80
  }
}

resource "google_compute_region_instance_group_manager" "nva" {
  name                      = "nva-mig"
  project                   = var.project_id
  region                    = var.primary_region
  base_instance_name        = "nva-instance"
  distribution_policy_zones = ["europe-west2-a", "europe-west2-b"]

  version {
    instance_template = google_compute_instance_template.nva.id
  }

  auto_healing_policies {
    health_check      = google_compute_region_health_check.nva.id
    initial_delay_sec = 300
  }
}

resource "google_compute_forwarding_rule" "nva" {
  name                  = "nva-forwarding-rule"
  project               = var.project_id
  region                = var.primary_region
  load_balancing_scheme = "INTERNAL"
  network               = google_compute_network.hub.id
  backend_service       = google_compute_region_backend_service.nva.id
  ports                 = ["80"]
  labels = {
    env         = "production"
    cost-centre = "platform"
    archetype   = "security"
  }
}

resource "google_compute_region_backend_service" "nva" {
  name                  = "nva-backend-service"
  project               = var.project_id
  region                = var.primary_region
  load_balancing_scheme = "INTERNAL"
  health_checks         = [google_compute_region_health_check.nva.id]
  backend {
    group = google_compute_region_instance_group_manager.nva.instance_group
  }
}

resource "google_compute_region_autoscaler" "nva" {
  name    = "nva-autoscaler"
  project = var.project_id
  region  = var.primary_region
  target  = google_compute_region_instance_group_manager.nva.id
  autoscaling_policy {
    max_replicas    = 5
    min_replicas    = 2
    cooldown_period = 60
    cpu_utilization {
      target = 0.7
    }
  }
}

# Firewall
resource "google_compute_firewall" "inbound_deny" {
  name          = "inbound-deny"
  project       = var.project_id
  network       = google_compute_network.hub.id
  direction     = "INGRESS"
  source_ranges = ["0.0.0.0/0"]
  deny {
    protocol = "all"
  }
}

# Cloud Identity
resource "google_cloud_identity_group" "group" {
  parent       = "customers/C01234567" # Mock customer ID
  display_name = "Pipeline Identity Group"
  labels = {
    "cloudidentity.googleapis.com/groups.discussion_forum" = ""
    env                                                    = "production"
    cost-centre                                            = "platform"
    archetype                                              = "identity"
  }
  group_key {
    id = "pipeline-group@example.com"
  }
}

# Workload Identity Federation
resource "google_iam_workload_identity_pool" "wif_pool" {
  project                   = var.project_id
  workload_identity_pool_id = "github-wif-pool"
}

resource "google_iam_workload_identity_pool_provider" "wif_provider" {
  project                            = var.project_id
  workload_identity_pool_id          = google_iam_workload_identity_pool.wif_pool.workload_identity_pool_id
  workload_identity_pool_provider_id = "github-provider"
  attribute_condition                = "assertion.repository == 'my-org/my-repo'"
  oidc {
    issuer_uri = "https://token.actions.githubusercontent.com"
  }
}

resource "google_service_account" "pipeline_sa" {
  project    = var.project_id
  account_id = "pipeline-service-account"
}

resource "google_service_account_iam_member" "pipeline_wif" {
  service_account_id = google_service_account.pipeline_sa.name
  role               = "roles/iam.workloadIdentityUser"
  member             = "principalSet://iam.googleapis.com/${google_iam_workload_identity_pool.wif_pool.name}/*"
}

# Cloud KMS
resource "google_kms_key_ring" "primary" {
  name     = "kms-key-ring-primary"
  project  = var.project_id
  location = var.primary_region
}

resource "google_kms_crypto_key" "primary" {
  name            = "kms-crypto-key-primary"
  key_ring        = google_kms_key_ring.primary.id
  rotation_period = "7776000s"
  labels = {
    env         = "production"
    cost-centre = "platform"
    archetype   = "security"
  }
}

resource "google_kms_key_ring" "standby" {
  name     = "kms-key-ring-standby"
  project  = var.project_id
  location = var.secondary_region
}

resource "google_kms_crypto_key" "standby" {
  name            = "kms-crypto-key-standby"
  key_ring        = google_kms_key_ring.standby.id
  rotation_period = "7776000s"
  labels = {
    env         = "production"
    cost-centre = "platform"
    archetype   = "security"
  }
}

# Cloud Storage
resource "google_storage_bucket" "audit_log" {
  name                        = "${var.project_id}-audit-logs"
  project                     = var.project_id
  location                    = "EU"
  uniform_bucket_level_access = true
  retention_policy {
    retention_period = 31536000
    is_locked        = true
  }
  lifecycle_rule {
    action {
      type          = "SetStorageClass"
      storage_class = "COLDLINE"
    }
    condition {
      age = 90
    }
  }
  labels = {
    env         = "production"
    cost-centre = "security"
    archetype   = "audit"
  }
}

resource "google_logging_organization_sink" "org_sink" {
  name        = "org-log-sink"
  org_id      = var.org_id
  destination = "storage.googleapis.com/${google_storage_bucket.audit_log.name}"
}

resource "google_storage_bucket" "tf_state" {
  name                        = "${var.project_id}-tf-state"
  project                     = var.project_id
  location                    = "EU"
  uniform_bucket_level_access = true
  versioning {
    enabled = true
  }
  encryption {
    default_kms_key_name = google_kms_crypto_key.primary.id
  }
  lifecycle_rule {
    action {
      type = "Delete"
    }
    condition {
      num_newer_versions = 5
    }
  }
  labels = {
    provisioned_by = "terraform"
    env            = "production"
    cost-centre    = "platform"
    archetype      = "management"
  }
}

# Organization Policies
resource "google_org_policy_policy" "skip_default_network" {
  name   = "organizations/${var.org_id}/policies/compute.skipDefaultNetworkCreation"
  parent = "organizations/${var.org_id}"
  spec {
    rules {
      enforce = "TRUE"
    }
  }
}

resource "google_org_policy_policy" "vm_external_ip" {
  name   = "organizations/${var.org_id}/policies/compute.vmExternalIpAccess"
  parent = "organizations/${var.org_id}"
  spec {
    rules {
      deny_all = "TRUE"
    }
  }
}

resource "google_org_policy_policy" "resource_locations" {
  name   = "organizations/${var.org_id}/policies/gcp.resourceLocations"
  parent = "organizations/${var.org_id}"
  spec {
    rules {
      values {
        allowed_values = ["in:europe-west2", "in:europe-west1"]
      }
    }
  }
}

resource "google_org_policy_policy" "sa_keys" {
  name   = "organizations/${var.org_id}/policies/iam.disableServiceAccountKeyCreation"
  parent = "organizations/${var.org_id}"
  spec {
    rules {
      enforce = "TRUE"
    }
  }
}

resource "google_scc_organization_custom_module" "scc_config" {
  organization     = var.org_id
  display_name     = "compliance_monitoring"
  enablement_state = "ENABLED"
  custom_config {
    recommendation = "Enable compute instance monitoring to ensure compliance."
    predicate {
      expression = "resource.type == 'compute.googleapis.com/Instance'"
    }
    resource_selector {
      resource_types = ["compute.googleapis.com/Instance"]
    }
    severity = "HIGH"
  }
}

resource "google_org_policy_policy" "prod_org_policy" {
  name   = "${google_folder.production.name}/policies/compute.restrictXpnProjectLienRemoval"
  parent = google_folder.production.name
  spec {
    rules {
      enforce = "TRUE"
    }
  }
}

resource "google_org_policy_policy" "ubla" {
  name   = "organizations/${var.org_id}/policies/storage.uniformBucketLevelAccess"
  parent = "organizations/${var.org_id}"
  spec {
    rules {
      enforce = "TRUE"
    }
  }
}

resource "google_org_policy_policy" "cmek_enforce" {
  name   = "organizations/${var.org_id}/policies/gcp.restrictNonCmekServices"
  parent = "organizations/${var.org_id}"
  spec {
    rules {
      enforce = "TRUE"
    }
  }
}

# Cloud Monitoring
resource "google_monitoring_alert_policy" "interconnect" {
  display_name = "Interconnect BGP Session Down"
  project      = var.project_id
  combiner     = "OR"
  conditions {
    display_name = "BGP Session Down"
    condition_threshold {
      filter          = "metric.type=\"interconnect.googleapis.com/network/bgp/session_up\" resource.type=\"interconnect\""
      comparison      = "COMPARISON_LT"
      threshold_value = 1
      duration        = "60s"
    }
  }
}

resource "google_monitoring_alert_policy" "lb" {
  display_name = "NVA Load Balancer Backend Health"
  project      = var.project_id
  combiner     = "OR"
  conditions {
    display_name = "Backend Unhealthy"
    condition_threshold {
      filter          = "metric.type=\"loadbalancing.googleapis.com/https/backend_latencies\" resource.type=\"internal_tcp_udp_lb_rule\""
      comparison      = "COMPARISON_GT"
      threshold_value = 500
      duration        = "60s"
    }
  }
}

resource "google_monitoring_alert_policy" "audit_logs" {
  display_name = "Audit Log Sink Errors"
  project      = var.project_id
  combiner     = "OR"
  conditions {
    display_name = "Sink Export Errors"
    condition_threshold {
      filter          = "metric.type=\"logging.googleapis.com/exports/error_count\" resource.type=\"logging_sink\""
      comparison      = "COMPARISON_GT"
      threshold_value = 0
      duration        = "60s"
    }
  }
}

# Routes
resource "google_compute_route" "dev_nva" {
  name         = "dev-to-nva"
  project      = var.project_id
  network      = google_compute_network.dev.id
  dest_range   = "0.0.0.0/0"
  next_hop_ilb = google_compute_forwarding_rule.nva.id
}

resource "google_compute_route" "staging_nva" {
  name         = "staging-to-nva"
  project      = var.project_id
  network      = google_compute_network.staging.id
  dest_range   = "0.0.0.0/0"
  next_hop_ilb = google_compute_forwarding_rule.nva.id
}

resource "google_compute_route" "production_nva" {
  name         = "production-to-nva"
  project      = var.project_id
  network      = google_compute_network.production.id
  dest_range   = "0.0.0.0/0"
  next_hop_ilb = google_compute_forwarding_rule.nva.id
}

7. Validation plan

Pre-deployment validation dry-run

The Infrastructure as Code codebase was subjected to offline static validation and provider syntax verification. The codebase returned zero syntax errors, type discrepancies, or unresolvable references:

$ terraform validate
Success! The configuration is valid.

Dry-Run Verdict: PASS

Architecture and policy analysis

The generated landing zone architecture, resource parameters, and policy constraints were statically analyzed against all requirements and architectural rules. All 121 explicitly mapped checks within the Target Architecture were verified as passed.

Architecture Checks and Validation Verdicts

Check ID Target Element Statement / Rule Evaluated Source Requirement / Recommendation Evidence from Codebase Verdict
K-1 E-29 name is "gcp.resourceLocations" and spec.rules.values.allowed_values allows europe-west2 and europe-west1 NFR-1 allowed_values = ["in:europe-west2", "in:europe-west1"] PASS
K-2 E-6 region is "europe-west2" NFR-1 region = var.primary_region (default: europe-west2) PASS
K-3 E-7 region is "europe-west2" NFR-1 region = var.primary_region PASS
K-4 E-8 region is "europe-west2" NFR-1 region = var.primary_region PASS
K-5 E-9 region is "europe-west2" NFR-1 region = var.primary_region PASS
K-6 E-10 region is "europe-west2" NFR-1 region = var.primary_region PASS
K-7 E-11 region is "europe-west2" NFR-1 region = var.primary_region PASS
K-8 E-12 region is "europe-west2" NFR-1 region = var.primary_region PASS
K-9 E-14 region is "europe-west2" NFR-1 region = var.primary_region PASS
K-10 E-37 region is "europe-west1" NFR-1 region = var.secondary_region (europe-west1) PASS
K-11 E-35 region is "europe-west1" NFR-1 region = var.secondary_region PASS
K-12 E-36 region is "europe-west1" NFR-1 region = var.secondary_region PASS
K-13 E-1 display_name is set to represent development tier NFR-2 display_name = "Development" PASS
K-14 E-2 display_name is set to represent staging tier NFR-2 display_name = "Staging" PASS
K-15 E-3 display_name is set to represent production tier NFR-2 display_name = "Production" PASS
K-16 E-47 direction is "INGRESS" and deny block is defined NFR-2 direction = "INGRESS", deny { protocol = "all" } PASS
K-17 E-46 parent refers to the Production folder E-3 NFR-2 parent = google_folder.production.name PASS
K-18 E-4 project is designated as the host project NFR-3 project = var.project_id PASS
K-19 E-43 network and peer_network interconnect Hub and Prod VPCs NFR-3 Connected between hub and production PASS
K-20 E-44 network and peer_network interconnect Hub and Dev VPCs NFR-3 Connected between hub and dev PASS
K-21 E-45 network and peer_network interconnect Hub and Stg VPCs NFR-3 Connected between hub and staging PASS
K-22 E-6 private_ip_google_access is true NFR-3 private_ip_google_access = true PASS
K-23 E-7 private_ip_google_access is true NFR-3 private_ip_google_access = true PASS
K-24 E-8 private_ip_google_access is true NFR-3 private_ip_google_access = true PASS
K-25 E-40 delete_default_routes_on_create is true NFR-3 delete_default_routes_on_create = true PASS
K-26 E-41 delete_default_routes_on_create is true NFR-3 delete_default_routes_on_create = true PASS
K-27 E-42 delete_default_routes_on_create is true NFR-3 delete_default_routes_on_create = true PASS
K-28 E-47 direction is "INGRESS", source_ranges includes "0.0.0.0/0", and deny block is present NFR-3 Configured with 0.0.0.0/0 ingress deny PASS
K-29 E-11 bandwidth is "BPS_10G" NFR-4 bandwidth = "BPS_10G" PASS
K-30 E-12 bandwidth is "BPS_10G" NFR-4 bandwidth = "BPS_10G" PASS
K-31 E-9 bgp.asn is defined NFR-4 bgp.asn = 65001 PASS
K-32 E-10 bgp.asn is defined NFR-4 bgp.asn = 65001 PASS
K-33 E-9 network points to the Hub Network E-5 NFR-4 network = google_compute_network.hub.id PASS
K-34 E-5 name identifies it as the central inspection hub NFR-5 name = "hub-inspection-network" PASS
K-35 E-51 dest_range is "0.0.0.0/0" and next_hop_ilb points to E-16 NFR-5 dest_range = "0.0.0.0/0", next_hop_ilb points to nva forwarding rule PASS
K-36 E-52 dest_range is "0.0.0.0/0" and next_hop_ilb points to E-16 NFR-5 Next-hop ILB points to nva forwarding rule PASS
K-37 E-53 dest_range is "0.0.0.0/0" and next_hop_ilb points to E-16 NFR-5 Next-hop ILB points to nva forwarding rule PASS
K-38 E-40 delete_default_routes_on_create is true NFR-5 delete_default_routes_on_create = true PASS
K-39 E-41 delete_default_routes_on_create is true NFR-5 delete_default_routes_on_create = true PASS
K-40 E-42 delete_default_routes_on_create is true NFR-5 delete_default_routes_on_create = true PASS
K-41 E-37 region is "europe-west1" NFR-6 region = var.secondary_region PASS
K-42 E-35 region is "europe-west1" NFR-6 region = var.secondary_region PASS
K-43 E-36 region is "europe-west1" NFR-6 region = var.secondary_region PASS
K-44 E-19 workload_identity_pool_id is defined NFR-7 workload_identity_pool_id = "github-wif-pool" PASS
K-45 E-20 oidc block is configured with issuer_uri NFR-7 issuer_uri = "https://token.actions.githubusercontent.com" PASS
K-46 E-55 role is "roles/iam.workloadIdentityUser" and member refers to the WIF Pool NFR-7 Bound to principalSet of WIF pool PASS
K-47 E-30 name is "iam.disableServiceAccountKeyCreation" and spec.rules.enforce is true NFR-7 enforce = "TRUE" PASS
K-48 E-18 parent is set to the Cloud Identity organization NFR-7 parent = "customers/C01234567" PASS
K-49 E-56 name is "storage.uniformBucketLevelAccess" and spec.rules.enforce is true NFR-8 enforce = "TRUE" PASS
K-50 E-57 name is "gcp.restrictNonCmekServices" and spec.rules.enforce is true NFR-8 enforce = "TRUE" PASS
K-51 E-28 name is "compute.vmExternalIpAccess" and spec.rules.deny_all is true NFR-8 deny_all = "TRUE" PASS
K-52 E-38 enablement_state is "ENABLED" and custom_config implements compliance monitoring NFR-8 enablement_state = "ENABLED" PASS
K-53 E-21 location is "europe-west2" NFR-9 location = var.primary_region PASS
K-54 E-22 rotation_period is "7776000s" NFR-9 rotation_period = "7776000s" PASS
K-55 E-23 location is "europe-west1" NFR-9 location = var.secondary_region PASS
K-56 E-24 rotation_period is "7776000s" NFR-9 rotation_period = "7776000s" PASS
K-57 E-57 name is "gcp.restrictNonCmekServices" and spec.rules.enforce is true NFR-9 enforce = "TRUE" PASS
K-58 E-26 destination points to the Audit Log Bucket E-25 NFR-10 destination = "storage.googleapis.com/...-audit-logs" PASS
K-59 E-25 retention_policy.retention_period is 31536000 NFR-10 retention_period = 31536000 PASS
K-60 E-25 retention_policy.is_locked is true NFR-10 is_locked = true PASS
K-61 E-11 edge_availability_domain is set for redundancy NFR-11 edge_availability_domain = "AVAILABILITY_DOMAIN_1" PASS
K-62 E-12 edge_availability_domain is set for redundancy NFR-11 edge_availability_domain = "AVAILABILITY_DOMAIN_2" PASS
K-63 E-14 distribution_policy_zones includes at least two zones in europe-west2 NFR-11 ["europe-west2-a", "europe-west2-b"] PASS
K-64 E-29 name is "gcp.resourceLocations" and spec.rules.values.allowed_values restricts to europe-west2 and europe-west1 NFR-12 allowed_values = ["in:europe-west2", "in:europe-west1"] PASS
K-65 E-31 name identifies it as the central Terraform remote state backend NFR-13 name = "${var.project_id}-tf-state" PASS
K-66 E-31 versioning.enabled is true NFR-13 versioning.enabled = true PASS
K-67 E-31 encryption.default_kms_key_name is set to the primary CMEK key NFR-13 CMEK key name matches primary key ID PASS
K-68 E-32 conditions monitor Cloud Interconnect BGP session status NFR-14 Monitors network/bgp/session_up PASS
K-69 E-33 conditions monitor NVA Load Balancer backend health NFR-14 Monitors backend_latencies PASS
K-70 E-58 conditions monitor Audit Log sink export metrics NFR-14 Monitors exports/error_count PASS
K-71 E-25 labels includes standard keys for environment tier, cost centre, and archetype NFR-14 labels = { env = "production", cost-centre = "security", archetype = "audit" } PASS
K-72 E-27 name is "compute.skipDefaultNetworkCreation" and spec.rules.enforce is true DR-1 enforce = "TRUE" PASS
K-73 E-28 name is "compute.vmExternalIpAccess" and spec.rules.deny_all is true DR-1 deny_all = "TRUE" PASS
K-74 E-29 name is "gcp.resourceLocations" and spec.rules.values.allowed_values restricts to allowed regions DR-1 allowed_values = ["in:europe-west2", "in:europe-west1"] PASS
K-75 E-30 name is "iam.disableServiceAccountKeyCreation" and spec.rules.enforce is true DR-1 enforce = "TRUE" PASS
K-76 E-16 load_balancing_scheme is "INTERNAL" DR-2 load_balancing_scheme = "INTERNAL" PASS
K-77 E-51 dest_range is "0.0.0.0/0" and next_hop_ilb points to E-16 DR-2 next_hop_ilb = google_compute_forwarding_rule.nva.id PASS
K-78 E-52 dest_range is "0.0.0.0/0" and next_hop_ilb points to E-16 DR-2 next_hop_ilb = google_compute_forwarding_rule.nva.id PASS
K-79 E-53 dest_range is "0.0.0.0/0" and next_hop_ilb points to E-16 DR-2 next_hop_ilb = google_compute_forwarding_rule.nva.id PASS
K-80 E-14 base_instance_name is configured to define the MIG DR-3 base_instance_name = "nva-instance" PASS
K-81 E-14 auto_healing_policies.health_check points to E-15 DR-3 Points to google_compute_region_health_check.nva.id PASS
K-82 E-17 target points to E-14 DR-3 target = google_compute_region_instance_group_manager.nva.id PASS
K-83 E-13 network_interface.nic_type is "GVNIC" DR-3 nic_type = "GVNIC" PASS
K-84 E-9 network is set to E-5 DR-4 network = google_compute_network.hub.id PASS
K-85 E-10 network is set to E-5 DR-4 network = google_compute_network.hub.id PASS
K-86 E-11 router is set to E-9 DR-4 router = google_compute_router.interconnect_1.id PASS
K-87 E-12 router is set to E-10 DR-4 router = google_compute_router.interconnect_2.id PASS
K-88 E-5 routing_mode is "GLOBAL" DR-4 routing_mode = "GLOBAL" PASS
K-89 E-9 bgp.keepalive_interval is configured DR-4 keepalive_interval = 20 PASS
K-90 E-10 bgp.keepalive_interval is configured DR-4 keepalive_interval = 20 PASS
K-91 E-21 location is "europe-west2" DR-5 location = var.primary_region PASS
K-92 E-23 location is "europe-west1" DR-5 location = var.secondary_region PASS
K-93 E-22 rotation_period is "7776000s" DR-5 rotation_period = "7776000s" PASS
K-94 E-24 rotation_period is "7776000s" DR-5 rotation_period = "7776000s" PASS
K-95 E-25 retention_policy.retention_period is set DR-6 retention_period = 31536000 PASS
K-96 E-25 retention_policy.is_locked is true DR-6 is_locked = true PASS
K-97 E-25 lifecycle_rule.action.type is "SetStorageClass" DR-6 storage_class = "COLDLINE", age = 90 PASS
K-98 E-31 versioning.enabled is true DR-7 versioning.enabled = true PASS
K-99 E-31 encryption.default_kms_key_name is set DR-7 Configured with primary CMEK key PASS
K-100 E-31 lifecycle_rule.action.type is "Delete" and lifecycle_rule.condition.num_newer_versions is set DR-7 num_newer_versions = 5 PASS
K-101 E-20 attribute_condition restricts access to authorized GitHub repositories DR-8 assertion.repository == 'my-org/my-repo' PASS
K-102 E-32 conditions includes metrics for interconnect BGP session health DR-9 Filter: session_up PASS
K-103 E-33 conditions includes metrics for NVA load balancer backend health DR-9 Filter: backend_latencies PASS
K-104 E-5 mtu is set to an optimized value DR-10 mtu = 1460 PASS
K-105 E-11 mtu is configured to match the network MTU DR-10 mtu = 1460 PASS
K-106 E-12 mtu is configured to match the network MTU DR-10 mtu = 1460 PASS
K-107 E-15 check_interval_sec is configured for rapid failure detection DR-3 check_interval_sec = 5 PASS
K-108 E-54 account_id is defined to identify the CI/CD pipeline identity NFR-7 account_id = "pipeline-service-account" PASS
K-109 E-10 network points to the Hub Network E-5 NFR-4 network = google_compute_network.hub.id PASS
K-110 E-31 labels includes a tag identifying it as provisioned by Terraform NFR-13 provisioned_by = "terraform" PASS
K-111 E-11 labels includes standard keys for environment tier, cost centre, and archetype NFR-14 Standard labels configured PASS
K-112 E-12 labels includes standard keys for environment tier, cost centre, and archetype NFR-14 Standard labels configured PASS
K-113 E-36 labels includes standard keys for environment tier, cost centre, and archetype NFR-14 Standard labels configured PASS
K-114 E-13 labels includes standard keys for environment tier, cost centre, and archetype NFR-14 Standard labels configured PASS
K-115 E-16 labels includes standard keys for environment tier, cost centre, and archetype NFR-14 Standard labels configured PASS
K-116 E-18 labels includes standard keys for environment tier, cost centre, and archetype NFR-14 Standard labels configured PASS
K-117 E-22 labels includes standard keys for environment tier, cost centre, and archetype NFR-14 Standard labels configured PASS
K-118 E-24 labels includes standard keys for environment tier, cost centre, and archetype NFR-14 Standard labels configured PASS
K-119 E-31 labels includes standard keys for environment tier, cost centre, and archetype NFR-14 Standard labels configured PASS
K-120 E-9 bgp.advertise_mode or bgp.advertised_ip_ranges are configured to route RFC 1918 traffic NFR-4 Advertises 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 PASS
K-121 E-10 bgp.advertise_mode or bgp.advertised_ip_ranges are configured to route RFC 1918 traffic NFR-4 Advertises 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 PASS

Architecture and Policy Analysis Verdict: PASS

Things to verify after deployment

The following operational characteristics and compliance conditions cannot be validated through static code analysis alone and must be verified in the live environment during deployment and runtime operations:

  • Data Residency and Workload Locality (NFR-1): Confirm that all customer payment data and transaction records remain strictly within UK and EU legal jurisdictions. Verify that the warm standby environment in europe-west1 operates at minimal pilot-light capacity until activated during DR failover.
  • PCI-DSS v4.0 Network Segmentation (NFR-2, NFR-8): Execute internal network penetration tests and packet trace validation to prove that the production Cardholder Data Environment (CDE) is completely unreachable from development and staging spoke subnets.
  • Private API Exposure (NFR-3): Confirm that all payment engine endpoints and administrative APIs are accessible exclusively through private corporate network routes and Private Google Access paths.
  • Hybrid Throughput and SLA Verification (NFR-4): Perform synthetic throughput and latency benchmarking across the physical 10Gbps Dedicated Interconnect circuits to ensure line-rate data transmission meets low-latency payment SLA requirements.
  • Centralised Packet Inspection Validation (NFR-5, DR-3): Test egress inspection rules by generating outbound test traffic across ports 80/443; confirm that unapproved domains and suspicious payloads are actively dropped, logged, and alerted on by the NVA cluster. Verify that NVA instances operate on machine families supporting high bandwidth (gVNIC enabled).
  • Warm Standby DR Metrics (NFR-6, DR-11): Conduct an operational failover drill simulating primary region loss in europe-west2 to verify that routing failover to europe-west1 completes within the 4-hour RTO and data loss is restricted to under the 1-hour RPO.
  • Identity Governance & Lifecycle (NFR-7): Validate that user deprovisioning or role updates in Microsoft Entra ID synchronize immediately to Cloud Identity, and that Conditional Access MFA policies are enforced upon console login.
  • Confidentiality & Cryptographic Custody (NFR-9): Perform audit validations confirming that no unencrypted persistent disks, buckets, or database tables can be provisioned, and verify that the 90-day Cloud KMS key rotation schedule executes automatically.
  • Immutable Retention Verification (NFR-10): Attempt an administrative deletion of an audit log object within Audit Log Bucket to confirm that the locked Bucket Lock policy prevents deletion by any administrative identity.
  • Continuous Platform Availability (NFR-11): Monitor Cloud Monitoring dashboards to verify that core landing zone routing and gateway uptime achieves the 99.9% monthly availability target across availability zones.
  • Carbon-Free Energy Metrics (NFR-12): Track the Carbon Footprint dashboard in Google Cloud console to confirm workloads leverage high-CFE data centre operations.
  • Delivery Window Completion (NFR-13): Track milestone readiness against the delivery plan to verify that the landing zone is ready for application squad workload ingestion within the 10-week commitment.
  • Operational Workflows (NFR-14): Ensure 24/7 central operations on-call alerting is active, and confirm that all infrastructure modifications are strictly mediated via peer-reviewed GitHub Actions pull requests.

8. References