Files
tom_analysis_agent/eval/results/20261021T203623Z-handoff/operating_model/operating-model-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

40 KiB

Operating model guide: Google Cloud Landing Zone for Core Payments Engine

Summary

This operating model guide governs the enterprise-grade Google Cloud platform foundation landing zone supporting the core payments engine, spanning multi-tier environment isolation, dedicated hybrid network interconnect, transit network fabric, centralised egress traffic inspection gateways, corporate identity federation, pipeline identity brokering, cryptographic key management, centralised immutable audit logging, governance guardrails, declarative infrastructure provisioning, and operational telemetry. The Managed Service Provider operates the platform foundation under a provider-operated model, holding operational accountability for infrastructure reliability, platform engineering, security monitoring, and regulatory evidence collation. The customer maintains workload governance and consumes foundation services autonomously via self-service, serving as a consulted stakeholder for architecture reviews and release approvals.

Operational fault response, telemetry triage, and security monitoring are maintained on a continuous 24x7 basis, while platform engineering changes, release deployments, enablement, and compliance governance operate during standard business hours. The reader should look first at the architectural findings and the operational checks that wait on them, where missing capabilities in the solution design—specifically automated backup tooling to meet the recovery point objective, automated budget anomaly alerts for the warm standby environment, and secure remote access for egress inspection appliances—require design resolution before full operational verification can be achieved.

Key figures

  • Operated: 11 Items, with 21 Conditions to keep true.
  • Faults responded to: 24x7 hours.
  • Capabilities: 21.
  • People: 12.2. Cost a month: 87,959 GBP, from rate card version draft-2026-10-13 (placeholder prices: an illustration).
  • Scenario walk-throughs: 44 of 44 pass.
  • Business outcomes: 3, 3 shown by a Measure.
  • Findings for whoever owns the design: 3.

Business outcomes

BO-1: Continuous and resilient payment processing with high availability and low-latency hybrid connectivity

Measure Layer Framework Target Measured by Answerable
Platform Availability service level 99.9% Service level management Platform Reliability Lead
Incident Response Time service level Under 30 minutes Service level management Platform Reliability Lead

BO-2: Sustained regulatory compliance with DORA and PCI-DSS v4.0 security and resilience standards

Measure Layer Framework Target Measured by Answerable
Compliance Audit Pass Rate service level 100% Regulatory evidence and reporting Compliance Officer

BO-3: Rapid and secure platform change releases through automated CI/CD delivery pipelines

Measure Layer Framework Target Measured by Answerable
Deployment frequency outcome dora-metrics Multiple times a day Delivery and developer experience measurement Product Manager
Satisfaction and well-being guardrail space-framework Positive trend Delivery and developer experience measurement Product Manager
Feedback loops leading devex-framework Minimal friction Delivery and developer experience measurement Product Manager

What is operated

Item What it is Kind Product From
S-1 Multi-Tier Environment Hierarchy & Isolation Boundary governance Resource Manager C-1
S-2 Dedicated Hybrid Network Interconnect Gateway network Cloud Interconnect C-2
S-3 Centralised Egress Traffic Inspection Gateway compute Compute Engine C-3
S-4 Transit Network Fabric & Routing Controller service Virtual Private Cloud C-4
S-5 Corporate Identity Federation Gateway identity Cloud Identity C-5
S-6 Automated Delivery Pipeline Identity Broker identity Workload Identity Federation C-6
S-7 Cryptographic Key Management & Rotation Service keys Cloud KMS C-7
S-8 Centralised Immutable Audit Log Repository storage Cloud Storage C-8
S-9 Platform Compliance & Governance Guardrail Controller governance Organization Policy Service C-9
S-10 Declarative Infrastructure Provisioning & State Engine storage Cloud Storage C-10
S-11 Centralised Operational Telemetry & Alerting Engine observability Cloud Monitoring C-11

What must be kept true while it is run:

Condition On What must hold From
K-1 S-1, S-7, S-9 Customer data and payment processing remain within United Kingdom and European Union legal jurisdictions. NFR-1
K-2 S-1, S-7, S-9 Warm standby environment operates with reduced capacity until activated during a disaster recovery failover. NFR-1
K-3 S-1, S-9 PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements. NFR-2
K-4 S-3, S-4 Workload APIs and payment services are accessible exclusively through private corporate network paths. NFR-3
K-5 S-2 Hybrid connection maintains low-latency, SLA-backed private data transmission between on-premises and Google Cloud. NFR-4
K-6 S-3 Centralised inspection appliances perform next-generation stateful packet inspection, URL filtering, and threat detection on outbound internet sessions. NFR-5
K-7 S-2, S-4 Platform foundation failover to europe-west1 can be completed within 4 hours during a primary region outage. NFR-6
K-8 S-2, S-4 Configuration drift and backup state achieve a maximum data loss window (RPO) of 1 hour. NFR-6
K-9 S-5, S-6 Corporate user lifecycle management and MFA enforcement are governed centrally by Entra ID conditional access policies. NFR-7
K-10 S-1, S-9 Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks. NFR-8
K-11 S-1, S-9 Production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements. NFR-8
K-12 S-7 Confidential payment data is secured against unauthorized platform-level access or data exposure. NFR-9
K-13 S-8 Audit logs cannot be modified, deleted, or shortened by any identity or administrator prior to retention expiration. NFR-10
K-14 S-2, S-4, S-11 Monthly availability of the core platform landing zone and network routing meets or exceeds 99.9%. NFR-11
K-15 S-9 Primary and secondary regions leverage Google Cloud data centres with published carbon-free energy (CFE) performance metrics. NFR-12
K-16 S-6, S-10 Platform foundation delivery and workload ingestion readiness are achieved within 10 weeks of project commencement. NFR-13
K-17 S-8, S-10, S-11 Central platform team operates 24/7 support for infrastructure incidents and availability alerts. NFR-14
K-18 S-8, S-10, S-11 Pull request workflows require automated CI/CD linting, validation, and peer approval prior to merge and deployment. NFR-14
K-19 S-3 NVA instances use machine families that support high bandwidth networking. DR-3
K-20 S-3 The warm standby environment operates at a minimal pilot light footprint during normal operations. DR-11
K-21 S-3 Automated disaster recovery scripts scale the standby environment to full capacity only during a failover event. DR-11

Operational requirements

Requirement Kind What must be achieved From
OR-1 service_level Priority 1 incidents on core platform foundation components are acknowledged within 30 minutes (assumed under service_levels.priority_1_response_minutes), supported continuously 24 hours a day, 7 days a week. operations.support_hours, service_levels.priority_1_response_minutes, K-17
OR-2 service_level The core platform landing zone and network routing maintain at least 99.9% monthly availability, operating 24 hours a day, 7 days a week. K-14, operations.availability_hours
OR-3 service_level Platform foundation failover to the secondary recovery region is completed within 4 hours (assumed under service_levels.recovery_time_hours) in the event of a primary region outage. K-7, service_levels.recovery_time_hours
OR-4 service_level Platform infrastructure configuration drift and backup state maintain a recovery point objective (RPO) of no more than 1 hour of data loss. K-8
OR-5 service_level Dedicated hybrid connectivity between on-premises environments and the cloud platform maintains SLA-backed, low-latency private data transmission. K-5
OR-6 service_level Centralised inspection appliances maintain high-bandwidth network throughput capacity to prevent traffic constraints during peak transaction flows. K-19
OR-7 process All infrastructure changes require automated pipeline validation, linting, and peer approval via pull requests prior to merge and release (assumed under operations.change_process). K-18, operations.change_process
OR-8 process Outbound internet traffic is inspected through centralised stateful packet inspection, URL filtering, and threat detection before leaving the environment. K-6
OR-9 process User lifecycle management and multi-factor authentication enforcement are governed through centralised identity provider conditional access policies. K-9
OR-10 process The warm standby environment operates at a minimal pilot light footprint with reduced capacity during normal operations until activated for failover. K-2, K-20
OR-11 process Standby disaster recovery infrastructure is scaled to full operational capacity automatically only upon invocation of a disaster recovery failover. K-21
OR-12 process Platform foundation operational readiness and workload ingestion readiness are achieved within 10 weeks (assumed as 50 working days under solution.build.duration_days) from commencement. K-16, solution.build.duration_days
OR-13 organisation Platform foundation operations and support are delivered under a service-provider operating model. sourcing.model
OR-14 organisation Operational activities and support delivery are conducted solely from within the United Kingdom, Poland, and India. sourcing.delivery_countries
OR-15 tooling Operational telemetry, metrics, and incident logging are integrated into the centralised platform operations suite (assumed under service_management.tooling). service_management.tooling
OR-16 compliance All customer data and payment processing activities remain strictly within United Kingdom and European Union legal jurisdictions. K-1
OR-17 compliance The PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements. K-3
OR-18 compliance Workload application programming interfaces and payment services are accessible exclusively through private corporate network paths. K-4
OR-19 compliance Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks. K-10
OR-20 compliance The production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements. K-11
OR-21 compliance Confidential payment data is secured using customer-controlled cryptographic keys against unauthorized platform-level access or data exposure. K-12
OR-22 compliance Audit logs are immutably retained and protected against modification, deletion, or truncation by any identity prior to retention expiration. K-13
OR-23 compliance Cloud data centres supporting primary and secondary regions have published carbon-free energy (CFE) performance metrics. K-15
OR-24 compliance Platform foundation operations maintain continuous compliance and audit evidence across DORA, ISO 27001, and PCI-DSS v4.0 frameworks. compliance.frameworks

Capabilities

Capability What it is Serves Covers Hours Effort a month
C-1 Incident management OR-1 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 24x7 40 h
C-2 Monitoring and alerting OR-1, OR-5, OR-15 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 24x7 60 h
C-3 Problem management OR-2 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 20 h
C-4 Service request fulfilment OR-13, OR-14 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 30 h
C-5 Change enablement OR-7 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 20 h
C-6 Release and deployment OR-7 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 20 h
C-7 Configuration management OR-4, OR-17, OR-18 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 15 h
C-8 Backup and recovery OR-4 S-7, S-8, S-10 business 10 h
C-9 Service continuity OR-3, OR-11 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 16 h
C-10 Capacity and performance management OR-2, OR-5, OR-6, OR-10 S-2, S-3, S-4 business 10 h
C-11 Access management OR-9, OR-14, OR-21 S-5, S-6, S-7 business 20 h
C-12 Vulnerability and patch management OR-20 S-3 business 25 h
C-13 Security monitoring and response OR-8, OR-17, OR-22 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 24x7 60 h
C-14 Cost management OR-10 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 8 h
C-15 Service level management OR-2 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 8 h
C-16 Platform product management OR-12 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 40 h
C-17 Self-service and golden paths OR-12 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 40 h
C-18 Enablement OR-12 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 40 h
C-19 Delivery and developer experience measurement OR-12 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 10 h
C-20 Supplier management OR-13, OR-19 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 10 h
C-21 Regulatory evidence and reporting OR-16, OR-19, OR-20, OR-22, OR-23, OR-24 S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9, S-10, S-11 business 30 h

Who does what

Role Party Country Level Hours
Platform Reliability Lead Managed Service Provider (provider) GB lead business
Platform SRE Managed Service Provider (provider) PL senior 24x7
Security Analyst Managed Service Provider (provider) IN senior 24x7
Platform Engineer Managed Service Provider (provider) PL senior business
Enablement Specialist Managed Service Provider (provider) GB senior business
Compliance Officer Managed Service Provider (provider) GB lead business
Product Manager Managed Service Provider (provider) GB lead business
Customer Service Owner Customer Organization (customer) GB lead business

The teams, as Team Topologies names their kinds:

Team Kind Party Roles Purpose
Platform Engineering Team platform Managed Service Provider Platform Reliability Lead, Platform Engineer, Compliance Officer, Product Manager
Platform Operations Team platform Managed Service Provider Platform SRE
Security Operations Team platform Managed Service Provider Security Analyst 24x7 Security Monitoring and Response
Developer Enablement Team enabling Managed Service Provider Enablement Specialist
Customer Governance and App Squads stream-aligned Customer Organization Customer Service Owner

How the teams work together:

From To Mode Until Purpose
Customer Governance and App Squads Platform Engineering Team x-as-a-service Application teams consume platform services through the self-service portal.
Developer Enablement Team Customer Governance and App Squads facilitating Enablement specialists help application teams adopt golden paths and DORA metrics.
Developer Enablement Team Customer Governance and App Squads collaboration End of the 10-week foundation build period, returning to a facilitating mode. Enablement team pairs with application teams for initial workload ingestion.
Capability Platform Reliability Lead Platform SRE Security Analyst Platform Engineer Enablement Specialist Compliance Officer Product Manager Customer Service Owner
Incident management (C-1) A R C
Monitoring and alerting (C-2) A R C
Problem management (C-3) A R C
Service request fulfilment (C-4) A R C
Change enablement (C-5) A R C
Release and deployment (C-6) A R C
Configuration management (C-7) A R C
Backup and recovery (C-8) A R C
Service continuity (C-9) A R C
Capacity and performance management (C-10) A R C
Access management (C-11) R A C
Vulnerability and patch management (C-12) R A C
Security monitoring and response (C-13) R A C
Cost management (C-14) R A C
Service level management (C-15) A R C
Platform product management (C-16) A/R C
Self-service and golden paths (C-17) R A C
Enablement (C-18) R A C
Delivery and developer experience measurement (C-19) R A C
Supplier management (C-20) A/R C
Regulatory evidence and reporting (C-21) A/R C

A accountable, R responsible, C consulted, I informed.

Staffing and cost

Role Party Country Level Hours Effort a month People Cost a month
Platform Reliability Lead Managed Service Provider GB lead business 18.0 h 0.1 1,991 GBP
Platform SRE Managed Service Provider PL senior 24x7 138.0 h 5.0 41,640 GBP
Security Analyst Managed Service Provider IN senior 24x7 85.0 h 5.0 24,605 GBP
Platform Engineer Managed Service Provider PL senior business 171.0 h 1.2 7,768 GBP
Enablement Specialist Managed Service Provider GB senior business 50.0 h 0.4 4,213 GBP
Compliance Officer Managed Service Provider GB lead business 30.0 h 0.2 3,318 GBP
Product Manager Managed Service Provider GB lead business 40.0 h 0.3 4,424 GBP
Customer Service Owner Customer Organization GB lead business 0.0 h 0.0 not priced

12.2 people in all. Cost a month: 87,959 GBP.

Worked from rate card rate-card, version draft-2026-10-13. Its figures are placeholders: no price has been set, and this cost is an illustration. Converted from USD at 0.79, a rate set on 2026-10-13. The customer's own staff are counted and not priced. A Role that covers hours wider than a working day is never smaller than the team that can cover them.

Validation

Check What must hold Verdict Evidence
OC-1 Declarative infrastructure configurations restrict data location to UK and EU regions. pass Capability C-7 handles declarative state and configuration management, covering all required items. Platform Engineer (R-4) is responsible during business hours.
OC-2 Warm standby capacity limits on identity, encryption, and governance components are maintained through DR automation. pass Capability C-9 manages service continuity and DR failover rehearsals, covering items S-1, S-7, and S-9. Platform Engineer (R-4) is responsible.
OC-3 PCI-regulated production network configurations enforce isolation from non-PCI scopes. pass Capability C-7 manages configuration state and audits, ensuring isolation configurations are maintained. Platform Engineer (R-4) is responsible.
OC-4 Workload APIs are confirmed to be routable only via private corporate network paths. pass Capability C-7 audits configuration state for workload APIs, and Platform Engineer (R-4) is responsible.
OC-5 Hybrid interconnect capacity metrics demonstrate SLA-backed low latency. pass Capability C-10 reviews capacity and performance metrics, including the dedicated hybrid network interconnect. Platform Engineer (R-4) is responsible.
OC-6 Centralised inspection appliances actively perform stateful packet inspection on all egress traffic. pass Capability C-13 provides security monitoring and response, analyzing egress traffic inspection data 24x7 via Security Analyst (R-3).
OC-7 Service continuity rehearsals demonstrate secondary region failover in under 4 hours. pass Capability C-9 conducts bi-monthly DR failover rehearsals to ensure the 4-hour RTO is achievable. Platform Engineer (R-4) is responsible.
OC-8 Backup validation ensures an RPO of at most 1 hour. waits on finding (AF-3) AF-3: The solution lacks an automated backup service or vault to ensure state and configuration achieve the maximum data loss window (RPO) of 1 hour.
OC-9 Identity access policies require Entra ID multi-factor authentication for corporate users. pass Capability C-11 covers access management and policy reviews for corporate identity gateways. Platform Engineer (R-4) is responsible.
OC-10 Third-party supplier reviews include DORA risk assessments. pass Capability C-20 conducts supplier management and service reviews, incorporating DORA risk assessments. Platform Reliability Lead (R-1) is responsible.
OC-11 Production cardholder data environments maintain PCI-DSS v4.0 network isolation control compliance. pass Capability C-21 continuously collates regulatory evidence for PCI-DSS v4.0. Compliance Officer (R-6) is responsible.
OC-12 Confidential payment data storage systems ensure unauthorized access protection via customer-controlled keys. pass Capability C-11 governs access management for the cryptographic key management service (S-7). Platform Engineer (R-4) is responsible.
OC-13 Audit logs are actively monitored for modifications and deletions. pass Capability C-13 provides 24x7 security monitoring and response for audit logs (S-8). Security Analyst (R-3) is responsible.
OC-14 Monthly availability of network routing components is tracked and meets the 99.9% target. pass Capability C-15 aggregates and reports on service level objectives, including availability targets. Platform SRE (R-2) is responsible.
OC-15 Data centres supporting operations provide publicly validated carbon-free energy (CFE) metrics. pass Capability C-21 collates regulatory and compliance evidence, including carbon-free energy metrics. Compliance Officer (R-6) is responsible.
OC-16 Workload ingestion metrics confirm operational readiness within the initial 10-week build. pass Capability C-16 manages the platform backlog and adoption roadmap to confirm workload ingestion readiness. Product Manager (R-7) is responsible.
OC-17 A 24/7 service desk is resourced to actively log and respond to infrastructure priority incidents. pass Capability C-1 handles 24x7 incident management, and Platform SRE (R-2) provides 24x7 coverage to log and respond to incidents.
OC-18 CI/CD pipeline hooks enforce pull request approvals, validation, and linting before merge. pass Capability C-5 manages change enablement and pull request approvals. Platform Engineer (R-4) is responsible.
OC-19 NVA capacity tracking confirms instances utilize high-bandwidth machine families. pass Capability C-10 reviews capacity and performance for network virtual appliances. Platform Engineer (R-4) is responsible.
OC-20 Platform budget anomaly alerts check that the warm standby uses minimal infrastructure footprint. waits on finding (AF-2) AF-2: The solution lacks automated budget anomaly alerts out-of-the-box to track the minimal pilot light footprint of the warm standby region.
OC-21 Disaster recovery infrastructure automation limits full-capacity scaling strictly to failover occurrences. pass Capability C-9 conducts service continuity failovers, managing the DR infrastructure automation. Platform Engineer (R-4) is responsible.
OC-22 Operations and support delivery are provided solely under the agreed service-provider framework. pass Role R-1 (Platform Reliability Lead) is part of the Managed Service Provider party, fulfilling the agreed service-provider framework.
OC-23 Staff are located solely in authorized delivery countries. pass Role R-1 is located in GB, which is an authorized delivery country.
OC-24 Operational telemetry and incident logging are fully integrated into the operations suite. pass Capability C-2 performs continuous monitoring and alerting using the integrated operations suite. Platform SRE (R-2) is responsible 24x7.
OC-25 Compliance audits consistently certify continuous adherence across DORA, ISO 27001, and PCI-DSS v4.0 frameworks. pass Capability C-21 continuously collates audit evidence across DORA, ISO 27001, and PCI-DSS v4.0. Compliance Officer (R-6) is responsible.
OC-26 Incident responders use a secure remote access mechanism to troubleshoot Centralised Egress Traffic Inspection Gateways. waits on finding (AF-1) AF-1: The solution lacks a secure remote access mechanism (such as a bastion host or Identity-Aware Proxy) as a way in for responders to the Centralised Egress Traffic Inspection Gateway.

Each scenario is generated from the operating model and traced through it by code.

Scenario Result Path
Multi-Tier Environment Hierarchy & Isolation Boundary (S-1) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Multi-Tier Environment Hierarchy & Isolation Boundary (S-1) must be changed. pass Platform Engineer makes the change under C-5.
Dedicated Hybrid Network Interconnect Gateway (S-2) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Dedicated Hybrid Network Interconnect Gateway (S-2) must be changed. pass Platform Engineer makes the change under C-5.
Centralised Egress Traffic Inspection Gateway (S-3) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Centralised Egress Traffic Inspection Gateway (S-3) must be changed. pass Platform Engineer makes the change under C-5.
Transit Network Fabric & Routing Controller (S-4) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Transit Network Fabric & Routing Controller (S-4) must be changed. pass Platform Engineer makes the change under C-5.
Corporate Identity Federation Gateway (S-5) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Corporate Identity Federation Gateway (S-5) must be changed. pass Platform Engineer makes the change under C-5.
Automated Delivery Pipeline Identity Broker (S-6) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Automated Delivery Pipeline Identity Broker (S-6) must be changed. pass Platform Engineer makes the change under C-5.
Cryptographic Key Management & Rotation Service (S-7) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Cryptographic Key Management & Rotation Service (S-7) must be changed. pass Platform Engineer makes the change under C-5.
Centralised Immutable Audit Log Repository (S-8) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Centralised Immutable Audit Log Repository (S-8) must be changed. pass Platform Engineer makes the change under C-5.
Platform Compliance & Governance Guardrail Controller (S-9) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Platform Compliance & Governance Guardrail Controller (S-9) must be changed. pass Platform Engineer makes the change under C-5.
Declarative Infrastructure Provisioning & State Engine (S-10) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Declarative Infrastructure Provisioning & State Engine (S-10) must be changed. pass Platform Engineer makes the change under C-5.
Centralised Operational Telemetry & Alerting Engine (S-11) fails at an hour faults are responded to (24x7). pass Platform SRE responds under C-1, and Platform Reliability Lead is answerable.
Centralised Operational Telemetry & Alerting Engine (S-11) must be changed. pass Platform Engineer makes the change under C-5.
Condition K-1 must be shown to hold: Customer data and payment processing remain within United Kingdom and European Union legal jurisdictions. pass Check OC-1 on C-7 keeps it true.
Condition K-2 must be shown to hold: Warm standby environment operates with reduced capacity until activated during a disaster recovery failover. pass Check OC-2 on C-9 keeps it true.
Condition K-3 must be shown to hold: PCI-regulated production environment is isolated from non-PCI scopes according to PCI-DSS v4.0 network segmentation requirements. pass Check OC-3 on C-7 keeps it true.
Condition K-4 must be shown to hold: Workload APIs and payment services are accessible exclusively through private corporate network paths. pass Check OC-4 on C-7 keeps it true.
Condition K-5 must be shown to hold: Hybrid connection maintains low-latency, SLA-backed private data transmission between on-premises and Google Cloud. pass Check OC-5 on C-10 keeps it true.
Condition K-6 must be shown to hold: Centralised inspection appliances perform next-generation stateful packet inspection, URL filtering, and threat detection on outbound internet sessions. pass Check OC-6 on C-13 keeps it true.
Condition K-7 must be shown to hold: Platform foundation failover to europe-west1 can be completed within 4 hours during a primary region outage. pass Check OC-7 on C-9 keeps it true.
Condition K-8 must be shown to hold: Configuration drift and backup state achieve a maximum data loss window (RPO) of 1 hour. pass Check OC-8 on C-7 keeps it true.
Condition K-9 must be shown to hold: Corporate user lifecycle management and MFA enforcement are governed centrally by Entra ID conditional access policies. pass Check OC-9 on C-11 keeps it true.
Condition K-10 must be shown to hold: Platform governance and resilience architecture comply with DORA regulatory testing and third-party risk management frameworks. pass Check OC-10 on C-20 keeps it true.
Condition K-11 must be shown to hold: Production cardholder data environment satisfies PCI-DSS v4.0 isolation and security control requirements. pass Check OC-11 on C-21 keeps it true.
Condition K-12 must be shown to hold: Confidential payment data is secured against unauthorized platform-level access or data exposure. pass Check OC-12 on C-11 keeps it true.
Condition K-13 must be shown to hold: Audit logs cannot be modified, deleted, or shortened by any identity or administrator prior to retention expiration. pass Check OC-13 on C-13 keeps it true.
Condition K-14 must be shown to hold: Monthly availability of the core platform landing zone and network routing meets or exceeds 99.9%. pass Check OC-14 on C-15 keeps it true.
Condition K-15 must be shown to hold: Primary and secondary regions leverage Google Cloud data centres with published carbon-free energy (CFE) performance metrics. pass Check OC-15 on C-21 keeps it true.
Condition K-16 must be shown to hold: Platform foundation delivery and workload ingestion readiness are achieved within 10 weeks of project commencement. pass Check OC-16 on C-16 keeps it true.
Condition K-17 must be shown to hold: Central platform team operates 24/7 support for infrastructure incidents and availability alerts. pass Check OC-17 on C-1 keeps it true.
Condition K-18 must be shown to hold: Pull request workflows require automated CI/CD linting, validation, and peer approval prior to merge and deployment. pass Check OC-18 on C-5 keeps it true.
Condition K-19 must be shown to hold: NVA instances use machine families that support high bandwidth networking. pass Check OC-19 on C-10 keeps it true.
Condition K-20 must be shown to hold: The warm standby environment operates at a minimal pilot light footprint during normal operations. pass Check OC-20 on C-14 keeps it true.
Condition K-21 must be shown to hold: Automated disaster recovery scripts scale the standby environment to full capacity only during a failover event. pass Check OC-21 on C-9 keeps it true.
Managed Service Provider cannot be reached. pass Every Capability it is answerable for has a Role in another Party to turn to.

Findings and open questions

What operating this solution needs that the solution, as described, does not provide. Nothing here was designed around: each is for whoever owns the design.

  • AF-1 (S-3): The solution lacks a secure remote access mechanism (such as a bastion host or Identity-Aware Proxy) as a way in for responders to the Centralised Egress Traffic Inspection Gateway. Proposed: Add Identity-Aware Proxy or a secure bastion host to allow responders to securely access instances.
  • AF-2 (S-11): The solution lacks automated budget anomaly alerts to ensure the warm standby environment maintains a minimal pilot light footprint. Proposed: Configure Google Cloud Billing Budgets and alerts tied to the standby environment.
  • AF-3 (S-2, S-4): The solution lacks an automated backup service or vault to ensure state and configuration achieve the maximum data loss window (RPO) of 1 hour. Proposed: Implement Google Cloud Backup and DR service or enable automated object versioning with lifecycle policies.

Assumed for the customer, and open to change when they answer:

  • intent.business_outcomes: {'outcome': 'Continuous and resilient payment processing with high availability and low-latency hybrid connectivity', 'id': 'BO-1'}, {'outcome': 'Sustained regulatory compliance with DORA and PCI-DSS v4.0 security and resilience standards', 'id': 'BO-2'}, {'id': 'BO-3', 'outcome': 'Rapid and secure platform change releases through automated CI/CD delivery pipelines'}. Derived from customer request for a UK-regulated payment platform requiring high resilience, continuous compliance, and automated delivery.
  • intent.exclusions: Application container deployment and runtime microservices managed by application squads, Active-active secondary region in phase 1 (warm standby adopted). Derived from workload scope boundaries where application workloads are managed by application squads, and secondary region is warm standby rather than active-active.
  • solution.build.duration_days: 50. Derived from 10-week delivery window at 5 working days per week.
  • operations.change_process: Infrastructure changes managed via pull requests with required approvals and automated GitHub Actions CI/CD pipelines. Derived from request and scope specification indicating pull-request driven changes with peer review and GitHub Actions CI/CD automation.
  • organisation.existing_teams: . Catalogue default: no existing operational teams assumed; roles to be provisioned under provider-operated model.
  • service_management.tooling: Google Cloud Operations Suite (Cloud Monitoring and Cloud Logging). Catalogue default: Google Cloud Operations Suite (Cloud Monitoring and Cloud Logging) with no separate third-party ticketing system mandated.
  • service_levels.priority_1_response_minutes: 30. Catalogue default for Priority 1 incident response acknowledgement.
  • service_levels.recovery_time_hours: 4. Catalogue default and aligned with target 4-hour RTO for warm standby disaster recovery in secondary region.

Sources

The Capabilities are from our own capability catalogue, which draws on these frameworks. It cites them and certifies nothing against them.

  • ITIL 4: Incident management practice; Monitoring and event management practice; Problem management practice; Service request management practice; Change enablement practice; Release management and Deployment management practices; Service configuration management practice; Service continuity management practice; Capacity and performance management practice; Service level management practice; Supplier management practice
  • Site Reliability Engineering: How Google Runs Production Systems: Managing Incidents; Monitoring Distributed Systems; Postmortem Culture: Learning from Failure; Release Engineering; Service Level Objectives
  • ISO/IEC 20000-1: Incident management; Service request management; Change management; Service continuity management; Capacity management; Service level management; Supplier management
  • Regulation (EU) 2022/2554, the Digital Operational Resilience Act: Article 17, ICT-related incident management process; Article 10, Detection; Article 12, Backup policies and procedures, restoration and recovery procedures and methods; Article 11, Response and recovery; Article 9, Protection and prevention; Article 28, General principles on ICT third-party risk; Article 19, Reporting of major ICT-related incidents
  • NIST Cybersecurity Framework: Detect: Continuous Monitoring; Identify: Asset Management; Recover: Incident Recovery Plan Execution; Protect: Identity Management, Authentication, and Access Control; Protect: Platform Security; Detect: Adverse Event Analysis; Respond: Incident Management
  • DevOps Research and Assessment (DORA) software delivery metrics: Change failure rate; Deployment frequency and lead time for changes; Deployment frequency; Lead time for changes; Change failure rate; Time to restore service
  • ISO/IEC 27001: Access control; Management of technical vulnerabilities; Information security incident management; Compliance with legal and contractual requirements
  • FinOps Framework: Allocation; Budgeting; Forecasting; Anomaly Management
  • CNCF Platforms White Paper (platform as a product): Platform as a product; Measuring platform success; Platform capabilities; Self-service; Platform as a product
  • Team Topologies: Organizing Business and Technology Teams for Fast Flow: Platform team; Thinnest viable platform; X-as-a-Service interaction mode; Enabling team; Facilitating interaction mode
  • The SPACE of Developer Productivity: Satisfaction and well-being; Performance; Activity; Communication and collaboration; Efficiency and flow
  • DevEx: What Actually Drives Productivity: Feedback loops; Cognitive load; Flow state

These references have not been checked against the frameworks by a person. Treat each as a pointer to where to look.