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>
This commit is contained in:
@@ -0,0 +1,191 @@
|
||||
[
|
||||
{
|
||||
"id": "C-1",
|
||||
"catalogue": "incident-management",
|
||||
"serves": ["OR-1", "OR-2"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 40,
|
||||
"basis": "Steady state handling of platform incidents and alerts across all components, expected to average around 10 hours a week."
|
||||
},
|
||||
{
|
||||
"id": "C-2",
|
||||
"catalogue": "monitoring-and-alerting",
|
||||
"serves": ["OR-1"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 30,
|
||||
"basis": "Configuring and tuning alerts for network, logs, and pipelines, and 24x7 event monitoring."
|
||||
},
|
||||
{
|
||||
"id": "C-3",
|
||||
"catalogue": "problem-management",
|
||||
"serves": ["OR-2", "OR-3"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Root cause analysis and problem record resolution following priority incidents."
|
||||
},
|
||||
{
|
||||
"id": "C-4",
|
||||
"catalogue": "service-request-fulfilment",
|
||||
"serves": ["OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Handling routine platform service requests in a shared operational model."
|
||||
},
|
||||
{
|
||||
"id": "C-5",
|
||||
"catalogue": "change-enablement",
|
||||
"serves": ["OR-4", "OR-5"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Managing change requests, ensuring customer platform team approval for network changes."
|
||||
},
|
||||
{
|
||||
"id": "C-6",
|
||||
"catalogue": "release-and-deployment",
|
||||
"serves": ["OR-4"],
|
||||
"items": ["S-3"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Managing pipeline execution to ensure approved changes reach production within one day."
|
||||
},
|
||||
{
|
||||
"id": "C-7",
|
||||
"catalogue": "configuration-management",
|
||||
"serves": ["OR-4", "OR-5", "OR-7"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Maintaining infrastructure as code configurations and tracking key rotation cycles."
|
||||
},
|
||||
{
|
||||
"id": "C-8",
|
||||
"catalogue": "backup-and-recovery",
|
||||
"serves": ["OR-2", "OR-10"],
|
||||
"items": ["S-2", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Validating retention policies for audit logs and backing up key configurations."
|
||||
},
|
||||
{
|
||||
"id": "C-9",
|
||||
"catalogue": "service-continuity",
|
||||
"serves": ["OR-3"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Periodic planning and rehearsal for regional disaster recovery."
|
||||
},
|
||||
{
|
||||
"id": "C-10",
|
||||
"catalogue": "capacity-and-performance",
|
||||
"serves": ["OR-3"],
|
||||
"items": ["S-1"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 5,
|
||||
"basis": "Reviewing network and interconnect utilization to maintain availability limits."
|
||||
},
|
||||
{
|
||||
"id": "C-11",
|
||||
"catalogue": "access-management",
|
||||
"serves": ["OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Managing permissions across the landing zone for customer and provider staff."
|
||||
},
|
||||
{
|
||||
"id": "C-12",
|
||||
"catalogue": "vulnerability-and-patch-management",
|
||||
"serves": ["OR-3"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Periodic scanning and application of security patches across platform components."
|
||||
},
|
||||
{
|
||||
"id": "C-13",
|
||||
"catalogue": "security-monitoring-and-response",
|
||||
"serves": ["OR-10"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 40,
|
||||
"basis": "24x7 monitoring of security events and ensuring audit log integrity is uncompromised."
|
||||
},
|
||||
{
|
||||
"id": "C-14",
|
||||
"catalogue": "cost-management",
|
||||
"serves": ["OR-6"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Compiling financial reports on monthly landing zone spend."
|
||||
},
|
||||
{
|
||||
"id": "C-15",
|
||||
"catalogue": "service-level-management",
|
||||
"serves": ["OR-6"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Measuring SLA achievement for the monthly report to the customer."
|
||||
},
|
||||
{
|
||||
"id": "C-16",
|
||||
"catalogue": "platform-product-management",
|
||||
"serves": ["OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Maintaining the backlog and roadmap for the platform foundation based on team needs."
|
||||
},
|
||||
{
|
||||
"id": "C-17",
|
||||
"catalogue": "self-service-and-golden-paths",
|
||||
"serves": ["OR-4", "OR-8"],
|
||||
"items": ["S-1", "S-3"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 25,
|
||||
"basis": "Automating network requests and pipeline steps to offer friction-free defaults."
|
||||
},
|
||||
{
|
||||
"id": "C-18",
|
||||
"catalogue": "enablement",
|
||||
"serves": ["OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Assisting platform teams through documentation and pairing to adopt the landing zone."
|
||||
},
|
||||
{
|
||||
"id": "C-19",
|
||||
"catalogue": "delivery-and-developer-experience-measurement",
|
||||
"serves": ["OR-4"],
|
||||
"items": ["S-3"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Measuring deployment frequency, cycle time, and team friction."
|
||||
},
|
||||
{
|
||||
"id": "C-20",
|
||||
"catalogue": "supplier-management",
|
||||
"serves": ["OR-8", "OR-9"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Ensuring provider compliance with SLA limits and delivery location constraints."
|
||||
},
|
||||
{
|
||||
"id": "C-21",
|
||||
"catalogue": "regulatory-evidence",
|
||||
"serves": ["OR-10"],
|
||||
"items": ["S-2"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Gathering regulatory evidence for EU DORA and tracking audit log retention periods."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,113 @@
|
||||
{
|
||||
"customer_case": "bench-landing-zone-shared",
|
||||
"execution_id": "case-01-landing-zone-shared-r1",
|
||||
"session_id": "9fe31b7a-c779-4d34-bcee-cc2e36533a1d",
|
||||
"intent_version": 1,
|
||||
"workflow_request": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.",
|
||||
"baseline": null,
|
||||
"overlay_skills": {},
|
||||
"options": {},
|
||||
"sources": {},
|
||||
"scope": {
|
||||
"status": "BASELINE_LOCKED",
|
||||
"readiness": {
|
||||
"supplied": 20,
|
||||
"answered": 0,
|
||||
"assumed": 3,
|
||||
"unknown": 10,
|
||||
"not_applicable": 0
|
||||
}
|
||||
},
|
||||
"status": "completed",
|
||||
"warnings": [],
|
||||
"risks": [],
|
||||
"assessment": null,
|
||||
"phases": {
|
||||
"scoping": "approved",
|
||||
"operational_requirements": "approved",
|
||||
"operating_model_design": "approved",
|
||||
"validation": "approved",
|
||||
"packaging": "approved"
|
||||
},
|
||||
"final_document": "operating-model-guide.md",
|
||||
"changes": null,
|
||||
"deliverables": {
|
||||
"operating_scope": {
|
||||
"document": "deliverables/operating_scope.md",
|
||||
"attachments": [
|
||||
"scope.json",
|
||||
"scope.yaml"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operational_requirements": {
|
||||
"document": "deliverables/operational_requirements.md",
|
||||
"attachments": [
|
||||
"operational-requirements.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"capability_model": {
|
||||
"document": "deliverables/capability_model.md",
|
||||
"attachments": [
|
||||
"capabilities.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"target_operating_model": {
|
||||
"document": "deliverables/target_operating_model.md",
|
||||
"attachments": [
|
||||
"findings.json",
|
||||
"organisation.mmd",
|
||||
"staffing.json",
|
||||
"target-operating-model.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"validation_results": {
|
||||
"document": "deliverables/validation_results.md",
|
||||
"attachments": [
|
||||
"scenarios.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operating_model_guide": {
|
||||
"document": "deliverables/operating_model_guide.md",
|
||||
"attachments": [],
|
||||
"status": "submitted"
|
||||
}
|
||||
},
|
||||
"files": [
|
||||
"capabilities.json",
|
||||
"deliverables/capability_model.md",
|
||||
"deliverables/operating_model_guide.md",
|
||||
"deliverables/operating_scope.md",
|
||||
"deliverables/operational_requirements.md",
|
||||
"deliverables/target_operating_model.md",
|
||||
"deliverables/validation_results.md",
|
||||
"findings.json",
|
||||
"operating-model-guide.md",
|
||||
"operational-requirements.json",
|
||||
"organisation.mmd",
|
||||
"scenarios.json",
|
||||
"scope.json",
|
||||
"scope.yaml",
|
||||
"staffing.json",
|
||||
"target-operating-model.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"staffing": {
|
||||
"people": 6.8,
|
||||
"cost_per_month": 46252,
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
}
|
||||
},
|
||||
"findings": [],
|
||||
"change_request": null,
|
||||
"capability_sources_verified": false
|
||||
}
|
||||
@@ -0,0 +1 @@
|
||||
[]
|
||||
@@ -0,0 +1,229 @@
|
||||
# Operating model guide: Google Cloud Landing Zone
|
||||
|
||||
## Summary
|
||||
|
||||
This guide sets out the target operating model for the Google Cloud landing zone platform foundation, which comprises the hub network and interconnect, the audit log store, the deployment pipeline, and encryption keys. The platform is operated under a shared service model between the customer and an external service provider. The service provider is responsible for incident response, continuous monitoring, and day-to-day administrative maintenance during 24x7 support hours, while the customer platform team operates during business hours, retaining architectural leadership, platform enablement, and final approval authority over all network changes.
|
||||
|
||||
Because all operational checks and scenario walk-throughs pass with no open findings and run costs remain within budget, the reader should look first at the assumptions and open questions, specifically the exclusion of hosted application workloads from platform foundation operations and the confirmation of the go-live date.
|
||||
|
||||
### Key figures
|
||||
|
||||
- Operated: 4 Items, with 3 Conditions to keep true.
|
||||
- Faults responded to: 24x7 hours.
|
||||
- Capabilities: 21.
|
||||
- People: 6.8. Cost a month: 46,252 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
|
||||
- Scenario walk-throughs: 13 of 13 pass.
|
||||
- Business outcomes: 3, 3 shown by a Measure.
|
||||
- Findings for whoever owns the design: 0.
|
||||
|
||||
## Business outcomes
|
||||
|
||||
**BO-1: New payment products reach customers in weeks rather than months.** Target: A change reaches production within a day of approval..
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Lead time for changes | outcome | dora-metrics | Within a day of approval | Delivery and developer experience measurement | Customer Platform Lead |
|
||||
|
||||
**BO-2: Payments are never unavailable for long.** Target: Restored within 4 hours..
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Time to restore service | outcome | dora-metrics | Restored within 4 hours | Delivery and developer experience measurement | Customer Platform Lead |
|
||||
|
||||
**BO-3: We keep the platform engineers we hire.**
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Developer satisfaction | guardrail | space-framework | | Delivery and developer experience measurement | Customer Platform Lead |
|
||||
| Developer cognitive load | leading | devex-framework | | Delivery and developer experience measurement | Customer Platform Lead |
|
||||
|
||||
## What is operated
|
||||
|
||||
| Item | What it is | Kind | Product | From |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| S-1 | Hub network and interconnect | network | Cloud Interconnect | |
|
||||
| S-2 | Audit log store | storage | Cloud Storage | |
|
||||
| S-3 | Deployment pipeline | pipeline | Cloud Build | |
|
||||
| S-4 | Encryption keys | keys | Cloud KMS | |
|
||||
|
||||
What must be kept true while it is run:
|
||||
|
||||
| Condition | On | What must hold | From |
|
||||
| --- | --- | --- | --- |
|
||||
| K-1 | S-1 | The platform is available at least 99.9% of each month. | |
|
||||
| K-2 | S-2 | Audit logs cannot be deleted for seven years. | |
|
||||
| K-3 | S-4 | Encryption keys are rotated every 90 days. | |
|
||||
|
||||
## Operational requirements
|
||||
|
||||
| Requirement | Kind | What must be achieved | From |
|
||||
| --- | --- | --- | --- |
|
||||
| OR-1 | service_level | A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour. | service_levels.priority_1_response_minutes, operations.support_hours |
|
||||
| OR-2 | service_level | Service is restored within 4 hours following a priority 1 incident. | service_levels.recovery_time_hours, BO-2 |
|
||||
| OR-3 | service_level | The hub network and interconnect maintains at least 99.9% availability during each month. | K-1 |
|
||||
| OR-4 | service_level | An approved change reaches production within one day of approval. | BO-1 |
|
||||
| OR-5 | process | Every change to the network requires approval from the customer platform team prior to implementation. | REQ-01 |
|
||||
| OR-6 | process | A report detailing service levels and operational costs is delivered to the customer monthly. | REQ-02 |
|
||||
| OR-7 | process | Encryption keys are rotated at least once every 90 days. | K-3 |
|
||||
| OR-8 | organisation | Platform operations is conducted under a shared service model between the customer and an external service provider. | sourcing.model |
|
||||
| OR-9 | organisation | Operational delivery is conducted exclusively from the United Kingdom, Poland, and India. | sourcing.delivery_countries |
|
||||
| OR-10 | compliance | Audit logs cannot be deleted for seven years. | K-2 |
|
||||
|
||||
## Capabilities
|
||||
|
||||
| Capability | What it is | Serves | Covers | Hours | Effort a month |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| C-1 | Incident management | OR-1, OR-2 | S-1, S-2, S-3, S-4 | 24x7 | 40 h |
|
||||
| C-2 | Monitoring and alerting | OR-1 | S-1, S-2, S-3, S-4 | 24x7 | 30 h |
|
||||
| C-3 | Problem management | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 15 h |
|
||||
| C-4 | Service request fulfilment | OR-8 | S-1, S-2, S-3, S-4 | business | 20 h |
|
||||
| C-5 | Change enablement | OR-4, OR-5 | S-1, S-2, S-3, S-4 | business | 20 h |
|
||||
| C-6 | Release and deployment | OR-4 | S-3 | business | 15 h |
|
||||
| C-7 | Configuration management | OR-4, OR-5, OR-7 | S-1, S-2, S-3, S-4 | business | 20 h |
|
||||
| C-8 | Backup and recovery | OR-2, OR-10 | S-2, S-4 | business | 10 h |
|
||||
| C-9 | Service continuity | OR-3 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-10 | Capacity and performance management | OR-3 | S-1 | business | 5 h |
|
||||
| C-11 | Access management | OR-8 | S-1, S-2, S-3, S-4 | business | 15 h |
|
||||
| C-12 | Vulnerability and patch management | OR-3 | S-1, S-2, S-3, S-4 | business | 20 h |
|
||||
| C-13 | Security monitoring and response | OR-10 | S-1, S-2, S-3, S-4 | 24x7 | 40 h |
|
||||
| C-14 | Cost management | OR-6 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-15 | Service level management | OR-6 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-16 | Platform product management | OR-8 | S-1, S-2, S-3, S-4 | business | 20 h |
|
||||
| C-17 | Self-service and golden paths | OR-4, OR-8 | S-1, S-3 | business | 25 h |
|
||||
| C-18 | Enablement | OR-8 | S-1, S-2, S-3, S-4 | business | 20 h |
|
||||
| C-19 | Delivery and developer experience measurement | OR-4 | S-3 | business | 15 h |
|
||||
| C-20 | Supplier management | OR-8, OR-9 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-21 | Regulatory evidence and reporting | OR-10 | S-2 | business | 10 h |
|
||||
|
||||
## Who does what
|
||||
|
||||
| Role | Party | Country | Level | Hours |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Customer Platform Lead | Customer (customer) | GB | lead | business |
|
||||
| Customer Platform Engineer | Customer (customer) | GB | senior | business |
|
||||
| Provider Delivery Lead | Service Provider (provider) | GB | lead | business |
|
||||
| Provider 24x7 SRE | Service Provider (provider) | PL | senior | 24x7 |
|
||||
| Provider Platform Engineer | Service Provider (provider) | IN | engineer | business |
|
||||
|
||||
The teams, as Team Topologies names their kinds:
|
||||
|
||||
| Team | Kind | Party | Roles | Purpose |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Platform team | platform | Customer | Customer Platform Lead, Customer Platform Engineer | Owns the platform roadmap, designs the networking, and provides explicit approvals for structural changes. |
|
||||
| Provider Operations | platform | Service Provider | Provider Delivery Lead, Provider 24x7 SRE, Provider Platform Engineer | Provides 24x7 incident response, security monitoring, and general infrastructure operational support. |
|
||||
|
||||
How the teams work together:
|
||||
|
||||
| From | To | Mode | Until | Purpose |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Platform team | Provider Operations | x-as-a-service | | The customer platform team consumes infrastructure monitoring and incident response from the provider operations team as a service. |
|
||||
|
||||
| Capability | Customer Platform Lead | Customer Platform Engineer | Provider Delivery Lead | Provider 24x7 SRE | Provider Platform Engineer |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Incident management (C-1) | C | | A | R | |
|
||||
| Monitoring and alerting (C-2) | C | | A | R | |
|
||||
| Problem management (C-3) | C | | A | | R |
|
||||
| Service request fulfilment (C-4) | C | | A | | R |
|
||||
| Change enablement (C-5) | A | R | | | R |
|
||||
| Release and deployment (C-6) | A | R | | | |
|
||||
| Configuration management (C-7) | A | | | | R |
|
||||
| Backup and recovery (C-8) | C | | A | | R |
|
||||
| Service continuity (C-9) | C | | A | | R |
|
||||
| Capacity and performance management (C-10) | A | | | | R |
|
||||
| Access management (C-11) | C | | A | | R |
|
||||
| Vulnerability and patch management (C-12) | C | | A | | R |
|
||||
| Security monitoring and response (C-13) | C | | A | R | |
|
||||
| Cost management (C-14) | A | | R | | |
|
||||
| Service level management (C-15) | C | | A/R | | |
|
||||
| Platform product management (C-16) | A/R | | | | |
|
||||
| Self-service and golden paths (C-17) | A | R | | | |
|
||||
| Enablement (C-18) | A | R | | | |
|
||||
| Delivery and developer experience measurement (C-19) | A | R | | | |
|
||||
| Supplier management (C-20) | A/R | | | | |
|
||||
| Regulatory evidence and reporting (C-21) | C | | A | | R |
|
||||
|
||||
A accountable, R responsible, C consulted, I informed.
|
||||
|
||||
## Staffing and cost
|
||||
|
||||
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
|
||||
| --- | --- | --- | --- | --- | --- | --- | --- |
|
||||
| Customer Platform Lead | Customer | GB | lead | business | 30.0 h | 0.2 | not priced |
|
||||
| Customer Platform Engineer | Customer | GB | senior | business | 85.0 h | 0.6 | not priced |
|
||||
| Provider Delivery Lead | Service Provider | GB | lead | business | 20.0 h | 0.1 | 2,212 GBP |
|
||||
| Provider 24x7 SRE | Service Provider | PL | senior | 24x7 | 110.0 h | 5.0 | 41,640 GBP |
|
||||
| Provider Platform Engineer | Service Provider | IN | engineer | business | 135.0 h | 0.9 | 2,400 GBP |
|
||||
|
||||
6.8 people in all. Cost a month: 46,252 GBP.
|
||||
The monthly budget is 60,000 GBP: this is within it.
|
||||
|
||||
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 | The hub network and interconnect maintains at least 99.9% availability during each month. | pass | Capability C-1 is responsible for incident management with 24x7 coverage by the Provider 24x7 SRE role (R-4), which is sufficient to maintain highly available operations by responding to faults around the clock. |
|
||||
| OC-2 | Audit logs are retained for seven years and cannot be deleted during this period. | pass | Capability C-8 manages backup and recovery, validating retention policies for audit logs. It is appropriately staffed during business hours. |
|
||||
| OC-3 | Encryption keys are rotated at least once every 90 days. | pass | Capability C-7 covers configuration management including tracking key rotation cycles, with the Customer Platform Lead (R-1) accountable and Provider Platform Engineer (R-5) responsible. |
|
||||
| OC-4 | A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour. | pass | Capability C-1 covers incident management 24x7 with the Provider 24x7 SRE (R-4) responsible, ensuring 15-minute acknowledgement at any hour. |
|
||||
| OC-5 | Service is restored within 4 hours following a priority 1 incident. | pass | Capability C-1 provides 24x7 incident response, ensuring that service is restored within the 4-hour target following a priority 1 incident. |
|
||||
| OC-6 | An approved change reaches production within one day of approval. | pass | Capability C-6 manages release and deployment, with the Customer Platform Engineer (R-2) responsible, ensuring approved changes reach production within a day. |
|
||||
| OC-7 | Every change to the network requires explicit approval from the customer platform team prior to implementation. | pass | Capability C-5 manages change enablement, with the Customer Platform Lead (R-1) accountable and engineers responsible, ensuring network changes require explicit approval. |
|
||||
| OC-8 | A report detailing service levels is delivered to the customer monthly. | pass | Capability C-15 covers service level management to measure SLA achievement and deliver the monthly report, with the Provider Delivery Lead (R-3) accountable and responsible. |
|
||||
| OC-9 | Platform operations is conducted under a shared service model between the customer and external provider. | pass | Capability C-20 handles supplier management to ensure shared service model compliance, with the Customer Platform Lead (R-1) accountable and responsible. |
|
||||
| OC-10 | The Customer Platform Lead role is located in the UK. | pass | The Customer Platform Lead role (R-1) is defined with country 'GB' (UK). |
|
||||
| OC-11 | The Customer Platform Engineer role is located in the UK. | pass | The Customer Platform Engineer role (R-2) is defined with country 'GB' (UK). |
|
||||
| OC-12 | The Provider Delivery Lead role is located in the UK. | pass | The Provider Delivery Lead role (R-3) is defined with country 'GB' (UK). |
|
||||
| OC-13 | The Provider 24x7 SRE role is located in Poland. | pass | The Provider 24x7 SRE role (R-4) is defined with country 'PL' (Poland). |
|
||||
| OC-14 | The Provider Platform Engineer role is located in India. | pass | The Provider Platform Engineer role (R-5) is defined with country 'IN' (India). |
|
||||
| OC-15 | A report detailing operational costs is delivered to the customer monthly. | pass | Capability C-14 covers cost management to compile financial reports on monthly landing zone spend, with the Provider Delivery Lead (R-3) responsible. |
|
||||
|
||||
Each scenario is generated from the operating model and traced through it by code.
|
||||
|
||||
| Scenario | Result | Path |
|
||||
| --- | --- | --- |
|
||||
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
|
||||
| Hub network and interconnect (S-1) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
|
||||
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
|
||||
| Audit log store (S-2) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
|
||||
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
|
||||
| Deployment pipeline (S-3) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
|
||||
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable. |
|
||||
| Encryption keys (S-4) must be changed. | pass | Customer Platform Engineer makes the change under C-5. |
|
||||
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-1 on C-1 keeps it true. |
|
||||
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-2 on C-8 keeps it true. |
|
||||
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-3 on C-7 keeps it true. |
|
||||
| Service Provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
|
||||
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 46,252 GBP, within the budget. |
|
||||
|
||||
## Findings and open questions
|
||||
|
||||
No findings: the solution provides what operating it needs.
|
||||
|
||||
Assumed for the customer, and open to change when they answer:
|
||||
|
||||
- `intent.exclusions`: Application workloads and services hosted on the platform foundation. Assumed based on platform foundation scope: workloads hosted on top of the landing zone are out of scope for this operating model.
|
||||
- `operations.change_process`: Changes go through a deployment pipeline with peer review, with explicit customer platform team approval required for all network changes.. Pipeline-driven changes with peer review, with customer platform team approval required for network changes per REQ-01.
|
||||
- `service_management.tooling`: Google Cloud operations suite and native Cloud provider tooling, with no separate external ITSM system.. Default native GCP operations tooling used as no external ITSM was specified.
|
||||
|
||||
## 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.
|
||||
@@ -0,0 +1,84 @@
|
||||
[
|
||||
{
|
||||
"id": "OR-1",
|
||||
"kind": "service_level",
|
||||
"statement": "A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour.",
|
||||
"source": [
|
||||
"service_levels.priority_1_response_minutes",
|
||||
"operations.support_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-2",
|
||||
"kind": "service_level",
|
||||
"statement": "Service is restored within 4 hours following a priority 1 incident.",
|
||||
"source": [
|
||||
"service_levels.recovery_time_hours",
|
||||
"BO-2"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-3",
|
||||
"kind": "service_level",
|
||||
"statement": "The hub network and interconnect maintains at least 99.9% availability during each month.",
|
||||
"source": [
|
||||
"K-1"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-4",
|
||||
"kind": "service_level",
|
||||
"statement": "An approved change reaches production within one day of approval.",
|
||||
"source": [
|
||||
"BO-1"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-5",
|
||||
"kind": "process",
|
||||
"statement": "Every change to the network requires approval from the customer platform team prior to implementation.",
|
||||
"source": [
|
||||
"REQ-01"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-6",
|
||||
"kind": "process",
|
||||
"statement": "A report detailing service levels and operational costs is delivered to the customer monthly.",
|
||||
"source": [
|
||||
"REQ-02"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-7",
|
||||
"kind": "process",
|
||||
"statement": "Encryption keys are rotated at least once every 90 days.",
|
||||
"source": [
|
||||
"K-3"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-8",
|
||||
"kind": "organisation",
|
||||
"statement": "Platform operations is conducted under a shared service model between the customer and an external service provider.",
|
||||
"source": [
|
||||
"sourcing.model"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-9",
|
||||
"kind": "organisation",
|
||||
"statement": "Operational delivery is conducted exclusively from the United Kingdom, Poland, and India.",
|
||||
"source": [
|
||||
"sourcing.delivery_countries"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-10",
|
||||
"kind": "compliance",
|
||||
"statement": "Audit logs cannot be deleted for seven years.",
|
||||
"source": [
|
||||
"K-2"
|
||||
]
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,15 @@
|
||||
flowchart TB
|
||||
subgraph P_1["Customer (customer)"]
|
||||
subgraph T_1["Platform team (platform team)"]
|
||||
R_1["Customer Platform Lead<br/>GB, lead, business"]
|
||||
R_2["Customer Platform Engineer<br/>GB, senior, business"]
|
||||
end
|
||||
end
|
||||
subgraph P_2["Service Provider (provider)"]
|
||||
subgraph T_2["Provider Operations (platform team)"]
|
||||
R_3["Provider Delivery Lead<br/>GB, lead, business"]
|
||||
R_4["Provider 24x7 SRE<br/>PL, senior, 24x7"]
|
||||
R_5["Provider Platform Engineer<br/>IN, engineer, business"]
|
||||
end
|
||||
end
|
||||
T_1 -- "x-as-a-service" --> T_2
|
||||
@@ -0,0 +1,93 @@
|
||||
[
|
||||
{
|
||||
"id": "SC-fault-S-1",
|
||||
"scenario": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-1",
|
||||
"scenario": "Hub network and interconnect (S-1) must be changed.",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Customer Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-2",
|
||||
"scenario": "Audit log store (S-2) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-2",
|
||||
"scenario": "Audit log store (S-2) must be changed.",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Customer Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-3",
|
||||
"scenario": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-3",
|
||||
"scenario": "Deployment pipeline (S-3) must be changed.",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Customer Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-4",
|
||||
"scenario": "Encryption keys (S-4) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-4",
|
||||
"scenario": "Encryption keys (S-4) must be changed.",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Customer Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-1",
|
||||
"scenario": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month.",
|
||||
"about": "K-1",
|
||||
"passes": true,
|
||||
"path": "Check OC-1 on C-1 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-2",
|
||||
"scenario": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years.",
|
||||
"about": "K-2",
|
||||
"passes": true,
|
||||
"path": "Check OC-2 on C-8 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-3",
|
||||
"scenario": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days.",
|
||||
"about": "K-3",
|
||||
"passes": true,
|
||||
"path": "Check OC-3 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-party-P-2",
|
||||
"scenario": "Service Provider cannot be reached.",
|
||||
"about": "P-2",
|
||||
"passes": true,
|
||||
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"id": "SC-budget",
|
||||
"scenario": "A month's cost of operating is compared with the budget of 60,000 GBP.",
|
||||
"about": "commercial.monthly_run_budget",
|
||||
"passes": true,
|
||||
"path": "The cost is 46,252 GBP, within the budget."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,202 @@
|
||||
{
|
||||
"kind": "platform_foundation",
|
||||
"stated": {
|
||||
"engagement": {
|
||||
"kind": "platform_foundation"
|
||||
},
|
||||
"intent": {
|
||||
"statement": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.\n",
|
||||
"requirements": [
|
||||
{
|
||||
"id": "REQ-01",
|
||||
"statement": "Our platform team approves every change to the network."
|
||||
},
|
||||
{
|
||||
"id": "REQ-02",
|
||||
"statement": "We receive a monthly report of service levels and cost."
|
||||
}
|
||||
],
|
||||
"business_outcomes": [
|
||||
{
|
||||
"id": "BO-1",
|
||||
"outcome": "New payment products reach customers in weeks rather than months.",
|
||||
"target": "A change reaches production within a day of approval."
|
||||
},
|
||||
{
|
||||
"id": "BO-2",
|
||||
"outcome": "Payments are never unavailable for long.",
|
||||
"target": "Restored within 4 hours."
|
||||
},
|
||||
{
|
||||
"id": "BO-3",
|
||||
"outcome": "We keep the platform engineers we hire."
|
||||
}
|
||||
]
|
||||
},
|
||||
"solution": {
|
||||
"cloud_provider": "gcp",
|
||||
"items": [
|
||||
{
|
||||
"id": "S-1",
|
||||
"name": "Hub network and interconnect",
|
||||
"kind": "network",
|
||||
"product": "Cloud Interconnect"
|
||||
},
|
||||
{
|
||||
"id": "S-2",
|
||||
"name": "Audit log store",
|
||||
"kind": "storage",
|
||||
"product": "Cloud Storage"
|
||||
},
|
||||
{
|
||||
"id": "S-3",
|
||||
"name": "Deployment pipeline",
|
||||
"kind": "pipeline",
|
||||
"product": "Cloud Build"
|
||||
},
|
||||
{
|
||||
"id": "S-4",
|
||||
"name": "Encryption keys",
|
||||
"kind": "keys",
|
||||
"product": "Cloud KMS"
|
||||
}
|
||||
],
|
||||
"conditions": [
|
||||
{
|
||||
"id": "K-1",
|
||||
"on": [
|
||||
"S-1"
|
||||
],
|
||||
"condition": "The platform is available at least 99.9% of each month."
|
||||
},
|
||||
{
|
||||
"id": "K-2",
|
||||
"on": [
|
||||
"S-2"
|
||||
],
|
||||
"condition": "Audit logs cannot be deleted for seven years."
|
||||
},
|
||||
{
|
||||
"id": "K-3",
|
||||
"on": [
|
||||
"S-4"
|
||||
],
|
||||
"condition": "Encryption keys are rotated every 90 days."
|
||||
}
|
||||
],
|
||||
"build": {
|
||||
"duration_days": 36
|
||||
}
|
||||
},
|
||||
"operations": {
|
||||
"support_hours": "24x7",
|
||||
"availability_hours": "24x7"
|
||||
},
|
||||
"sourcing": {
|
||||
"model": "shared",
|
||||
"delivery_countries": [
|
||||
"GB",
|
||||
"PL",
|
||||
"IN"
|
||||
]
|
||||
},
|
||||
"organisation": {
|
||||
"existing_teams": [
|
||||
{
|
||||
"name": "Platform team",
|
||||
"party": "customer",
|
||||
"hours": "business",
|
||||
"country": "GB"
|
||||
}
|
||||
]
|
||||
},
|
||||
"service_levels": {
|
||||
"priority_1_response_minutes": 15,
|
||||
"recovery_time_hours": 4
|
||||
},
|
||||
"compliance": {
|
||||
"frameworks": [
|
||||
"DORA"
|
||||
]
|
||||
},
|
||||
"commercial": {
|
||||
"currency": "GBP",
|
||||
"monthly_run_budget": 60000
|
||||
}
|
||||
},
|
||||
"binding": [
|
||||
"operations.support_hours",
|
||||
"sourcing.model",
|
||||
"sourcing.delivery_countries",
|
||||
"service_levels.priority_1_response_minutes",
|
||||
"service_levels.recovery_time_hours"
|
||||
],
|
||||
"assumed": [
|
||||
{
|
||||
"field": "intent.exclusions",
|
||||
"value": [
|
||||
"Application workloads and services hosted on the platform foundation"
|
||||
],
|
||||
"why": "Assumed based on platform foundation scope: workloads hosted on top of the landing zone are out of scope for this operating model."
|
||||
},
|
||||
{
|
||||
"field": "operations.change_process",
|
||||
"value": "Changes go through a deployment pipeline with peer review, with explicit customer platform team approval required for all network changes.",
|
||||
"why": "Pipeline-driven changes with peer review, with customer platform team approval required for network changes per REQ-01."
|
||||
},
|
||||
{
|
||||
"field": "service_management.tooling",
|
||||
"value": "Google Cloud operations suite and native Cloud provider tooling, with no separate external ITSM system.",
|
||||
"why": "Default native GCP operations tooling used as no external ITSM was specified."
|
||||
}
|
||||
],
|
||||
"to_decide": [],
|
||||
"to_ask": [
|
||||
{
|
||||
"field": "metadata.client_name",
|
||||
"prompt": "What is metadata.client_name?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.author",
|
||||
"prompt": "What is metadata.author?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.revision",
|
||||
"prompt": "What is metadata.revision?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.source",
|
||||
"prompt": "What is metadata.source?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "solution.build.customer_owned",
|
||||
"prompt": "Which parts of the build does the customer or their supplier own?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "solution.inherited_risks",
|
||||
"prompt": "What is already known to be unverified or at risk in the solution?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "operations.monitoring",
|
||||
"prompt": "Which monitoring and alerting is already in place or required?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "organisation.headcount_limit",
|
||||
"prompt": "Is there a limit on the number of people operating this?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "transition.go_live_date",
|
||||
"prompt": "When must the solution be in operation?",
|
||||
"severity": "LOW"
|
||||
}
|
||||
],
|
||||
"not_applicable": []
|
||||
}
|
||||
@@ -0,0 +1,198 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: bench-landing-zone-shared
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: ask
|
||||
status: BASELINE_LOCKED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We want our landing zone run as a shared service from go-live. A provider
|
||||
should
|
||||
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
|
||||
over changes to the network.
|
||||
|
||||
'
|
||||
requirements:
|
||||
- id: REQ-01
|
||||
statement: Our platform team approves every change to the network.
|
||||
- id: REQ-02
|
||||
statement: We receive a monthly report of service levels and cost.
|
||||
business_outcomes:
|
||||
- id: BO-1
|
||||
outcome: New payment products reach customers in weeks rather than months.
|
||||
target: A change reaches production within a day of approval.
|
||||
- id: BO-2
|
||||
outcome: Payments are never unavailable for long.
|
||||
target: Restored within 4 hours.
|
||||
- id: BO-3
|
||||
outcome: We keep the platform engineers we hire.
|
||||
exclusions:
|
||||
- Application workloads and services hosted on the platform foundation
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Hub network and interconnect
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
- id: S-2
|
||||
name: Audit log store
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
- id: S-3
|
||||
name: Deployment pipeline
|
||||
kind: pipeline
|
||||
product: Cloud Build
|
||||
- id: S-4
|
||||
name: Encryption keys
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
condition: The platform is available at least 99.9% of each month.
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-2
|
||||
condition: Audit logs cannot be deleted for seven years.
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-4
|
||||
condition: Encryption keys are rotated every 90 days.
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned: ask
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Changes go through a deployment pipeline with peer review, with
|
||||
explicit customer platform team approval required for all network changes.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: shared
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams:
|
||||
- name: Platform team
|
||||
party: customer
|
||||
hours: business
|
||||
country: GB
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: Google Cloud operations suite and native Cloud provider tooling, with no
|
||||
separate external ITSM system.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 15
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: 60000
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.exclusions
|
||||
statement: 'Assumed intent.exclusions is [''Application workloads and services hosted
|
||||
on the platform foundation'']. Assumed based on platform foundation scope: workloads
|
||||
hosted on top of the landing zone are out of scope for this operating model.'
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-02
|
||||
field: operations.change_process
|
||||
statement: Assumed operations.change_process is Changes go through a deployment
|
||||
pipeline with peer review, with explicit customer platform team approval required
|
||||
for all network changes.. Pipeline-driven changes with peer review, with customer
|
||||
platform team approval required for network changes per REQ-01.
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-03
|
||||
field: service_management.tooling
|
||||
statement: Assumed service_management.tooling is Google Cloud operations suite and
|
||||
native Cloud provider tooling, with no separate external ITSM system.. Default
|
||||
native GCP operations tooling used as no external ITSM was specified.
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: metadata.source
|
||||
prompt: What is metadata.source?
|
||||
severity: LOW
|
||||
- field: solution.build.customer_owned
|
||||
prompt: Which parts of the build does the customer or their supplier own?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: supplied
|
||||
commercial.monthly_run_budget: supplied
|
||||
compliance.frameworks: supplied
|
||||
engagement.kind: supplied
|
||||
intent.business_outcomes: supplied
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: supplied
|
||||
intent.statement: supplied
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: supplied
|
||||
metadata.revision: unknown
|
||||
metadata.source: unknown
|
||||
operations.availability_hours: supplied
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: supplied
|
||||
organisation.existing_teams: supplied
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: supplied
|
||||
service_levels.recovery_time_hours: supplied
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: unknown
|
||||
solution.build.duration_days: supplied
|
||||
solution.cloud_provider: supplied
|
||||
solution.conditions: supplied
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: supplied
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 20
|
||||
answered: 0
|
||||
assumed: 3
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
@@ -0,0 +1,102 @@
|
||||
{
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
},
|
||||
"conversion": {
|
||||
"from": "USD",
|
||||
"rate": 0.79,
|
||||
"as_of": "2026-10-13"
|
||||
},
|
||||
"roles": [
|
||||
{
|
||||
"role": "R-1",
|
||||
"name": "Customer Platform Lead",
|
||||
"party": "P-1",
|
||||
"party_name": "Customer",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 30.0,
|
||||
"people": 0.2,
|
||||
"cost_per_month": null
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"name": "Customer Platform Engineer",
|
||||
"party": "P-1",
|
||||
"party_name": "Customer",
|
||||
"country": "GB",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 85.0,
|
||||
"people": 0.6,
|
||||
"cost_per_month": null
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"name": "Provider Delivery Lead",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20.0,
|
||||
"people": 0.1,
|
||||
"cost_per_month": 2212
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"name": "Provider 24x7 SRE",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 110.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 41640
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"name": "Provider Platform Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "IN",
|
||||
"level": "engineer",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 135.0,
|
||||
"people": 0.9,
|
||||
"cost_per_month": 2400
|
||||
}
|
||||
],
|
||||
"people": 6.8,
|
||||
"cost_per_month": 46252,
|
||||
"by_party": {
|
||||
"P-2": 46252
|
||||
},
|
||||
"by_country": {
|
||||
"GB": 2212,
|
||||
"PL": 41640,
|
||||
"IN": 2400
|
||||
},
|
||||
"by_capability": {
|
||||
"C-14": 1106,
|
||||
"C-15": 1106,
|
||||
"C-1": 15142,
|
||||
"C-2": 11356,
|
||||
"C-13": 15142,
|
||||
"C-3": 267,
|
||||
"C-4": 355,
|
||||
"C-5": 178,
|
||||
"C-7": 355,
|
||||
"C-8": 178,
|
||||
"C-9": 178,
|
||||
"C-10": 89,
|
||||
"C-11": 267,
|
||||
"C-12": 355,
|
||||
"C-21": 178
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,540 @@
|
||||
{
|
||||
"parties": [
|
||||
{
|
||||
"kind": "customer",
|
||||
"id": "P-1",
|
||||
"name": "Customer"
|
||||
},
|
||||
{
|
||||
"kind": "provider",
|
||||
"name": "Service Provider",
|
||||
"id": "P-2"
|
||||
}
|
||||
],
|
||||
"teams": [
|
||||
{
|
||||
"party": "P-1",
|
||||
"id": "T-1",
|
||||
"name": "Platform team",
|
||||
"type": "platform",
|
||||
"purpose": "Owns the platform roadmap, designs the networking, and provides explicit approvals for structural changes."
|
||||
},
|
||||
{
|
||||
"purpose": "Provides 24x7 incident response, security monitoring, and general infrastructure operational support.",
|
||||
"id": "T-2",
|
||||
"type": "platform",
|
||||
"name": "Provider Operations",
|
||||
"party": "P-2"
|
||||
}
|
||||
],
|
||||
"roles": [
|
||||
{
|
||||
"team": "T-1",
|
||||
"country": "GB",
|
||||
"party": "P-1",
|
||||
"level": "lead",
|
||||
"id": "R-1",
|
||||
"hours": "business",
|
||||
"name": "Customer Platform Lead"
|
||||
},
|
||||
{
|
||||
"hours": "business",
|
||||
"team": "T-1",
|
||||
"level": "senior",
|
||||
"id": "R-2",
|
||||
"name": "Customer Platform Engineer",
|
||||
"country": "GB",
|
||||
"party": "P-1"
|
||||
},
|
||||
{
|
||||
"party": "P-2",
|
||||
"country": "GB",
|
||||
"team": "T-2",
|
||||
"hours": "business",
|
||||
"id": "R-3",
|
||||
"name": "Provider Delivery Lead",
|
||||
"level": "lead"
|
||||
},
|
||||
{
|
||||
"hours": "24x7",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"team": "T-2",
|
||||
"name": "Provider 24x7 SRE",
|
||||
"party": "P-2",
|
||||
"id": "R-4"
|
||||
},
|
||||
{
|
||||
"party": "P-2",
|
||||
"country": "IN",
|
||||
"name": "Provider Platform Engineer",
|
||||
"team": "T-2",
|
||||
"hours": "business",
|
||||
"id": "R-5",
|
||||
"level": "engineer"
|
||||
}
|
||||
],
|
||||
"interactions": [
|
||||
{
|
||||
"id": "I-1",
|
||||
"from": "T-1",
|
||||
"purpose": "The customer platform team consumes infrastructure monitoring and incident response from the provider operations team as a service.",
|
||||
"mode": "x_as_a_service",
|
||||
"to": "T-2"
|
||||
}
|
||||
],
|
||||
"measures": [
|
||||
{
|
||||
"id": "M-1",
|
||||
"framework": "dora-metrics",
|
||||
"measured_by": "C-19",
|
||||
"target": "Within a day of approval",
|
||||
"name": "Lead time for changes",
|
||||
"layer": "outcome",
|
||||
"outcome": "BO-1"
|
||||
},
|
||||
{
|
||||
"target": "Restored within 4 hours",
|
||||
"name": "Time to restore service",
|
||||
"outcome": "BO-2",
|
||||
"framework": "dora-metrics",
|
||||
"id": "M-2",
|
||||
"measured_by": "C-19",
|
||||
"layer": "outcome"
|
||||
},
|
||||
{
|
||||
"framework": "space-framework",
|
||||
"name": "Developer satisfaction",
|
||||
"measured_by": "C-19",
|
||||
"outcome": "BO-3",
|
||||
"layer": "guardrail",
|
||||
"id": "M-3"
|
||||
},
|
||||
{
|
||||
"framework": "devex-framework",
|
||||
"outcome": "BO-3",
|
||||
"name": "Developer cognitive load",
|
||||
"layer": "leading",
|
||||
"measured_by": "C-19",
|
||||
"id": "M-4"
|
||||
}
|
||||
],
|
||||
"responsibilities": [
|
||||
{
|
||||
"capability": "C-1",
|
||||
"kind": "accountable",
|
||||
"role": "R-3",
|
||||
"id": "RS-1"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"capability": "C-1",
|
||||
"id": "RS-2",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"id": "RS-3",
|
||||
"capability": "C-1",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"capability": "C-2",
|
||||
"role": "R-3",
|
||||
"kind": "accountable",
|
||||
"id": "RS-4"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"capability": "C-2",
|
||||
"id": "RS-5",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"capability": "C-2",
|
||||
"role": "R-1",
|
||||
"kind": "consulted",
|
||||
"id": "RS-6"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"id": "RS-7",
|
||||
"capability": "C-3",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"id": "RS-8",
|
||||
"capability": "C-3",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"capability": "C-3",
|
||||
"id": "RS-9",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"capability": "C-4",
|
||||
"kind": "accountable",
|
||||
"id": "RS-10",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"id": "RS-11",
|
||||
"capability": "C-4",
|
||||
"kind": "responsible",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"capability": "C-4",
|
||||
"kind": "consulted",
|
||||
"id": "RS-12",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"capability": "C-5",
|
||||
"id": "RS-13",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-5",
|
||||
"kind": "responsible",
|
||||
"id": "RS-14",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"capability": "C-5",
|
||||
"role": "R-5",
|
||||
"id": "RS-15",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"role": "R-1",
|
||||
"capability": "C-6",
|
||||
"id": "RS-16"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"id": "RS-17",
|
||||
"capability": "C-6",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-7",
|
||||
"id": "RS-18",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"id": "RS-19",
|
||||
"capability": "C-7",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"id": "RS-20",
|
||||
"kind": "accountable",
|
||||
"capability": "C-8",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"capability": "C-8",
|
||||
"role": "R-5",
|
||||
"kind": "responsible",
|
||||
"id": "RS-21"
|
||||
},
|
||||
{
|
||||
"capability": "C-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-22",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"capability": "C-9",
|
||||
"kind": "accountable",
|
||||
"id": "RS-23"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"id": "RS-24",
|
||||
"capability": "C-9",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"capability": "C-9",
|
||||
"id": "RS-25",
|
||||
"role": "R-1",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-10",
|
||||
"id": "RS-26",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"capability": "C-10",
|
||||
"id": "RS-27",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"capability": "C-11",
|
||||
"id": "RS-28",
|
||||
"kind": "accountable",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"capability": "C-11",
|
||||
"kind": "responsible",
|
||||
"role": "R-5",
|
||||
"id": "RS-29"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"capability": "C-11",
|
||||
"id": "RS-30",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-12",
|
||||
"id": "RS-31",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"capability": "C-12",
|
||||
"id": "RS-32",
|
||||
"role": "R-5",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"capability": "C-12",
|
||||
"role": "R-1",
|
||||
"id": "RS-33"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"id": "RS-34",
|
||||
"kind": "accountable",
|
||||
"capability": "C-13"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"id": "RS-35",
|
||||
"role": "R-4",
|
||||
"capability": "C-13"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"kind": "consulted",
|
||||
"capability": "C-13",
|
||||
"id": "RS-36"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"id": "RS-37",
|
||||
"role": "R-1",
|
||||
"capability": "C-14"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"capability": "C-14",
|
||||
"id": "RS-38",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"id": "RS-39",
|
||||
"capability": "C-15",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-3",
|
||||
"id": "RS-40",
|
||||
"capability": "C-15"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"id": "RS-41",
|
||||
"capability": "C-15",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-16",
|
||||
"id": "RS-42",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"kind": "responsible",
|
||||
"id": "RS-43",
|
||||
"capability": "C-16"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"role": "R-1",
|
||||
"id": "RS-44",
|
||||
"capability": "C-17"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"id": "RS-45",
|
||||
"role": "R-2",
|
||||
"capability": "C-17"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"capability": "C-18",
|
||||
"id": "RS-46",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"id": "RS-47",
|
||||
"kind": "responsible",
|
||||
"role": "R-2",
|
||||
"capability": "C-18"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"id": "RS-48",
|
||||
"capability": "C-19",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"kind": "responsible",
|
||||
"capability": "C-19",
|
||||
"id": "RS-49"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"capability": "C-20",
|
||||
"id": "RS-50",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"id": "RS-51",
|
||||
"kind": "responsible",
|
||||
"capability": "C-20",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"id": "RS-52",
|
||||
"kind": "accountable",
|
||||
"capability": "C-21",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"id": "RS-53",
|
||||
"role": "R-5",
|
||||
"kind": "responsible",
|
||||
"capability": "C-21"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"id": "RS-54",
|
||||
"capability": "C-21",
|
||||
"kind": "consulted"
|
||||
}
|
||||
],
|
||||
"checks": [
|
||||
{
|
||||
"condition": "The hub network and interconnect maintains at least 99.9% availability during each month.",
|
||||
"id": "OC-1",
|
||||
"source": "K-1",
|
||||
"on": "C-1"
|
||||
},
|
||||
{
|
||||
"condition": "Audit logs are retained for seven years and cannot be deleted during this period.",
|
||||
"on": "C-8",
|
||||
"source": "K-2",
|
||||
"id": "OC-2"
|
||||
},
|
||||
{
|
||||
"on": "C-7",
|
||||
"condition": "Encryption keys are rotated at least once every 90 days.",
|
||||
"source": "K-3",
|
||||
"id": "OC-3"
|
||||
},
|
||||
{
|
||||
"condition": "A priority 1 fault on any Item is acknowledged within 15 minutes, at any hour.",
|
||||
"id": "OC-4",
|
||||
"source": "OR-1",
|
||||
"on": "C-1"
|
||||
},
|
||||
{
|
||||
"id": "OC-5",
|
||||
"condition": "Service is restored within 4 hours following a priority 1 incident.",
|
||||
"on": "C-1",
|
||||
"source": "OR-2"
|
||||
},
|
||||
{
|
||||
"condition": "An approved change reaches production within one day of approval.",
|
||||
"on": "C-6",
|
||||
"source": "OR-4",
|
||||
"id": "OC-6"
|
||||
},
|
||||
{
|
||||
"source": "OR-5",
|
||||
"id": "OC-7",
|
||||
"on": "C-5",
|
||||
"condition": "Every change to the network requires explicit approval from the customer platform team prior to implementation."
|
||||
},
|
||||
{
|
||||
"source": "OR-6",
|
||||
"id": "OC-8",
|
||||
"condition": "A report detailing service levels is delivered to the customer monthly.",
|
||||
"on": "C-15"
|
||||
},
|
||||
{
|
||||
"on": "C-20",
|
||||
"source": "OR-8",
|
||||
"condition": "Platform operations is conducted under a shared service model between the customer and external provider.",
|
||||
"id": "OC-9"
|
||||
},
|
||||
{
|
||||
"on": "R-1",
|
||||
"condition": "The Customer Platform Lead role is located in the UK.",
|
||||
"source": "OR-9",
|
||||
"id": "OC-10"
|
||||
},
|
||||
{
|
||||
"source": "OR-9",
|
||||
"on": "R-2",
|
||||
"condition": "The Customer Platform Engineer role is located in the UK.",
|
||||
"id": "OC-11"
|
||||
},
|
||||
{
|
||||
"on": "R-3",
|
||||
"condition": "The Provider Delivery Lead role is located in the UK.",
|
||||
"source": "OR-9",
|
||||
"id": "OC-12"
|
||||
},
|
||||
{
|
||||
"id": "OC-13",
|
||||
"condition": "The Provider 24x7 SRE role is located in Poland.",
|
||||
"on": "R-4",
|
||||
"source": "OR-9"
|
||||
},
|
||||
{
|
||||
"id": "OC-14",
|
||||
"condition": "The Provider Platform Engineer role is located in India.",
|
||||
"source": "OR-9",
|
||||
"on": "R-5"
|
||||
},
|
||||
{
|
||||
"source": "OR-6",
|
||||
"on": "C-14",
|
||||
"id": "OC-15",
|
||||
"condition": "A report detailing operational costs is delivered to the customer monthly."
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,149 @@
|
||||
{
|
||||
"dry_run": {
|
||||
"verdict": "pass",
|
||||
"evidence": "13 of 13 scenario walk-throughs pass."
|
||||
},
|
||||
"checks": [
|
||||
{
|
||||
"check": "OC-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-1 is responsible for incident management with 24x7 coverage by the Provider 24x7 SRE role (R-4), which is sufficient to maintain highly available operations by responding to faults around the clock."
|
||||
},
|
||||
{
|
||||
"check": "OC-2",
|
||||
"evidence": "Capability C-8 manages backup and recovery, validating retention policies for audit logs. It is appropriately staffed during business hours.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "OC-3",
|
||||
"evidence": "Capability C-7 covers configuration management including tracking key rotation cycles, with the Customer Platform Lead (R-1) accountable and Provider Platform Engineer (R-5) responsible.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-1 covers incident management 24x7 with the Provider 24x7 SRE (R-4) responsible, ensuring 15-minute acknowledgement at any hour.",
|
||||
"check": "OC-4"
|
||||
},
|
||||
{
|
||||
"check": "OC-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-1 provides 24x7 incident response, ensuring that service is restored within the 4-hour target following a priority 1 incident."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-6 manages release and deployment, with the Customer Platform Engineer (R-2) responsible, ensuring approved changes reach production within a day.",
|
||||
"check": "OC-6"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-5 manages change enablement, with the Customer Platform Lead (R-1) accountable and engineers responsible, ensuring network changes require explicit approval.",
|
||||
"check": "OC-7"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-8",
|
||||
"evidence": "Capability C-15 covers service level management to measure SLA achievement and deliver the monthly report, with the Provider Delivery Lead (R-3) accountable and responsible."
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-20 handles supplier management to ensure shared service model compliance, with the Customer Platform Lead (R-1) accountable and responsible.",
|
||||
"verdict": "pass",
|
||||
"check": "OC-9"
|
||||
},
|
||||
{
|
||||
"check": "OC-10",
|
||||
"verdict": "pass",
|
||||
"evidence": "The Customer Platform Lead role (R-1) is defined with country 'GB' (UK)."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-11",
|
||||
"evidence": "The Customer Platform Engineer role (R-2) is defined with country 'GB' (UK)."
|
||||
},
|
||||
{
|
||||
"check": "OC-12",
|
||||
"evidence": "The Provider Delivery Lead role (R-3) is defined with country 'GB' (UK).",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "The Provider 24x7 SRE role (R-4) is defined with country 'PL' (Poland).",
|
||||
"check": "OC-13"
|
||||
},
|
||||
{
|
||||
"check": "OC-14",
|
||||
"verdict": "pass",
|
||||
"evidence": "The Provider Platform Engineer role (R-5) is defined with country 'IN' (India)."
|
||||
},
|
||||
{
|
||||
"check": "OC-15",
|
||||
"evidence": "Capability C-14 covers cost management to compile financial reports on monthly landing zone spend, with the Provider Delivery Lead (R-3) responsible.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Hub network and interconnect (S-1) must be changed. Customer Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Audit log store (S-2) fails at an hour faults are responded to (24x7). Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Audit log store (S-2) must be changed. Customer Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Deployment pipeline (S-3) must be changed. Customer Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Encryption keys (S-4) fails at an hour faults are responded to (24x7). Provider 24x7 SRE responds under C-1, and Provider Delivery Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Encryption keys (S-4) must be changed. Customer Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. Check OC-1 on C-1 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. Check OC-2 on C-8 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. Check OC-3 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-party-P-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Service Provider cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"check": "SC-budget",
|
||||
"verdict": "pass",
|
||||
"evidence": "A month's cost of operating is compared with the budget of 60,000 GBP. The cost is 46,252 GBP, within the budget."
|
||||
}
|
||||
],
|
||||
"proposed_additions": []
|
||||
}
|
||||
@@ -0,0 +1,329 @@
|
||||
[
|
||||
{
|
||||
"id": "C-1",
|
||||
"catalogue": "incident-management",
|
||||
"serves": [
|
||||
"OR-1",
|
||||
"OR-2"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Triage of platform alerts and handling an estimated 1-2 major incidents per month."
|
||||
},
|
||||
{
|
||||
"id": "C-2",
|
||||
"catalogue": "monitoring-and-alerting",
|
||||
"serves": [
|
||||
"OR-1",
|
||||
"OR-3"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 24,
|
||||
"basis": "Continuous watching of alerts and maintaining dashboard configurations across all foundational components."
|
||||
},
|
||||
{
|
||||
"id": "C-3",
|
||||
"catalogue": "problem-management",
|
||||
"serves": [
|
||||
"OR-2",
|
||||
"OR-3"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 12,
|
||||
"basis": "Conducting post-mortems and root cause analysis for any significant platform degradation."
|
||||
},
|
||||
{
|
||||
"id": "C-4",
|
||||
"catalogue": "service-request-fulfilment",
|
||||
"serves": [
|
||||
"OR-6"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Handling access requests, log extraction, or ad-hoc platform configuration inquiries from the customer team."
|
||||
},
|
||||
{
|
||||
"id": "C-5",
|
||||
"catalogue": "change-enablement",
|
||||
"serves": [
|
||||
"OR-4"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Reviewing and coordinating hub network modifications requiring customer team approvals."
|
||||
},
|
||||
{
|
||||
"id": "C-6",
|
||||
"catalogue": "release-and-deployment",
|
||||
"serves": [
|
||||
"OR-4"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-3"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 12,
|
||||
"basis": "Overseeing automated pipeline executions and intervening in any failed pipeline deployments."
|
||||
},
|
||||
{
|
||||
"id": "C-7",
|
||||
"catalogue": "configuration-management",
|
||||
"serves": [
|
||||
"OR-4"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 8,
|
||||
"basis": "Validating infrastructure-as-code state drifts and ensuring configuration matches approved deployments."
|
||||
},
|
||||
{
|
||||
"id": "C-8",
|
||||
"catalogue": "backup-and-recovery",
|
||||
"serves": [
|
||||
"OR-2"
|
||||
],
|
||||
"items": [
|
||||
"S-2",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 4,
|
||||
"basis": "Periodic testing of key recovery procedures and verifying log retention accessibility."
|
||||
},
|
||||
{
|
||||
"id": "C-9",
|
||||
"catalogue": "service-continuity",
|
||||
"serves": [
|
||||
"OR-2",
|
||||
"OR-3"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 8,
|
||||
"basis": "Quarterly rehearsal of regional failover scenarios amortized monthly."
|
||||
},
|
||||
{
|
||||
"id": "C-10",
|
||||
"catalogue": "capacity-and-performance",
|
||||
"serves": [
|
||||
"OR-3"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-3"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 4,
|
||||
"basis": "Reviewing hub network interconnect utilization and deployment pipeline throughput."
|
||||
},
|
||||
{
|
||||
"id": "C-11",
|
||||
"catalogue": "access-management",
|
||||
"serves": [
|
||||
"OR-8"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Managing and auditing IAM access limits to ensure the immutability of the audit log store."
|
||||
},
|
||||
{
|
||||
"id": "C-12",
|
||||
"catalogue": "vulnerability-and-patch-management",
|
||||
"serves": [
|
||||
"OR-3"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 16,
|
||||
"basis": "Routine scanning and applying necessary patches or mitigations to the cloud foundation components."
|
||||
},
|
||||
{
|
||||
"id": "C-13",
|
||||
"catalogue": "security-monitoring-and-response",
|
||||
"serves": [
|
||||
"OR-1",
|
||||
"OR-8"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 24,
|
||||
"basis": "Monitoring security event signals and investigating potential unauthorized access attempts across all hours."
|
||||
},
|
||||
{
|
||||
"id": "C-14",
|
||||
"catalogue": "cost-management",
|
||||
"serves": [
|
||||
"OR-5"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 6,
|
||||
"basis": "Reconciling cloud spend against budget and preparing the financial sections of the monthly report."
|
||||
},
|
||||
{
|
||||
"id": "C-15",
|
||||
"catalogue": "service-level-management",
|
||||
"serves": [
|
||||
"OR-5"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 8,
|
||||
"basis": "Aggregating metrics to produce the monthly reporting package on SLA achievements."
|
||||
},
|
||||
{
|
||||
"id": "C-16",
|
||||
"catalogue": "platform-product-management",
|
||||
"serves": [
|
||||
"OR-6"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 12,
|
||||
"basis": "Prioritizing the internal platform backlog to address friction reported by the customer engineering team."
|
||||
},
|
||||
{
|
||||
"id": "C-17",
|
||||
"catalogue": "self-service-and-golden-paths",
|
||||
"serves": [
|
||||
"OR-4",
|
||||
"OR-6"
|
||||
],
|
||||
"items": [
|
||||
"S-3"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 16,
|
||||
"basis": "Maintaining default pipeline configurations and automating network modification paths for easier customer team adoption."
|
||||
},
|
||||
{
|
||||
"id": "C-18",
|
||||
"catalogue": "enablement",
|
||||
"serves": [
|
||||
"OR-6"
|
||||
],
|
||||
"items": [
|
||||
"S-3"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Onboarding the customer platform team to the delivery pipelines and providing guidance on self-service usage."
|
||||
},
|
||||
{
|
||||
"id": "C-19",
|
||||
"catalogue": "delivery-and-developer-experience-measurement",
|
||||
"serves": [
|
||||
"OR-5"
|
||||
],
|
||||
"items": [
|
||||
"S-3"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 8,
|
||||
"basis": "Measuring deployment frequency, change failure rate, and surveying developer productivity and friction."
|
||||
},
|
||||
{
|
||||
"id": "C-20",
|
||||
"catalogue": "supplier-management",
|
||||
"serves": [
|
||||
"OR-6",
|
||||
"OR-7"
|
||||
],
|
||||
"items": [
|
||||
"S-1",
|
||||
"S-2",
|
||||
"S-3",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 4,
|
||||
"basis": "Overseeing the shared operational delivery structure and ensuring alignment with location restrictions."
|
||||
},
|
||||
{
|
||||
"id": "C-21",
|
||||
"catalogue": "regulatory-evidence",
|
||||
"serves": [
|
||||
"OR-8",
|
||||
"OR-9"
|
||||
],
|
||||
"items": [
|
||||
"S-2",
|
||||
"S-4"
|
||||
],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 8,
|
||||
"basis": "Collecting evidence for 90-day cryptographic key rotations and long-term audit log retention to support DORA alignment."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,113 @@
|
||||
{
|
||||
"customer_case": "bench-landing-zone-shared",
|
||||
"execution_id": "case-01-landing-zone-shared-r2",
|
||||
"session_id": "c7cf78e8-2f3b-4f26-bd2f-850de41fe1d6",
|
||||
"intent_version": 2,
|
||||
"workflow_request": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.",
|
||||
"baseline": null,
|
||||
"overlay_skills": {},
|
||||
"options": {},
|
||||
"sources": {},
|
||||
"scope": {
|
||||
"status": "BASELINE_LOCKED",
|
||||
"readiness": {
|
||||
"supplied": 20,
|
||||
"answered": 0,
|
||||
"assumed": 3,
|
||||
"unknown": 10,
|
||||
"not_applicable": 0
|
||||
}
|
||||
},
|
||||
"status": "completed",
|
||||
"warnings": [],
|
||||
"risks": [],
|
||||
"assessment": null,
|
||||
"phases": {
|
||||
"scoping": "approved",
|
||||
"operational_requirements": "approved",
|
||||
"operating_model_design": "approved",
|
||||
"validation": "approved",
|
||||
"packaging": "approved"
|
||||
},
|
||||
"final_document": "operating-model-guide.md",
|
||||
"changes": null,
|
||||
"deliverables": {
|
||||
"operating_scope": {
|
||||
"document": "deliverables/operating_scope.md",
|
||||
"attachments": [
|
||||
"scope.json",
|
||||
"scope.yaml"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operational_requirements": {
|
||||
"document": "deliverables/operational_requirements.md",
|
||||
"attachments": [
|
||||
"operational-requirements.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"capability_model": {
|
||||
"document": "deliverables/capability_model.md",
|
||||
"attachments": [
|
||||
"capabilities.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"target_operating_model": {
|
||||
"document": "deliverables/target_operating_model.md",
|
||||
"attachments": [
|
||||
"findings.json",
|
||||
"organisation.mmd",
|
||||
"staffing.json",
|
||||
"target-operating-model.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"validation_results": {
|
||||
"document": "deliverables/validation_results.md",
|
||||
"attachments": [
|
||||
"scenarios.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operating_model_guide": {
|
||||
"document": "deliverables/operating_model_guide.md",
|
||||
"attachments": [],
|
||||
"status": "submitted"
|
||||
}
|
||||
},
|
||||
"files": [
|
||||
"capabilities.json",
|
||||
"deliverables/capability_model.md",
|
||||
"deliverables/operating_model_guide.md",
|
||||
"deliverables/operating_scope.md",
|
||||
"deliverables/operational_requirements.md",
|
||||
"deliverables/target_operating_model.md",
|
||||
"deliverables/validation_results.md",
|
||||
"findings.json",
|
||||
"operating-model-guide.md",
|
||||
"operational-requirements.json",
|
||||
"organisation.mmd",
|
||||
"scenarios.json",
|
||||
"scope.json",
|
||||
"scope.yaml",
|
||||
"staffing.json",
|
||||
"target-operating-model.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"staffing": {
|
||||
"people": 11.0,
|
||||
"cost_per_month": 44720,
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
}
|
||||
},
|
||||
"findings": [],
|
||||
"change_request": null,
|
||||
"capability_sources_verified": false
|
||||
}
|
||||
@@ -0,0 +1 @@
|
||||
[]
|
||||
@@ -0,0 +1,234 @@
|
||||
# Operating model guide: Google Cloud landing zone foundation
|
||||
|
||||
## Summary
|
||||
|
||||
This guide defines the target operating model for running the Google Cloud Platform landing zone foundation, comprising the hub network and interconnect, audit log store, deployment pipeline, and cryptographic keys, while application workloads deployed onto the foundation remain out of operational scope. Operations are shared between the customer platform team and an external service provider across the United Kingdom, Poland, and India. The customer platform team retains platform product ownership and final approval authority over all network changes, while the external service provider delivers continuous monitoring and rapid fault response alongside pipeline maintenance and enablement.
|
||||
|
||||
Operational support and platform availability operate continuously round the clock, with the provider handling fault response across all hours, while change enablement, platform engineering, and governance occur during business hours. Readers should look first at the findings and open questions section to review the unconfirmed operational assumptions and unstated items—including the native operations tooling baseline and workload boundaries—as well as the provisional nature of the draft rate card.
|
||||
|
||||
### Key figures
|
||||
|
||||
- Operated: 4 Items, with 3 Conditions to keep true.
|
||||
- Faults responded to: 24x7 hours.
|
||||
- Capabilities: 21.
|
||||
- People: 11.0. Cost a month: 44,720 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
|
||||
- Scenario walk-throughs: 13 of 13 pass.
|
||||
- Business outcomes: 3, 3 shown by a Measure.
|
||||
- Findings for whoever owns the design: 0.
|
||||
|
||||
## Business outcomes
|
||||
|
||||
**BO-1: New payment products reach customers in weeks rather than months.** Target: A change reaches production within a day of approval..
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Deployment frequency | outcome | dora-metrics | A change reaches production within a day of approval. | Delivery and developer experience measurement | Operations Lead |
|
||||
|
||||
**BO-2: Payments are never unavailable for long.** Target: Restored within 4 hours..
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Time to restore service | outcome | dora-metrics | Restored within 4 hours. | Delivery and developer experience measurement | Operations Lead |
|
||||
|
||||
**BO-3: We keep the platform engineers we hire.**
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Satisfaction and well-being | guardrail | space-framework | | Delivery and developer experience measurement | Operations Lead |
|
||||
| Friction and cognitive load | leading | devex-framework | | Delivery and developer experience measurement | Operations Lead |
|
||||
|
||||
## What is operated
|
||||
|
||||
| Item | What it is | Kind | Product | From |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| S-1 | Hub network and interconnect | network | Cloud Interconnect | |
|
||||
| S-2 | Audit log store | storage | Cloud Storage | |
|
||||
| S-3 | Deployment pipeline | pipeline | Cloud Build | |
|
||||
| S-4 | Encryption keys | keys | Cloud KMS | |
|
||||
|
||||
What must be kept true while it is run:
|
||||
|
||||
| Condition | On | What must hold | From |
|
||||
| --- | --- | --- | --- |
|
||||
| K-1 | S-1 | The platform is available at least 99.9% of each month. | |
|
||||
| K-2 | S-2 | Audit logs cannot be deleted for seven years. | |
|
||||
| K-3 | S-4 | Encryption keys are rotated every 90 days. | |
|
||||
|
||||
## Operational requirements
|
||||
|
||||
| Requirement | Kind | What must be achieved | From |
|
||||
| --- | --- | --- | --- |
|
||||
| OR-1 | service_level | A Priority 1 fault on any landing zone component is acknowledged and responded to within 15 minutes, at any hour (24x7). | service_levels.priority_1_response_minutes, operations.support_hours |
|
||||
| OR-2 | service_level | Normal platform operations are restored within 4 hours of a Priority 1 incident occurring. | service_levels.recovery_time_hours |
|
||||
| OR-3 | service_level | The platform foundation maintains an operational availability of at least 99.9% across all hours (24x7) of each calendar month. | K-1, operations.availability_hours |
|
||||
| OR-4 | process | Every change to the hub network requires customer platform team approval prior to deployment. | REQ-01 |
|
||||
| OR-5 | process | A reporting package detailing achieved service levels and operational costs is delivered to the customer on a monthly basis. | REQ-02 |
|
||||
| OR-6 | organisation | Platform foundation operations are delivered under a shared sourcing model between the customer and an external service provider. | sourcing.model |
|
||||
| OR-7 | organisation | Operational services are delivered exclusively from the United Kingdom, Poland, and India. | sourcing.delivery_countries |
|
||||
| OR-8 | compliance | Audit logs stored in the audit log store cannot be deleted and are retained for at least seven years. | K-2 |
|
||||
| OR-9 | compliance | Cryptographic encryption keys are rotated at least once every 90 days. | K-3 |
|
||||
|
||||
## Capabilities
|
||||
|
||||
| Capability | What it is | Serves | Covers | Hours | Effort a month |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| C-1 | Incident management | OR-1, OR-2 | S-1, S-2, S-3, S-4 | 24x7 | 20 h |
|
||||
| C-2 | Monitoring and alerting | OR-1, OR-3 | S-1, S-2, S-3, S-4 | 24x7 | 24 h |
|
||||
| C-3 | Problem management | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 12 h |
|
||||
| C-4 | Service request fulfilment | OR-6 | S-1, S-2, S-3, S-4 | business | 15 h |
|
||||
| C-5 | Change enablement | OR-4 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-6 | Release and deployment | OR-4 | S-1, S-3 | business | 12 h |
|
||||
| C-7 | Configuration management | OR-4 | S-1, S-2, S-3, S-4 | business | 8 h |
|
||||
| C-8 | Backup and recovery | OR-2 | S-2, S-4 | business | 4 h |
|
||||
| C-9 | Service continuity | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 8 h |
|
||||
| C-10 | Capacity and performance management | OR-3 | S-1, S-3 | business | 4 h |
|
||||
| C-11 | Access management | OR-8 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-12 | Vulnerability and patch management | OR-3 | S-1, S-2, S-3, S-4 | business | 16 h |
|
||||
| C-13 | Security monitoring and response | OR-1, OR-8 | S-1, S-2, S-3, S-4 | 24x7 | 24 h |
|
||||
| C-14 | Cost management | OR-5 | S-1, S-2, S-3, S-4 | business | 6 h |
|
||||
| C-15 | Service level management | OR-5 | S-1, S-2, S-3, S-4 | business | 8 h |
|
||||
| C-16 | Platform product management | OR-6 | S-1, S-2, S-3, S-4 | business | 12 h |
|
||||
| C-17 | Self-service and golden paths | OR-4, OR-6 | S-3 | business | 16 h |
|
||||
| C-18 | Enablement | OR-6 | S-3 | business | 10 h |
|
||||
| C-19 | Delivery and developer experience measurement | OR-5 | S-3 | business | 8 h |
|
||||
| C-20 | Supplier management | OR-6, OR-7 | S-1, S-2, S-3, S-4 | business | 4 h |
|
||||
| C-21 | Regulatory evidence and reporting | OR-8, OR-9 | S-2, S-4 | business | 8 h |
|
||||
|
||||
## Who does what
|
||||
|
||||
| Role | Party | Country | Level | Hours |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Platform Lead | Customer platform team (customer) | GB | lead | business |
|
||||
| Platform Engineer | Customer platform team (customer) | GB | engineer | business |
|
||||
| Operations Lead | External service provider (provider) | PL | lead | business |
|
||||
| Operations Engineer | External service provider (provider) | IN | engineer | 24x7 |
|
||||
| Security Operations Engineer | External service provider (provider) | IN | senior | 24x7 |
|
||||
| Senior SRE | External service provider (provider) | IN | senior | business |
|
||||
| Enablement Engineer | External service provider (provider) | IN | senior | business |
|
||||
|
||||
The teams, as Team Topologies names their kinds:
|
||||
|
||||
| Team | Kind | Party | Roles | Purpose |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Platform team | platform | Customer platform team | Platform Lead, Platform Engineer | Customer platform foundation ownership |
|
||||
| Shared operations | platform | External service provider | Operations Lead, Operations Engineer, Security Operations Engineer, Senior SRE | Shared operational delivery of platform foundations |
|
||||
| Enablement team | enabling | External service provider | Enablement Engineer | Facilitating adoption of pipelines |
|
||||
|
||||
How the teams work together:
|
||||
|
||||
| From | To | Mode | Until | Purpose |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Platform team | Shared operations | x-as-a-service | | Customer platform team consumes shared operational services and platforms provided by the external provider. |
|
||||
| Enablement team | Platform team | facilitating | Adoption of foundational pipelines is complete and customer team is self-sufficient. | Provider enablement team assists the customer with adopting foundational deployment pipelines. |
|
||||
|
||||
| Capability | Platform Lead | Platform Engineer | Operations Lead | Operations Engineer | Security Operations Engineer | Senior SRE | Enablement Engineer |
|
||||
| --- | --- | --- | --- | --- | --- | --- | --- |
|
||||
| Incident management (C-1) | | C | A | R | | | |
|
||||
| Monitoring and alerting (C-2) | | C | A | R | | | |
|
||||
| Problem management (C-3) | | C | A | | | R | |
|
||||
| Service request fulfilment (C-4) | | C | A | R | | | |
|
||||
| Change enablement (C-5) | A | R | | | | C | |
|
||||
| Release and deployment (C-6) | | C | A | | | R | |
|
||||
| Configuration management (C-7) | | C | A | | | R | |
|
||||
| Backup and recovery (C-8) | | C | A | | | R | |
|
||||
| Service continuity (C-9) | | C | A | | | R | |
|
||||
| Capacity and performance management (C-10) | | C | A | | | R | |
|
||||
| Access management (C-11) | | C | A | | R | | |
|
||||
| Vulnerability and patch management (C-12) | | C | A | | | R | |
|
||||
| Security monitoring and response (C-13) | | C | A | | R | | |
|
||||
| Cost management (C-14) | C | | A | | | R | |
|
||||
| Service level management (C-15) | C | | A | | | R | |
|
||||
| Platform product management (C-16) | A/R | | | | | | |
|
||||
| Self-service and golden paths (C-17) | | C | A | | | R | |
|
||||
| Enablement (C-18) | | C | A | | | | R |
|
||||
| Delivery and developer experience measurement (C-19) | C | | A | | | R | |
|
||||
| Supplier management (C-20) | A/R | | | | | | |
|
||||
| Regulatory evidence and reporting (C-21) | | C | A | | | R | |
|
||||
|
||||
A accountable, R responsible, C consulted, I informed.
|
||||
|
||||
## Staffing and cost
|
||||
|
||||
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
|
||||
| --- | --- | --- | --- | --- | --- | --- | --- |
|
||||
| Platform Lead | Customer platform team | GB | lead | business | 16.0 h | 0.1 | not priced |
|
||||
| Platform Engineer | Customer platform team | GB | engineer | business | 10.0 h | 0.1 | not priced |
|
||||
| Operations Lead | External service provider | PL | lead | business | 0.0 h | 0.0 | 0 GBP |
|
||||
| Operations Engineer | External service provider | IN | engineer | 24x7 | 59.0 h | 5.0 | 17,034 GBP |
|
||||
| Security Operations Engineer | External service provider | IN | senior | 24x7 | 34.0 h | 5.0 | 24,605 GBP |
|
||||
| Senior SRE | External service provider | IN | senior | business | 110.0 h | 0.7 | 2,824 GBP |
|
||||
| Enablement Engineer | External service provider | IN | senior | business | 10.0 h | 0.1 | 257 GBP |
|
||||
|
||||
11.0 people in all. Cost a month: 44,720 GBP.
|
||||
The monthly budget is 60,000 GBP: this is within it.
|
||||
|
||||
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 | A Priority 1 fault on the platform is acknowledged and responded to within 15 minutes, at any hour. | pass | Capability C-1 covers incident management and operates 24x7. Role R-4 (Operations Engineer) is responsible and operates 24x7. |
|
||||
| OC-2 | Normal platform operations are restored within 4 hours of a Priority 1 incident occurring. | pass | Capability C-1 operates 24x7 and responds to incidents. |
|
||||
| OC-3 | The hub network (S-1) is monitored to verify it maintains at least 99.9% availability. | pass | Capability C-2 covers monitoring and operates 24x7, with Role R-4 responsible. The operating model configures native Google Cloud monitoring tools to fulfill this. |
|
||||
| OC-4 | Changes to the hub network (S-1) are blocked unless approved by the customer platform team. | pass | Capability C-5 covers change enablement. Role R-1 (Platform Lead from the customer team) is accountable and Role R-2 (Platform Engineer from the customer team) is responsible, giving the customer final approval. |
|
||||
| OC-5 | A reporting package detailing achieved service levels and operational costs is delivered to the customer monthly. | pass | Capability C-15 covers service level management. Role R-6 (Senior SRE) is responsible for producing the monthly reporting package. |
|
||||
| OC-6 | Platform foundation operations are governed under a shared sourcing model. | pass | Capability C-20 covers supplier management to govern the shared sourcing model. Role R-1 (Platform Lead) is accountable and responsible. |
|
||||
| OC-7 | Access controls prevent audit logs in the audit log store (S-2) from being deleted for at least seven years. | pass | Capability C-11 covers access management. Role R-5 (Security Operations Engineer) is responsible. |
|
||||
| OC-8 | Evidence is collected to demonstrate cryptographic encryption keys (S-4) are rotated at least once every 90 days. | pass | Capability C-21 covers regulatory evidence collection. Role R-6 (Senior SRE) is responsible. |
|
||||
| OC-9 | The Operations Lead role sits in Poland (PL). | pass | Role R-3 (Operations Lead) is defined with country 'PL' (Poland). |
|
||||
| OC-10 | The Operations Engineer role sits in India (IN). | pass | Role R-4 (Operations Engineer) is defined with country 'IN' (India). |
|
||||
| OC-11 | The Security Operations Engineer role sits in India (IN). | pass | Role R-5 (Security Operations Engineer) is defined with country 'IN' (India). |
|
||||
| OC-12 | The Senior SRE role sits in India (IN). | pass | Role R-6 (Senior SRE) is defined with country 'IN' (India). |
|
||||
| OC-13 | The Enablement Engineer role sits in India (IN). | pass | Role R-7 (Enablement Engineer) is defined with country 'IN' (India). |
|
||||
| OC-14 | The Platform Lead role sits in the United Kingdom (GB). | pass | Role R-1 (Platform Lead) is defined with country 'GB' (United Kingdom). |
|
||||
| OC-15 | The Platform Engineer role sits in the United Kingdom (GB). | pass | Role R-2 (Platform Engineer) is defined with country 'GB' (United Kingdom). |
|
||||
|
||||
Each scenario is generated from the operating model and traced through it by code.
|
||||
|
||||
| Scenario | Result | Path |
|
||||
| --- | --- | --- |
|
||||
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
|
||||
| Hub network and interconnect (S-1) must be changed. | pass | Platform Engineer makes the change under C-5. |
|
||||
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
|
||||
| Audit log store (S-2) must be changed. | pass | Platform Engineer makes the change under C-5. |
|
||||
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
|
||||
| Deployment pipeline (S-3) must be changed. | pass | Platform Engineer makes the change under C-5. |
|
||||
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
|
||||
| Encryption keys (S-4) must be changed. | pass | Platform Engineer makes the change under C-5. |
|
||||
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-3 on C-2 keeps it true. |
|
||||
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-7 on C-11 keeps it true. |
|
||||
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-8 on C-21 keeps it true. |
|
||||
| External service provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
|
||||
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 44,720 GBP, within the budget. |
|
||||
|
||||
## Findings and open questions
|
||||
|
||||
No findings: the solution provides what operating it needs.
|
||||
|
||||
Assumed for the customer, and open to change when they answer:
|
||||
|
||||
- `intent.exclusions`: Application workloads deployed onto the platform foundation. Workloads deployed onto the platform foundation are excluded; operations is confined to the landing zone foundation itself.
|
||||
- `operations.change_process`: Changes go through automated pipelines with peer review; changes affecting the hub network require customer platform team approval prior to release.. Changes follow automated deployment pipelines with peer review, with network changes requiring explicit customer platform team approval per REQ-01.
|
||||
- `service_management.tooling`: Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging), with no separate service management system.. Defaulting to GCP native operations tooling with no separate ITSM system.
|
||||
|
||||
## 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.
|
||||
@@ -0,0 +1,76 @@
|
||||
[
|
||||
{
|
||||
"id": "OR-1",
|
||||
"kind": "service_level",
|
||||
"statement": "A Priority 1 fault on any landing zone component is acknowledged and responded to within 15 minutes, at any hour (24x7).",
|
||||
"source": [
|
||||
"service_levels.priority_1_response_minutes",
|
||||
"operations.support_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-2",
|
||||
"kind": "service_level",
|
||||
"statement": "Normal platform operations are restored within 4 hours of a Priority 1 incident occurring.",
|
||||
"source": [
|
||||
"service_levels.recovery_time_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-3",
|
||||
"kind": "service_level",
|
||||
"statement": "The platform foundation maintains an operational availability of at least 99.9% across all hours (24x7) of each calendar month.",
|
||||
"source": [
|
||||
"K-1",
|
||||
"operations.availability_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-4",
|
||||
"kind": "process",
|
||||
"statement": "Every change to the hub network requires customer platform team approval prior to deployment.",
|
||||
"source": [
|
||||
"REQ-01"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-5",
|
||||
"kind": "process",
|
||||
"statement": "A reporting package detailing achieved service levels and operational costs is delivered to the customer on a monthly basis.",
|
||||
"source": [
|
||||
"REQ-02"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-6",
|
||||
"kind": "organisation",
|
||||
"statement": "Platform foundation operations are delivered under a shared sourcing model between the customer and an external service provider.",
|
||||
"source": [
|
||||
"sourcing.model"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-7",
|
||||
"kind": "organisation",
|
||||
"statement": "Operational services are delivered exclusively from the United Kingdom, Poland, and India.",
|
||||
"source": [
|
||||
"sourcing.delivery_countries"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-8",
|
||||
"kind": "compliance",
|
||||
"statement": "Audit logs stored in the audit log store cannot be deleted and are retained for at least seven years.",
|
||||
"source": [
|
||||
"K-2"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-9",
|
||||
"kind": "compliance",
|
||||
"statement": "Cryptographic encryption keys are rotated at least once every 90 days.",
|
||||
"source": [
|
||||
"K-3"
|
||||
]
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,20 @@
|
||||
flowchart TB
|
||||
subgraph P_1["Customer platform team (customer)"]
|
||||
subgraph T_1["Platform team (platform team)"]
|
||||
R_1["Platform Lead<br/>GB, lead, business"]
|
||||
R_2["Platform Engineer<br/>GB, engineer, business"]
|
||||
end
|
||||
end
|
||||
subgraph P_2["External service provider (provider)"]
|
||||
subgraph T_2["Shared operations (platform team)"]
|
||||
R_3["Operations Lead<br/>PL, lead, business"]
|
||||
R_4["Operations Engineer<br/>IN, engineer, 24x7"]
|
||||
R_5["Security Operations Engineer<br/>IN, senior, 24x7"]
|
||||
R_6["Senior SRE<br/>IN, senior, business"]
|
||||
end
|
||||
subgraph T_3["Enablement team (enabling team)"]
|
||||
R_7["Enablement Engineer<br/>IN, senior, business"]
|
||||
end
|
||||
end
|
||||
T_1 -- "x-as-a-service" --> T_2
|
||||
T_3 -- "facilitating until Adoption of foundational pipelines is complete and customer team is self-sufficient." --> T_1
|
||||
@@ -0,0 +1,93 @@
|
||||
[
|
||||
{
|
||||
"id": "SC-fault-S-1",
|
||||
"scenario": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-1",
|
||||
"scenario": "Hub network and interconnect (S-1) must be changed.",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-2",
|
||||
"scenario": "Audit log store (S-2) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-2",
|
||||
"scenario": "Audit log store (S-2) must be changed.",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-3",
|
||||
"scenario": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-3",
|
||||
"scenario": "Deployment pipeline (S-3) must be changed.",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-4",
|
||||
"scenario": "Encryption keys (S-4) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-4",
|
||||
"scenario": "Encryption keys (S-4) must be changed.",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-1",
|
||||
"scenario": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month.",
|
||||
"about": "K-1",
|
||||
"passes": true,
|
||||
"path": "Check OC-3 on C-2 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-2",
|
||||
"scenario": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years.",
|
||||
"about": "K-2",
|
||||
"passes": true,
|
||||
"path": "Check OC-7 on C-11 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-3",
|
||||
"scenario": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days.",
|
||||
"about": "K-3",
|
||||
"passes": true,
|
||||
"path": "Check OC-8 on C-21 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-party-P-2",
|
||||
"scenario": "External service provider cannot be reached.",
|
||||
"about": "P-2",
|
||||
"passes": true,
|
||||
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"id": "SC-budget",
|
||||
"scenario": "A month's cost of operating is compared with the budget of 60,000 GBP.",
|
||||
"about": "commercial.monthly_run_budget",
|
||||
"passes": true,
|
||||
"path": "The cost is 44,720 GBP, within the budget."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,202 @@
|
||||
{
|
||||
"kind": "platform_foundation",
|
||||
"stated": {
|
||||
"engagement": {
|
||||
"kind": "platform_foundation"
|
||||
},
|
||||
"intent": {
|
||||
"statement": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.\n",
|
||||
"requirements": [
|
||||
{
|
||||
"id": "REQ-01",
|
||||
"statement": "Our platform team approves every change to the network."
|
||||
},
|
||||
{
|
||||
"id": "REQ-02",
|
||||
"statement": "We receive a monthly report of service levels and cost."
|
||||
}
|
||||
],
|
||||
"business_outcomes": [
|
||||
{
|
||||
"id": "BO-1",
|
||||
"outcome": "New payment products reach customers in weeks rather than months.",
|
||||
"target": "A change reaches production within a day of approval."
|
||||
},
|
||||
{
|
||||
"id": "BO-2",
|
||||
"outcome": "Payments are never unavailable for long.",
|
||||
"target": "Restored within 4 hours."
|
||||
},
|
||||
{
|
||||
"id": "BO-3",
|
||||
"outcome": "We keep the platform engineers we hire."
|
||||
}
|
||||
]
|
||||
},
|
||||
"solution": {
|
||||
"cloud_provider": "gcp",
|
||||
"items": [
|
||||
{
|
||||
"id": "S-1",
|
||||
"name": "Hub network and interconnect",
|
||||
"kind": "network",
|
||||
"product": "Cloud Interconnect"
|
||||
},
|
||||
{
|
||||
"id": "S-2",
|
||||
"name": "Audit log store",
|
||||
"kind": "storage",
|
||||
"product": "Cloud Storage"
|
||||
},
|
||||
{
|
||||
"id": "S-3",
|
||||
"name": "Deployment pipeline",
|
||||
"kind": "pipeline",
|
||||
"product": "Cloud Build"
|
||||
},
|
||||
{
|
||||
"id": "S-4",
|
||||
"name": "Encryption keys",
|
||||
"kind": "keys",
|
||||
"product": "Cloud KMS"
|
||||
}
|
||||
],
|
||||
"conditions": [
|
||||
{
|
||||
"id": "K-1",
|
||||
"on": [
|
||||
"S-1"
|
||||
],
|
||||
"condition": "The platform is available at least 99.9% of each month."
|
||||
},
|
||||
{
|
||||
"id": "K-2",
|
||||
"on": [
|
||||
"S-2"
|
||||
],
|
||||
"condition": "Audit logs cannot be deleted for seven years."
|
||||
},
|
||||
{
|
||||
"id": "K-3",
|
||||
"on": [
|
||||
"S-4"
|
||||
],
|
||||
"condition": "Encryption keys are rotated every 90 days."
|
||||
}
|
||||
],
|
||||
"build": {
|
||||
"duration_days": 36
|
||||
}
|
||||
},
|
||||
"operations": {
|
||||
"support_hours": "24x7",
|
||||
"availability_hours": "24x7"
|
||||
},
|
||||
"sourcing": {
|
||||
"model": "shared",
|
||||
"delivery_countries": [
|
||||
"GB",
|
||||
"PL",
|
||||
"IN"
|
||||
]
|
||||
},
|
||||
"organisation": {
|
||||
"existing_teams": [
|
||||
{
|
||||
"name": "Platform team",
|
||||
"party": "customer",
|
||||
"hours": "business",
|
||||
"country": "GB"
|
||||
}
|
||||
]
|
||||
},
|
||||
"service_levels": {
|
||||
"priority_1_response_minutes": 15,
|
||||
"recovery_time_hours": 4
|
||||
},
|
||||
"compliance": {
|
||||
"frameworks": [
|
||||
"DORA"
|
||||
]
|
||||
},
|
||||
"commercial": {
|
||||
"currency": "GBP",
|
||||
"monthly_run_budget": 60000
|
||||
}
|
||||
},
|
||||
"binding": [
|
||||
"operations.support_hours",
|
||||
"sourcing.model",
|
||||
"sourcing.delivery_countries",
|
||||
"service_levels.priority_1_response_minutes",
|
||||
"service_levels.recovery_time_hours"
|
||||
],
|
||||
"assumed": [
|
||||
{
|
||||
"field": "intent.exclusions",
|
||||
"value": [
|
||||
"Application workloads deployed onto the platform foundation"
|
||||
],
|
||||
"why": "Workloads deployed onto the platform foundation are excluded; operations is confined to the landing zone foundation itself."
|
||||
},
|
||||
{
|
||||
"field": "operations.change_process",
|
||||
"value": "Changes go through automated pipelines with peer review; changes affecting the hub network require customer platform team approval prior to release.",
|
||||
"why": "Changes follow automated deployment pipelines with peer review, with network changes requiring explicit customer platform team approval per REQ-01."
|
||||
},
|
||||
{
|
||||
"field": "service_management.tooling",
|
||||
"value": "Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging), with no separate service management system.",
|
||||
"why": "Defaulting to GCP native operations tooling with no separate ITSM system."
|
||||
}
|
||||
],
|
||||
"to_decide": [],
|
||||
"to_ask": [
|
||||
{
|
||||
"field": "metadata.client_name",
|
||||
"prompt": "What is metadata.client_name?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.author",
|
||||
"prompt": "What is metadata.author?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.revision",
|
||||
"prompt": "What is metadata.revision?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.source",
|
||||
"prompt": "What is metadata.source?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "solution.build.customer_owned",
|
||||
"prompt": "Which parts of the build does the customer or their supplier own?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "solution.inherited_risks",
|
||||
"prompt": "What is already known to be unverified or at risk in the solution?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "operations.monitoring",
|
||||
"prompt": "Which monitoring and alerting is already in place or required?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "organisation.headcount_limit",
|
||||
"prompt": "Is there a limit on the number of people operating this?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "transition.go_live_date",
|
||||
"prompt": "When must the solution be in operation?",
|
||||
"severity": "LOW"
|
||||
}
|
||||
],
|
||||
"not_applicable": []
|
||||
}
|
||||
@@ -0,0 +1,199 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: bench-landing-zone-shared
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: ask
|
||||
status: BASELINE_LOCKED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We want our landing zone run as a shared service from go-live. A provider
|
||||
should
|
||||
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
|
||||
over changes to the network.
|
||||
|
||||
'
|
||||
requirements:
|
||||
- id: REQ-01
|
||||
statement: Our platform team approves every change to the network.
|
||||
- id: REQ-02
|
||||
statement: We receive a monthly report of service levels and cost.
|
||||
business_outcomes:
|
||||
- id: BO-1
|
||||
outcome: New payment products reach customers in weeks rather than months.
|
||||
target: A change reaches production within a day of approval.
|
||||
- id: BO-2
|
||||
outcome: Payments are never unavailable for long.
|
||||
target: Restored within 4 hours.
|
||||
- id: BO-3
|
||||
outcome: We keep the platform engineers we hire.
|
||||
exclusions:
|
||||
- Application workloads deployed onto the platform foundation
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Hub network and interconnect
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
- id: S-2
|
||||
name: Audit log store
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
- id: S-3
|
||||
name: Deployment pipeline
|
||||
kind: pipeline
|
||||
product: Cloud Build
|
||||
- id: S-4
|
||||
name: Encryption keys
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
condition: The platform is available at least 99.9% of each month.
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-2
|
||||
condition: Audit logs cannot be deleted for seven years.
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-4
|
||||
condition: Encryption keys are rotated every 90 days.
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned: ask
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Changes go through automated pipelines with peer review; changes
|
||||
affecting the hub network require customer platform team approval prior to release.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: shared
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams:
|
||||
- name: Platform team
|
||||
party: customer
|
||||
hours: business
|
||||
country: GB
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging),
|
||||
with no separate service management system.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 15
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: 60000
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.exclusions
|
||||
statement: Assumed intent.exclusions is ['Application workloads deployed onto the
|
||||
platform foundation']. Workloads deployed onto the platform foundation are excluded;
|
||||
operations is confined to the landing zone foundation itself.
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-02
|
||||
field: operations.change_process
|
||||
statement: Assumed operations.change_process is Changes go through automated pipelines
|
||||
with peer review; changes affecting the hub network require customer platform
|
||||
team approval prior to release.. Changes follow automated deployment pipelines
|
||||
with peer review, with network changes requiring explicit customer platform team
|
||||
approval per REQ-01.
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-03
|
||||
field: service_management.tooling
|
||||
statement: Assumed service_management.tooling is Google Cloud native operations
|
||||
tooling (Cloud Monitoring and Cloud Logging), with no separate service management
|
||||
system.. Defaulting to GCP native operations tooling with no separate ITSM system.
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: metadata.source
|
||||
prompt: What is metadata.source?
|
||||
severity: LOW
|
||||
- field: solution.build.customer_owned
|
||||
prompt: Which parts of the build does the customer or their supplier own?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: supplied
|
||||
commercial.monthly_run_budget: supplied
|
||||
compliance.frameworks: supplied
|
||||
engagement.kind: supplied
|
||||
intent.business_outcomes: supplied
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: supplied
|
||||
intent.statement: supplied
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: supplied
|
||||
metadata.revision: unknown
|
||||
metadata.source: unknown
|
||||
operations.availability_hours: supplied
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: supplied
|
||||
organisation.existing_teams: supplied
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: supplied
|
||||
service_levels.recovery_time_hours: supplied
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: unknown
|
||||
solution.build.duration_days: supplied
|
||||
solution.cloud_provider: supplied
|
||||
solution.conditions: supplied
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: supplied
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 20
|
||||
answered: 0
|
||||
assumed: 3
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
@@ -0,0 +1,128 @@
|
||||
{
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
},
|
||||
"conversion": {
|
||||
"from": "USD",
|
||||
"rate": 0.79,
|
||||
"as_of": "2026-10-13"
|
||||
},
|
||||
"roles": [
|
||||
{
|
||||
"role": "R-1",
|
||||
"name": "Platform Lead",
|
||||
"party": "P-1",
|
||||
"party_name": "Customer platform team",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 16.0,
|
||||
"people": 0.1,
|
||||
"cost_per_month": null
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"name": "Platform Engineer",
|
||||
"party": "P-1",
|
||||
"party_name": "Customer platform team",
|
||||
"country": "GB",
|
||||
"level": "engineer",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10.0,
|
||||
"people": 0.1,
|
||||
"cost_per_month": null
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"name": "Operations Lead",
|
||||
"party": "P-2",
|
||||
"party_name": "External service provider",
|
||||
"country": "PL",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 0.0,
|
||||
"people": 0.0,
|
||||
"cost_per_month": 0
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"name": "Operations Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "External service provider",
|
||||
"country": "IN",
|
||||
"level": "engineer",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 59.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 17034
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"name": "Security Operations Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "External service provider",
|
||||
"country": "IN",
|
||||
"level": "senior",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 34.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 24605
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"name": "Senior SRE",
|
||||
"party": "P-2",
|
||||
"party_name": "External service provider",
|
||||
"country": "IN",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 110.0,
|
||||
"people": 0.7,
|
||||
"cost_per_month": 2824
|
||||
},
|
||||
{
|
||||
"role": "R-7",
|
||||
"name": "Enablement Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "External service provider",
|
||||
"country": "IN",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10.0,
|
||||
"people": 0.1,
|
||||
"cost_per_month": 257
|
||||
}
|
||||
],
|
||||
"people": 11.0,
|
||||
"cost_per_month": 44720,
|
||||
"by_party": {
|
||||
"P-2": 44720
|
||||
},
|
||||
"by_country": {
|
||||
"PL": 0,
|
||||
"IN": 44720
|
||||
},
|
||||
"by_capability": {
|
||||
"C-1": 5774,
|
||||
"C-2": 6929,
|
||||
"C-4": 4331,
|
||||
"C-11": 7237,
|
||||
"C-13": 17368,
|
||||
"C-3": 308,
|
||||
"C-6": 308,
|
||||
"C-7": 205,
|
||||
"C-8": 103,
|
||||
"C-9": 205,
|
||||
"C-10": 103,
|
||||
"C-12": 411,
|
||||
"C-14": 154,
|
||||
"C-15": 205,
|
||||
"C-17": 411,
|
||||
"C-19": 205,
|
||||
"C-21": 205,
|
||||
"C-18": 257
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,615 @@
|
||||
{
|
||||
"parties": [
|
||||
{
|
||||
"kind": "customer",
|
||||
"name": "Customer platform team",
|
||||
"id": "P-1"
|
||||
},
|
||||
{
|
||||
"id": "P-2",
|
||||
"kind": "provider",
|
||||
"name": "External service provider"
|
||||
}
|
||||
],
|
||||
"teams": [
|
||||
{
|
||||
"purpose": "Customer platform foundation ownership",
|
||||
"name": "Platform team",
|
||||
"id": "T-1",
|
||||
"party": "P-1",
|
||||
"type": "platform"
|
||||
},
|
||||
{
|
||||
"name": "Shared operations",
|
||||
"id": "T-2",
|
||||
"type": "platform",
|
||||
"purpose": "Shared operational delivery of platform foundations",
|
||||
"party": "P-2"
|
||||
},
|
||||
{
|
||||
"type": "enabling",
|
||||
"party": "P-2",
|
||||
"purpose": "Facilitating adoption of pipelines",
|
||||
"id": "T-3",
|
||||
"name": "Enablement team"
|
||||
}
|
||||
],
|
||||
"roles": [
|
||||
{
|
||||
"hours": "business",
|
||||
"party": "P-1",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"team": "T-1",
|
||||
"id": "R-1",
|
||||
"name": "Platform Lead"
|
||||
},
|
||||
{
|
||||
"country": "GB",
|
||||
"id": "R-2",
|
||||
"hours": "business",
|
||||
"team": "T-1",
|
||||
"name": "Platform Engineer",
|
||||
"party": "P-1",
|
||||
"level": "engineer"
|
||||
},
|
||||
{
|
||||
"hours": "business",
|
||||
"id": "R-3",
|
||||
"party": "P-2",
|
||||
"level": "lead",
|
||||
"country": "PL",
|
||||
"team": "T-2",
|
||||
"name": "Operations Lead"
|
||||
},
|
||||
{
|
||||
"hours": "24x7",
|
||||
"name": "Operations Engineer",
|
||||
"level": "engineer",
|
||||
"id": "R-4",
|
||||
"country": "IN",
|
||||
"team": "T-2",
|
||||
"party": "P-2"
|
||||
},
|
||||
{
|
||||
"country": "IN",
|
||||
"hours": "24x7",
|
||||
"name": "Security Operations Engineer",
|
||||
"team": "T-2",
|
||||
"id": "R-5",
|
||||
"level": "senior",
|
||||
"party": "P-2"
|
||||
},
|
||||
{
|
||||
"level": "senior",
|
||||
"name": "Senior SRE",
|
||||
"id": "R-6",
|
||||
"party": "P-2",
|
||||
"team": "T-2",
|
||||
"country": "IN",
|
||||
"hours": "business"
|
||||
},
|
||||
{
|
||||
"id": "R-7",
|
||||
"name": "Enablement Engineer",
|
||||
"hours": "business",
|
||||
"level": "senior",
|
||||
"team": "T-3",
|
||||
"country": "IN",
|
||||
"party": "P-2"
|
||||
}
|
||||
],
|
||||
"interactions": [
|
||||
{
|
||||
"mode": "x_as_a_service",
|
||||
"from": "T-1",
|
||||
"to": "T-2",
|
||||
"id": "I-1",
|
||||
"purpose": "Customer platform team consumes shared operational services and platforms provided by the external provider."
|
||||
},
|
||||
{
|
||||
"to": "T-1",
|
||||
"from": "T-3",
|
||||
"mode": "facilitating",
|
||||
"purpose": "Provider enablement team assists the customer with adopting foundational deployment pipelines.",
|
||||
"id": "I-2",
|
||||
"until": "Adoption of foundational pipelines is complete and customer team is self-sufficient."
|
||||
}
|
||||
],
|
||||
"measures": [
|
||||
{
|
||||
"layer": "outcome",
|
||||
"name": "Deployment frequency",
|
||||
"framework": "dora-metrics",
|
||||
"outcome": "BO-1",
|
||||
"measured_by": "C-19",
|
||||
"id": "M-1",
|
||||
"target": "A change reaches production within a day of approval."
|
||||
},
|
||||
{
|
||||
"target": "Restored within 4 hours.",
|
||||
"outcome": "BO-2",
|
||||
"layer": "outcome",
|
||||
"measured_by": "C-19",
|
||||
"framework": "dora-metrics",
|
||||
"name": "Time to restore service",
|
||||
"id": "M-2"
|
||||
},
|
||||
{
|
||||
"outcome": "BO-3",
|
||||
"layer": "guardrail",
|
||||
"measured_by": "C-19",
|
||||
"name": "Satisfaction and well-being",
|
||||
"id": "M-3",
|
||||
"framework": "space-framework"
|
||||
},
|
||||
{
|
||||
"measured_by": "C-19",
|
||||
"layer": "leading",
|
||||
"id": "M-4",
|
||||
"name": "Friction and cognitive load",
|
||||
"framework": "devex-framework",
|
||||
"outcome": "BO-3"
|
||||
}
|
||||
],
|
||||
"responsibilities": [
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-1",
|
||||
"id": "RS-1A",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-4",
|
||||
"capability": "C-1",
|
||||
"id": "RS-1R"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"kind": "consulted",
|
||||
"capability": "C-1",
|
||||
"id": "RS-1C"
|
||||
},
|
||||
{
|
||||
"capability": "C-2",
|
||||
"kind": "accountable",
|
||||
"id": "RS-2A",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"id": "RS-2R",
|
||||
"capability": "C-2",
|
||||
"role": "R-4",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"capability": "C-2",
|
||||
"id": "RS-2C",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"id": "RS-3A",
|
||||
"role": "R-3",
|
||||
"capability": "C-3",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-3",
|
||||
"kind": "responsible",
|
||||
"id": "RS-3R",
|
||||
"role": "R-6"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"id": "RS-3C",
|
||||
"capability": "C-3",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"capability": "C-4",
|
||||
"id": "RS-4A",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-4",
|
||||
"id": "RS-4R",
|
||||
"role": "R-4",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"capability": "C-4",
|
||||
"role": "R-2",
|
||||
"id": "RS-4C",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-5",
|
||||
"role": "R-1",
|
||||
"id": "RS-5A"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"capability": "C-5",
|
||||
"id": "RS-5R",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"capability": "C-5",
|
||||
"kind": "consulted",
|
||||
"id": "RS-5C"
|
||||
},
|
||||
{
|
||||
"id": "RS-6A",
|
||||
"capability": "C-6",
|
||||
"kind": "accountable",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"capability": "C-6",
|
||||
"id": "RS-6R",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"capability": "C-6",
|
||||
"kind": "consulted",
|
||||
"id": "RS-6C",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"capability": "C-7",
|
||||
"role": "R-3",
|
||||
"id": "RS-7A",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"id": "RS-7R",
|
||||
"kind": "responsible",
|
||||
"capability": "C-7",
|
||||
"role": "R-6"
|
||||
},
|
||||
{
|
||||
"capability": "C-7",
|
||||
"id": "RS-7C",
|
||||
"kind": "consulted",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"capability": "C-8",
|
||||
"id": "RS-8A",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"id": "RS-8R",
|
||||
"kind": "responsible",
|
||||
"capability": "C-8"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"capability": "C-8",
|
||||
"id": "RS-8C",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-9",
|
||||
"id": "RS-9A",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"capability": "C-9",
|
||||
"role": "R-6",
|
||||
"id": "RS-9R",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"id": "RS-9C",
|
||||
"role": "R-2",
|
||||
"capability": "C-9"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"capability": "C-10",
|
||||
"id": "RS-10A",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"id": "RS-10R",
|
||||
"role": "R-6",
|
||||
"capability": "C-10",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"id": "RS-10C",
|
||||
"capability": "C-10",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"id": "RS-11A",
|
||||
"kind": "accountable",
|
||||
"role": "R-3",
|
||||
"capability": "C-11"
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"kind": "responsible",
|
||||
"capability": "C-11",
|
||||
"id": "RS-11R"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-2",
|
||||
"id": "RS-11C",
|
||||
"capability": "C-11"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"capability": "C-12",
|
||||
"id": "RS-12A",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"id": "RS-12R",
|
||||
"kind": "responsible",
|
||||
"capability": "C-12"
|
||||
},
|
||||
{
|
||||
"capability": "C-12",
|
||||
"id": "RS-12C",
|
||||
"kind": "consulted",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"id": "RS-13A",
|
||||
"capability": "C-13",
|
||||
"kind": "accountable",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"id": "RS-13R",
|
||||
"role": "R-5",
|
||||
"kind": "responsible",
|
||||
"capability": "C-13"
|
||||
},
|
||||
{
|
||||
"id": "RS-13C",
|
||||
"role": "R-2",
|
||||
"capability": "C-13",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"id": "RS-14A",
|
||||
"capability": "C-14",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"capability": "C-14",
|
||||
"id": "RS-14R",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"capability": "C-14",
|
||||
"role": "R-1",
|
||||
"id": "RS-14C"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"role": "R-3",
|
||||
"capability": "C-15",
|
||||
"id": "RS-15A"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"id": "RS-15R",
|
||||
"kind": "responsible",
|
||||
"capability": "C-15"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-1",
|
||||
"id": "RS-15C",
|
||||
"capability": "C-15"
|
||||
},
|
||||
{
|
||||
"id": "RS-16A",
|
||||
"capability": "C-16",
|
||||
"role": "R-1",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"id": "RS-16R",
|
||||
"kind": "responsible",
|
||||
"capability": "C-16",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"id": "RS-17A",
|
||||
"capability": "C-17",
|
||||
"kind": "accountable",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"id": "RS-17R",
|
||||
"capability": "C-17",
|
||||
"kind": "responsible",
|
||||
"role": "R-6"
|
||||
},
|
||||
{
|
||||
"capability": "C-17",
|
||||
"role": "R-2",
|
||||
"id": "RS-17C",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"capability": "C-18",
|
||||
"kind": "accountable",
|
||||
"id": "RS-18A",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"role": "R-7",
|
||||
"capability": "C-18",
|
||||
"id": "RS-18R",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"capability": "C-18",
|
||||
"id": "RS-18C",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"capability": "C-19",
|
||||
"kind": "accountable",
|
||||
"id": "RS-19A"
|
||||
},
|
||||
{
|
||||
"id": "RS-19R",
|
||||
"kind": "responsible",
|
||||
"capability": "C-19",
|
||||
"role": "R-6"
|
||||
},
|
||||
{
|
||||
"id": "RS-19C",
|
||||
"kind": "consulted",
|
||||
"capability": "C-19",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"id": "RS-20A",
|
||||
"role": "R-1",
|
||||
"capability": "C-20",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-20",
|
||||
"id": "RS-20R",
|
||||
"role": "R-1",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"id": "RS-21A",
|
||||
"capability": "C-21",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"id": "RS-21R",
|
||||
"kind": "responsible",
|
||||
"capability": "C-21",
|
||||
"role": "R-6"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"capability": "C-21",
|
||||
"role": "R-2",
|
||||
"id": "RS-21C"
|
||||
}
|
||||
],
|
||||
"checks": [
|
||||
{
|
||||
"on": "C-1",
|
||||
"id": "OC-1",
|
||||
"condition": "A Priority 1 fault on the platform is acknowledged and responded to within 15 minutes, at any hour.",
|
||||
"source": "OR-1"
|
||||
},
|
||||
{
|
||||
"on": "C-1",
|
||||
"id": "OC-2",
|
||||
"source": "OR-2",
|
||||
"condition": "Normal platform operations are restored within 4 hours of a Priority 1 incident occurring."
|
||||
},
|
||||
{
|
||||
"id": "OC-3",
|
||||
"on": "C-2",
|
||||
"condition": "The hub network (S-1) is monitored to verify it maintains at least 99.9% availability.",
|
||||
"source": "K-1"
|
||||
},
|
||||
{
|
||||
"id": "OC-4",
|
||||
"source": "OR-4",
|
||||
"condition": "Changes to the hub network (S-1) are blocked unless approved by the customer platform team.",
|
||||
"on": "C-5"
|
||||
},
|
||||
{
|
||||
"source": "OR-5",
|
||||
"id": "OC-5",
|
||||
"on": "C-15",
|
||||
"condition": "A reporting package detailing achieved service levels and operational costs is delivered to the customer monthly."
|
||||
},
|
||||
{
|
||||
"id": "OC-6",
|
||||
"condition": "Platform foundation operations are governed under a shared sourcing model.",
|
||||
"source": "OR-6",
|
||||
"on": "C-20"
|
||||
},
|
||||
{
|
||||
"source": "K-2",
|
||||
"condition": "Access controls prevent audit logs in the audit log store (S-2) from being deleted for at least seven years.",
|
||||
"id": "OC-7",
|
||||
"on": "C-11"
|
||||
},
|
||||
{
|
||||
"condition": "Evidence is collected to demonstrate cryptographic encryption keys (S-4) are rotated at least once every 90 days.",
|
||||
"id": "OC-8",
|
||||
"source": "K-3",
|
||||
"on": "C-21"
|
||||
},
|
||||
{
|
||||
"condition": "The Operations Lead role sits in Poland (PL).",
|
||||
"source": "OR-7",
|
||||
"id": "OC-9",
|
||||
"on": "R-3"
|
||||
},
|
||||
{
|
||||
"on": "R-4",
|
||||
"id": "OC-10",
|
||||
"source": "OR-7",
|
||||
"condition": "The Operations Engineer role sits in India (IN)."
|
||||
},
|
||||
{
|
||||
"condition": "The Security Operations Engineer role sits in India (IN).",
|
||||
"source": "OR-7",
|
||||
"on": "R-5",
|
||||
"id": "OC-11"
|
||||
},
|
||||
{
|
||||
"condition": "The Senior SRE role sits in India (IN).",
|
||||
"on": "R-6",
|
||||
"id": "OC-12",
|
||||
"source": "OR-7"
|
||||
},
|
||||
{
|
||||
"condition": "The Enablement Engineer role sits in India (IN).",
|
||||
"source": "OR-7",
|
||||
"id": "OC-13",
|
||||
"on": "R-7"
|
||||
},
|
||||
{
|
||||
"condition": "The Platform Lead role sits in the United Kingdom (GB).",
|
||||
"id": "OC-14",
|
||||
"on": "R-1",
|
||||
"source": "OR-7"
|
||||
},
|
||||
{
|
||||
"on": "R-2",
|
||||
"condition": "The Platform Engineer role sits in the United Kingdom (GB).",
|
||||
"id": "OC-15",
|
||||
"source": "OR-7"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,149 @@
|
||||
{
|
||||
"dry_run": {
|
||||
"verdict": "pass",
|
||||
"evidence": "13 of 13 scenario walk-throughs pass."
|
||||
},
|
||||
"checks": [
|
||||
{
|
||||
"check": "OC-1",
|
||||
"evidence": "Capability C-1 covers incident management and operates 24x7. Role R-4 (Operations Engineer) is responsible and operates 24x7.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-1 operates 24x7 and responds to incidents.",
|
||||
"check": "OC-2"
|
||||
},
|
||||
{
|
||||
"check": "OC-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-2 covers monitoring and operates 24x7, with Role R-4 responsible. The operating model configures native Google Cloud monitoring tools to fulfill this."
|
||||
},
|
||||
{
|
||||
"check": "OC-4",
|
||||
"evidence": "Capability C-5 covers change enablement. Role R-1 (Platform Lead from the customer team) is accountable and Role R-2 (Platform Engineer from the customer team) is responsible, giving the customer final approval.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-15 covers service level management. Role R-6 (Senior SRE) is responsible for producing the monthly reporting package.",
|
||||
"check": "OC-5"
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-20 covers supplier management to govern the shared sourcing model. Role R-1 (Platform Lead) is accountable and responsible.",
|
||||
"verdict": "pass",
|
||||
"check": "OC-6"
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-11 covers access management. Role R-5 (Security Operations Engineer) is responsible.",
|
||||
"verdict": "pass",
|
||||
"check": "OC-7"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-8",
|
||||
"evidence": "Capability C-21 covers regulatory evidence collection. Role R-6 (Senior SRE) is responsible."
|
||||
},
|
||||
{
|
||||
"check": "OC-9",
|
||||
"verdict": "pass",
|
||||
"evidence": "Role R-3 (Operations Lead) is defined with country 'PL' (Poland)."
|
||||
},
|
||||
{
|
||||
"evidence": "Role R-4 (Operations Engineer) is defined with country 'IN' (India).",
|
||||
"verdict": "pass",
|
||||
"check": "OC-10"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Role R-5 (Security Operations Engineer) is defined with country 'IN' (India).",
|
||||
"check": "OC-11"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Role R-6 (Senior SRE) is defined with country 'IN' (India).",
|
||||
"check": "OC-12"
|
||||
},
|
||||
{
|
||||
"check": "OC-13",
|
||||
"verdict": "pass",
|
||||
"evidence": "Role R-7 (Enablement Engineer) is defined with country 'IN' (India)."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-14",
|
||||
"evidence": "Role R-1 (Platform Lead) is defined with country 'GB' (United Kingdom)."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Role R-2 (Platform Engineer) is defined with country 'GB' (United Kingdom).",
|
||||
"check": "OC-15"
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Hub network and interconnect (S-1) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Audit log store (S-2) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Audit log store (S-2) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Deployment pipeline (S-3) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Encryption keys (S-4) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Encryption keys (S-4) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. Check OC-3 on C-2 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. Check OC-7 on C-11 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. Check OC-8 on C-21 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-party-P-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "External service provider cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"check": "SC-budget",
|
||||
"verdict": "pass",
|
||||
"evidence": "A month's cost of operating is compared with the budget of 60,000 GBP. The cost is 44,720 GBP, within the budget."
|
||||
}
|
||||
],
|
||||
"proposed_additions": []
|
||||
}
|
||||
@@ -0,0 +1,191 @@
|
||||
[
|
||||
{
|
||||
"id": "C-1",
|
||||
"catalogue": "incident-management",
|
||||
"serves": ["OR-1", "OR-2"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 30,
|
||||
"basis": "Triaging alerts and handling an estimated 2-4 incidents per month across the 4 platform items."
|
||||
},
|
||||
{
|
||||
"id": "C-2",
|
||||
"catalogue": "monitoring-and-alerting",
|
||||
"serves": ["OR-1", "OR-3"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Maintaining monitoring configurations and tuning alerts for the 4 Items continuously."
|
||||
},
|
||||
{
|
||||
"id": "C-3",
|
||||
"catalogue": "problem-management",
|
||||
"serves": ["OR-2"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Conducting root cause analysis and post-incident reviews for major faults."
|
||||
},
|
||||
{
|
||||
"id": "C-4",
|
||||
"catalogue": "service-request-fulfilment",
|
||||
"serves": ["OR-6"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Fulfilling routine non-fault requests such as access provisioning or adjusting limits."
|
||||
},
|
||||
{
|
||||
"id": "C-5",
|
||||
"catalogue": "change-enablement",
|
||||
"serves": ["OR-4", "OR-10"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Reviewing change requests and coordinating network change approvals with the customer."
|
||||
},
|
||||
{
|
||||
"id": "C-6",
|
||||
"catalogue": "release-and-deployment",
|
||||
"serves": ["OR-10"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Overseeing deployment pipelines to ensure approved changes reach production within a day."
|
||||
},
|
||||
{
|
||||
"id": "C-7",
|
||||
"catalogue": "configuration-management",
|
||||
"serves": ["OR-8", "OR-9"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Auditing configuration drift, managing key rotation schedules, and maintaining audit log retention settings."
|
||||
},
|
||||
{
|
||||
"id": "C-8",
|
||||
"catalogue": "backup-and-recovery",
|
||||
"serves": ["OR-2", "OR-8"],
|
||||
"items": ["S-2", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Maintaining backups of audit logs and encryption keys, and testing restore procedures."
|
||||
},
|
||||
{
|
||||
"id": "C-9",
|
||||
"catalogue": "service-continuity",
|
||||
"serves": ["OR-2", "OR-3"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Planning and periodic rehearsal of disaster recovery procedures for the platform."
|
||||
},
|
||||
{
|
||||
"id": "C-10",
|
||||
"catalogue": "capacity-and-performance",
|
||||
"serves": ["OR-3"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Reviewing capacity trends for interconnect and storage to assure 99.9% availability."
|
||||
},
|
||||
{
|
||||
"id": "C-11",
|
||||
"catalogue": "access-management",
|
||||
"serves": ["OR-6", "OR-7"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Managing identity and access boundaries between provider and customer in the specified delivery countries."
|
||||
},
|
||||
{
|
||||
"id": "C-12",
|
||||
"catalogue": "vulnerability-and-patch-management",
|
||||
"serves": ["OR-9"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Regular patching and vulnerability remediation of the pipeline and infrastructure components."
|
||||
},
|
||||
{
|
||||
"id": "C-13",
|
||||
"catalogue": "security-monitoring-and-response",
|
||||
"serves": ["OR-1", "OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 40,
|
||||
"basis": "Continuous monitoring of security events and continuous analysis of audit logs."
|
||||
},
|
||||
{
|
||||
"id": "C-14",
|
||||
"catalogue": "cost-management",
|
||||
"serves": ["OR-5"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Tracking run rate against budget and reporting costs monthly."
|
||||
},
|
||||
{
|
||||
"id": "C-15",
|
||||
"catalogue": "service-level-management",
|
||||
"serves": ["OR-3", "OR-5"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Gathering metrics on 99.9% availability and compiling the monthly operational report."
|
||||
},
|
||||
{
|
||||
"id": "C-16",
|
||||
"catalogue": "platform-product-management",
|
||||
"serves": ["OR-6"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Managing the platform's roadmap and backlog based on feedback from the customer platform team."
|
||||
},
|
||||
{
|
||||
"id": "C-17",
|
||||
"catalogue": "self-service-and-golden-paths",
|
||||
"serves": ["OR-10"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Building automated self-service paths and maintaining fast-flow deployment pipelines."
|
||||
},
|
||||
{
|
||||
"id": "C-18",
|
||||
"catalogue": "enablement",
|
||||
"serves": ["OR-10"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Assisting customer engineers with adopting golden paths and best practices."
|
||||
},
|
||||
{
|
||||
"id": "C-19",
|
||||
"catalogue": "delivery-and-developer-experience-measurement",
|
||||
"serves": ["OR-10"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Measuring DORA delivery metrics, developer productivity guardrails, and leading flow signals."
|
||||
},
|
||||
{
|
||||
"id": "C-20",
|
||||
"catalogue": "supplier-management",
|
||||
"serves": ["OR-6", "OR-7"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Coordinating responsibilities and hand-offs across shared delivery borders and governance locations."
|
||||
},
|
||||
{
|
||||
"id": "C-21",
|
||||
"catalogue": "regulatory-evidence",
|
||||
"serves": ["OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Gathering and retaining evidence to meet compliance requirements such as EU DORA."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,113 @@
|
||||
{
|
||||
"customer_case": "bench-landing-zone-shared",
|
||||
"execution_id": "case-01-landing-zone-shared-r3",
|
||||
"session_id": "d0d953a6-5254-4646-8d70-7fd6139f1afc",
|
||||
"intent_version": 3,
|
||||
"workflow_request": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.",
|
||||
"baseline": null,
|
||||
"overlay_skills": {},
|
||||
"options": {},
|
||||
"sources": {},
|
||||
"scope": {
|
||||
"status": "BASELINE_LOCKED",
|
||||
"readiness": {
|
||||
"supplied": 20,
|
||||
"answered": 0,
|
||||
"assumed": 3,
|
||||
"unknown": 10,
|
||||
"not_applicable": 0
|
||||
}
|
||||
},
|
||||
"status": "completed",
|
||||
"warnings": [],
|
||||
"risks": [],
|
||||
"assessment": null,
|
||||
"phases": {
|
||||
"scoping": "approved",
|
||||
"operational_requirements": "approved",
|
||||
"operating_model_design": "approved",
|
||||
"validation": "approved",
|
||||
"packaging": "approved"
|
||||
},
|
||||
"final_document": "operating-model-guide.md",
|
||||
"changes": null,
|
||||
"deliverables": {
|
||||
"operating_scope": {
|
||||
"document": "deliverables/operating_scope.md",
|
||||
"attachments": [
|
||||
"scope.json",
|
||||
"scope.yaml"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operational_requirements": {
|
||||
"document": "deliverables/operational_requirements.md",
|
||||
"attachments": [
|
||||
"operational-requirements.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"capability_model": {
|
||||
"document": "deliverables/capability_model.md",
|
||||
"attachments": [
|
||||
"capabilities.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"target_operating_model": {
|
||||
"document": "deliverables/target_operating_model.md",
|
||||
"attachments": [
|
||||
"findings.json",
|
||||
"organisation.mmd",
|
||||
"staffing.json",
|
||||
"target-operating-model.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"validation_results": {
|
||||
"document": "deliverables/validation_results.md",
|
||||
"attachments": [
|
||||
"scenarios.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operating_model_guide": {
|
||||
"document": "deliverables/operating_model_guide.md",
|
||||
"attachments": [],
|
||||
"status": "submitted"
|
||||
}
|
||||
},
|
||||
"files": [
|
||||
"capabilities.json",
|
||||
"deliverables/capability_model.md",
|
||||
"deliverables/operating_model_guide.md",
|
||||
"deliverables/operating_scope.md",
|
||||
"deliverables/operational_requirements.md",
|
||||
"deliverables/target_operating_model.md",
|
||||
"deliverables/validation_results.md",
|
||||
"findings.json",
|
||||
"operating-model-guide.md",
|
||||
"operational-requirements.json",
|
||||
"organisation.mmd",
|
||||
"scenarios.json",
|
||||
"scope.json",
|
||||
"scope.yaml",
|
||||
"staffing.json",
|
||||
"target-operating-model.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"staffing": {
|
||||
"people": 11.4,
|
||||
"cost_per_month": 47603,
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
}
|
||||
},
|
||||
"findings": [],
|
||||
"change_request": null,
|
||||
"capability_sources_verified": false
|
||||
}
|
||||
@@ -0,0 +1 @@
|
||||
[]
|
||||
@@ -0,0 +1,237 @@
|
||||
# Operating model guide: Google Cloud landing zone platform foundation
|
||||
|
||||
## Summary
|
||||
|
||||
This guide sets out the target operating model for the Google Cloud landing zone platform foundation, covering the hub network and interconnect, audit log store, deployment pipeline, and encryption keys. Operational responsibility is shared between the customer and an external service provider across the United Kingdom, Poland, and India. The customer platform team steers platform product direction, developer flow measurement, and retains approval authority over all network changes, while the service provider operations team runs day-to-day operations, maintenance, and incident management. Fault response and platform availability are maintained around the clock (24x7), while change governance, service continuity, and lifecycle management are conducted during business hours.
|
||||
|
||||
Readers should look first at the findings and open questions, particularly the catalogue assumptions regarding cloud-native operations tooling, change pipeline procedures, and the exclusion of workload applications, as well as the draft status of the rate card. All scenario walk-throughs and validation checks pass successfully within the allocated operational budget.
|
||||
|
||||
### Key figures
|
||||
|
||||
- Operated: 4 Items, with 3 Conditions to keep true.
|
||||
- Faults responded to: 24x7 hours.
|
||||
- Capabilities: 21.
|
||||
- People: 11.4. Cost a month: 47,603 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
|
||||
- Scenario walk-throughs: 13 of 13 pass.
|
||||
- Business outcomes: 3, 3 shown by a Measure.
|
||||
- Findings for whoever owns the design: 0.
|
||||
|
||||
## Business outcomes
|
||||
|
||||
**BO-1: New payment products reach customers in weeks rather than months.** Target: A change reaches production within a day of approval..
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Deployment frequency | outcome | dora-metrics | A change reaches production within a day of approval. | Delivery and developer experience measurement | Platform Product Manager |
|
||||
| Friction and cognitive load | leading | devex-framework | | Delivery and developer experience measurement | Platform Product Manager |
|
||||
|
||||
**BO-2: Payments are never unavailable for long.** Target: Restored within 4 hours..
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Time to restore service | outcome | dora-metrics | Restored within 4 hours. | Incident management | Operations Lead |
|
||||
|
||||
**BO-3: We keep the platform engineers we hire.**
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Developer satisfaction | guardrail | space-framework | | Delivery and developer experience measurement | Platform Product Manager |
|
||||
|
||||
## What is operated
|
||||
|
||||
| Item | What it is | Kind | Product | From |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| S-1 | Hub network and interconnect | network | Cloud Interconnect | |
|
||||
| S-2 | Audit log store | storage | Cloud Storage | |
|
||||
| S-3 | Deployment pipeline | pipeline | Cloud Build | |
|
||||
| S-4 | Encryption keys | keys | Cloud KMS | |
|
||||
|
||||
What must be kept true while it is run:
|
||||
|
||||
| Condition | On | What must hold | From |
|
||||
| --- | --- | --- | --- |
|
||||
| K-1 | S-1 | The platform is available at least 99.9% of each month. | |
|
||||
| K-2 | S-2 | Audit logs cannot be deleted for seven years. | |
|
||||
| K-3 | S-4 | Encryption keys are rotated every 90 days. | |
|
||||
|
||||
## Operational requirements
|
||||
|
||||
| Requirement | Kind | What must be achieved | From |
|
||||
| --- | --- | --- | --- |
|
||||
| OR-1 | service_level | A fault on any Item is acknowledged within 15 minutes, at any hour. | service_levels.priority_1_response_minutes, operations.support_hours |
|
||||
| OR-2 | service_level | Service is restored within 4 hours of a major failure. | service_levels.recovery_time_hours, BO-2 |
|
||||
| OR-3 | service_level | The platform is available at least 99.9% of each month. | K-1 |
|
||||
| OR-4 | process | Every change to the network requires customer platform team approval prior to implementation. | REQ-01 |
|
||||
| OR-5 | process | A report of service levels and operating costs is provided monthly. | REQ-02 |
|
||||
| OR-6 | organisation | The platform foundation is operated under a shared service model between the customer and an external service provider. | sourcing.model |
|
||||
| OR-7 | organisation | Operational delivery is performed exclusively from the United Kingdom, Poland, and India. | sourcing.delivery_countries |
|
||||
| OR-8 | compliance | Audit logs cannot be deleted for seven years. | K-2 |
|
||||
| OR-9 | process | Encryption keys are rotated every 90 days. | K-3 |
|
||||
| OR-10 | service_level | An approved change reaches production within one day of approval. | BO-1 |
|
||||
|
||||
## Capabilities
|
||||
|
||||
| Capability | What it is | Serves | Covers | Hours | Effort a month |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| C-1 | Incident management | OR-1, OR-2 | S-1, S-2, S-3, S-4 | 24x7 | 30 h |
|
||||
| C-2 | Monitoring and alerting | OR-1, OR-3 | S-1, S-2, S-3, S-4 | 24x7 | 20 h |
|
||||
| C-3 | Problem management | OR-2 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-4 | Service request fulfilment | OR-6 | S-1, S-2, S-3, S-4 | business | 20 h |
|
||||
| C-5 | Change enablement | OR-4, OR-10 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-6 | Release and deployment | OR-10 | S-1, S-2, S-3, S-4 | business | 20 h |
|
||||
| C-7 | Configuration management | OR-8, OR-9 | S-1, S-2, S-3, S-4 | business | 15 h |
|
||||
| C-8 | Backup and recovery | OR-2, OR-8 | S-2, S-4 | business | 10 h |
|
||||
| C-9 | Service continuity | OR-2, OR-3 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-10 | Capacity and performance management | OR-3 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-11 | Access management | OR-6, OR-7 | S-1, S-2, S-3, S-4 | business | 15 h |
|
||||
| C-12 | Vulnerability and patch management | OR-9 | S-1, S-2, S-3, S-4 | business | 15 h |
|
||||
| C-13 | Security monitoring and response | OR-1, OR-8 | S-1, S-2, S-3, S-4 | 24x7 | 40 h |
|
||||
| C-14 | Cost management | OR-5 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-15 | Service level management | OR-3, OR-5 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-16 | Platform product management | OR-6 | S-1, S-2, S-3, S-4 | business | 15 h |
|
||||
| C-17 | Self-service and golden paths | OR-10 | S-1, S-2, S-3, S-4 | business | 20 h |
|
||||
| C-18 | Enablement | OR-10 | S-1, S-2, S-3, S-4 | business | 20 h |
|
||||
| C-19 | Delivery and developer experience measurement | OR-10 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-20 | Supplier management | OR-6, OR-7 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
| C-21 | Regulatory evidence and reporting | OR-8 | S-1, S-2, S-3, S-4 | business | 10 h |
|
||||
|
||||
## Who does what
|
||||
|
||||
| Role | Party | Country | Level | Hours |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Platform Product Manager | Customer (customer) | GB | lead | business |
|
||||
| Platform Engineer | Customer (customer) | GB | senior | business |
|
||||
| Operations Engineer | Service Provider (provider) | IN | engineer | 24x7 |
|
||||
| Operations Lead | Service Provider (provider) | IN | lead | business |
|
||||
| Security Operations Analyst | Service Provider (provider) | IN | senior | 24x7 |
|
||||
| Platform Ops Specialist | Service Provider (provider) | PL | senior | business |
|
||||
|
||||
The teams, as Team Topologies names their kinds:
|
||||
|
||||
| Team | Kind | Party | Roles | Purpose |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Customer Platform Team | platform | Customer | Platform Product Manager, Platform Engineer | Owns the platform roadmap, retains network change approvals, and measures developer flow. |
|
||||
| Provider Operations Team | platform | Service Provider | Operations Engineer, Operations Lead, Security Operations Analyst, Platform Ops Specialist | Provides 24x7 monitoring, incident response, and day-to-day operations of the platform foundation. |
|
||||
|
||||
How the teams work together:
|
||||
|
||||
| From | To | Mode | Until | Purpose |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Provider Operations Team | Customer Platform Team | x-as-a-service | | Provider requests network change approvals from the Customer Platform Team. |
|
||||
| Customer Platform Team | Provider Operations Team | x-as-a-service | | Customer relies on Provider Operations Team for 24x7 incident response and monitoring. |
|
||||
| Provider Operations Team | Customer Platform Team | collaboration | Month 3 after go-live, shifting to x-as-a-service. | Handover of runbooks and initial operational processes. |
|
||||
|
||||
| Capability | Platform Product Manager | Platform Engineer | Operations Engineer | Operations Lead | Security Operations Analyst | Platform Ops Specialist |
|
||||
| --- | --- | --- | --- | --- | --- | --- |
|
||||
| Incident management (C-1) | | C | R | A | | |
|
||||
| Monitoring and alerting (C-2) | | C | R | A | | |
|
||||
| Problem management (C-3) | | C | | A | | R |
|
||||
| Service request fulfilment (C-4) | | C | R | A | | |
|
||||
| Change enablement (C-5) | | A/R | | | | R |
|
||||
| Release and deployment (C-6) | | A/R | | | | R |
|
||||
| Configuration management (C-7) | | C | | A | | R |
|
||||
| Backup and recovery (C-8) | | C | | A | | R |
|
||||
| Service continuity (C-9) | | C | | A | | R |
|
||||
| Capacity and performance management (C-10) | | C | | A/R | | |
|
||||
| Access management (C-11) | | C | | A/R | | |
|
||||
| Vulnerability and patch management (C-12) | | C | | | A/R | |
|
||||
| Security monitoring and response (C-13) | | C | | | A/R | |
|
||||
| Cost management (C-14) | C | | | A/R | | |
|
||||
| Service level management (C-15) | C | | | A/R | | |
|
||||
| Platform product management (C-16) | A/R | | | C | | |
|
||||
| Self-service and golden paths (C-17) | | A/R | | | | R |
|
||||
| Enablement (C-18) | | A/R | | | | R |
|
||||
| Delivery and developer experience measurement (C-19) | A/R | | | C | | |
|
||||
| Supplier management (C-20) | A/R | | | R | | |
|
||||
| Regulatory evidence and reporting (C-21) | | C | | A | | R |
|
||||
|
||||
A accountable, R responsible, C consulted, I informed.
|
||||
|
||||
## Staffing and cost
|
||||
|
||||
| Role | Party | Country | Level | Hours | Effort a month | People | Cost a month |
|
||||
| --- | --- | --- | --- | --- | --- | --- | --- |
|
||||
| Platform Product Manager | Customer | GB | lead | business | 30.0 h | 0.2 | not priced |
|
||||
| Platform Engineer | Customer | GB | senior | business | 35.0 h | 0.3 | not priced |
|
||||
| Operations Engineer | Service Provider | IN | engineer | 24x7 | 70.0 h | 5.0 | 17,034 GBP |
|
||||
| Operations Lead | Service Provider | IN | lead | business | 50.0 h | 0.3 | 1,876 GBP |
|
||||
| Security Operations Analyst | Service Provider | IN | senior | 24x7 | 55.0 h | 5.0 | 24,605 GBP |
|
||||
| Platform Ops Specialist | Service Provider | PL | senior | business | 90.0 h | 0.6 | 4,088 GBP |
|
||||
|
||||
11.4 people in all. Cost a month: 47,603 GBP.
|
||||
The monthly budget is 60,000 GBP: this is within it.
|
||||
|
||||
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 | A fault on the hub network or any other item is acknowledged within 15 minutes at any hour. | pass | C-1 handles incident management 24x7, with a 24x7 Operations Engineer responsible, enabling acknowledgement of faults within 15 minutes at any hour. The cloud provider's native tooling (via C-2) supports configuring alerts without requiring a separate finding. |
|
||||
| OC-2 | Service is restored within 4 hours of a major failure on the platform. | pass | C-1 manages incident resolution with a 24x7 Operations Engineer responsible, allowing restoration of service within 4 hours of a major failure regardless of when the failure occurs. |
|
||||
| OC-3 | The platform availability is tracked to ensure at least 99.9% uptime each month. | pass | C-15 tracks and gathers metrics on availability to ensure the 99.9% target is tracked, with business-hours roles accountable and responsible. |
|
||||
| OC-4 | Capacity limits for the platform interconnect are managed to support 99.9% availability. | pass | C-10 reviews capacity trends for the interconnect to assure 99.9% availability, managed by the Operations Lead. |
|
||||
| OC-5 | Every change to the hub network requires explicit approval from the customer platform team. | pass | C-5 coordinates network change approvals with the customer, and a Customer Platform Engineer is accountable and responsible for it, ensuring explicit approval from the customer platform team. |
|
||||
| OC-6 | A consolidated monthly report includes service levels and operating costs. | pass | C-15 compiles the monthly operational report, pulling in cost data tracked by C-14, both managed by the Operations Lead. |
|
||||
| OC-7 | The shared service model responsibilities between customer and external service provider are governed. | pass | C-20 coordinates responsibilities across shared delivery borders, with roles from both the customer and provider teams responsible. |
|
||||
| OC-8a | Role performs operational delivery from India. | pass | R-3 (Operations Engineer) is based in India, satisfying the geographical requirement. |
|
||||
| OC-8b | Role performs operational delivery from India. | pass | R-4 (Operations Lead) is based in India, satisfying the geographical requirement. |
|
||||
| OC-8c | Role performs operational delivery from India. | pass | R-5 (Security Operations Analyst) is based in India, satisfying the geographical requirement. |
|
||||
| OC-8d | Role performs operational delivery from Poland. | pass | R-6 (Platform Ops Specialist) is based in Poland, satisfying the geographical requirement. |
|
||||
| OC-8e | Role performs operational delivery from the UK. | pass | R-1 (Platform Product Manager) is based in the UK, satisfying the geographical requirement. |
|
||||
| OC-8f | Role performs operational delivery from the UK. | pass | R-2 (Platform Engineer) is based in the UK, satisfying the geographical requirement. |
|
||||
| OC-9 | Audit log storage configuration ensures logs cannot be deleted for seven years. | pass | C-7 maintains audit log retention settings, with the Platform Ops Specialist responsible, ensuring logs cannot be deleted for seven years. |
|
||||
| OC-10 | Retention policies on Cloud Storage for audit logs are verified to prevent deletion for seven years. | pass | C-7 maintains and verifies retention settings on Cloud Storage for audit logs, satisfying the seven-year retention condition. |
|
||||
| OC-11 | Encryption key configurations are audited to ensure rotation every 90 days. | pass | C-7 audits configuration drift and manages key rotation schedules, ensuring encryption keys are rotated every 90 days. |
|
||||
| OC-12 | Cloud KMS encryption keys are verified to rotate every 90 days. | pass | C-7 manages key rotation schedules for the Cloud KMS encryption keys, verifying they rotate every 90 days. |
|
||||
| OC-13 | Deployment pipelines ensure an approved change reaches production within one day. | pass | C-6 oversees deployment pipelines to ensure approved changes reach production within a day, with customer and provider roles responsible. |
|
||||
| OC-14 | Backups of audit logs and encryption keys are successfully tested for restoration. | pass | C-8 maintains backups of logs and keys and successfully tests restore procedures, managed by the Platform Ops Specialist. |
|
||||
|
||||
Each scenario is generated from the operating model and traced through it by code.
|
||||
|
||||
| Scenario | Result | Path |
|
||||
| --- | --- | --- |
|
||||
| Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
|
||||
| Hub network and interconnect (S-1) must be changed. | pass | Platform Engineer makes the change under C-5. |
|
||||
| Audit log store (S-2) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
|
||||
| Audit log store (S-2) must be changed. | pass | Platform Engineer makes the change under C-5. |
|
||||
| Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
|
||||
| Deployment pipeline (S-3) must be changed. | pass | Platform Engineer makes the change under C-5. |
|
||||
| Encryption keys (S-4) fails at an hour faults are responded to (24x7). | pass | Operations Engineer responds under C-1, and Operations Lead is answerable. |
|
||||
| Encryption keys (S-4) must be changed. | pass | Platform Engineer makes the change under C-5. |
|
||||
| Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. | pass | Check OC-4 on C-10 keeps it true. |
|
||||
| Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. | pass | Check OC-10 on C-7 keeps it true. |
|
||||
| Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. | pass | Check OC-12 on C-7 keeps it true. |
|
||||
| Service Provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
|
||||
| A month's cost of operating is compared with the budget of 60,000 GBP. | pass | The cost is 47,603 GBP, within the budget. |
|
||||
|
||||
## Findings and open questions
|
||||
|
||||
No findings: the solution provides what operating it needs.
|
||||
|
||||
Assumed for the customer, and open to change when they answer:
|
||||
|
||||
- `intent.exclusions`: Workload applications running on the platform foundation, Network change approvals (retained by customer platform team). Assumed from the platform foundation scope: workload applications running on the platform are out of scope, and customer platform team retains network change approvals.
|
||||
- `operations.change_process`: Changes go through a deployment pipeline with peer review, with network changes requiring customer platform team approval.. Catalogue default adapted to customer requirement REQ-01: changes go through deployment pipelines with peer review, with customer platform team retaining approval over network changes.
|
||||
- `service_management.tooling`: The Cloud provider's own operations tooling, with no separate system.. Catalogue default: Cloud provider's native operations tooling with no separate system.
|
||||
|
||||
## 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.
|
||||
@@ -0,0 +1,84 @@
|
||||
[
|
||||
{
|
||||
"id": "OR-1",
|
||||
"kind": "service_level",
|
||||
"statement": "A fault on any Item is acknowledged within 15 minutes, at any hour.",
|
||||
"source": [
|
||||
"service_levels.priority_1_response_minutes",
|
||||
"operations.support_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-2",
|
||||
"kind": "service_level",
|
||||
"statement": "Service is restored within 4 hours of a major failure.",
|
||||
"source": [
|
||||
"service_levels.recovery_time_hours",
|
||||
"BO-2"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-3",
|
||||
"kind": "service_level",
|
||||
"statement": "The platform is available at least 99.9% of each month.",
|
||||
"source": [
|
||||
"K-1"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-4",
|
||||
"kind": "process",
|
||||
"statement": "Every change to the network requires customer platform team approval prior to implementation.",
|
||||
"source": [
|
||||
"REQ-01"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-5",
|
||||
"kind": "process",
|
||||
"statement": "A report of service levels and operating costs is provided monthly.",
|
||||
"source": [
|
||||
"REQ-02"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-6",
|
||||
"kind": "organisation",
|
||||
"statement": "The platform foundation is operated under a shared service model between the customer and an external service provider.",
|
||||
"source": [
|
||||
"sourcing.model"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-7",
|
||||
"kind": "organisation",
|
||||
"statement": "Operational delivery is performed exclusively from the United Kingdom, Poland, and India.",
|
||||
"source": [
|
||||
"sourcing.delivery_countries"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-8",
|
||||
"kind": "compliance",
|
||||
"statement": "Audit logs cannot be deleted for seven years.",
|
||||
"source": [
|
||||
"K-2"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-9",
|
||||
"kind": "process",
|
||||
"statement": "Encryption keys are rotated every 90 days.",
|
||||
"source": [
|
||||
"K-3"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-10",
|
||||
"kind": "service_level",
|
||||
"statement": "An approved change reaches production within one day of approval.",
|
||||
"source": [
|
||||
"BO-1"
|
||||
]
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,18 @@
|
||||
flowchart TB
|
||||
subgraph P_1["Customer (customer)"]
|
||||
subgraph T_1["Customer Platform Team (platform team)"]
|
||||
R_1["Platform Product Manager<br/>GB, lead, business"]
|
||||
R_2["Platform Engineer<br/>GB, senior, business"]
|
||||
end
|
||||
end
|
||||
subgraph P_2["Service Provider (provider)"]
|
||||
subgraph T_2["Provider Operations Team (platform team)"]
|
||||
R_3["Operations Engineer<br/>IN, engineer, 24x7"]
|
||||
R_4["Operations Lead<br/>IN, lead, business"]
|
||||
R_5["Security Operations Analyst<br/>IN, senior, 24x7"]
|
||||
R_6["Platform Ops Specialist<br/>PL, senior, business"]
|
||||
end
|
||||
end
|
||||
T_2 -- "x-as-a-service" --> T_1
|
||||
T_1 -- "x-as-a-service" --> T_2
|
||||
T_2 -- "collaboration until Month 3 after go-live, shifting to x-as-a-service." --> T_1
|
||||
@@ -0,0 +1,93 @@
|
||||
[
|
||||
{
|
||||
"id": "SC-fault-S-1",
|
||||
"scenario": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-1",
|
||||
"scenario": "Hub network and interconnect (S-1) must be changed.",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-2",
|
||||
"scenario": "Audit log store (S-2) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-2",
|
||||
"scenario": "Audit log store (S-2) must be changed.",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-3",
|
||||
"scenario": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-3",
|
||||
"scenario": "Deployment pipeline (S-3) must be changed.",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-4",
|
||||
"scenario": "Encryption keys (S-4) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-4",
|
||||
"scenario": "Encryption keys (S-4) must be changed.",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-1",
|
||||
"scenario": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month.",
|
||||
"about": "K-1",
|
||||
"passes": true,
|
||||
"path": "Check OC-4 on C-10 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-2",
|
||||
"scenario": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years.",
|
||||
"about": "K-2",
|
||||
"passes": true,
|
||||
"path": "Check OC-10 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-3",
|
||||
"scenario": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days.",
|
||||
"about": "K-3",
|
||||
"passes": true,
|
||||
"path": "Check OC-12 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-party-P-2",
|
||||
"scenario": "Service Provider cannot be reached.",
|
||||
"about": "P-2",
|
||||
"passes": true,
|
||||
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"id": "SC-budget",
|
||||
"scenario": "A month's cost of operating is compared with the budget of 60,000 GBP.",
|
||||
"about": "commercial.monthly_run_budget",
|
||||
"passes": true,
|
||||
"path": "The cost is 47,603 GBP, within the budget."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,203 @@
|
||||
{
|
||||
"kind": "platform_foundation",
|
||||
"stated": {
|
||||
"engagement": {
|
||||
"kind": "platform_foundation"
|
||||
},
|
||||
"intent": {
|
||||
"statement": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.\n",
|
||||
"requirements": [
|
||||
{
|
||||
"id": "REQ-01",
|
||||
"statement": "Our platform team approves every change to the network."
|
||||
},
|
||||
{
|
||||
"id": "REQ-02",
|
||||
"statement": "We receive a monthly report of service levels and cost."
|
||||
}
|
||||
],
|
||||
"business_outcomes": [
|
||||
{
|
||||
"id": "BO-1",
|
||||
"outcome": "New payment products reach customers in weeks rather than months.",
|
||||
"target": "A change reaches production within a day of approval."
|
||||
},
|
||||
{
|
||||
"id": "BO-2",
|
||||
"outcome": "Payments are never unavailable for long.",
|
||||
"target": "Restored within 4 hours."
|
||||
},
|
||||
{
|
||||
"id": "BO-3",
|
||||
"outcome": "We keep the platform engineers we hire."
|
||||
}
|
||||
]
|
||||
},
|
||||
"solution": {
|
||||
"cloud_provider": "gcp",
|
||||
"items": [
|
||||
{
|
||||
"id": "S-1",
|
||||
"name": "Hub network and interconnect",
|
||||
"kind": "network",
|
||||
"product": "Cloud Interconnect"
|
||||
},
|
||||
{
|
||||
"id": "S-2",
|
||||
"name": "Audit log store",
|
||||
"kind": "storage",
|
||||
"product": "Cloud Storage"
|
||||
},
|
||||
{
|
||||
"id": "S-3",
|
||||
"name": "Deployment pipeline",
|
||||
"kind": "pipeline",
|
||||
"product": "Cloud Build"
|
||||
},
|
||||
{
|
||||
"id": "S-4",
|
||||
"name": "Encryption keys",
|
||||
"kind": "keys",
|
||||
"product": "Cloud KMS"
|
||||
}
|
||||
],
|
||||
"conditions": [
|
||||
{
|
||||
"id": "K-1",
|
||||
"on": [
|
||||
"S-1"
|
||||
],
|
||||
"condition": "The platform is available at least 99.9% of each month."
|
||||
},
|
||||
{
|
||||
"id": "K-2",
|
||||
"on": [
|
||||
"S-2"
|
||||
],
|
||||
"condition": "Audit logs cannot be deleted for seven years."
|
||||
},
|
||||
{
|
||||
"id": "K-3",
|
||||
"on": [
|
||||
"S-4"
|
||||
],
|
||||
"condition": "Encryption keys are rotated every 90 days."
|
||||
}
|
||||
],
|
||||
"build": {
|
||||
"duration_days": 36
|
||||
}
|
||||
},
|
||||
"operations": {
|
||||
"support_hours": "24x7",
|
||||
"availability_hours": "24x7"
|
||||
},
|
||||
"sourcing": {
|
||||
"model": "shared",
|
||||
"delivery_countries": [
|
||||
"GB",
|
||||
"PL",
|
||||
"IN"
|
||||
]
|
||||
},
|
||||
"organisation": {
|
||||
"existing_teams": [
|
||||
{
|
||||
"name": "Platform team",
|
||||
"party": "customer",
|
||||
"hours": "business",
|
||||
"country": "GB"
|
||||
}
|
||||
]
|
||||
},
|
||||
"service_levels": {
|
||||
"priority_1_response_minutes": 15,
|
||||
"recovery_time_hours": 4
|
||||
},
|
||||
"compliance": {
|
||||
"frameworks": [
|
||||
"DORA"
|
||||
]
|
||||
},
|
||||
"commercial": {
|
||||
"currency": "GBP",
|
||||
"monthly_run_budget": 60000
|
||||
}
|
||||
},
|
||||
"binding": [
|
||||
"operations.support_hours",
|
||||
"sourcing.model",
|
||||
"sourcing.delivery_countries",
|
||||
"service_levels.priority_1_response_minutes",
|
||||
"service_levels.recovery_time_hours"
|
||||
],
|
||||
"assumed": [
|
||||
{
|
||||
"field": "intent.exclusions",
|
||||
"value": [
|
||||
"Workload applications running on the platform foundation",
|
||||
"Network change approvals (retained by customer platform team)"
|
||||
],
|
||||
"why": "Assumed from the platform foundation scope: workload applications running on the platform are out of scope, and customer platform team retains network change approvals."
|
||||
},
|
||||
{
|
||||
"field": "operations.change_process",
|
||||
"value": "Changes go through a deployment pipeline with peer review, with network changes requiring customer platform team approval.",
|
||||
"why": "Catalogue default adapted to customer requirement REQ-01: changes go through deployment pipelines with peer review, with customer platform team retaining approval over network changes."
|
||||
},
|
||||
{
|
||||
"field": "service_management.tooling",
|
||||
"value": "The Cloud provider's own operations tooling, with no separate system.",
|
||||
"why": "Catalogue default: Cloud provider's native operations tooling with no separate system."
|
||||
}
|
||||
],
|
||||
"to_decide": [],
|
||||
"to_ask": [
|
||||
{
|
||||
"field": "metadata.client_name",
|
||||
"prompt": "What is metadata.client_name?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.author",
|
||||
"prompt": "What is metadata.author?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.revision",
|
||||
"prompt": "What is metadata.revision?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.source",
|
||||
"prompt": "What is metadata.source?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "solution.build.customer_owned",
|
||||
"prompt": "Which parts of the build does the customer or their supplier own?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "solution.inherited_risks",
|
||||
"prompt": "What is already known to be unverified or at risk in the solution?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "operations.monitoring",
|
||||
"prompt": "Which monitoring and alerting is already in place or required?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "organisation.headcount_limit",
|
||||
"prompt": "Is there a limit on the number of people operating this?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "transition.go_live_date",
|
||||
"prompt": "When must the solution be in operation?",
|
||||
"severity": "LOW"
|
||||
}
|
||||
],
|
||||
"not_applicable": []
|
||||
}
|
||||
@@ -0,0 +1,201 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: bench-landing-zone-shared
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: ask
|
||||
status: BASELINE_LOCKED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We want our landing zone run as a shared service from go-live. A provider
|
||||
should
|
||||
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
|
||||
over changes to the network.
|
||||
|
||||
'
|
||||
requirements:
|
||||
- id: REQ-01
|
||||
statement: Our platform team approves every change to the network.
|
||||
- id: REQ-02
|
||||
statement: We receive a monthly report of service levels and cost.
|
||||
business_outcomes:
|
||||
- id: BO-1
|
||||
outcome: New payment products reach customers in weeks rather than months.
|
||||
target: A change reaches production within a day of approval.
|
||||
- id: BO-2
|
||||
outcome: Payments are never unavailable for long.
|
||||
target: Restored within 4 hours.
|
||||
- id: BO-3
|
||||
outcome: We keep the platform engineers we hire.
|
||||
exclusions:
|
||||
- Workload applications running on the platform foundation
|
||||
- Network change approvals (retained by customer platform team)
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Hub network and interconnect
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
- id: S-2
|
||||
name: Audit log store
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
- id: S-3
|
||||
name: Deployment pipeline
|
||||
kind: pipeline
|
||||
product: Cloud Build
|
||||
- id: S-4
|
||||
name: Encryption keys
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
condition: The platform is available at least 99.9% of each month.
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-2
|
||||
condition: Audit logs cannot be deleted for seven years.
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-4
|
||||
condition: Encryption keys are rotated every 90 days.
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned: ask
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Changes go through a deployment pipeline with peer review, with
|
||||
network changes requiring customer platform team approval.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: shared
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams:
|
||||
- name: Platform team
|
||||
party: customer
|
||||
hours: business
|
||||
country: GB
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: The Cloud provider's own operations tooling, with no separate system.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 15
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: 60000
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.exclusions
|
||||
statement: 'Assumed intent.exclusions is [''Workload applications running on the
|
||||
platform foundation'', ''Network change approvals (retained by customer platform
|
||||
team)'']. Assumed from the platform foundation scope: workload applications running
|
||||
on the platform are out of scope, and customer platform team retains network change
|
||||
approvals.'
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-02
|
||||
field: operations.change_process
|
||||
statement: 'Assumed operations.change_process is Changes go through a deployment
|
||||
pipeline with peer review, with network changes requiring customer platform team
|
||||
approval.. Catalogue default adapted to customer requirement REQ-01: changes go
|
||||
through deployment pipelines with peer review, with customer platform team retaining
|
||||
approval over network changes.'
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-03
|
||||
field: service_management.tooling
|
||||
statement: 'Assumed service_management.tooling is The Cloud provider''s own operations
|
||||
tooling, with no separate system.. Catalogue default: Cloud provider''s native
|
||||
operations tooling with no separate system.'
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: metadata.source
|
||||
prompt: What is metadata.source?
|
||||
severity: LOW
|
||||
- field: solution.build.customer_owned
|
||||
prompt: Which parts of the build does the customer or their supplier own?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: supplied
|
||||
commercial.monthly_run_budget: supplied
|
||||
compliance.frameworks: supplied
|
||||
engagement.kind: supplied
|
||||
intent.business_outcomes: supplied
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: supplied
|
||||
intent.statement: supplied
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: supplied
|
||||
metadata.revision: unknown
|
||||
metadata.source: unknown
|
||||
operations.availability_hours: supplied
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: supplied
|
||||
organisation.existing_teams: supplied
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: supplied
|
||||
service_levels.recovery_time_hours: supplied
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: unknown
|
||||
solution.build.duration_days: supplied
|
||||
solution.cloud_provider: supplied
|
||||
solution.conditions: supplied
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: supplied
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 20
|
||||
answered: 0
|
||||
assumed: 3
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
@@ -0,0 +1,117 @@
|
||||
{
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
},
|
||||
"conversion": {
|
||||
"from": "USD",
|
||||
"rate": 0.79,
|
||||
"as_of": "2026-10-13"
|
||||
},
|
||||
"roles": [
|
||||
{
|
||||
"role": "R-1",
|
||||
"name": "Platform Product Manager",
|
||||
"party": "P-1",
|
||||
"party_name": "Customer",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 30.0,
|
||||
"people": 0.2,
|
||||
"cost_per_month": null
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"name": "Platform Engineer",
|
||||
"party": "P-1",
|
||||
"party_name": "Customer",
|
||||
"country": "GB",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 35.0,
|
||||
"people": 0.3,
|
||||
"cost_per_month": null
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"name": "Operations Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "IN",
|
||||
"level": "engineer",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 70.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 17034
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"name": "Operations Lead",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "IN",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 50.0,
|
||||
"people": 0.3,
|
||||
"cost_per_month": 1876
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"name": "Security Operations Analyst",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "IN",
|
||||
"level": "senior",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 55.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 24605
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"name": "Platform Ops Specialist",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 90.0,
|
||||
"people": 0.6,
|
||||
"cost_per_month": 4088
|
||||
}
|
||||
],
|
||||
"people": 11.4,
|
||||
"cost_per_month": 47603,
|
||||
"by_party": {
|
||||
"P-2": 47603
|
||||
},
|
||||
"by_country": {
|
||||
"IN": 43515,
|
||||
"PL": 4088
|
||||
},
|
||||
"by_capability": {
|
||||
"C-1": 7300,
|
||||
"C-2": 4867,
|
||||
"C-4": 4867,
|
||||
"C-10": 375,
|
||||
"C-11": 563,
|
||||
"C-14": 375,
|
||||
"C-15": 375,
|
||||
"C-20": 188,
|
||||
"C-12": 6711,
|
||||
"C-13": 17895,
|
||||
"C-3": 454,
|
||||
"C-5": 227,
|
||||
"C-6": 454,
|
||||
"C-7": 681,
|
||||
"C-8": 454,
|
||||
"C-9": 454,
|
||||
"C-17": 454,
|
||||
"C-18": 454,
|
||||
"C-21": 454
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,642 @@
|
||||
{
|
||||
"parties": [
|
||||
{
|
||||
"kind": "customer",
|
||||
"name": "Customer",
|
||||
"id": "P-1"
|
||||
},
|
||||
{
|
||||
"kind": "provider",
|
||||
"name": "Service Provider",
|
||||
"id": "P-2"
|
||||
}
|
||||
],
|
||||
"teams": [
|
||||
{
|
||||
"purpose": "Owns the platform roadmap, retains network change approvals, and measures developer flow.",
|
||||
"id": "T-1",
|
||||
"party": "P-1",
|
||||
"type": "platform",
|
||||
"name": "Customer Platform Team"
|
||||
},
|
||||
{
|
||||
"id": "T-2",
|
||||
"name": "Provider Operations Team",
|
||||
"type": "platform",
|
||||
"party": "P-2",
|
||||
"purpose": "Provides 24x7 monitoring, incident response, and day-to-day operations of the platform foundation."
|
||||
}
|
||||
],
|
||||
"roles": [
|
||||
{
|
||||
"party": "P-1",
|
||||
"id": "R-1",
|
||||
"hours": "business",
|
||||
"team": "T-1",
|
||||
"name": "Platform Product Manager",
|
||||
"level": "lead",
|
||||
"country": "GB"
|
||||
},
|
||||
{
|
||||
"party": "P-1",
|
||||
"hours": "business",
|
||||
"team": "T-1",
|
||||
"level": "senior",
|
||||
"id": "R-2",
|
||||
"name": "Platform Engineer",
|
||||
"country": "GB"
|
||||
},
|
||||
{
|
||||
"level": "engineer",
|
||||
"hours": "24x7",
|
||||
"party": "P-2",
|
||||
"name": "Operations Engineer",
|
||||
"team": "T-2",
|
||||
"id": "R-3",
|
||||
"country": "IN"
|
||||
},
|
||||
{
|
||||
"country": "IN",
|
||||
"level": "lead",
|
||||
"id": "R-4",
|
||||
"name": "Operations Lead",
|
||||
"hours": "business",
|
||||
"team": "T-2",
|
||||
"party": "P-2"
|
||||
},
|
||||
{
|
||||
"level": "senior",
|
||||
"party": "P-2",
|
||||
"id": "R-5",
|
||||
"hours": "24x7",
|
||||
"name": "Security Operations Analyst",
|
||||
"country": "IN",
|
||||
"team": "T-2"
|
||||
},
|
||||
{
|
||||
"id": "R-6",
|
||||
"name": "Platform Ops Specialist",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"team": "T-2",
|
||||
"party": "P-2"
|
||||
}
|
||||
],
|
||||
"interactions": [
|
||||
{
|
||||
"to": "T-1",
|
||||
"mode": "x_as_a_service",
|
||||
"from": "T-2",
|
||||
"purpose": "Provider requests network change approvals from the Customer Platform Team.",
|
||||
"id": "I-1"
|
||||
},
|
||||
{
|
||||
"id": "I-2",
|
||||
"mode": "x_as_a_service",
|
||||
"to": "T-2",
|
||||
"purpose": "Customer relies on Provider Operations Team for 24x7 incident response and monitoring.",
|
||||
"from": "T-1"
|
||||
},
|
||||
{
|
||||
"from": "T-2",
|
||||
"to": "T-1",
|
||||
"purpose": "Handover of runbooks and initial operational processes.",
|
||||
"mode": "collaboration",
|
||||
"until": "Month 3 after go-live, shifting to x-as-a-service.",
|
||||
"id": "I-3"
|
||||
}
|
||||
],
|
||||
"measures": [
|
||||
{
|
||||
"framework": "dora-metrics",
|
||||
"name": "Deployment frequency",
|
||||
"outcome": "BO-1",
|
||||
"layer": "outcome",
|
||||
"id": "M-1",
|
||||
"target": "A change reaches production within a day of approval.",
|
||||
"measured_by": "C-19"
|
||||
},
|
||||
{
|
||||
"outcome": "BO-3",
|
||||
"id": "M-2",
|
||||
"name": "Developer satisfaction",
|
||||
"layer": "guardrail",
|
||||
"measured_by": "C-19",
|
||||
"framework": "space-framework"
|
||||
},
|
||||
{
|
||||
"measured_by": "C-19",
|
||||
"outcome": "BO-1",
|
||||
"framework": "devex-framework",
|
||||
"name": "Friction and cognitive load",
|
||||
"id": "M-3",
|
||||
"layer": "leading"
|
||||
},
|
||||
{
|
||||
"layer": "outcome",
|
||||
"outcome": "BO-2",
|
||||
"measured_by": "C-1",
|
||||
"target": "Restored within 4 hours.",
|
||||
"name": "Time to restore service",
|
||||
"framework": "dora-metrics",
|
||||
"id": "M-4"
|
||||
}
|
||||
],
|
||||
"responsibilities": [
|
||||
{
|
||||
"id": "RS-1-acc",
|
||||
"capability": "C-1",
|
||||
"kind": "accountable",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"id": "RS-1-res",
|
||||
"kind": "responsible",
|
||||
"role": "R-3",
|
||||
"capability": "C-1"
|
||||
},
|
||||
{
|
||||
"id": "RS-1-con",
|
||||
"capability": "C-1",
|
||||
"role": "R-2",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"id": "RS-2-acc",
|
||||
"role": "R-4",
|
||||
"capability": "C-2",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-2",
|
||||
"id": "RS-2-res",
|
||||
"kind": "responsible",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"capability": "C-2",
|
||||
"role": "R-2",
|
||||
"kind": "consulted",
|
||||
"id": "RS-2-con"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"role": "R-4",
|
||||
"capability": "C-3",
|
||||
"id": "RS-3-acc"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"kind": "responsible",
|
||||
"id": "RS-3-res",
|
||||
"capability": "C-3"
|
||||
},
|
||||
{
|
||||
"capability": "C-3",
|
||||
"role": "R-2",
|
||||
"id": "RS-3-con",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"kind": "accountable",
|
||||
"capability": "C-4",
|
||||
"id": "RS-4-acc"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-3",
|
||||
"capability": "C-4",
|
||||
"id": "RS-4-res"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-2",
|
||||
"id": "RS-4-con",
|
||||
"capability": "C-4"
|
||||
},
|
||||
{
|
||||
"id": "RS-5-acc",
|
||||
"role": "R-2",
|
||||
"kind": "accountable",
|
||||
"capability": "C-5"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"kind": "responsible",
|
||||
"capability": "C-5",
|
||||
"id": "RS-5-res1"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-6",
|
||||
"id": "RS-5-res2",
|
||||
"capability": "C-5"
|
||||
},
|
||||
{
|
||||
"capability": "C-6",
|
||||
"role": "R-2",
|
||||
"id": "RS-6-acc",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-6",
|
||||
"id": "RS-6-res1",
|
||||
"kind": "responsible",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"id": "RS-6-res2",
|
||||
"kind": "responsible",
|
||||
"capability": "C-6"
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"id": "RS-7-acc",
|
||||
"capability": "C-7",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"capability": "C-7",
|
||||
"id": "RS-7-res",
|
||||
"role": "R-6"
|
||||
},
|
||||
{
|
||||
"capability": "C-7",
|
||||
"role": "R-2",
|
||||
"id": "RS-7-con",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"role": "R-4",
|
||||
"id": "RS-8-acc",
|
||||
"capability": "C-8"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"capability": "C-8",
|
||||
"id": "RS-8-res",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"capability": "C-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-8-con"
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"id": "RS-9-acc",
|
||||
"capability": "C-9",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-6",
|
||||
"capability": "C-9",
|
||||
"id": "RS-9-res"
|
||||
},
|
||||
{
|
||||
"id": "RS-9-con",
|
||||
"role": "R-2",
|
||||
"kind": "consulted",
|
||||
"capability": "C-9"
|
||||
},
|
||||
{
|
||||
"id": "RS-10-acc",
|
||||
"kind": "accountable",
|
||||
"capability": "C-10",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"id": "RS-10-res",
|
||||
"capability": "C-10",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"id": "RS-10-con",
|
||||
"role": "R-2",
|
||||
"capability": "C-10"
|
||||
},
|
||||
{
|
||||
"capability": "C-11",
|
||||
"role": "R-4",
|
||||
"id": "RS-11-acc",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-11",
|
||||
"role": "R-4",
|
||||
"id": "RS-11-res",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"capability": "C-11",
|
||||
"id": "RS-11-con",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"id": "RS-12-acc",
|
||||
"role": "R-5",
|
||||
"capability": "C-12"
|
||||
},
|
||||
{
|
||||
"capability": "C-12",
|
||||
"kind": "responsible",
|
||||
"id": "RS-12-res",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-2",
|
||||
"capability": "C-12",
|
||||
"id": "RS-12-con"
|
||||
},
|
||||
{
|
||||
"capability": "C-13",
|
||||
"kind": "accountable",
|
||||
"role": "R-5",
|
||||
"id": "RS-13-acc"
|
||||
},
|
||||
{
|
||||
"id": "RS-13-res",
|
||||
"capability": "C-13",
|
||||
"kind": "responsible",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"id": "RS-13-con",
|
||||
"capability": "C-13",
|
||||
"role": "R-2",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"role": "R-4",
|
||||
"capability": "C-14",
|
||||
"id": "RS-14-acc"
|
||||
},
|
||||
{
|
||||
"id": "RS-14-res",
|
||||
"capability": "C-14",
|
||||
"role": "R-4",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-1",
|
||||
"capability": "C-14",
|
||||
"id": "RS-14-con"
|
||||
},
|
||||
{
|
||||
"capability": "C-15",
|
||||
"kind": "accountable",
|
||||
"id": "RS-15-acc",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"id": "RS-15-res",
|
||||
"kind": "responsible",
|
||||
"capability": "C-15",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"capability": "C-15",
|
||||
"id": "RS-15-con",
|
||||
"role": "R-1",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"role": "R-1",
|
||||
"id": "RS-16-acc",
|
||||
"capability": "C-16"
|
||||
},
|
||||
{
|
||||
"id": "RS-16-res",
|
||||
"capability": "C-16",
|
||||
"role": "R-1",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"id": "RS-16-con",
|
||||
"role": "R-4",
|
||||
"kind": "consulted",
|
||||
"capability": "C-16"
|
||||
},
|
||||
{
|
||||
"id": "RS-17-acc",
|
||||
"role": "R-2",
|
||||
"kind": "accountable",
|
||||
"capability": "C-17"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-2",
|
||||
"id": "RS-17-res1",
|
||||
"capability": "C-17"
|
||||
},
|
||||
{
|
||||
"capability": "C-17",
|
||||
"kind": "responsible",
|
||||
"role": "R-6",
|
||||
"id": "RS-17-res2"
|
||||
},
|
||||
{
|
||||
"capability": "C-18",
|
||||
"role": "R-2",
|
||||
"id": "RS-18-acc",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-2",
|
||||
"id": "RS-18-res1",
|
||||
"capability": "C-18"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"kind": "responsible",
|
||||
"capability": "C-18",
|
||||
"id": "RS-18-res2"
|
||||
},
|
||||
{
|
||||
"capability": "C-19",
|
||||
"kind": "accountable",
|
||||
"role": "R-1",
|
||||
"id": "RS-19-acc"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"capability": "C-19",
|
||||
"id": "RS-19-res",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"id": "RS-19-con",
|
||||
"role": "R-4",
|
||||
"kind": "consulted",
|
||||
"capability": "C-19"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"id": "RS-20-acc",
|
||||
"capability": "C-20",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"capability": "C-20",
|
||||
"id": "RS-20-res1",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"capability": "C-20",
|
||||
"role": "R-4",
|
||||
"id": "RS-20-res2"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-21",
|
||||
"id": "RS-21-acc",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"id": "RS-21-res",
|
||||
"capability": "C-21",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"id": "RS-21-con",
|
||||
"capability": "C-21",
|
||||
"kind": "consulted"
|
||||
}
|
||||
],
|
||||
"checks": [
|
||||
{
|
||||
"source": "OR-1",
|
||||
"id": "OC-1",
|
||||
"condition": "A fault on the hub network or any other item is acknowledged within 15 minutes at any hour.",
|
||||
"on": "C-1"
|
||||
},
|
||||
{
|
||||
"condition": "Service is restored within 4 hours of a major failure on the platform.",
|
||||
"on": "C-1",
|
||||
"source": "OR-2",
|
||||
"id": "OC-2"
|
||||
},
|
||||
{
|
||||
"on": "C-15",
|
||||
"condition": "The platform availability is tracked to ensure at least 99.9% uptime each month.",
|
||||
"source": "OR-3",
|
||||
"id": "OC-3"
|
||||
},
|
||||
{
|
||||
"source": "K-1",
|
||||
"id": "OC-4",
|
||||
"condition": "Capacity limits for the platform interconnect are managed to support 99.9% availability.",
|
||||
"on": "C-10"
|
||||
},
|
||||
{
|
||||
"source": "OR-4",
|
||||
"condition": "Every change to the hub network requires explicit approval from the customer platform team.",
|
||||
"id": "OC-5",
|
||||
"on": "C-5"
|
||||
},
|
||||
{
|
||||
"condition": "A consolidated monthly report includes service levels and operating costs.",
|
||||
"source": "OR-5",
|
||||
"on": "C-15",
|
||||
"id": "OC-6"
|
||||
},
|
||||
{
|
||||
"source": "OR-6",
|
||||
"id": "OC-7",
|
||||
"condition": "The shared service model responsibilities between customer and external service provider are governed.",
|
||||
"on": "C-20"
|
||||
},
|
||||
{
|
||||
"on": "R-3",
|
||||
"id": "OC-8a",
|
||||
"source": "OR-7",
|
||||
"condition": "Role performs operational delivery from India."
|
||||
},
|
||||
{
|
||||
"condition": "Role performs operational delivery from India.",
|
||||
"id": "OC-8b",
|
||||
"source": "OR-7",
|
||||
"on": "R-4"
|
||||
},
|
||||
{
|
||||
"source": "OR-7",
|
||||
"id": "OC-8c",
|
||||
"condition": "Role performs operational delivery from India.",
|
||||
"on": "R-5"
|
||||
},
|
||||
{
|
||||
"condition": "Role performs operational delivery from Poland.",
|
||||
"id": "OC-8d",
|
||||
"on": "R-6",
|
||||
"source": "OR-7"
|
||||
},
|
||||
{
|
||||
"condition": "Role performs operational delivery from the UK.",
|
||||
"source": "OR-7",
|
||||
"id": "OC-8e",
|
||||
"on": "R-1"
|
||||
},
|
||||
{
|
||||
"condition": "Role performs operational delivery from the UK.",
|
||||
"on": "R-2",
|
||||
"source": "OR-7",
|
||||
"id": "OC-8f"
|
||||
},
|
||||
{
|
||||
"on": "C-7",
|
||||
"source": "OR-8",
|
||||
"condition": "Audit log storage configuration ensures logs cannot be deleted for seven years.",
|
||||
"id": "OC-9"
|
||||
},
|
||||
{
|
||||
"condition": "Retention policies on Cloud Storage for audit logs are verified to prevent deletion for seven years.",
|
||||
"source": "K-2",
|
||||
"id": "OC-10",
|
||||
"on": "C-7"
|
||||
},
|
||||
{
|
||||
"condition": "Encryption key configurations are audited to ensure rotation every 90 days.",
|
||||
"source": "OR-9",
|
||||
"id": "OC-11",
|
||||
"on": "C-7"
|
||||
},
|
||||
{
|
||||
"on": "C-7",
|
||||
"id": "OC-12",
|
||||
"source": "K-3",
|
||||
"condition": "Cloud KMS encryption keys are verified to rotate every 90 days."
|
||||
},
|
||||
{
|
||||
"on": "C-6",
|
||||
"id": "OC-13",
|
||||
"source": "OR-10",
|
||||
"condition": "Deployment pipelines ensure an approved change reaches production within one day."
|
||||
},
|
||||
{
|
||||
"condition": "Backups of audit logs and encryption keys are successfully tested for restoration.",
|
||||
"id": "OC-14",
|
||||
"source": "OR-2",
|
||||
"on": "C-8"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,169 @@
|
||||
{
|
||||
"dry_run": {
|
||||
"verdict": "pass",
|
||||
"evidence": "13 of 13 scenario walk-throughs pass."
|
||||
},
|
||||
"checks": [
|
||||
{
|
||||
"check": "OC-1",
|
||||
"evidence": "C-1 handles incident management 24x7, with a 24x7 Operations Engineer responsible, enabling acknowledgement of faults within 15 minutes at any hour. The cloud provider's native tooling (via C-2) supports configuring alerts without requiring a separate finding.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "C-1 manages incident resolution with a 24x7 Operations Engineer responsible, allowing restoration of service within 4 hours of a major failure regardless of when the failure occurs.",
|
||||
"check": "OC-2",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "C-15 tracks and gathers metrics on availability to ensure the 99.9% target is tracked, with business-hours roles accountable and responsible.",
|
||||
"check": "OC-3"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "C-10 reviews capacity trends for the interconnect to assure 99.9% availability, managed by the Operations Lead.",
|
||||
"check": "OC-4"
|
||||
},
|
||||
{
|
||||
"evidence": "C-5 coordinates network change approvals with the customer, and a Customer Platform Engineer is accountable and responsible for it, ensuring explicit approval from the customer platform team.",
|
||||
"check": "OC-5",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-6",
|
||||
"evidence": "C-15 compiles the monthly operational report, pulling in cost data tracked by C-14, both managed by the Operations Lead."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-7",
|
||||
"evidence": "C-20 coordinates responsibilities across shared delivery borders, with roles from both the customer and provider teams responsible."
|
||||
},
|
||||
{
|
||||
"check": "OC-8a",
|
||||
"evidence": "R-3 (Operations Engineer) is based in India, satisfying the geographical requirement.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "R-4 (Operations Lead) is based in India, satisfying the geographical requirement.",
|
||||
"check": "OC-8b",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-8c",
|
||||
"evidence": "R-5 (Security Operations Analyst) is based in India, satisfying the geographical requirement."
|
||||
},
|
||||
{
|
||||
"check": "OC-8d",
|
||||
"verdict": "pass",
|
||||
"evidence": "R-6 (Platform Ops Specialist) is based in Poland, satisfying the geographical requirement."
|
||||
},
|
||||
{
|
||||
"check": "OC-8e",
|
||||
"evidence": "R-1 (Platform Product Manager) is based in the UK, satisfying the geographical requirement.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "OC-8f",
|
||||
"verdict": "pass",
|
||||
"evidence": "R-2 (Platform Engineer) is based in the UK, satisfying the geographical requirement."
|
||||
},
|
||||
{
|
||||
"evidence": "C-7 maintains audit log retention settings, with the Platform Ops Specialist responsible, ensuring logs cannot be deleted for seven years.",
|
||||
"check": "OC-9",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "OC-10",
|
||||
"verdict": "pass",
|
||||
"evidence": "C-7 maintains and verifies retention settings on Cloud Storage for audit logs, satisfying the seven-year retention condition."
|
||||
},
|
||||
{
|
||||
"check": "OC-11",
|
||||
"verdict": "pass",
|
||||
"evidence": "C-7 audits configuration drift and manages key rotation schedules, ensuring encryption keys are rotated every 90 days."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "C-7 manages key rotation schedules for the Cloud KMS encryption keys, verifying they rotate every 90 days.",
|
||||
"check": "OC-12"
|
||||
},
|
||||
{
|
||||
"check": "OC-13",
|
||||
"verdict": "pass",
|
||||
"evidence": "C-6 oversees deployment pipelines to ensure approved changes reach production within a day, with customer and provider roles responsible."
|
||||
},
|
||||
{
|
||||
"evidence": "C-8 maintains backups of logs and keys and successfully tests restore procedures, managed by the Platform Ops Specialist.",
|
||||
"check": "OC-14",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Hub network and interconnect (S-1) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Hub network and interconnect (S-1) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Audit log store (S-2) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Audit log store (S-2) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Deployment pipeline (S-3) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Deployment pipeline (S-3) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Encryption keys (S-4) fails at an hour faults are responded to (24x7). Operations Engineer responds under C-1, and Operations Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Encryption keys (S-4) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-1 must be shown to hold: The platform is available at least 99.9% of each month. Check OC-4 on C-10 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-2 must be shown to hold: Audit logs cannot be deleted for seven years. Check OC-10 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-3 must be shown to hold: Encryption keys are rotated every 90 days. Check OC-12 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-party-P-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Service Provider cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"check": "SC-budget",
|
||||
"verdict": "pass",
|
||||
"evidence": "A month's cost of operating is compared with the budget of 60,000 GBP. The cost is 47,603 GBP, within the budget."
|
||||
}
|
||||
],
|
||||
"proposed_additions": []
|
||||
}
|
||||
@@ -0,0 +1,10 @@
|
||||
# Intent 1: bench-landing-zone-shared
|
||||
|
||||
- Recorded: 2026-10-21T20:36:25+00:00
|
||||
- Execution: `case-01-landing-zone-shared-r1`
|
||||
|
||||
## What the customer wants
|
||||
|
||||
We want our landing zone run as a shared service from go-live. A provider should
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
over changes to the network.
|
||||
@@ -0,0 +1,198 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: bench-landing-zone-shared
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: ask
|
||||
status: BASELINE_LOCKED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We want our landing zone run as a shared service from go-live. A provider
|
||||
should
|
||||
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
|
||||
over changes to the network.
|
||||
|
||||
'
|
||||
requirements:
|
||||
- id: REQ-01
|
||||
statement: Our platform team approves every change to the network.
|
||||
- id: REQ-02
|
||||
statement: We receive a monthly report of service levels and cost.
|
||||
business_outcomes:
|
||||
- id: BO-1
|
||||
outcome: New payment products reach customers in weeks rather than months.
|
||||
target: A change reaches production within a day of approval.
|
||||
- id: BO-2
|
||||
outcome: Payments are never unavailable for long.
|
||||
target: Restored within 4 hours.
|
||||
- id: BO-3
|
||||
outcome: We keep the platform engineers we hire.
|
||||
exclusions:
|
||||
- Application workloads and services hosted on the platform foundation
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Hub network and interconnect
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
- id: S-2
|
||||
name: Audit log store
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
- id: S-3
|
||||
name: Deployment pipeline
|
||||
kind: pipeline
|
||||
product: Cloud Build
|
||||
- id: S-4
|
||||
name: Encryption keys
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
condition: The platform is available at least 99.9% of each month.
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-2
|
||||
condition: Audit logs cannot be deleted for seven years.
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-4
|
||||
condition: Encryption keys are rotated every 90 days.
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned: ask
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Changes go through a deployment pipeline with peer review, with
|
||||
explicit customer platform team approval required for all network changes.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: shared
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams:
|
||||
- name: Platform team
|
||||
party: customer
|
||||
hours: business
|
||||
country: GB
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: Google Cloud operations suite and native Cloud provider tooling, with no
|
||||
separate external ITSM system.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 15
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: 60000
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.exclusions
|
||||
statement: 'Assumed intent.exclusions is [''Application workloads and services hosted
|
||||
on the platform foundation'']. Assumed based on platform foundation scope: workloads
|
||||
hosted on top of the landing zone are out of scope for this operating model.'
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-02
|
||||
field: operations.change_process
|
||||
statement: Assumed operations.change_process is Changes go through a deployment
|
||||
pipeline with peer review, with explicit customer platform team approval required
|
||||
for all network changes.. Pipeline-driven changes with peer review, with customer
|
||||
platform team approval required for network changes per REQ-01.
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-03
|
||||
field: service_management.tooling
|
||||
statement: Assumed service_management.tooling is Google Cloud operations suite and
|
||||
native Cloud provider tooling, with no separate external ITSM system.. Default
|
||||
native GCP operations tooling used as no external ITSM was specified.
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: metadata.source
|
||||
prompt: What is metadata.source?
|
||||
severity: LOW
|
||||
- field: solution.build.customer_owned
|
||||
prompt: Which parts of the build does the customer or their supplier own?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: supplied
|
||||
commercial.monthly_run_budget: supplied
|
||||
compliance.frameworks: supplied
|
||||
engagement.kind: supplied
|
||||
intent.business_outcomes: supplied
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: supplied
|
||||
intent.statement: supplied
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: supplied
|
||||
metadata.revision: unknown
|
||||
metadata.source: unknown
|
||||
operations.availability_hours: supplied
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: supplied
|
||||
organisation.existing_teams: supplied
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: supplied
|
||||
service_levels.recovery_time_hours: supplied
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: unknown
|
||||
solution.build.duration_days: supplied
|
||||
solution.cloud_provider: supplied
|
||||
solution.conditions: supplied
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: supplied
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 20
|
||||
answered: 0
|
||||
assumed: 3
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
@@ -0,0 +1,53 @@
|
||||
# A fictional benchmark: a small landing zone run as a shared service. No customer's
|
||||
# data is in it. Complete enough to run with nobody to ask.
|
||||
metadata:
|
||||
customer_case: bench-landing-zone-shared
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: |
|
||||
We want our landing zone run as a shared service from go-live. A provider should
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
over changes to the network.
|
||||
business_outcomes:
|
||||
- {id: BO-1, outcome: New payment products reach customers in weeks rather than months., target: "A change reaches production within a day of approval."}
|
||||
- {id: BO-2, outcome: Payments are never unavailable for long., target: "Restored within 4 hours."}
|
||||
- {id: BO-3, outcome: We keep the platform engineers we hire.}
|
||||
requirements:
|
||||
- {id: REQ-01, statement: Our platform team approves every change to the network.}
|
||||
- {id: REQ-02, statement: We receive a monthly report of service levels and cost.}
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- {id: S-1, name: Hub network and interconnect, kind: network, product: Cloud Interconnect}
|
||||
- {id: S-2, name: Audit log store, kind: storage, product: Cloud Storage}
|
||||
- {id: S-3, name: Deployment pipeline, kind: pipeline, product: Cloud Build}
|
||||
- {id: S-4, name: Encryption keys, kind: keys, product: Cloud KMS}
|
||||
conditions:
|
||||
- {id: K-1, "on": [S-1], condition: The platform is available at least 99.9% of each month.}
|
||||
- {id: K-2, "on": [S-2], condition: Audit logs cannot be deleted for seven years.}
|
||||
- {id: K-3, "on": [S-4], condition: Encryption keys are rotated every 90 days.}
|
||||
build:
|
||||
duration_days: 36
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: decide
|
||||
sourcing:
|
||||
model: shared
|
||||
delivery_countries: [GB, PL, IN]
|
||||
organisation:
|
||||
existing_teams:
|
||||
- {name: Platform team, party: customer, hours: business, country: GB}
|
||||
service_management:
|
||||
tooling: decide
|
||||
service_levels:
|
||||
priority_1_response_minutes: 15
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks: [DORA]
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: 60000
|
||||
run:
|
||||
pre_approved: true
|
||||
@@ -0,0 +1,10 @@
|
||||
# Intent 2: bench-landing-zone-shared
|
||||
|
||||
- Recorded: 2026-10-21T20:54:36+00:00
|
||||
- Execution: `case-01-landing-zone-shared-r2`
|
||||
|
||||
## What the customer wants
|
||||
|
||||
We want our landing zone run as a shared service from go-live. A provider should
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
over changes to the network.
|
||||
@@ -0,0 +1,199 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: bench-landing-zone-shared
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: ask
|
||||
status: BASELINE_LOCKED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We want our landing zone run as a shared service from go-live. A provider
|
||||
should
|
||||
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
|
||||
over changes to the network.
|
||||
|
||||
'
|
||||
requirements:
|
||||
- id: REQ-01
|
||||
statement: Our platform team approves every change to the network.
|
||||
- id: REQ-02
|
||||
statement: We receive a monthly report of service levels and cost.
|
||||
business_outcomes:
|
||||
- id: BO-1
|
||||
outcome: New payment products reach customers in weeks rather than months.
|
||||
target: A change reaches production within a day of approval.
|
||||
- id: BO-2
|
||||
outcome: Payments are never unavailable for long.
|
||||
target: Restored within 4 hours.
|
||||
- id: BO-3
|
||||
outcome: We keep the platform engineers we hire.
|
||||
exclusions:
|
||||
- Application workloads deployed onto the platform foundation
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Hub network and interconnect
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
- id: S-2
|
||||
name: Audit log store
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
- id: S-3
|
||||
name: Deployment pipeline
|
||||
kind: pipeline
|
||||
product: Cloud Build
|
||||
- id: S-4
|
||||
name: Encryption keys
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
condition: The platform is available at least 99.9% of each month.
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-2
|
||||
condition: Audit logs cannot be deleted for seven years.
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-4
|
||||
condition: Encryption keys are rotated every 90 days.
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned: ask
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Changes go through automated pipelines with peer review; changes
|
||||
affecting the hub network require customer platform team approval prior to release.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: shared
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams:
|
||||
- name: Platform team
|
||||
party: customer
|
||||
hours: business
|
||||
country: GB
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: Google Cloud native operations tooling (Cloud Monitoring and Cloud Logging),
|
||||
with no separate service management system.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 15
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: 60000
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.exclusions
|
||||
statement: Assumed intent.exclusions is ['Application workloads deployed onto the
|
||||
platform foundation']. Workloads deployed onto the platform foundation are excluded;
|
||||
operations is confined to the landing zone foundation itself.
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-02
|
||||
field: operations.change_process
|
||||
statement: Assumed operations.change_process is Changes go through automated pipelines
|
||||
with peer review; changes affecting the hub network require customer platform
|
||||
team approval prior to release.. Changes follow automated deployment pipelines
|
||||
with peer review, with network changes requiring explicit customer platform team
|
||||
approval per REQ-01.
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-03
|
||||
field: service_management.tooling
|
||||
statement: Assumed service_management.tooling is Google Cloud native operations
|
||||
tooling (Cloud Monitoring and Cloud Logging), with no separate service management
|
||||
system.. Defaulting to GCP native operations tooling with no separate ITSM system.
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: metadata.source
|
||||
prompt: What is metadata.source?
|
||||
severity: LOW
|
||||
- field: solution.build.customer_owned
|
||||
prompt: Which parts of the build does the customer or their supplier own?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: supplied
|
||||
commercial.monthly_run_budget: supplied
|
||||
compliance.frameworks: supplied
|
||||
engagement.kind: supplied
|
||||
intent.business_outcomes: supplied
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: supplied
|
||||
intent.statement: supplied
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: supplied
|
||||
metadata.revision: unknown
|
||||
metadata.source: unknown
|
||||
operations.availability_hours: supplied
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: supplied
|
||||
organisation.existing_teams: supplied
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: supplied
|
||||
service_levels.recovery_time_hours: supplied
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: unknown
|
||||
solution.build.duration_days: supplied
|
||||
solution.cloud_provider: supplied
|
||||
solution.conditions: supplied
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: supplied
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 20
|
||||
answered: 0
|
||||
assumed: 3
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
@@ -0,0 +1,53 @@
|
||||
# A fictional benchmark: a small landing zone run as a shared service. No customer's
|
||||
# data is in it. Complete enough to run with nobody to ask.
|
||||
metadata:
|
||||
customer_case: bench-landing-zone-shared
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: |
|
||||
We want our landing zone run as a shared service from go-live. A provider should
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
over changes to the network.
|
||||
business_outcomes:
|
||||
- {id: BO-1, outcome: New payment products reach customers in weeks rather than months., target: "A change reaches production within a day of approval."}
|
||||
- {id: BO-2, outcome: Payments are never unavailable for long., target: "Restored within 4 hours."}
|
||||
- {id: BO-3, outcome: We keep the platform engineers we hire.}
|
||||
requirements:
|
||||
- {id: REQ-01, statement: Our platform team approves every change to the network.}
|
||||
- {id: REQ-02, statement: We receive a monthly report of service levels and cost.}
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- {id: S-1, name: Hub network and interconnect, kind: network, product: Cloud Interconnect}
|
||||
- {id: S-2, name: Audit log store, kind: storage, product: Cloud Storage}
|
||||
- {id: S-3, name: Deployment pipeline, kind: pipeline, product: Cloud Build}
|
||||
- {id: S-4, name: Encryption keys, kind: keys, product: Cloud KMS}
|
||||
conditions:
|
||||
- {id: K-1, "on": [S-1], condition: The platform is available at least 99.9% of each month.}
|
||||
- {id: K-2, "on": [S-2], condition: Audit logs cannot be deleted for seven years.}
|
||||
- {id: K-3, "on": [S-4], condition: Encryption keys are rotated every 90 days.}
|
||||
build:
|
||||
duration_days: 36
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: decide
|
||||
sourcing:
|
||||
model: shared
|
||||
delivery_countries: [GB, PL, IN]
|
||||
organisation:
|
||||
existing_teams:
|
||||
- {name: Platform team, party: customer, hours: business, country: GB}
|
||||
service_management:
|
||||
tooling: decide
|
||||
service_levels:
|
||||
priority_1_response_minutes: 15
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks: [DORA]
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: 60000
|
||||
run:
|
||||
pre_approved: true
|
||||
@@ -0,0 +1,10 @@
|
||||
# Intent 3: bench-landing-zone-shared
|
||||
|
||||
- Recorded: 2026-10-21T21:11:10+00:00
|
||||
- Execution: `case-01-landing-zone-shared-r3`
|
||||
|
||||
## What the customer wants
|
||||
|
||||
We want our landing zone run as a shared service from go-live. A provider should
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
over changes to the network.
|
||||
@@ -0,0 +1,201 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: bench-landing-zone-shared
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: ask
|
||||
status: BASELINE_LOCKED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We want our landing zone run as a shared service from go-live. A provider
|
||||
should
|
||||
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
|
||||
over changes to the network.
|
||||
|
||||
'
|
||||
requirements:
|
||||
- id: REQ-01
|
||||
statement: Our platform team approves every change to the network.
|
||||
- id: REQ-02
|
||||
statement: We receive a monthly report of service levels and cost.
|
||||
business_outcomes:
|
||||
- id: BO-1
|
||||
outcome: New payment products reach customers in weeks rather than months.
|
||||
target: A change reaches production within a day of approval.
|
||||
- id: BO-2
|
||||
outcome: Payments are never unavailable for long.
|
||||
target: Restored within 4 hours.
|
||||
- id: BO-3
|
||||
outcome: We keep the platform engineers we hire.
|
||||
exclusions:
|
||||
- Workload applications running on the platform foundation
|
||||
- Network change approvals (retained by customer platform team)
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Hub network and interconnect
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
- id: S-2
|
||||
name: Audit log store
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
- id: S-3
|
||||
name: Deployment pipeline
|
||||
kind: pipeline
|
||||
product: Cloud Build
|
||||
- id: S-4
|
||||
name: Encryption keys
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
condition: The platform is available at least 99.9% of each month.
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-2
|
||||
condition: Audit logs cannot be deleted for seven years.
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-4
|
||||
condition: Encryption keys are rotated every 90 days.
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned: ask
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Changes go through a deployment pipeline with peer review, with
|
||||
network changes requiring customer platform team approval.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: shared
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams:
|
||||
- name: Platform team
|
||||
party: customer
|
||||
hours: business
|
||||
country: GB
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: The Cloud provider's own operations tooling, with no separate system.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 15
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: 60000
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.exclusions
|
||||
statement: 'Assumed intent.exclusions is [''Workload applications running on the
|
||||
platform foundation'', ''Network change approvals (retained by customer platform
|
||||
team)'']. Assumed from the platform foundation scope: workload applications running
|
||||
on the platform are out of scope, and customer platform team retains network change
|
||||
approvals.'
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-02
|
||||
field: operations.change_process
|
||||
statement: 'Assumed operations.change_process is Changes go through a deployment
|
||||
pipeline with peer review, with network changes requiring customer platform team
|
||||
approval.. Catalogue default adapted to customer requirement REQ-01: changes go
|
||||
through deployment pipelines with peer review, with customer platform team retaining
|
||||
approval over network changes.'
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-03
|
||||
field: service_management.tooling
|
||||
statement: 'Assumed service_management.tooling is The Cloud provider''s own operations
|
||||
tooling, with no separate system.. Catalogue default: Cloud provider''s native
|
||||
operations tooling with no separate system.'
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: metadata.source
|
||||
prompt: What is metadata.source?
|
||||
severity: LOW
|
||||
- field: solution.build.customer_owned
|
||||
prompt: Which parts of the build does the customer or their supplier own?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: supplied
|
||||
commercial.monthly_run_budget: supplied
|
||||
compliance.frameworks: supplied
|
||||
engagement.kind: supplied
|
||||
intent.business_outcomes: supplied
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: supplied
|
||||
intent.statement: supplied
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: supplied
|
||||
metadata.revision: unknown
|
||||
metadata.source: unknown
|
||||
operations.availability_hours: supplied
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: supplied
|
||||
organisation.existing_teams: supplied
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: supplied
|
||||
service_levels.recovery_time_hours: supplied
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: unknown
|
||||
solution.build.duration_days: supplied
|
||||
solution.cloud_provider: supplied
|
||||
solution.conditions: supplied
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: supplied
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 20
|
||||
answered: 0
|
||||
assumed: 3
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
@@ -0,0 +1,53 @@
|
||||
# A fictional benchmark: a small landing zone run as a shared service. No customer's
|
||||
# data is in it. Complete enough to run with nobody to ask.
|
||||
metadata:
|
||||
customer_case: bench-landing-zone-shared
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: |
|
||||
We want our landing zone run as a shared service from go-live. A provider should
|
||||
respond to faults at every hour, and our own platform team keeps the final say
|
||||
over changes to the network.
|
||||
business_outcomes:
|
||||
- {id: BO-1, outcome: New payment products reach customers in weeks rather than months., target: "A change reaches production within a day of approval."}
|
||||
- {id: BO-2, outcome: Payments are never unavailable for long., target: "Restored within 4 hours."}
|
||||
- {id: BO-3, outcome: We keep the platform engineers we hire.}
|
||||
requirements:
|
||||
- {id: REQ-01, statement: Our platform team approves every change to the network.}
|
||||
- {id: REQ-02, statement: We receive a monthly report of service levels and cost.}
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- {id: S-1, name: Hub network and interconnect, kind: network, product: Cloud Interconnect}
|
||||
- {id: S-2, name: Audit log store, kind: storage, product: Cloud Storage}
|
||||
- {id: S-3, name: Deployment pipeline, kind: pipeline, product: Cloud Build}
|
||||
- {id: S-4, name: Encryption keys, kind: keys, product: Cloud KMS}
|
||||
conditions:
|
||||
- {id: K-1, "on": [S-1], condition: The platform is available at least 99.9% of each month.}
|
||||
- {id: K-2, "on": [S-2], condition: Audit logs cannot be deleted for seven years.}
|
||||
- {id: K-3, "on": [S-4], condition: Encryption keys are rotated every 90 days.}
|
||||
build:
|
||||
duration_days: 36
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: decide
|
||||
sourcing:
|
||||
model: shared
|
||||
delivery_countries: [GB, PL, IN]
|
||||
organisation:
|
||||
existing_teams:
|
||||
- {name: Platform team, party: customer, hours: business, country: GB}
|
||||
service_management:
|
||||
tooling: decide
|
||||
service_levels:
|
||||
priority_1_response_minutes: 15
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks: [DORA]
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: 60000
|
||||
run:
|
||||
pre_approved: true
|
||||
@@ -0,0 +1,53 @@
|
||||
{
|
||||
"customer_case": "bench-landing-zone-shared",
|
||||
"intents": [
|
||||
{
|
||||
"version": 1,
|
||||
"recorded_at": "2026-10-21T20:36:25+00:00",
|
||||
"statement": "intent/001.md",
|
||||
"workflow_request": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.",
|
||||
"execution_id": "case-01-landing-zone-shared-r1",
|
||||
"session_id": "9fe31b7a-c779-4d34-bcee-cc2e36533a1d",
|
||||
"status": "completed",
|
||||
"execution": "executions/case-01-landing-zone-shared-r1",
|
||||
"baseline": null,
|
||||
"scope": {
|
||||
"completed": "intent/001.scope.completed.yaml",
|
||||
"supplied": "intent/001.scope.yaml"
|
||||
},
|
||||
"sources": null
|
||||
},
|
||||
{
|
||||
"version": 2,
|
||||
"recorded_at": "2026-10-21T20:54:36+00:00",
|
||||
"statement": "intent/002.md",
|
||||
"workflow_request": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.",
|
||||
"execution_id": "case-01-landing-zone-shared-r2",
|
||||
"session_id": "c7cf78e8-2f3b-4f26-bd2f-850de41fe1d6",
|
||||
"status": "completed",
|
||||
"execution": "executions/case-01-landing-zone-shared-r2",
|
||||
"baseline": null,
|
||||
"scope": {
|
||||
"completed": "intent/002.scope.completed.yaml",
|
||||
"supplied": "intent/002.scope.yaml"
|
||||
},
|
||||
"sources": null
|
||||
},
|
||||
{
|
||||
"version": 3,
|
||||
"recorded_at": "2026-10-21T21:11:10+00:00",
|
||||
"statement": "intent/003.md",
|
||||
"workflow_request": "We want our landing zone run as a shared service from go-live. A provider should\nrespond to faults at every hour, and our own platform team keeps the final say\nover changes to the network.",
|
||||
"execution_id": "case-01-landing-zone-shared-r3",
|
||||
"session_id": "d0d953a6-5254-4646-8d70-7fd6139f1afc",
|
||||
"status": "completed",
|
||||
"execution": "executions/case-01-landing-zone-shared-r3",
|
||||
"baseline": null,
|
||||
"scope": {
|
||||
"completed": "intent/003.scope.completed.yaml",
|
||||
"supplied": "intent/003.scope.yaml"
|
||||
},
|
||||
"sources": null
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,191 @@
|
||||
[
|
||||
{
|
||||
"id": "C-1",
|
||||
"catalogue": "incident-management",
|
||||
"serves": ["OR-1", "OR-6"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 40,
|
||||
"basis": "Triage of 24x7 operational alerts and managing approximately 2 priority incidents per month across platform infrastructure."
|
||||
},
|
||||
{
|
||||
"id": "C-2",
|
||||
"catalogue": "monitoring-and-alerting",
|
||||
"serves": ["OR-6", "OR-15"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 30,
|
||||
"basis": "Tuning Cloud Monitoring alert thresholds, maintaining dashboards, and integrating telemetry into operational systems."
|
||||
},
|
||||
{
|
||||
"id": "C-3",
|
||||
"catalogue": "problem-management",
|
||||
"serves": ["OR-2"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 16,
|
||||
"basis": "Investigating root causes for platform anomalies and driving permanent problem resolution."
|
||||
},
|
||||
{
|
||||
"id": "C-4",
|
||||
"catalogue": "service-request-fulfilment",
|
||||
"serves": ["OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Fulfilling non-standard operational requests and provisioning adjustments for core payments engine ingestion."
|
||||
},
|
||||
{
|
||||
"id": "C-5",
|
||||
"catalogue": "change-enablement",
|
||||
"serves": ["OR-12"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Reviewing automated pipeline outputs and conducting peer approvals for all infrastructure-as-code changes."
|
||||
},
|
||||
{
|
||||
"id": "C-6",
|
||||
"catalogue": "release-and-deployment",
|
||||
"serves": ["OR-10", "OR-12"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 30,
|
||||
"basis": "Managing automated GitHub Actions pipelines, resolving deployment failures, and optimizing deployments and resource placements to maximize carbon-free energy utilization."
|
||||
},
|
||||
{
|
||||
"id": "C-7",
|
||||
"catalogue": "configuration-management",
|
||||
"serves": ["OR-16"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 12,
|
||||
"basis": "Tracking infrastructure state files and ensuring alignment with PCI-DSS v4.0 baseline configurations."
|
||||
},
|
||||
{
|
||||
"id": "C-8",
|
||||
"catalogue": "backup-and-recovery",
|
||||
"serves": ["OR-4"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Monitoring automated backup routines and performing scheduled restore tests to ensure 1-hour RPO."
|
||||
},
|
||||
{
|
||||
"id": "C-9",
|
||||
"catalogue": "service-continuity",
|
||||
"serves": ["OR-3", "OR-7"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Maintaining the active warm standby in europe-west1 to immediately receive failover traffic, and governing 4-hour disaster recovery procedures."
|
||||
},
|
||||
{
|
||||
"id": "C-10",
|
||||
"catalogue": "capacity-and-performance",
|
||||
"serves": ["OR-5"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 12,
|
||||
"basis": "Reviewing 10Gbps interconnect bandwidth and ensuring deterministic low-latency performance for payment transactions."
|
||||
},
|
||||
{
|
||||
"id": "C-11",
|
||||
"catalogue": "access-management",
|
||||
"serves": ["OR-11", "OR-14"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 24,
|
||||
"basis": "Rightsizing permissions based on IAM Recommender findings and controlling access from approved delivery countries."
|
||||
},
|
||||
{
|
||||
"id": "C-12",
|
||||
"catalogue": "vulnerability-and-patch-management",
|
||||
"serves": ["OR-16"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 24,
|
||||
"basis": "Scanning platform foundation assets and applying security patches to maintain compliance standards."
|
||||
},
|
||||
{
|
||||
"id": "C-13",
|
||||
"catalogue": "security-monitoring-and-response",
|
||||
"serves": ["OR-1", "OR-6"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 40,
|
||||
"basis": "Continuous 24x7 monitoring of security events and rapid response to security-related alerts."
|
||||
},
|
||||
{
|
||||
"id": "C-14",
|
||||
"catalogue": "cost-management",
|
||||
"serves": ["OR-9"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 12,
|
||||
"basis": "Tracking Google Cloud spend against budget allocations and escalating anomalies."
|
||||
},
|
||||
{
|
||||
"id": "C-15",
|
||||
"catalogue": "service-level-management",
|
||||
"serves": ["OR-2"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Compiling reports on 99.9% availability and incident response times."
|
||||
},
|
||||
{
|
||||
"id": "C-16",
|
||||
"catalogue": "platform-product-management",
|
||||
"serves": ["OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 16,
|
||||
"basis": "Managing the foundation roadmap to ensure readiness for core payments engine workload ingestion."
|
||||
},
|
||||
{
|
||||
"id": "C-17",
|
||||
"catalogue": "self-service-and-golden-paths",
|
||||
"serves": ["OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Building reusable templates and automated paved paths for payment engine teams."
|
||||
},
|
||||
{
|
||||
"id": "C-18",
|
||||
"catalogue": "enablement",
|
||||
"serves": ["OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Assisting development teams through pairing and documentation to rapidly adopt the platform within the 10-week window."
|
||||
},
|
||||
{
|
||||
"id": "C-19",
|
||||
"catalogue": "delivery-and-developer-experience-measurement",
|
||||
"serves": ["OR-12"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Collecting DORA metrics for pipeline performance, and evaluating developer productivity and wellbeing to determine friction feedback."
|
||||
},
|
||||
{
|
||||
"id": "C-20",
|
||||
"catalogue": "supplier-management",
|
||||
"serves": ["OR-13"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 8,
|
||||
"basis": "Managing relationships and service reviews with Google Cloud and interconnect carriers."
|
||||
},
|
||||
{
|
||||
"id": "C-21",
|
||||
"catalogue": "regulatory-evidence",
|
||||
"serves": ["OR-16", "OR-17"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 16,
|
||||
"basis": "Collating compliance evidence for DORA, PCI-DSS v4.0, ISO27001, and guaranteeing UK/EU data residency records."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,146 @@
|
||||
{
|
||||
"customer_case": "case-08-landing-zone",
|
||||
"execution_id": "case-02-from-architecture-r1",
|
||||
"session_id": "bc30257a-ff81-4114-86b9-83afd8a8ae5b",
|
||||
"intent_version": 1,
|
||||
"workflow_request": "We are a UK-regulated payment platform expanding into Google Cloud. We need an\nenterprise-grade landing zone ready in under 10 weeks to support our core payments\nengine. All payment processing must comply with DORA and PCI-DSS v4.0. We have\nexisting on-premises systems that require private, low-latency connectivity over a\n10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and\nGitHub Actions for our delivery pipelines. Security requires that all egress\ntraffic flows through centralised inspection appliances before touching the public\ninternet, and customer data must be encrypted with keys we control.",
|
||||
"baseline": null,
|
||||
"overlay_skills": {},
|
||||
"options": {},
|
||||
"sources": {
|
||||
"execution.json": {
|
||||
"sha256": "8bf269deffc8e4bce474bd8d66959c03b04de01dc137eefaf96ead74b46a5a45",
|
||||
"digested": true
|
||||
},
|
||||
"scope.json": {
|
||||
"sha256": "57dc28ab7397f514ef0e83b292fc2165554ac2b516775c973f4965765a9e905f",
|
||||
"digested": true
|
||||
},
|
||||
"requirements.json": {
|
||||
"sha256": "5aecbef9eaea254fb5123bcc1d107b4a7b7d4d45d60d940464d1fde690d2973d",
|
||||
"digested": true
|
||||
},
|
||||
"recommendations.json": {
|
||||
"sha256": "95958b1a107705280d65c9d088bba57352d1f9fa8e67e89b2b3379f78d91cd24",
|
||||
"digested": true
|
||||
},
|
||||
"components.json": {
|
||||
"sha256": "49e47dbfa90a85d086711eb2ba66370c145f13fd3cd3595c1df1366224db392c",
|
||||
"digested": true
|
||||
},
|
||||
"products.json": {
|
||||
"sha256": "75d51cba319f83000e6f85277b0fb21a7ec02faabac332c5d1800c8f512136db",
|
||||
"digested": true
|
||||
},
|
||||
"target-architecture.json": {
|
||||
"sha256": "40879607aaa7041103d8f4d3ba804df8751d2159aa0ce0977d7d821d35f7608b",
|
||||
"digested": true
|
||||
},
|
||||
"verdicts.json": {
|
||||
"sha256": "75e17da790266e94a6775d90857a9b503cacd62fd55c92be2d7a3435de301853",
|
||||
"digested": true
|
||||
},
|
||||
"work-breakdown.json": {
|
||||
"sha256": "057fd1b0ecd6350a6f9f6101b712a61e78fc10d758a67e785a1dca7e1e674dc3",
|
||||
"digested": true
|
||||
}
|
||||
},
|
||||
"scope": {
|
||||
"status": "APPROVED",
|
||||
"readiness": {
|
||||
"supplied": 3,
|
||||
"answered": 0,
|
||||
"assumed": 7,
|
||||
"unknown": 10,
|
||||
"not_applicable": 0,
|
||||
"digested": 13
|
||||
}
|
||||
},
|
||||
"status": "completed_with_warnings",
|
||||
"warnings": [
|
||||
"target_operating_model has reached its revision limit (3). Requested change: OC-2 failed: The check requires the secondary region to be 'continuously maintained' as an active warm standby, but Capability C-9 is configured for 'business' hours, meaning maintenance cannot be continuous (24x7). C-9 should be 24x7 or another capability should provide continuous maintenance.; OC-4 failed: The check requires validation within 10 weeks, but Capability C-16 covers managing the roadmap without explicitly mentioning the 10-week requirement (which is instead mentioned in C-18). C-16 must mention the 10-week validation or the check mapped to C-18.; OC-9 failed: The check requires that expenditure does not exceed target allocations without 'documented operational sign-off', but Capability C-14 only mentions 'escalating anomalies' and does not explicitly guarantee documented sign-off.; OC-12 failed: The check requires identity permissions to be 'continuously reviewed', but Capability C-11 operates only during 'business' hours, meaning reviews cannot be continuous. C-11 must be 24x7.; OC-17 failed: The check requires verifiable alignment with DORA, PCI-DSS v4.0, and ISO 27001. Capability C-7 only ensures alignment with PCI-DSS v4.0 baseline configurations, completely missing DORA and ISO 27001 controls.. Ask the user whether to revise it again or accept it as it stands."
|
||||
],
|
||||
"risks": [],
|
||||
"assessment": null,
|
||||
"phases": {
|
||||
"scoping": "approved",
|
||||
"operational_requirements": "approved",
|
||||
"operating_model_design": "approved",
|
||||
"validation": "open",
|
||||
"packaging": "open"
|
||||
},
|
||||
"final_document": null,
|
||||
"changes": null,
|
||||
"deliverables": {
|
||||
"operating_scope": {
|
||||
"document": "deliverables/operating_scope.md",
|
||||
"attachments": [
|
||||
"scope.json",
|
||||
"scope.yaml"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operational_requirements": {
|
||||
"document": "deliverables/operational_requirements.md",
|
||||
"attachments": [
|
||||
"operational-requirements.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"capability_model": {
|
||||
"document": "deliverables/capability_model.md",
|
||||
"attachments": [
|
||||
"capabilities.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"target_operating_model": {
|
||||
"document": "deliverables/target_operating_model.md",
|
||||
"attachments": [
|
||||
"findings.json",
|
||||
"organisation.mmd",
|
||||
"staffing.json",
|
||||
"target-operating-model.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"validation_results": {
|
||||
"document": "deliverables/validation_results.md",
|
||||
"attachments": [
|
||||
"scenarios.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
}
|
||||
},
|
||||
"files": [
|
||||
"capabilities.json",
|
||||
"deliverables/capability_model.md",
|
||||
"deliverables/operating_scope.md",
|
||||
"deliverables/operational_requirements.md",
|
||||
"deliverables/target_operating_model.md",
|
||||
"deliverables/validation_results.md",
|
||||
"findings.json",
|
||||
"operational-requirements.json",
|
||||
"organisation.mmd",
|
||||
"scenarios.json",
|
||||
"scope.json",
|
||||
"scope.yaml",
|
||||
"staffing.json",
|
||||
"target-operating-model.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"staffing": {
|
||||
"people": 11.7,
|
||||
"cost_per_month": 73863,
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
}
|
||||
},
|
||||
"findings": [],
|
||||
"change_request": null,
|
||||
"capability_sources_verified": false
|
||||
}
|
||||
@@ -0,0 +1 @@
|
||||
[]
|
||||
@@ -0,0 +1,143 @@
|
||||
[
|
||||
{
|
||||
"id": "OR-1",
|
||||
"kind": "service_level",
|
||||
"statement": "A Priority 1 incident on any platform foundation item is acknowledged within 30 minutes (assumed in service_levels.priority_1_response_minutes), at any hour of any day.",
|
||||
"source": [
|
||||
"service_levels.priority_1_response_minutes",
|
||||
"operations.support_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-2",
|
||||
"kind": "service_level",
|
||||
"statement": "The platform foundation infrastructure maintains measured monthly availability of at least 99.9% across 24x7 operating hours.",
|
||||
"source": [
|
||||
"K-5",
|
||||
"operations.availability_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-3",
|
||||
"kind": "service_level",
|
||||
"statement": "Platform service restoration following a disaster declaration achieves a recovery time objective (RTO) of 4 hours (assumed in service_levels.recovery_time_hours).",
|
||||
"source": [
|
||||
"K-6",
|
||||
"service_levels.recovery_time_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-4",
|
||||
"kind": "service_level",
|
||||
"statement": "Disaster recovery processes achieve a recovery point objective (RPO) of no more than 1 hour of platform data or configuration loss.",
|
||||
"source": [
|
||||
"K-7"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-5",
|
||||
"kind": "service_level",
|
||||
"statement": "The dedicated private hybrid connectivity gateway maintains deterministic low-latency network performance suitable for real-time payment transaction processing.",
|
||||
"source": [
|
||||
"K-10"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-6",
|
||||
"kind": "process",
|
||||
"statement": "Platform alert notifications trigger operational incident workflows on a 24x7 continuous basis.",
|
||||
"source": [
|
||||
"K-8",
|
||||
"operations.support_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-7",
|
||||
"kind": "process",
|
||||
"statement": "The secondary cloud region in europe-west1 is continuously maintained as an active warm standby ready to receive operational failover traffic.",
|
||||
"source": [
|
||||
"K-2"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-8",
|
||||
"kind": "process",
|
||||
"statement": "The platform foundation is fully provisioned, hardened, and validated for core payments engine workload ingestion within 10 weeks.",
|
||||
"source": [
|
||||
"K-4"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-9",
|
||||
"kind": "process",
|
||||
"statement": "Monthly cloud foundation operational expenditure is monitored against budget allocations and does not exceed target allocations without documented operational sign-off.",
|
||||
"source": [
|
||||
"K-9"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-10",
|
||||
"kind": "process",
|
||||
"statement": "Operational deployments and platform resource placements optimize carbon-free energy utilization based on regional carbon-free energy scores.",
|
||||
"source": [
|
||||
"K-11"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-11",
|
||||
"kind": "process",
|
||||
"statement": "Platform identity permissions and access roles are continuously reviewed and rightsized based on automated recommender findings.",
|
||||
"source": [
|
||||
"K-12"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-12",
|
||||
"kind": "process",
|
||||
"statement": "Infrastructure changes are deployed via automated pipelines with automated linting, security scans, and peer approvals without a manual change advisory board (assumed in operations.change_process).",
|
||||
"source": [
|
||||
"operations.change_process"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-13",
|
||||
"kind": "organisation",
|
||||
"statement": "Platform foundation operations, ongoing maintenance, and incident remediation are delivered under a provider-operated sourcing model.",
|
||||
"source": [
|
||||
"sourcing.model"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-14",
|
||||
"kind": "organisation",
|
||||
"statement": "Platform operational delivery and administrative access are restricted to personnel operating from the United Kingdom (GB), Poland (PL), and India (IN).",
|
||||
"source": [
|
||||
"sourcing.delivery_countries"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-15",
|
||||
"kind": "tooling",
|
||||
"statement": "Platform operational telemetry, logging, and incident alerting are integrated into operational event management systems (assumed in service_management.tooling).",
|
||||
"source": [
|
||||
"service_management.tooling"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-16",
|
||||
"kind": "compliance",
|
||||
"statement": "The platform foundation configuration maintains verifiable alignment with DORA operational resiliency guidelines, PCI-DSS v4.0 perimeter isolation standards, and ISO 27001 controls during operational reviews and external audits.",
|
||||
"source": [
|
||||
"K-1",
|
||||
"compliance.frameworks"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-17",
|
||||
"kind": "compliance",
|
||||
"statement": "Data residency is guaranteed within the United Kingdom and European Union for all platform foundation resources and stored data.",
|
||||
"source": [
|
||||
"K-3"
|
||||
]
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,23 @@
|
||||
flowchart TB
|
||||
subgraph P_1["Customer (customer)"]
|
||||
subgraph T_2["Core Payments Engine Team (stream-aligned team)"]
|
||||
R_8["Core Payments Team Lead<br/>GB, senior, business"]
|
||||
end
|
||||
end
|
||||
subgraph P_2["Platform Provider (provider)"]
|
||||
subgraph T_1["Platform Foundation Team (platform team)"]
|
||||
R_1["Platform Foundation Lead<br/>GB, lead, business"]
|
||||
R_2["Platform Engineer<br/>PL, senior, business"]
|
||||
R_3["Platform SRE<br/>IN, engineer, 24x7"]
|
||||
R_6["Platform Product Manager<br/>GB, senior, business"]
|
||||
R_7["Compliance Analyst<br/>PL, senior, business"]
|
||||
end
|
||||
subgraph T_3["Platform Security Team (complicated-subsystem team)"]
|
||||
R_4["Security Operations Analyst<br/>PL, senior, 24x7"]
|
||||
end
|
||||
subgraph T_4["Developer Enablement Team (enabling team)"]
|
||||
R_5["Developer Enabler<br/>GB, senior, business"]
|
||||
end
|
||||
end
|
||||
T_2 -- "x-as-a-service" --> T_1
|
||||
T_4 -- "facilitating" --> T_2
|
||||
@@ -0,0 +1,219 @@
|
||||
[
|
||||
{
|
||||
"id": "SC-fault-S-1",
|
||||
"scenario": "Resource Hierarchy and Environment Boundary Manager (S-1) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-1",
|
||||
"scenario": "Resource Hierarchy and Environment Boundary Manager (S-1) must be changed.",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-2",
|
||||
"scenario": "Dedicated Private Hybrid Connectivity Gateway (S-2) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-2",
|
||||
"scenario": "Dedicated Private Hybrid Connectivity Gateway (S-2) must be changed.",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-3",
|
||||
"scenario": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-3",
|
||||
"scenario": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) must be changed.",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-4",
|
||||
"scenario": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-4",
|
||||
"scenario": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) must be changed.",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-5",
|
||||
"scenario": "Automated Infrastructure Orchestration and Deployment Engine (S-5) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-5",
|
||||
"passes": true,
|
||||
"path": "Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-5",
|
||||
"scenario": "Automated Infrastructure Orchestration and Deployment Engine (S-5) must be changed.",
|
||||
"about": "S-5",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-6",
|
||||
"scenario": "Federated Identity and Role Governance Authority (S-6) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-6",
|
||||
"passes": true,
|
||||
"path": "Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-6",
|
||||
"scenario": "Federated Identity and Role Governance Authority (S-6) must be changed.",
|
||||
"about": "S-6",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-7",
|
||||
"scenario": "Cryptographic Key Lifecycle and Encryption Controller (S-7) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-7",
|
||||
"passes": true,
|
||||
"path": "Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-7",
|
||||
"scenario": "Cryptographic Key Lifecycle and Encryption Controller (S-7) must be changed.",
|
||||
"about": "S-7",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-8",
|
||||
"scenario": "Platform Telemetry and Operational Alerting Engine (S-8) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-8",
|
||||
"passes": true,
|
||||
"path": "Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-8",
|
||||
"scenario": "Platform Telemetry and Operational Alerting Engine (S-8) must be changed.",
|
||||
"about": "S-8",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-9",
|
||||
"scenario": "Financial Governance and Budget Enforcement Monitor (S-9) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-9",
|
||||
"passes": true,
|
||||
"path": "Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-9",
|
||||
"scenario": "Financial Governance and Budget Enforcement Monitor (S-9) must be changed.",
|
||||
"about": "S-9",
|
||||
"passes": true,
|
||||
"path": "Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-1",
|
||||
"scenario": "Condition K-1 must be shown to hold: The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.",
|
||||
"about": "K-1",
|
||||
"passes": true,
|
||||
"path": "Check OC-17 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-2",
|
||||
"scenario": "Condition K-2 must be shown to hold: The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic.",
|
||||
"about": "K-2",
|
||||
"passes": true,
|
||||
"path": "Check OC-2 on C-9 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-3",
|
||||
"scenario": "Condition K-3 must be shown to hold: Data residency is guaranteed within the United Kingdom and European Union.",
|
||||
"about": "K-3",
|
||||
"passes": true,
|
||||
"path": "Check OC-3 on C-21 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-4",
|
||||
"scenario": "Condition K-4 must be shown to hold: Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks.",
|
||||
"about": "K-4",
|
||||
"passes": true,
|
||||
"path": "Check OC-4 on C-16 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-5",
|
||||
"scenario": "Condition K-5 must be shown to hold: Platform foundation infrastructure maintains measured monthly availability of at least 99.9%.",
|
||||
"about": "K-5",
|
||||
"passes": true,
|
||||
"path": "Check OC-5 on C-15 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-6",
|
||||
"scenario": "Condition K-6 must be shown to hold: Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours.",
|
||||
"about": "K-6",
|
||||
"passes": true,
|
||||
"path": "Check OC-6 on C-9 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-7",
|
||||
"scenario": "Condition K-7 must be shown to hold: Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour.",
|
||||
"about": "K-7",
|
||||
"passes": true,
|
||||
"path": "Check OC-7 on C-8 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-8",
|
||||
"scenario": "Condition K-8 must be shown to hold: Alert notifications trigger operational incident workflows for the 24/7 central platform operations team.",
|
||||
"about": "K-8",
|
||||
"passes": true,
|
||||
"path": "Check OC-8 on C-2 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-9",
|
||||
"scenario": "Condition K-9 must be shown to hold: Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off.",
|
||||
"about": "K-9",
|
||||
"passes": true,
|
||||
"path": "Check OC-9 on C-14 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-10",
|
||||
"scenario": "Condition K-10 must be shown to hold: Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing.",
|
||||
"about": "K-10",
|
||||
"passes": true,
|
||||
"path": "Check OC-10 on C-10 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-11",
|
||||
"scenario": "Condition K-11 must be shown to hold: Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores.",
|
||||
"about": "K-11",
|
||||
"passes": true,
|
||||
"path": "Check OC-11 on C-6 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-12",
|
||||
"scenario": "Condition K-12 must be shown to hold: Permissions are continuously rightsized based on IAM Recommender findings.",
|
||||
"about": "K-12",
|
||||
"passes": true,
|
||||
"path": "Check OC-12 on C-11 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-party-P-2",
|
||||
"scenario": "Platform Provider cannot be reached.",
|
||||
"about": "P-2",
|
||||
"passes": true,
|
||||
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,396 @@
|
||||
{
|
||||
"kind": "platform_foundation",
|
||||
"stated": {
|
||||
"engagement": {
|
||||
"kind": "platform_foundation"
|
||||
},
|
||||
"intent": {
|
||||
"statement": "We are a UK-regulated payment platform expanding into Google Cloud. We need an\nenterprise-grade landing zone ready in under 10 weeks to support our core payments\nengine. All payment processing must comply with DORA and PCI-DSS v4.0. We have\nexisting on-premises systems that require private, low-latency connectivity over a\n10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and\nGitHub Actions for our delivery pipelines. Security requires that all egress\ntraffic flows through centralised inspection appliances before touching the public\ninternet, and customer data must be encrypted with keys we control."
|
||||
},
|
||||
"solution": {
|
||||
"cloud_provider": "gcp",
|
||||
"items": [
|
||||
{
|
||||
"id": "S-1",
|
||||
"name": "Resource Hierarchy and Environment Boundary Manager",
|
||||
"kind": "governance",
|
||||
"product": "Resource Manager",
|
||||
"source_ref": "C-1",
|
||||
"elements": [
|
||||
"E-1",
|
||||
"E-2",
|
||||
"E-3",
|
||||
"E-4",
|
||||
"E-5",
|
||||
"E-6",
|
||||
"E-7",
|
||||
"E-8",
|
||||
"E-9",
|
||||
"E-10",
|
||||
"E-34",
|
||||
"E-35",
|
||||
"E-36",
|
||||
"E-37",
|
||||
"E-38",
|
||||
"E-50",
|
||||
"E-51",
|
||||
"E-55",
|
||||
"E-60"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-2",
|
||||
"name": "Dedicated Private Hybrid Connectivity Gateway",
|
||||
"kind": "network",
|
||||
"product": "Cloud Interconnect",
|
||||
"source_ref": "C-2",
|
||||
"elements": [
|
||||
"E-11",
|
||||
"E-12",
|
||||
"E-13",
|
||||
"E-14",
|
||||
"E-56",
|
||||
"E-57"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-3",
|
||||
"name": "Centralised Outbound Traffic Inspection and Egress Boundary",
|
||||
"kind": "service",
|
||||
"product": "Palo Alto Networks VM-Series",
|
||||
"source_ref": "C-3",
|
||||
"elements": [
|
||||
"E-15",
|
||||
"E-16",
|
||||
"E-17",
|
||||
"E-18",
|
||||
"E-19",
|
||||
"E-20",
|
||||
"E-47",
|
||||
"E-48",
|
||||
"E-53"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-4",
|
||||
"name": "Centralised Immutable Audit Event and Compliance Log Repository",
|
||||
"kind": "storage",
|
||||
"product": "Cloud Storage",
|
||||
"source_ref": "C-4",
|
||||
"elements": [
|
||||
"E-21",
|
||||
"E-22",
|
||||
"E-39"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-5",
|
||||
"name": "Automated Infrastructure Orchestration and Deployment Engine",
|
||||
"kind": "service",
|
||||
"product": "GitHub Actions",
|
||||
"source_ref": "C-5",
|
||||
"elements": [
|
||||
"E-42",
|
||||
"E-43"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-6",
|
||||
"name": "Federated Identity and Role Governance Authority",
|
||||
"kind": "identity",
|
||||
"product": "IAM Workload Identity Federation",
|
||||
"source_ref": "C-6",
|
||||
"elements": [
|
||||
"E-23",
|
||||
"E-24",
|
||||
"E-25",
|
||||
"E-26",
|
||||
"E-27",
|
||||
"E-45"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-7",
|
||||
"name": "Cryptographic Key Lifecycle and Encryption Controller",
|
||||
"kind": "keys",
|
||||
"product": "Cloud KMS",
|
||||
"source_ref": "C-7",
|
||||
"elements": [
|
||||
"E-28",
|
||||
"E-29",
|
||||
"E-30",
|
||||
"E-31",
|
||||
"E-49",
|
||||
"E-58",
|
||||
"E-59"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-8",
|
||||
"name": "Platform Telemetry and Operational Alerting Engine",
|
||||
"kind": "observability",
|
||||
"product": "Cloud Monitoring",
|
||||
"source_ref": "C-8",
|
||||
"elements": [
|
||||
"E-32",
|
||||
"E-40",
|
||||
"E-41",
|
||||
"E-44",
|
||||
"E-52"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-9",
|
||||
"name": "Financial Governance and Budget Enforcement Monitor",
|
||||
"kind": "billing",
|
||||
"product": "Cloud Billing",
|
||||
"source_ref": "C-9",
|
||||
"elements": [
|
||||
"E-33",
|
||||
"E-46",
|
||||
"E-54"
|
||||
]
|
||||
}
|
||||
],
|
||||
"conditions": [
|
||||
{
|
||||
"id": "K-1",
|
||||
"on": [
|
||||
"S-1",
|
||||
"S-4",
|
||||
"S-7"
|
||||
],
|
||||
"condition": "The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.",
|
||||
"source_ref": "NFR-8"
|
||||
},
|
||||
{
|
||||
"id": "K-2",
|
||||
"on": [
|
||||
"S-1"
|
||||
],
|
||||
"condition": "The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic.",
|
||||
"source_ref": "NFR-9"
|
||||
},
|
||||
{
|
||||
"id": "K-3",
|
||||
"on": [
|
||||
"S-1"
|
||||
],
|
||||
"condition": "Data residency is guaranteed within the United Kingdom and European Union.",
|
||||
"source_ref": "NFR-9"
|
||||
},
|
||||
{
|
||||
"id": "K-4",
|
||||
"on": [
|
||||
"S-5"
|
||||
],
|
||||
"condition": "Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks.",
|
||||
"source_ref": "NFR-10"
|
||||
},
|
||||
{
|
||||
"id": "K-5",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Platform foundation infrastructure maintains measured monthly availability of at least 99.9%.",
|
||||
"source_ref": "NFR-11"
|
||||
},
|
||||
{
|
||||
"id": "K-6",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours.",
|
||||
"source_ref": "NFR-11"
|
||||
},
|
||||
{
|
||||
"id": "K-7",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour.",
|
||||
"source_ref": "NFR-11"
|
||||
},
|
||||
{
|
||||
"id": "K-8",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Alert notifications trigger operational incident workflows for the 24/7 central platform operations team.",
|
||||
"source_ref": "NFR-12"
|
||||
},
|
||||
{
|
||||
"id": "K-9",
|
||||
"on": [
|
||||
"S-9"
|
||||
],
|
||||
"condition": "Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off.",
|
||||
"source_ref": "NFR-13"
|
||||
},
|
||||
{
|
||||
"id": "K-10",
|
||||
"on": [
|
||||
"S-2"
|
||||
],
|
||||
"condition": "Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing.",
|
||||
"source_ref": "NFR-14"
|
||||
},
|
||||
{
|
||||
"id": "K-11",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores.",
|
||||
"source_ref": "NFR-15"
|
||||
},
|
||||
{
|
||||
"id": "K-12",
|
||||
"on": [
|
||||
"S-6"
|
||||
],
|
||||
"condition": "Permissions are continuously rightsized based on IAM Recommender findings.",
|
||||
"source_ref": "DR-OP-3"
|
||||
}
|
||||
],
|
||||
"build": {
|
||||
"duration_days": 36,
|
||||
"customer_owned": [
|
||||
"Order and provision the Interconnect carrier circuits"
|
||||
]
|
||||
}
|
||||
},
|
||||
"operations": {
|
||||
"support_hours": "24x7",
|
||||
"availability_hours": "24x7"
|
||||
},
|
||||
"sourcing": {
|
||||
"model": "provider_operated",
|
||||
"delivery_countries": [
|
||||
"GB",
|
||||
"PL",
|
||||
"IN"
|
||||
]
|
||||
},
|
||||
"compliance": {
|
||||
"frameworks": [
|
||||
"DORA",
|
||||
"ISO27001",
|
||||
"PCI_DSS_v4"
|
||||
]
|
||||
},
|
||||
"commercial": {
|
||||
"currency": "GBP"
|
||||
}
|
||||
},
|
||||
"binding": [
|
||||
"operations.support_hours",
|
||||
"sourcing.model",
|
||||
"sourcing.delivery_countries"
|
||||
],
|
||||
"assumed": [
|
||||
{
|
||||
"field": "intent.business_outcomes",
|
||||
"value": [
|
||||
{
|
||||
"outcome": "Enterprise landing zone ready to ingest core payments engine workloads within 10 weeks",
|
||||
"id": "BO-1",
|
||||
"target": "Workload ready within 10 weeks"
|
||||
},
|
||||
{
|
||||
"outcome": "Continuous operational resilience and regulatory compliance under DORA and PCI-DSS v4.0",
|
||||
"target": "Zero audit non-conformances and >= 99.9% platform availability",
|
||||
"id": "BO-2"
|
||||
},
|
||||
{
|
||||
"id": "BO-3",
|
||||
"target": "Continuous 10Gbps dedicated interconnect availability with centralized inspection",
|
||||
"outcome": "Secure, deterministic low-latency hybrid connectivity supporting real-time payment transactions"
|
||||
}
|
||||
],
|
||||
"why": "Derived from the workflow request specifying rapid 10-week landing zone delivery, DORA and PCI-DSS v4.0 compliance, and deterministic hybrid connectivity."
|
||||
},
|
||||
{
|
||||
"field": "intent.exclusions",
|
||||
"value": [
|
||||
"Application workload code, payment engine business logic, and database-level transaction data management",
|
||||
"Physical data centre hosting, hardware maintenance, and on-premises network infrastructure",
|
||||
"Corporate Entra ID user identity lifecycle management outside Google Cloud federation"
|
||||
],
|
||||
"why": "Assumed from platform foundation scope: excludes application-level payment processing logic, physical on-premises hardware maintenance, and end-user identity administration beyond cloud federation."
|
||||
},
|
||||
{
|
||||
"field": "operations.change_process",
|
||||
"value": "Automated infrastructure-as-code deployment via GitHub Actions pipelines with automated linting, security scans, and peer review approvals without a manual CAB.",
|
||||
"why": "Assumed based on catalogue default and stated use of GitHub Actions delivery pipelines."
|
||||
},
|
||||
{
|
||||
"field": "organisation.existing_teams",
|
||||
"value": [],
|
||||
"why": "Assumed catalogue default: no existing customer operational roles carry forward into the platform foundation; operations are delivered under a provider-operated model."
|
||||
},
|
||||
{
|
||||
"field": "service_management.tooling",
|
||||
"value": "Google Cloud operations suite (Cloud Monitoring, Cloud Logging) integrated with provider operational incident and alerting management systems.",
|
||||
"why": "Assumed based on catalogue default and solution item S-8 (Cloud Monitoring)."
|
||||
},
|
||||
{
|
||||
"field": "service_levels.priority_1_response_minutes",
|
||||
"value": 30,
|
||||
"why": "Assumed catalogue default of 30 minutes for critical incident response."
|
||||
},
|
||||
{
|
||||
"field": "service_levels.recovery_time_hours",
|
||||
"value": 4,
|
||||
"why": "Derived from solution condition K-6 specifying a disaster recovery RTO of 4 hours, matching catalogue default."
|
||||
}
|
||||
],
|
||||
"to_decide": [],
|
||||
"to_ask": [
|
||||
{
|
||||
"field": "metadata.client_name",
|
||||
"prompt": "What is metadata.client_name?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.author",
|
||||
"prompt": "What is metadata.author?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.revision",
|
||||
"prompt": "What is metadata.revision?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "intent.requirements",
|
||||
"prompt": "Which requirements for operations has the customer stated outright?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "solution.inherited_risks",
|
||||
"prompt": "What is already known to be unverified or at risk in the solution?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "operations.monitoring",
|
||||
"prompt": "Which monitoring and alerting is already in place or required?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "organisation.headcount_limit",
|
||||
"prompt": "Is there a limit on the number of people operating this?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "commercial.monthly_run_budget",
|
||||
"prompt": "Is there a monthly budget for operating this, in that currency?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "transition.go_live_date",
|
||||
"prompt": "When must the solution be in operation?",
|
||||
"severity": "LOW"
|
||||
}
|
||||
],
|
||||
"not_applicable": []
|
||||
}
|
||||
@@ -0,0 +1,406 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: case-08-landing-zone
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: architecture:case-08-landing-zone-185426
|
||||
status: APPROVED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We are a UK-regulated payment platform expanding into Google Cloud.
|
||||
We need an
|
||||
|
||||
enterprise-grade landing zone ready in under 10 weeks to support our core payments
|
||||
|
||||
engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have
|
||||
|
||||
existing on-premises systems that require private, low-latency connectivity over
|
||||
a
|
||||
|
||||
10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and
|
||||
|
||||
GitHub Actions for our delivery pipelines. Security requires that all egress
|
||||
|
||||
traffic flows through centralised inspection appliances before touching the public
|
||||
|
||||
internet, and customer data must be encrypted with keys we control.'
|
||||
requirements: ask
|
||||
business_outcomes:
|
||||
- outcome: Enterprise landing zone ready to ingest core payments engine workloads
|
||||
within 10 weeks
|
||||
id: BO-1
|
||||
target: Workload ready within 10 weeks
|
||||
- outcome: Continuous operational resilience and regulatory compliance under DORA
|
||||
and PCI-DSS v4.0
|
||||
target: Zero audit non-conformances and >= 99.9% platform availability
|
||||
id: BO-2
|
||||
- id: BO-3
|
||||
target: Continuous 10Gbps dedicated interconnect availability with centralized
|
||||
inspection
|
||||
outcome: Secure, deterministic low-latency hybrid connectivity supporting real-time
|
||||
payment transactions
|
||||
exclusions:
|
||||
- Application workload code, payment engine business logic, and database-level transaction
|
||||
data management
|
||||
- Physical data centre hosting, hardware maintenance, and on-premises network infrastructure
|
||||
- Corporate Entra ID user identity lifecycle management outside Google Cloud federation
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Resource Hierarchy and Environment Boundary Manager
|
||||
kind: governance
|
||||
product: Resource Manager
|
||||
source_ref: C-1
|
||||
elements:
|
||||
- E-1
|
||||
- E-2
|
||||
- E-3
|
||||
- E-4
|
||||
- E-5
|
||||
- E-6
|
||||
- E-7
|
||||
- E-8
|
||||
- E-9
|
||||
- E-10
|
||||
- E-34
|
||||
- E-35
|
||||
- E-36
|
||||
- E-37
|
||||
- E-38
|
||||
- E-50
|
||||
- E-51
|
||||
- E-55
|
||||
- E-60
|
||||
- id: S-2
|
||||
name: Dedicated Private Hybrid Connectivity Gateway
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
source_ref: C-2
|
||||
elements:
|
||||
- E-11
|
||||
- E-12
|
||||
- E-13
|
||||
- E-14
|
||||
- E-56
|
||||
- E-57
|
||||
- id: S-3
|
||||
name: Centralised Outbound Traffic Inspection and Egress Boundary
|
||||
kind: service
|
||||
product: Palo Alto Networks VM-Series
|
||||
source_ref: C-3
|
||||
elements:
|
||||
- E-15
|
||||
- E-16
|
||||
- E-17
|
||||
- E-18
|
||||
- E-19
|
||||
- E-20
|
||||
- E-47
|
||||
- E-48
|
||||
- E-53
|
||||
- id: S-4
|
||||
name: Centralised Immutable Audit Event and Compliance Log Repository
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
source_ref: C-4
|
||||
elements:
|
||||
- E-21
|
||||
- E-22
|
||||
- E-39
|
||||
- id: S-5
|
||||
name: Automated Infrastructure Orchestration and Deployment Engine
|
||||
kind: service
|
||||
product: GitHub Actions
|
||||
source_ref: C-5
|
||||
elements:
|
||||
- E-42
|
||||
- E-43
|
||||
- id: S-6
|
||||
name: Federated Identity and Role Governance Authority
|
||||
kind: identity
|
||||
product: IAM Workload Identity Federation
|
||||
source_ref: C-6
|
||||
elements:
|
||||
- E-23
|
||||
- E-24
|
||||
- E-25
|
||||
- E-26
|
||||
- E-27
|
||||
- E-45
|
||||
- id: S-7
|
||||
name: Cryptographic Key Lifecycle and Encryption Controller
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
source_ref: C-7
|
||||
elements:
|
||||
- E-28
|
||||
- E-29
|
||||
- E-30
|
||||
- E-31
|
||||
- E-49
|
||||
- E-58
|
||||
- E-59
|
||||
- id: S-8
|
||||
name: Platform Telemetry and Operational Alerting Engine
|
||||
kind: observability
|
||||
product: Cloud Monitoring
|
||||
source_ref: C-8
|
||||
elements:
|
||||
- E-32
|
||||
- E-40
|
||||
- E-41
|
||||
- E-44
|
||||
- E-52
|
||||
- id: S-9
|
||||
name: Financial Governance and Budget Enforcement Monitor
|
||||
kind: billing
|
||||
product: Cloud Billing
|
||||
source_ref: C-9
|
||||
elements:
|
||||
- E-33
|
||||
- E-46
|
||||
- E-54
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
- S-4
|
||||
- S-7
|
||||
condition: The landing zone configuration aligns with DORA operational resiliency
|
||||
guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.
|
||||
source_ref: NFR-8
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-1
|
||||
condition: The secondary region in europe-west1 operates as a warm standby ready
|
||||
to receive failover traffic.
|
||||
source_ref: NFR-9
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-1
|
||||
condition: Data residency is guaranteed within the United Kingdom and European
|
||||
Union.
|
||||
source_ref: NFR-9
|
||||
- id: K-4
|
||||
'on':
|
||||
- S-5
|
||||
condition: Platform foundation is fully provisioned and validated for core payments
|
||||
engine workload ingestion within 10 weeks.
|
||||
source_ref: NFR-10
|
||||
- id: K-5
|
||||
'on':
|
||||
- S-8
|
||||
condition: Platform foundation infrastructure maintains measured monthly availability
|
||||
of at least 99.9%.
|
||||
source_ref: NFR-11
|
||||
- id: K-6
|
||||
'on':
|
||||
- S-8
|
||||
condition: Disaster recovery activation achieves a recovery time objective (RTO)
|
||||
of 4 hours.
|
||||
source_ref: NFR-11
|
||||
- id: K-7
|
||||
'on':
|
||||
- S-8
|
||||
condition: Disaster recovery processes achieve a recovery point objective (RPO)
|
||||
of 1 hour.
|
||||
source_ref: NFR-11
|
||||
- id: K-8
|
||||
'on':
|
||||
- S-8
|
||||
condition: Alert notifications trigger operational incident workflows for the
|
||||
24/7 central platform operations team.
|
||||
source_ref: NFR-12
|
||||
- id: K-9
|
||||
'on':
|
||||
- S-9
|
||||
condition: Monthly cloud foundation expenditure does not exceed the target allocation
|
||||
without operational sign-off.
|
||||
source_ref: NFR-13
|
||||
- id: K-10
|
||||
'on':
|
||||
- S-2
|
||||
condition: Hybrid connection provides deterministic low latency suitable for real-time
|
||||
payment transaction processing.
|
||||
source_ref: NFR-14
|
||||
- id: K-11
|
||||
'on':
|
||||
- S-8
|
||||
condition: Deployments optimize carbon-free energy utilization based on Google
|
||||
Cloud regional CFE scores.
|
||||
source_ref: NFR-15
|
||||
- id: K-12
|
||||
'on':
|
||||
- S-6
|
||||
condition: Permissions are continuously rightsized based on IAM Recommender findings.
|
||||
source_ref: DR-OP-3
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned:
|
||||
- Order and provision the Interconnect carrier circuits
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Automated infrastructure-as-code deployment via GitHub Actions pipelines
|
||||
with automated linting, security scans, and peer review approvals without a manual
|
||||
CAB.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: provider_operated
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams: []
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: Google Cloud operations suite (Cloud Monitoring, Cloud Logging) integrated
|
||||
with provider operational incident and alerting management systems.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 30
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
- ISO27001
|
||||
- PCI_DSS_v4
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: ask
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.business_outcomes
|
||||
statement: 'Assumed intent.business_outcomes is [{''outcome'': ''Enterprise landing
|
||||
zone ready to ingest core payments engine workloads within 10 weeks'', ''id'':
|
||||
''BO-1'', ''target'': ''Workload ready within 10 weeks''}, {''outcome'': ''Continuous
|
||||
operational resilience and regulatory compliance under DORA and PCI-DSS v4.0'',
|
||||
''target'': ''Zero audit non-conformances and >= 99.9% platform availability'',
|
||||
''id'': ''BO-2''}, {''id'': ''BO-3'', ''target'': ''Continuous 10Gbps dedicated
|
||||
interconnect availability with centralized inspection'', ''outcome'': ''Secure,
|
||||
deterministic low-latency hybrid connectivity supporting real-time payment transactions''}].
|
||||
Derived from the workflow request specifying rapid 10-week landing zone delivery,
|
||||
DORA and PCI-DSS v4.0 compliance, and deterministic hybrid connectivity.'
|
||||
impact_if_invalid: Changes what is measured, and what each measure is for.
|
||||
- id: ASSUMP-02
|
||||
field: intent.exclusions
|
||||
statement: 'Assumed intent.exclusions is [''Application workload code, payment engine
|
||||
business logic, and database-level transaction data management'', ''Physical data
|
||||
centre hosting, hardware maintenance, and on-premises network infrastructure'',
|
||||
''Corporate Entra ID user identity lifecycle management outside Google Cloud federation''].
|
||||
Assumed from platform foundation scope: excludes application-level payment processing
|
||||
logic, physical on-premises hardware maintenance, and end-user identity administration
|
||||
beyond cloud federation.'
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-03
|
||||
field: operations.change_process
|
||||
statement: Assumed operations.change_process is Automated infrastructure-as-code
|
||||
deployment via GitHub Actions pipelines with automated linting, security scans,
|
||||
and peer review approvals without a manual CAB.. Assumed based on catalogue default
|
||||
and stated use of GitHub Actions delivery pipelines.
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-04
|
||||
field: organisation.existing_teams
|
||||
statement: 'Assumed organisation.existing_teams is []. Assumed catalogue default:
|
||||
no existing customer operational roles carry forward into the platform foundation;
|
||||
operations are delivered under a provider-operated model.'
|
||||
impact_if_invalid: Changes which Roles are new and which are filled.
|
||||
- id: ASSUMP-05
|
||||
field: service_management.tooling
|
||||
statement: Assumed service_management.tooling is Google Cloud operations suite (Cloud
|
||||
Monitoring, Cloud Logging) integrated with provider operational incident and alerting
|
||||
management systems.. Assumed based on catalogue default and solution item S-8
|
||||
(Cloud Monitoring).
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
- id: ASSUMP-06
|
||||
field: service_levels.priority_1_response_minutes
|
||||
statement: Assumed service_levels.priority_1_response_minutes is 30. Assumed catalogue
|
||||
default of 30 minutes for critical incident response.
|
||||
impact_if_invalid: Changes on-call arrangements and staffing.
|
||||
- id: ASSUMP-07
|
||||
field: service_levels.recovery_time_hours
|
||||
statement: Assumed service_levels.recovery_time_hours is 4. Derived from solution
|
||||
condition K-6 specifying a disaster recovery RTO of 4 hours, matching catalogue
|
||||
default.
|
||||
impact_if_invalid: Changes continuity arrangements.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: intent.requirements
|
||||
prompt: Which requirements for operations has the customer stated outright?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: commercial.monthly_run_budget
|
||||
prompt: Is there a monthly budget for operating this, in that currency?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: digested
|
||||
commercial.monthly_run_budget: unknown
|
||||
compliance.frameworks: digested
|
||||
engagement.kind: digested
|
||||
intent.business_outcomes: assumed
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: unknown
|
||||
intent.statement: digested
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: digested
|
||||
metadata.revision: unknown
|
||||
metadata.source: digested
|
||||
operations.availability_hours: digested
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: digested
|
||||
organisation.existing_teams: assumed
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: assumed
|
||||
service_levels.recovery_time_hours: assumed
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: digested
|
||||
solution.build.duration_days: digested
|
||||
solution.cloud_provider: digested
|
||||
solution.conditions: digested
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: digested
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 3
|
||||
answered: 0
|
||||
assumed: 7
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
digested: 13
|
||||
@@ -0,0 +1,144 @@
|
||||
{
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
},
|
||||
"conversion": {
|
||||
"from": "USD",
|
||||
"rate": 0.79,
|
||||
"as_of": "2026-10-13"
|
||||
},
|
||||
"roles": [
|
||||
{
|
||||
"role": "R-1",
|
||||
"name": "Platform Foundation Lead",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Provider",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 30.0,
|
||||
"people": 0.2,
|
||||
"cost_per_month": 3318
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"name": "Platform Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Provider",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 160.0,
|
||||
"people": 1.1,
|
||||
"cost_per_month": 7268
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"name": "Platform SRE",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Provider",
|
||||
"country": "IN",
|
||||
"level": "engineer",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 70.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 17034
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"name": "Security Operations Analyst",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Provider",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 88.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 41640
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"name": "Developer Enabler",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Provider",
|
||||
"country": "GB",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 30.0,
|
||||
"people": 0.2,
|
||||
"cost_per_month": 2528
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"name": "Platform Product Manager",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Provider",
|
||||
"country": "GB",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 16.0,
|
||||
"people": 0.1,
|
||||
"cost_per_month": 1348
|
||||
},
|
||||
{
|
||||
"role": "R-7",
|
||||
"name": "Compliance Analyst",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Provider",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 16.0,
|
||||
"people": 0.1,
|
||||
"cost_per_month": 727
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"name": "Core Payments Team Lead",
|
||||
"party": "P-1",
|
||||
"party_name": "Customer",
|
||||
"country": "GB",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 0.0,
|
||||
"people": 0.0,
|
||||
"cost_per_month": null
|
||||
}
|
||||
],
|
||||
"people": 11.7,
|
||||
"cost_per_month": 73863,
|
||||
"by_party": {
|
||||
"P-2": 73863
|
||||
},
|
||||
"by_country": {
|
||||
"GB": 7194,
|
||||
"PL": 49635,
|
||||
"IN": 17034
|
||||
},
|
||||
"by_capability": {
|
||||
"C-14": 1327,
|
||||
"C-15": 1106,
|
||||
"C-20": 885,
|
||||
"C-3": 727,
|
||||
"C-4": 909,
|
||||
"C-5": 909,
|
||||
"C-6": 1363,
|
||||
"C-7": 545,
|
||||
"C-8": 454,
|
||||
"C-9": 909,
|
||||
"C-10": 545,
|
||||
"C-17": 909,
|
||||
"C-1": 9734,
|
||||
"C-2": 7300,
|
||||
"C-11": 11356,
|
||||
"C-12": 11356,
|
||||
"C-13": 18927,
|
||||
"C-18": 1685,
|
||||
"C-19": 843,
|
||||
"C-16": 1348,
|
||||
"C-21": 727
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,667 @@
|
||||
{
|
||||
"parties": [
|
||||
{
|
||||
"kind": "customer",
|
||||
"id": "P-1",
|
||||
"name": "Customer"
|
||||
},
|
||||
{
|
||||
"kind": "provider",
|
||||
"id": "P-2",
|
||||
"name": "Platform Provider"
|
||||
}
|
||||
],
|
||||
"teams": [
|
||||
{
|
||||
"party": "P-2",
|
||||
"id": "T-1",
|
||||
"name": "Platform Foundation Team",
|
||||
"type": "platform"
|
||||
},
|
||||
{
|
||||
"name": "Core Payments Engine Team",
|
||||
"type": "stream_aligned",
|
||||
"party": "P-1",
|
||||
"id": "T-2"
|
||||
},
|
||||
{
|
||||
"id": "T-3",
|
||||
"party": "P-2",
|
||||
"name": "Platform Security Team",
|
||||
"type": "complicated_subsystem"
|
||||
},
|
||||
{
|
||||
"party": "P-2",
|
||||
"name": "Developer Enablement Team",
|
||||
"type": "enabling",
|
||||
"id": "T-4"
|
||||
}
|
||||
],
|
||||
"roles": [
|
||||
{
|
||||
"hours": "business",
|
||||
"level": "lead",
|
||||
"name": "Platform Foundation Lead",
|
||||
"team": "T-1",
|
||||
"party": "P-2",
|
||||
"country": "GB",
|
||||
"id": "R-1"
|
||||
},
|
||||
{
|
||||
"country": "PL",
|
||||
"id": "R-2",
|
||||
"name": "Platform Engineer",
|
||||
"party": "P-2",
|
||||
"hours": "business",
|
||||
"level": "senior",
|
||||
"team": "T-1"
|
||||
},
|
||||
{
|
||||
"hours": "24x7",
|
||||
"level": "engineer",
|
||||
"id": "R-3",
|
||||
"country": "IN",
|
||||
"name": "Platform SRE",
|
||||
"team": "T-1",
|
||||
"party": "P-2"
|
||||
},
|
||||
{
|
||||
"country": "PL",
|
||||
"team": "T-3",
|
||||
"party": "P-2",
|
||||
"id": "R-4",
|
||||
"hours": "24x7",
|
||||
"level": "senior",
|
||||
"name": "Security Operations Analyst"
|
||||
},
|
||||
{
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"team": "T-4",
|
||||
"country": "GB",
|
||||
"party": "P-2",
|
||||
"name": "Developer Enabler",
|
||||
"id": "R-5"
|
||||
},
|
||||
{
|
||||
"party": "P-2",
|
||||
"team": "T-1",
|
||||
"country": "GB",
|
||||
"name": "Platform Product Manager",
|
||||
"hours": "business",
|
||||
"level": "senior",
|
||||
"id": "R-6"
|
||||
},
|
||||
{
|
||||
"hours": "business",
|
||||
"level": "senior",
|
||||
"name": "Compliance Analyst",
|
||||
"team": "T-1",
|
||||
"country": "PL",
|
||||
"party": "P-2",
|
||||
"id": "R-7"
|
||||
},
|
||||
{
|
||||
"id": "R-8",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"country": "GB",
|
||||
"name": "Core Payments Team Lead",
|
||||
"team": "T-2",
|
||||
"party": "P-1"
|
||||
}
|
||||
],
|
||||
"interactions": [
|
||||
{
|
||||
"id": "I-1",
|
||||
"mode": "x_as_a_service",
|
||||
"to": "T-1",
|
||||
"purpose": "Stream-aligned teams request environments and paved paths via the self-service foundation.",
|
||||
"from": "T-2"
|
||||
},
|
||||
{
|
||||
"mode": "facilitating",
|
||||
"to": "T-2",
|
||||
"purpose": "Enablement team assists core payments engineers to adopt the platform landing zone.",
|
||||
"id": "I-2",
|
||||
"from": "T-4"
|
||||
}
|
||||
],
|
||||
"measures": [
|
||||
{
|
||||
"outcome": "BO-1",
|
||||
"name": "Deployment Frequency",
|
||||
"framework": "dora-metrics",
|
||||
"id": "M-1",
|
||||
"layer": "outcome",
|
||||
"measured_by": "C-19",
|
||||
"target": "Daily"
|
||||
},
|
||||
{
|
||||
"name": "Satisfaction and Well-being",
|
||||
"id": "M-2",
|
||||
"outcome": "BO-1",
|
||||
"layer": "guardrail",
|
||||
"framework": "space-framework",
|
||||
"target": "High satisfaction scores",
|
||||
"measured_by": "C-19"
|
||||
},
|
||||
{
|
||||
"framework": "devex-framework",
|
||||
"name": "Cognitive Load",
|
||||
"measured_by": "C-19",
|
||||
"outcome": "BO-1",
|
||||
"layer": "leading",
|
||||
"target": "Low complexity ratings",
|
||||
"id": "M-3"
|
||||
},
|
||||
{
|
||||
"id": "M-4",
|
||||
"outcome": "BO-2",
|
||||
"target": "99.9%",
|
||||
"name": "Platform Availability",
|
||||
"layer": "service_level",
|
||||
"measured_by": "C-15"
|
||||
},
|
||||
{
|
||||
"outcome": "BO-2",
|
||||
"id": "M-5",
|
||||
"name": "Compliance Conformance",
|
||||
"measured_by": "C-21",
|
||||
"layer": "service_level",
|
||||
"target": "Zero non-conformances"
|
||||
},
|
||||
{
|
||||
"id": "M-6",
|
||||
"target": "Deterministic low-latency",
|
||||
"layer": "service_level",
|
||||
"name": "Network Latency",
|
||||
"measured_by": "C-10",
|
||||
"outcome": "BO-3"
|
||||
}
|
||||
],
|
||||
"responsibilities": [
|
||||
{
|
||||
"role": "R-1",
|
||||
"kind": "accountable",
|
||||
"capability": "C-1",
|
||||
"id": "RS-1"
|
||||
},
|
||||
{
|
||||
"id": "RS-2",
|
||||
"capability": "C-1",
|
||||
"kind": "responsible",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"capability": "C-1",
|
||||
"id": "RS-3"
|
||||
},
|
||||
{
|
||||
"id": "RS-4",
|
||||
"role": "R-1",
|
||||
"kind": "accountable",
|
||||
"capability": "C-2"
|
||||
},
|
||||
{
|
||||
"capability": "C-2",
|
||||
"id": "RS-5",
|
||||
"role": "R-3",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"capability": "C-2",
|
||||
"kind": "consulted",
|
||||
"role": "R-8",
|
||||
"id": "RS-6"
|
||||
},
|
||||
{
|
||||
"id": "RS-7",
|
||||
"role": "R-1",
|
||||
"kind": "accountable",
|
||||
"capability": "C-3"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-2",
|
||||
"capability": "C-3",
|
||||
"id": "RS-8"
|
||||
},
|
||||
{
|
||||
"capability": "C-3",
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-9"
|
||||
},
|
||||
{
|
||||
"id": "RS-10",
|
||||
"kind": "accountable",
|
||||
"role": "R-1",
|
||||
"capability": "C-4"
|
||||
},
|
||||
{
|
||||
"id": "RS-11",
|
||||
"capability": "C-4",
|
||||
"kind": "responsible",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-12",
|
||||
"capability": "C-4"
|
||||
},
|
||||
{
|
||||
"capability": "C-5",
|
||||
"id": "RS-13",
|
||||
"kind": "accountable",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"capability": "C-5",
|
||||
"id": "RS-14",
|
||||
"role": "R-2",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-15",
|
||||
"capability": "C-5"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"id": "RS-16",
|
||||
"capability": "C-6",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"capability": "C-6",
|
||||
"id": "RS-17",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"capability": "C-6",
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-18"
|
||||
},
|
||||
{
|
||||
"capability": "C-7",
|
||||
"kind": "accountable",
|
||||
"role": "R-1",
|
||||
"id": "RS-19"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"capability": "C-7",
|
||||
"kind": "responsible",
|
||||
"id": "RS-20"
|
||||
},
|
||||
{
|
||||
"id": "RS-21",
|
||||
"kind": "consulted",
|
||||
"capability": "C-7",
|
||||
"role": "R-8"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"id": "RS-22",
|
||||
"capability": "C-8",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"id": "RS-23",
|
||||
"role": "R-2",
|
||||
"kind": "responsible",
|
||||
"capability": "C-8"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"capability": "C-8",
|
||||
"id": "RS-24",
|
||||
"role": "R-8"
|
||||
},
|
||||
{
|
||||
"role": "R-1",
|
||||
"id": "RS-25",
|
||||
"capability": "C-9",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"id": "RS-26",
|
||||
"capability": "C-9",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"capability": "C-9",
|
||||
"kind": "consulted",
|
||||
"id": "RS-27"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-10",
|
||||
"id": "RS-28",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"capability": "C-10",
|
||||
"id": "RS-29",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"capability": "C-10",
|
||||
"id": "RS-30",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"id": "RS-31",
|
||||
"capability": "C-11",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"id": "RS-32",
|
||||
"role": "R-4",
|
||||
"capability": "C-11"
|
||||
},
|
||||
{
|
||||
"capability": "C-11",
|
||||
"kind": "consulted",
|
||||
"id": "RS-33",
|
||||
"role": "R-8"
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"capability": "C-12",
|
||||
"id": "RS-34",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"id": "RS-35",
|
||||
"capability": "C-12",
|
||||
"kind": "responsible",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"id": "RS-36",
|
||||
"kind": "consulted",
|
||||
"role": "R-8",
|
||||
"capability": "C-12"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"role": "R-4",
|
||||
"id": "RS-37",
|
||||
"capability": "C-13"
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"kind": "responsible",
|
||||
"capability": "C-13",
|
||||
"id": "RS-38"
|
||||
},
|
||||
{
|
||||
"id": "RS-39",
|
||||
"capability": "C-13",
|
||||
"kind": "consulted",
|
||||
"role": "R-8"
|
||||
},
|
||||
{
|
||||
"capability": "C-14",
|
||||
"role": "R-1",
|
||||
"kind": "accountable",
|
||||
"id": "RS-40"
|
||||
},
|
||||
{
|
||||
"id": "RS-41",
|
||||
"kind": "responsible",
|
||||
"role": "R-1",
|
||||
"capability": "C-14"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-8",
|
||||
"id": "RS-42",
|
||||
"capability": "C-14"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"role": "R-1",
|
||||
"capability": "C-15",
|
||||
"id": "RS-43"
|
||||
},
|
||||
{
|
||||
"id": "RS-44",
|
||||
"role": "R-1",
|
||||
"kind": "responsible",
|
||||
"capability": "C-15"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-8",
|
||||
"capability": "C-15",
|
||||
"id": "RS-45"
|
||||
},
|
||||
{
|
||||
"id": "RS-46",
|
||||
"capability": "C-16",
|
||||
"role": "R-6",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"kind": "responsible",
|
||||
"id": "RS-47",
|
||||
"capability": "C-16"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-48",
|
||||
"capability": "C-16"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"role": "R-6",
|
||||
"id": "RS-49",
|
||||
"capability": "C-17"
|
||||
},
|
||||
{
|
||||
"capability": "C-17",
|
||||
"id": "RS-50",
|
||||
"kind": "responsible",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"id": "RS-51",
|
||||
"capability": "C-17",
|
||||
"role": "R-8",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"id": "RS-52",
|
||||
"role": "R-6",
|
||||
"kind": "accountable",
|
||||
"capability": "C-18"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-5",
|
||||
"id": "RS-53",
|
||||
"capability": "C-18"
|
||||
},
|
||||
{
|
||||
"capability": "C-18",
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-54"
|
||||
},
|
||||
{
|
||||
"capability": "C-19",
|
||||
"kind": "accountable",
|
||||
"role": "R-6",
|
||||
"id": "RS-55"
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"kind": "responsible",
|
||||
"capability": "C-19",
|
||||
"id": "RS-56"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"capability": "C-19",
|
||||
"id": "RS-57"
|
||||
},
|
||||
{
|
||||
"id": "RS-58",
|
||||
"capability": "C-20",
|
||||
"kind": "accountable",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"id": "RS-59",
|
||||
"capability": "C-20",
|
||||
"role": "R-1",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"capability": "C-20",
|
||||
"id": "RS-60"
|
||||
},
|
||||
{
|
||||
"id": "RS-61",
|
||||
"capability": "C-21",
|
||||
"kind": "accountable",
|
||||
"role": "R-7"
|
||||
},
|
||||
{
|
||||
"capability": "C-21",
|
||||
"kind": "responsible",
|
||||
"role": "R-7",
|
||||
"id": "RS-62"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-8",
|
||||
"capability": "C-21",
|
||||
"id": "RS-63"
|
||||
}
|
||||
],
|
||||
"checks": [
|
||||
{
|
||||
"condition": "A Priority 1 incident on any platform foundation item is acknowledged within 30 minutes, at any hour of any day.",
|
||||
"id": "OC-1",
|
||||
"source": "OR-1",
|
||||
"on": "C-1"
|
||||
},
|
||||
{
|
||||
"condition": "The secondary region in europe-west1 is continuously maintained as an active warm standby ready to receive failover traffic.",
|
||||
"id": "OC-2",
|
||||
"on": "C-9",
|
||||
"source": "K-2"
|
||||
},
|
||||
{
|
||||
"on": "C-21",
|
||||
"source": "K-3",
|
||||
"id": "OC-3",
|
||||
"condition": "Data residency is guaranteed within the United Kingdom and European Union for all platform foundation resources and stored data, proven by continuous audit evidence."
|
||||
},
|
||||
{
|
||||
"id": "OC-4",
|
||||
"source": "K-4",
|
||||
"condition": "Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks.",
|
||||
"on": "C-16"
|
||||
},
|
||||
{
|
||||
"on": "C-15",
|
||||
"source": "K-5",
|
||||
"id": "OC-5",
|
||||
"condition": "Platform foundation infrastructure maintains measured monthly availability of at least 99.9%."
|
||||
},
|
||||
{
|
||||
"condition": "Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours.",
|
||||
"on": "C-9",
|
||||
"id": "OC-6",
|
||||
"source": "K-6"
|
||||
},
|
||||
{
|
||||
"id": "OC-7",
|
||||
"on": "C-8",
|
||||
"source": "K-7",
|
||||
"condition": "Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour."
|
||||
},
|
||||
{
|
||||
"condition": "Alert notifications trigger operational incident workflows for the 24/7 central platform operations team.",
|
||||
"id": "OC-8",
|
||||
"on": "C-2",
|
||||
"source": "K-8"
|
||||
},
|
||||
{
|
||||
"condition": "Monthly cloud foundation expenditure does not exceed target allocations without documented operational sign-off.",
|
||||
"on": "C-14",
|
||||
"source": "K-9",
|
||||
"id": "OC-9"
|
||||
},
|
||||
{
|
||||
"condition": "Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing.",
|
||||
"id": "OC-10",
|
||||
"on": "C-10",
|
||||
"source": "K-10"
|
||||
},
|
||||
{
|
||||
"condition": "Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores.",
|
||||
"on": "C-6",
|
||||
"id": "OC-11",
|
||||
"source": "K-11"
|
||||
},
|
||||
{
|
||||
"source": "K-12",
|
||||
"on": "C-11",
|
||||
"id": "OC-12",
|
||||
"condition": "Platform identity permissions and access roles are continuously reviewed and rightsized based on automated recommender findings."
|
||||
},
|
||||
{
|
||||
"on": "C-5",
|
||||
"source": "OR-12",
|
||||
"condition": "Infrastructure changes are deployed via automated pipelines with automated linting, security scans, and peer approvals without a manual change advisory board.",
|
||||
"id": "OC-13"
|
||||
},
|
||||
{
|
||||
"on": "R-1",
|
||||
"source": "OR-13",
|
||||
"id": "OC-14",
|
||||
"condition": "Platform foundation operations, ongoing maintenance, and incident remediation are delivered under a provider-operated sourcing model."
|
||||
},
|
||||
{
|
||||
"on": "R-3",
|
||||
"source": "OR-14",
|
||||
"id": "OC-15",
|
||||
"condition": "Platform operational delivery and administrative access are restricted to personnel operating from the United Kingdom (GB), Poland (PL), and India (IN)."
|
||||
},
|
||||
{
|
||||
"source": "OR-15",
|
||||
"id": "OC-16",
|
||||
"condition": "Platform operational telemetry, logging, and incident alerting are integrated into operational event management systems.",
|
||||
"on": "C-2"
|
||||
},
|
||||
{
|
||||
"id": "OC-17",
|
||||
"condition": "The platform foundation configuration maintains verifiable alignment with DORA operational resiliency guidelines, PCI-DSS v4.0 perimeter isolation standards, and ISO 27001 controls.",
|
||||
"source": "K-1",
|
||||
"on": "C-7"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,249 @@
|
||||
{
|
||||
"dry_run": {
|
||||
"verdict": "pass",
|
||||
"evidence": "31 of 31 scenario walk-throughs pass."
|
||||
},
|
||||
"checks": [
|
||||
{
|
||||
"check": "OC-1",
|
||||
"evidence": "Capability C-1 is staffed 24x7 and explicitly covers triage of 24x7 operational alerts and managing priority incidents, fully meeting the requirement.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "OC-2",
|
||||
"verdict": "fail",
|
||||
"evidence": "The check requires the secondary region to be 'continuously maintained' as an active warm standby, but Capability C-9 is configured for 'business' hours, meaning maintenance cannot be continuous (24x7). C-9 should be 24x7 or another capability should provide continuous maintenance."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-3",
|
||||
"evidence": "Capability C-21 explicitly covers guaranteeing UK/EU data residency records and collating compliance evidence."
|
||||
},
|
||||
{
|
||||
"verdict": "fail",
|
||||
"evidence": "The check requires validation within 10 weeks, but Capability C-16 covers managing the roadmap without explicitly mentioning the 10-week requirement (which is instead mentioned in C-18). C-16 must mention the 10-week validation or the check mapped to C-18.",
|
||||
"check": "OC-4"
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-15 covers compiling reports on 99.9% availability, meeting the condition.",
|
||||
"check": "OC-5",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-9 explicitly states it governs 4-hour disaster recovery procedures, meeting the 4-hour RTO condition.",
|
||||
"verdict": "pass",
|
||||
"check": "OC-6"
|
||||
},
|
||||
{
|
||||
"check": "OC-7",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-8 covers monitoring backups and performing restore tests to ensure a 1-hour RPO."
|
||||
},
|
||||
{
|
||||
"check": "OC-8",
|
||||
"evidence": "Capability C-2 is a 24x7 capability that tunes alerts and integrates telemetry into operational systems, handled by the 24x7 Platform SRE role.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "OC-9",
|
||||
"evidence": "The check requires that expenditure does not exceed target allocations without 'documented operational sign-off', but Capability C-14 only mentions 'escalating anomalies' and does not explicitly guarantee documented sign-off.",
|
||||
"verdict": "fail"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-10",
|
||||
"evidence": "Capability C-10 covers reviewing bandwidth and ensuring deterministic low-latency performance for payment transactions."
|
||||
},
|
||||
{
|
||||
"check": "OC-11",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-6 covers optimizing deployments and resource placements to maximize carbon-free energy utilization."
|
||||
},
|
||||
{
|
||||
"evidence": "The check requires identity permissions to be 'continuously reviewed', but Capability C-11 operates only during 'business' hours, meaning reviews cannot be continuous. C-11 must be 24x7.",
|
||||
"verdict": "fail",
|
||||
"check": "OC-12"
|
||||
},
|
||||
{
|
||||
"check": "OC-13",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-5 covers conducting peer approvals for automated infrastructure-as-code changes, supporting pipeline automated deployment."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Role R-1 (Platform Foundation Lead) is part of Party P-2 (Platform Provider), satisfying the provider-operated sourcing model.",
|
||||
"check": "OC-14"
|
||||
},
|
||||
{
|
||||
"check": "OC-15",
|
||||
"verdict": "pass",
|
||||
"evidence": "Role R-3 operates from India, and all other provider roles operate from GB and PL, meeting the delivery countries restriction."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-2 integrates telemetry into operational systems, aligning with the event management systems requirement.",
|
||||
"check": "OC-16"
|
||||
},
|
||||
{
|
||||
"check": "OC-17",
|
||||
"evidence": "The check requires verifiable alignment with DORA, PCI-DSS v4.0, and ISO 27001. Capability C-7 only ensures alignment with PCI-DSS v4.0 baseline configurations, completely missing DORA and ISO 27001 controls.",
|
||||
"verdict": "fail"
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Resource Hierarchy and Environment Boundary Manager (S-1) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Resource Hierarchy and Environment Boundary Manager (S-1) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Dedicated Private Hybrid Connectivity Gateway (S-2) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Dedicated Private Hybrid Connectivity Gateway (S-2) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Automated Infrastructure Orchestration and Deployment Engine (S-5) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Automated Infrastructure Orchestration and Deployment Engine (S-5) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-6",
|
||||
"verdict": "pass",
|
||||
"evidence": "Federated Identity and Role Governance Authority (S-6) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-6",
|
||||
"verdict": "pass",
|
||||
"evidence": "Federated Identity and Role Governance Authority (S-6) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-7",
|
||||
"verdict": "pass",
|
||||
"evidence": "Cryptographic Key Lifecycle and Encryption Controller (S-7) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-7",
|
||||
"verdict": "pass",
|
||||
"evidence": "Cryptographic Key Lifecycle and Encryption Controller (S-7) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Platform Telemetry and Operational Alerting Engine (S-8) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Platform Telemetry and Operational Alerting Engine (S-8) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-9",
|
||||
"verdict": "pass",
|
||||
"evidence": "Financial Governance and Budget Enforcement Monitor (S-9) fails at an hour faults are responded to (24x7). Platform SRE responds under C-1, and Platform Foundation Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-9",
|
||||
"verdict": "pass",
|
||||
"evidence": "Financial Governance and Budget Enforcement Monitor (S-9) must be changed. Platform Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-1 must be shown to hold: The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit. Check OC-17 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-2 must be shown to hold: The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic. Check OC-2 on C-9 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-3 must be shown to hold: Data residency is guaranteed within the United Kingdom and European Union. Check OC-3 on C-21 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-4 must be shown to hold: Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks. Check OC-4 on C-16 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-5 must be shown to hold: Platform foundation infrastructure maintains measured monthly availability of at least 99.9%. Check OC-5 on C-15 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-6",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-6 must be shown to hold: Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours. Check OC-6 on C-9 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-7",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-7 must be shown to hold: Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour. Check OC-7 on C-8 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-8 must be shown to hold: Alert notifications trigger operational incident workflows for the 24/7 central platform operations team. Check OC-8 on C-2 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-9",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-9 must be shown to hold: Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off. Check OC-9 on C-14 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-10",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-10 must be shown to hold: Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing. Check OC-10 on C-10 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-11",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-11 must be shown to hold: Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores. Check OC-11 on C-6 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-12",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-12 must be shown to hold: Permissions are continuously rightsized based on IAM Recommender findings. Check OC-12 on C-11 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-party-P-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Platform Provider cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
}
|
||||
],
|
||||
"proposed_additions": []
|
||||
}
|
||||
@@ -0,0 +1,191 @@
|
||||
[
|
||||
{
|
||||
"id": "C-1",
|
||||
"catalogue": "incident-management",
|
||||
"serves": ["OR-1"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 40,
|
||||
"basis": "24x7 coverage to acknowledge priority 1 incidents within 30 minutes, managing communications and resolution."
|
||||
},
|
||||
{
|
||||
"id": "C-2",
|
||||
"catalogue": "monitoring-and-alerting",
|
||||
"serves": ["OR-11", "OR-8", "OR-13"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 40,
|
||||
"basis": "Continuous tuning of alert thresholds and immediate 24x7 response to telemetry signals across the foundation."
|
||||
},
|
||||
{
|
||||
"id": "C-3",
|
||||
"catalogue": "problem-management",
|
||||
"serves": ["OR-1", "OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Investigating the root causes of major or recurring platform faults to prevent recurrence."
|
||||
},
|
||||
{
|
||||
"id": "C-4",
|
||||
"catalogue": "service-request-fulfilment",
|
||||
"serves": ["OR-2"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Handling non-fault operational requests, access adjustments, and configuration inquiries from application teams."
|
||||
},
|
||||
{
|
||||
"id": "C-5",
|
||||
"catalogue": "change-enablement",
|
||||
"serves": ["OR-4", "OR-7"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Ensuring automated policy validations and mandatory peer reviews are correctly enforced across CI/CD pipelines."
|
||||
},
|
||||
{
|
||||
"id": "C-6",
|
||||
"catalogue": "release-and-deployment",
|
||||
"serves": ["OR-7", "OR-14"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Managing GitHub Actions infrastructure-as-code delivery pipelines and executing rollbacks if required."
|
||||
},
|
||||
{
|
||||
"id": "C-7",
|
||||
"catalogue": "configuration-management",
|
||||
"serves": ["OR-4", "OR-6"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Maintaining version-controlled desired states and auditing actual environment configurations against data residency boundaries."
|
||||
},
|
||||
{
|
||||
"id": "C-8",
|
||||
"catalogue": "backup-and-recovery",
|
||||
"serves": ["OR-10"],
|
||||
"items": ["S-4", "S-7"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Ensuring compliance logs and cryptographic materials backups meet the 1-hour RPO and testing restores."
|
||||
},
|
||||
{
|
||||
"id": "C-9",
|
||||
"catalogue": "service-continuity",
|
||||
"serves": ["OR-5", "OR-9"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Maintaining runbooks for 4-hour RTO and verifying the europe-west1 secondary region warm standby readiness."
|
||||
},
|
||||
{
|
||||
"id": "C-10",
|
||||
"catalogue": "capacity-and-performance",
|
||||
"serves": ["OR-8", "OR-13", "OR-14"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Monitoring Interconnect latency and overall infrastructure capacity to maintain strict performance for payments processing and optimizing workload placements for CFE."
|
||||
},
|
||||
{
|
||||
"id": "C-11",
|
||||
"catalogue": "access-management",
|
||||
"serves": ["OR-15", "OR-3"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Executing continuous identity rightsizing based on automated findings and restricting access to approved delivery locations."
|
||||
},
|
||||
{
|
||||
"id": "C-12",
|
||||
"catalogue": "vulnerability-and-patch-management",
|
||||
"serves": ["OR-4"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Regular vulnerability scanning and patching of egress VMs and other resources to align with security standards."
|
||||
},
|
||||
{
|
||||
"id": "C-13",
|
||||
"catalogue": "security-monitoring-and-response",
|
||||
"serves": ["OR-4"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 40,
|
||||
"basis": "Continuous detection and response to security events from egress inspection and identity telemetry."
|
||||
},
|
||||
{
|
||||
"id": "C-14",
|
||||
"catalogue": "cost-management",
|
||||
"serves": ["OR-12"],
|
||||
"items": ["S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Monitoring foundational spend against agreed budgets and seeking sign-offs for anomalies."
|
||||
},
|
||||
{
|
||||
"id": "C-15",
|
||||
"catalogue": "service-level-management",
|
||||
"serves": ["OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Reporting monthly on the 99.9% availability requirement and other agreed service levels."
|
||||
},
|
||||
{
|
||||
"id": "C-16",
|
||||
"catalogue": "platform-product-management",
|
||||
"serves": ["OR-7"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Managing the platform's roadmap and backlog to ensure readiness within 10 weeks and driving adoption."
|
||||
},
|
||||
{
|
||||
"id": "C-17",
|
||||
"catalogue": "self-service-and-golden-paths",
|
||||
"serves": ["OR-7"],
|
||||
"items": ["S-5"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 30,
|
||||
"basis": "Building automated templates and CI/CD elements so teams can onboard workloads seamlessly."
|
||||
},
|
||||
{
|
||||
"id": "C-18",
|
||||
"catalogue": "enablement",
|
||||
"serves": ["OR-7"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 30,
|
||||
"basis": "Actively pairing with and helping payment platform teams ingest into the foundation within the timeframe."
|
||||
},
|
||||
{
|
||||
"id": "C-19",
|
||||
"catalogue": "delivery-and-developer-experience-measurement",
|
||||
"serves": ["OR-7"],
|
||||
"items": ["S-5"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Collecting delivery metrics and assessing friction to refine the deployment pipelines."
|
||||
},
|
||||
{
|
||||
"id": "C-20",
|
||||
"catalogue": "supplier-management",
|
||||
"serves": ["OR-2", "OR-13"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Managing relationships and SLAs with the cloud provider, Palo Alto Networks, and Interconnect carrier."
|
||||
},
|
||||
{
|
||||
"id": "C-21",
|
||||
"catalogue": "regulatory-evidence",
|
||||
"serves": ["OR-4", "OR-6"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 25,
|
||||
"basis": "Compiling and retaining the audit evidence required for ongoing DORA, PCI-DSS v4.0, and ISO27001 assessments."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,151 @@
|
||||
{
|
||||
"customer_case": "case-08-landing-zone",
|
||||
"execution_id": "case-02-from-architecture-r2",
|
||||
"session_id": "d29687eb-8857-48e4-8c98-c2251c1c2c8f",
|
||||
"intent_version": 2,
|
||||
"workflow_request": "We are a UK-regulated payment platform expanding into Google Cloud. We need an\nenterprise-grade landing zone ready in under 10 weeks to support our core payments\nengine. All payment processing must comply with DORA and PCI-DSS v4.0. We have\nexisting on-premises systems that require private, low-latency connectivity over a\n10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and\nGitHub Actions for our delivery pipelines. Security requires that all egress\ntraffic flows through centralised inspection appliances before touching the public\ninternet, and customer data must be encrypted with keys we control.",
|
||||
"baseline": null,
|
||||
"overlay_skills": {},
|
||||
"options": {},
|
||||
"sources": {
|
||||
"execution.json": {
|
||||
"sha256": "8bf269deffc8e4bce474bd8d66959c03b04de01dc137eefaf96ead74b46a5a45",
|
||||
"digested": true
|
||||
},
|
||||
"scope.json": {
|
||||
"sha256": "57dc28ab7397f514ef0e83b292fc2165554ac2b516775c973f4965765a9e905f",
|
||||
"digested": true
|
||||
},
|
||||
"requirements.json": {
|
||||
"sha256": "5aecbef9eaea254fb5123bcc1d107b4a7b7d4d45d60d940464d1fde690d2973d",
|
||||
"digested": true
|
||||
},
|
||||
"recommendations.json": {
|
||||
"sha256": "95958b1a107705280d65c9d088bba57352d1f9fa8e67e89b2b3379f78d91cd24",
|
||||
"digested": true
|
||||
},
|
||||
"components.json": {
|
||||
"sha256": "49e47dbfa90a85d086711eb2ba66370c145f13fd3cd3595c1df1366224db392c",
|
||||
"digested": true
|
||||
},
|
||||
"products.json": {
|
||||
"sha256": "75d51cba319f83000e6f85277b0fb21a7ec02faabac332c5d1800c8f512136db",
|
||||
"digested": true
|
||||
},
|
||||
"target-architecture.json": {
|
||||
"sha256": "40879607aaa7041103d8f4d3ba804df8751d2159aa0ce0977d7d821d35f7608b",
|
||||
"digested": true
|
||||
},
|
||||
"verdicts.json": {
|
||||
"sha256": "75e17da790266e94a6775d90857a9b503cacd62fd55c92be2d7a3435de301853",
|
||||
"digested": true
|
||||
},
|
||||
"work-breakdown.json": {
|
||||
"sha256": "057fd1b0ecd6350a6f9f6101b712a61e78fc10d758a67e785a1dca7e1e674dc3",
|
||||
"digested": true
|
||||
}
|
||||
},
|
||||
"scope": {
|
||||
"status": "BASELINE_LOCKED",
|
||||
"readiness": {
|
||||
"supplied": 3,
|
||||
"answered": 0,
|
||||
"assumed": 7,
|
||||
"unknown": 10,
|
||||
"not_applicable": 0,
|
||||
"digested": 13
|
||||
}
|
||||
},
|
||||
"status": "completed",
|
||||
"warnings": [],
|
||||
"risks": [],
|
||||
"assessment": null,
|
||||
"phases": {
|
||||
"scoping": "approved",
|
||||
"operational_requirements": "approved",
|
||||
"operating_model_design": "approved",
|
||||
"validation": "approved",
|
||||
"packaging": "approved"
|
||||
},
|
||||
"final_document": "operating-model-guide.md",
|
||||
"changes": null,
|
||||
"deliverables": {
|
||||
"operating_scope": {
|
||||
"document": "deliverables/operating_scope.md",
|
||||
"attachments": [
|
||||
"scope.json",
|
||||
"scope.yaml"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operational_requirements": {
|
||||
"document": "deliverables/operational_requirements.md",
|
||||
"attachments": [
|
||||
"operational-requirements.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"capability_model": {
|
||||
"document": "deliverables/capability_model.md",
|
||||
"attachments": [
|
||||
"capabilities.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"target_operating_model": {
|
||||
"document": "deliverables/target_operating_model.md",
|
||||
"attachments": [
|
||||
"findings.json",
|
||||
"organisation.mmd",
|
||||
"staffing.json",
|
||||
"target-operating-model.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"validation_results": {
|
||||
"document": "deliverables/validation_results.md",
|
||||
"attachments": [
|
||||
"scenarios.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operating_model_guide": {
|
||||
"document": "deliverables/operating_model_guide.md",
|
||||
"attachments": [],
|
||||
"status": "submitted"
|
||||
}
|
||||
},
|
||||
"files": [
|
||||
"capabilities.json",
|
||||
"deliverables/capability_model.md",
|
||||
"deliverables/operating_model_guide.md",
|
||||
"deliverables/operating_scope.md",
|
||||
"deliverables/operational_requirements.md",
|
||||
"deliverables/target_operating_model.md",
|
||||
"deliverables/validation_results.md",
|
||||
"findings.json",
|
||||
"operating-model-guide.md",
|
||||
"operational-requirements.json",
|
||||
"organisation.mmd",
|
||||
"scenarios.json",
|
||||
"scope.json",
|
||||
"scope.yaml",
|
||||
"staffing.json",
|
||||
"target-operating-model.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"staffing": {
|
||||
"people": 10.8,
|
||||
"cost_per_month": 83846,
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
}
|
||||
},
|
||||
"findings": [],
|
||||
"change_request": null,
|
||||
"capability_sources_verified": false
|
||||
}
|
||||
@@ -0,0 +1 @@
|
||||
[]
|
||||
@@ -0,0 +1,280 @@
|
||||
# Operating model guide: Google Cloud Payments Platform Foundation
|
||||
|
||||
## Summary
|
||||
|
||||
This operating model governs the enterprise-grade Google Cloud platform foundation and landing zone supporting the core payments engine, encompassing the resource hierarchy, dedicated hybrid interconnectivity, centralised egress inspection, immutable compliance audit logging, automated deployment pipelines, federated identity, customer-managed encryption keys, platform telemetry, and financial governance. Operational delivery follows a provider-operated model in which the Service Provider maintains primary operational accountability and responsibility for platform foundation health, continuous monitoring, incident resolution, infrastructure maintenance, and regulatory evidence collection, while the Customer Platform Team retains ownership of payment workload applications and consumes platform services via automated self-service delivery paths.
|
||||
|
||||
Platform support and infrastructure availability are maintained continuously around the clock, with platform reliability leadership, enablement, and product management operating during standard business hours. The reader should look first at the operational assumptions and open questions—specifically the native cloud operations tooling architecture, pipeline-driven change enablement without a manual change advisory board, and interconnect circuit lead times—as well as the staffing figures, which reflect illustrative placeholder rates from a draft rate card.
|
||||
|
||||
### Key figures
|
||||
|
||||
- Operated: 9 Items, with 12 Conditions to keep true.
|
||||
- Faults responded to: 24x7 hours.
|
||||
- Capabilities: 21.
|
||||
- People: 10.8. Cost a month: 83,846 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
|
||||
- Scenario walk-throughs: 31 of 31 pass.
|
||||
- Business outcomes: 3, 3 shown by a Measure.
|
||||
- Findings for whoever owns the design: 0.
|
||||
|
||||
## Business outcomes
|
||||
|
||||
**BO-1: Continuous, highly available, and low-latency operation of the core payments platform foundation** Target: 99.9% foundation availability with deterministic low latency.
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Platform Availability | service level | | 99.9% availability | Service level management | Platform Reliability Lead |
|
||||
| Hybrid Network Latency | service level | | Deterministic low latency | Capacity and performance management | Platform Reliability Lead |
|
||||
|
||||
**BO-2: Continuous compliance with DORA and PCI-DSS v4.0 standards using customer-managed encryption keys and centralised egress inspection** Target: Zero audit non-conformances.
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Audit Non-conformances | service level | | Zero non-conformances | Regulatory evidence and reporting | Platform Reliability Lead |
|
||||
|
||||
**BO-3: Automated, secure infrastructure release pipelines enabling workload ingestion within 10 weeks** Target: Operational readiness achieved within 10 weeks.
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Deployment frequency | outcome | dora-metrics | On-demand | Delivery and developer experience measurement | Platform Product Manager |
|
||||
| Developer satisfaction | guardrail | space-framework | High satisfaction | Delivery and developer experience measurement | Platform Product Manager |
|
||||
| Feedback loops | leading | devex-framework | < 10 minutes | Delivery and developer experience measurement | Platform Product Manager |
|
||||
|
||||
## What is operated
|
||||
|
||||
| Item | What it is | Kind | Product | From |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| S-1 | Resource Hierarchy and Environment Boundary Manager | governance | Resource Manager | C-1 |
|
||||
| S-2 | Dedicated Private Hybrid Connectivity Gateway | network | Cloud Interconnect | C-2 |
|
||||
| S-3 | Centralised Outbound Traffic Inspection and Egress Boundary | service | Palo Alto Networks VM-Series | C-3 |
|
||||
| S-4 | Centralised Immutable Audit Event and Compliance Log Repository | storage | Cloud Storage | C-4 |
|
||||
| S-5 | Automated Infrastructure Orchestration and Deployment Engine | service | GitHub Actions | C-5 |
|
||||
| S-6 | Federated Identity and Role Governance Authority | identity | IAM Workload Identity Federation | C-6 |
|
||||
| S-7 | Cryptographic Key Lifecycle and Encryption Controller | keys | Cloud KMS | C-7 |
|
||||
| S-8 | Platform Telemetry and Operational Alerting Engine | observability | Cloud Monitoring | C-8 |
|
||||
| S-9 | Financial Governance and Budget Enforcement Monitor | billing | Cloud Billing | C-9 |
|
||||
|
||||
What must be kept true while it is run:
|
||||
|
||||
| Condition | On | What must hold | From |
|
||||
| --- | --- | --- | --- |
|
||||
| K-1 | S-1, S-4, S-7 | The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit. | NFR-8 |
|
||||
| K-2 | S-1 | The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic. | NFR-9 |
|
||||
| K-3 | S-1 | Data residency is guaranteed within the United Kingdom and European Union. | NFR-9 |
|
||||
| K-4 | S-5 | Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks. | NFR-10 |
|
||||
| K-5 | S-8 | Platform foundation infrastructure maintains measured monthly availability of at least 99.9%. | NFR-11 |
|
||||
| K-6 | S-8 | Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours. | NFR-11 |
|
||||
| K-7 | S-8 | Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour. | NFR-11 |
|
||||
| K-8 | S-8 | Alert notifications trigger operational incident workflows for the 24/7 central platform operations team. | NFR-12 |
|
||||
| K-9 | S-9 | Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off. | NFR-13 |
|
||||
| K-10 | S-2 | Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing. | NFR-14 |
|
||||
| K-11 | S-8 | Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores. | NFR-15 |
|
||||
| K-12 | S-6 | Permissions are continuously rightsized based on IAM Recommender findings. | DR-OP-3 |
|
||||
|
||||
## Operational requirements
|
||||
|
||||
| Requirement | Kind | What must be achieved | From |
|
||||
| --- | --- | --- | --- |
|
||||
| OR-1 | service_level | Priority 1 critical incidents on platform foundation components are acknowledged and responded to within 30 minutes (as assumed in service_levels.priority_1_response_minutes), 24 hours a day, 7 days a week. | operations.support_hours, service_levels.priority_1_response_minutes |
|
||||
| OR-2 | organisation | Platform foundation operations are delivered under a provider-operated model where external operational management is provided by the service provider. | sourcing.model |
|
||||
| OR-3 | organisation | Platform operational support and administrative access are conducted exclusively from approved delivery countries: United Kingdom (GB), Poland (PL), and India (IN). | sourcing.delivery_countries |
|
||||
| OR-4 | compliance | Landing zone configuration and operational governance maintain demonstrable alignment with DORA operational resiliency guidelines, PCI-DSS v4.0 perimeter isolation standards, and ISO27001 security standards during external audit. | K-1, compliance.frameworks |
|
||||
| OR-5 | service_level | The secondary cloud region in europe-west1 is maintained in warm standby operational readiness to receive failover traffic at all times. | K-2 |
|
||||
| OR-6 | compliance | Data storage, cryptographic processing, and compliance log retention remain strictly resident within the United Kingdom and European Union. | K-3 |
|
||||
| OR-7 | service_level | Platform foundation provisioning, configuration, and operational validation are completed to support core payments engine workload ingestion within 10 weeks. | K-4 |
|
||||
| OR-8 | service_level | Platform foundation infrastructure maintains measured monthly availability of at least 99.9%, available 24 hours a day, 7 days a week. | K-5, operations.availability_hours |
|
||||
| OR-9 | service_level | Platform foundation disaster recovery activation achieves a recovery time objective (RTO) of no more than 4 hours (as assumed in service_levels.recovery_time_hours). | K-6, service_levels.recovery_time_hours |
|
||||
| OR-10 | service_level | Disaster recovery processes achieve a recovery point objective (RPO) of no more than 1 hour of data loss. | K-7 |
|
||||
| OR-11 | process | Platform telemetry alert notifications trigger operational incident workflows immediately upon detection, 24 hours a day, 7 days a week. | K-8 |
|
||||
| OR-12 | process | Monthly cloud foundation expenditure does not exceed the agreed target budget allocation without prior operational review and formal sign-off. | K-9 |
|
||||
| OR-13 | service_level | Hybrid connectivity between cloud and on-premises environments maintains deterministic low latency suitable for real-time payment transaction processing. | K-10 |
|
||||
| OR-14 | process | Deployments and operational workload executions optimize carbon-free energy utilization based on regional carbon-free energy (CFE) scores. | K-11 |
|
||||
| OR-15 | process | Access permissions across platform identities are continuously rightsized to least privilege based on automated access findings. | K-12 |
|
||||
|
||||
## 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 | 24x7 | 40 h |
|
||||
| C-2 | Monitoring and alerting | OR-11, OR-8, OR-13 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | 24x7 | 40 h |
|
||||
| C-3 | Problem management | OR-1, OR-8 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 20 h |
|
||||
| C-4 | Service request fulfilment | OR-2 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 20 h |
|
||||
| C-5 | Change enablement | OR-4, OR-7 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 15 h |
|
||||
| C-6 | Release and deployment | OR-7, OR-14 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 20 h |
|
||||
| C-7 | Configuration management | OR-4, OR-6 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 15 h |
|
||||
| C-8 | Backup and recovery | OR-10 | S-4, S-7 | business | 10 h |
|
||||
| C-9 | Service continuity | OR-5, OR-9 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 15 h |
|
||||
| C-10 | Capacity and performance management | OR-8, OR-13, OR-14 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 15 h |
|
||||
| C-11 | Access management | OR-15, OR-3 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 15 h |
|
||||
| C-12 | Vulnerability and patch management | OR-4 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 20 h |
|
||||
| C-13 | Security monitoring and response | OR-4 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | 24x7 | 40 h |
|
||||
| C-14 | Cost management | OR-12 | S-9 | business | 10 h |
|
||||
| C-15 | Service level management | OR-8 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 10 h |
|
||||
| C-16 | Platform product management | OR-7 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 20 h |
|
||||
| C-17 | Self-service and golden paths | OR-7 | S-5 | business | 30 h |
|
||||
| C-18 | Enablement | OR-7 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 30 h |
|
||||
| C-19 | Delivery and developer experience measurement | OR-7 | S-5 | business | 10 h |
|
||||
| C-20 | Supplier management | OR-2, OR-13 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 10 h |
|
||||
| C-21 | Regulatory evidence and reporting | OR-4, OR-6 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 25 h |
|
||||
|
||||
## Who does what
|
||||
|
||||
| Role | Party | Country | Level | Hours |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Platform Operations Engineer | Service Provider (provider) | PL | engineer | 24x7 |
|
||||
| Platform Security & Network Engineer | Service Provider (provider) | PL | senior | 24x7 |
|
||||
| Platform Reliability Lead | Service Provider (provider) | GB | lead | business |
|
||||
| Platform Product Manager | Service Provider (provider) | GB | lead | business |
|
||||
| Platform Enablement Engineer | Service Provider (provider) | GB | senior | business |
|
||||
| Customer Stakeholder | Customer Platform Team (customer) | GB | lead | business |
|
||||
|
||||
The teams, as Team Topologies names their kinds:
|
||||
|
||||
| Team | Kind | Party | Roles | Purpose |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Central Platform Operations Team | platform | Service Provider | Platform Operations Engineer, Platform Security & Network Engineer, Platform Reliability Lead | 24/7 central platform operations and foundation management. |
|
||||
| Platform Product & Enablement Team | platform | Service Provider | Platform Product Manager, Platform Enablement Engineer | Platform product management, enablement, and measurement. |
|
||||
| Customer Application Teams | stream-aligned | Customer Platform Team | Customer Stakeholder | Core payments engine development and workload deployment. |
|
||||
|
||||
How the teams work together:
|
||||
|
||||
| From | To | Mode | Until | Purpose |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Customer Application Teams | Central Platform Operations Team | x-as-a-service | | Customer teams consume platform foundation services and infrastructure via automated pipelines. |
|
||||
| Platform Product & Enablement Team | Customer Application Teams | facilitating | | Enablement team facilitates customer application teams in adopting pipelines and ingesting workloads. |
|
||||
|
||||
| Capability | Platform Operations Engineer | Platform Security & Network Engineer | Platform Reliability Lead | Platform Product Manager | Platform Enablement Engineer | Customer Stakeholder |
|
||||
| --- | --- | --- | --- | --- | --- | --- |
|
||||
| Incident management (C-1) | R | | A | | | C |
|
||||
| Monitoring and alerting (C-2) | R | | A | | | C |
|
||||
| Problem management (C-3) | | R | A | | | C |
|
||||
| Service request fulfilment (C-4) | R | | A | | | C |
|
||||
| Change enablement (C-5) | | R | A | | | C |
|
||||
| Release and deployment (C-6) | | R | A | | | C |
|
||||
| Configuration management (C-7) | | R | A | | | C |
|
||||
| Backup and recovery (C-8) | R | | A | | | C |
|
||||
| Service continuity (C-9) | | R | A | | | C |
|
||||
| Capacity and performance management (C-10) | | R | A | | | 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) | | | | A/R | | C |
|
||||
| Service level management (C-15) | | | A/R | | | C |
|
||||
| Platform product management (C-16) | | | | A/R | | C |
|
||||
| Self-service and golden paths (C-17) | | | | A | R | C |
|
||||
| Enablement (C-18) | | | | A | R | C |
|
||||
| Delivery and developer experience measurement (C-19) | | | | A | R | C |
|
||||
| Supplier management (C-20) | | | A/R | | | C |
|
||||
| Regulatory evidence and reporting (C-21) | | R | A | | | 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 Operations Engineer | Service Provider | PL | engineer | 24x7 | 125.0 h | 5.0 | 30,777 GBP |
|
||||
| Platform Security & Network Engineer | Service Provider | PL | senior | 24x7 | 185.0 h | 5.0 | 41,640 GBP |
|
||||
| Platform Reliability Lead | Service Provider | GB | lead | business | 20.0 h | 0.1 | 2,212 GBP |
|
||||
| Platform Product Manager | Service Provider | GB | lead | business | 30.0 h | 0.2 | 3,318 GBP |
|
||||
| Platform Enablement Engineer | Service Provider | GB | senior | business | 70.0 h | 0.5 | 5,899 GBP |
|
||||
| Customer Stakeholder | Customer Platform Team | GB | lead | business | 0.0 h | 0.0 | not priced |
|
||||
|
||||
10.8 people in all. Cost a month: 83,846 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-K1 | Regulatory alignment with DORA and PCI-DSS v4.0 is maintained and verified during external audit with zero non-conformances. | pass | Capability C-21 (regulatory-evidence) exists to compile and retain audit evidence for DORA and PCI-DSS v4.0 assessments. Role R-2 is responsible for it. |
|
||||
| OC-K2 | The europe-west1 secondary region is verified as a warm standby ready to receive failover traffic. | pass | Capability C-9 (service-continuity) is tasked with maintaining runbooks and verifying the europe-west1 secondary region warm standby readiness. Role R-2 is responsible. |
|
||||
| OC-K3 | Data residency remains strictly within the United Kingdom and European Union boundaries. | pass | Capability C-7 (configuration-management) audits actual environment configurations against data residency boundaries (UK and EU). Role R-2 is responsible. |
|
||||
| OC-K4 | Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks. | pass | Capability C-16 (platform-product-management) is responsible for ensuring the platform foundation is provisioned and validated within 10 weeks. Role R-4 is responsible. |
|
||||
| OC-K5 | Platform foundation infrastructure maintains measured monthly availability of at least 99.9%. | pass | Capability C-15 (service-level-management) is set up to track and report on the 99.9% availability requirement. Role R-3 is responsible. |
|
||||
| OC-K6 | Disaster recovery activation achieves a recovery time objective (RTO) of no more than 4 hours. | pass | Capability C-1 (incident-management) operates 24x7 and takes responsibility for executing disaster recovery activation within the 4-hour RTO at any time of day. Role R-1 provides the 24x7 coverage. |
|
||||
| OC-K7 | Disaster recovery achieves a recovery point objective (RPO) of no more than 1 hour of data loss. | pass | Capability C-8 (backup-and-recovery) ensures backups meet the 1-hour RPO and handles testing restores. Role R-1 is responsible. |
|
||||
| OC-K8 | Alert notifications trigger operational incident workflows for the 24/7 central platform operations team immediately. | pass | Capability C-2 (monitoring-and-alerting) operates 24x7 for immediate response to telemetry signals. Role R-1 provides 24x7 coverage. |
|
||||
| OC-K9 | Monthly cloud foundation expenditure does not exceed the agreed target allocation without prior operational review and formal sign-off. | pass | Capability C-14 (cost-management) monitors foundation spend against agreed budgets and manages sign-offs for anomalies. Role R-4 is responsible. |
|
||||
| OC-K10 | Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing. | pass | Capability C-10 (capacity-and-performance) monitors Dedicated Interconnect latency and overall infrastructure capacity for payment processing performance. Role R-2 is responsible. |
|
||||
| OC-K11 | Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores. | pass | Capability C-10 (capacity-and-performance) oversees optimization of workload placements for carbon-free energy (CFE). Role R-2 is responsible. |
|
||||
| OC-K12 | Permissions are continuously rightsized based on IAM Recommender findings. | pass | Capability C-11 (access-management) executes continuous identity rightsizing based on automated findings. Role R-1 is responsible. |
|
||||
| OC-OR1 | Priority 1 critical incidents on platform foundation components are acknowledged and responded to within 30 minutes, 24 hours a day, 7 days a week. | pass | Capability C-1 (incident-management) explicitly offers 24x7 coverage to acknowledge priority 1 incidents within 30 minutes, supported by the 24x7 R-1 role. |
|
||||
| OC-OR2 | External operational management is consistently provided by the service provider. | pass | Capability C-4 (service-request-fulfilment) represents non-fault operational management by the Service Provider. Sourcing model ensures external operational management. |
|
||||
| OC-OR8 | Platform foundation infrastructure maintains measured monthly availability of at least 99.9%, available 24 hours a day, 7 days a week. | pass | Capability C-15 (service-level-management) tracks and reports on the 99.9% availability requirement on a monthly basis. Role R-3 is responsible. |
|
||||
| OC-OR3-R1 | Role operates from an approved delivery country. | pass | Role R-1 operates from Poland (PL), which is an approved delivery country. |
|
||||
| OC-OR3-R2 | Role operates from an approved delivery country. | pass | Role R-2 operates from Poland (PL), which is an approved delivery country. |
|
||||
| OC-OR3-R3 | Role operates from an approved delivery country. | pass | Role R-3 operates from the United Kingdom (GB), which is an approved delivery country. |
|
||||
| OC-OR3-R4 | Role operates from an approved delivery country. | pass | Role R-4 operates from the United Kingdom (GB), which is an approved delivery country. |
|
||||
| OC-OR3-R5 | Role operates from an approved delivery country. | pass | Role R-5 operates from the United Kingdom (GB), which is an approved delivery country. |
|
||||
|
||||
Each scenario is generated from the operating model and traced through it by code.
|
||||
|
||||
| Scenario | Result | Path |
|
||||
| --- | --- | --- |
|
||||
| Resource Hierarchy and Environment Boundary Manager (S-1) fails at an hour faults are responded to (24x7). | pass | Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable. |
|
||||
| Resource Hierarchy and Environment Boundary Manager (S-1) must be changed. | pass | Platform Security & Network Engineer makes the change under C-5. |
|
||||
| Dedicated Private Hybrid Connectivity Gateway (S-2) fails at an hour faults are responded to (24x7). | pass | Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable. |
|
||||
| Dedicated Private Hybrid Connectivity Gateway (S-2) must be changed. | pass | Platform Security & Network Engineer makes the change under C-5. |
|
||||
| Centralised Outbound Traffic Inspection and Egress Boundary (S-3) fails at an hour faults are responded to (24x7). | pass | Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable. |
|
||||
| Centralised Outbound Traffic Inspection and Egress Boundary (S-3) must be changed. | pass | Platform Security & Network Engineer makes the change under C-5. |
|
||||
| Centralised Immutable Audit Event and Compliance Log Repository (S-4) fails at an hour faults are responded to (24x7). | pass | Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable. |
|
||||
| Centralised Immutable Audit Event and Compliance Log Repository (S-4) must be changed. | pass | Platform Security & Network Engineer makes the change under C-5. |
|
||||
| Automated Infrastructure Orchestration and Deployment Engine (S-5) fails at an hour faults are responded to (24x7). | pass | Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable. |
|
||||
| Automated Infrastructure Orchestration and Deployment Engine (S-5) must be changed. | pass | Platform Security & Network Engineer makes the change under C-5. |
|
||||
| Federated Identity and Role Governance Authority (S-6) fails at an hour faults are responded to (24x7). | pass | Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable. |
|
||||
| Federated Identity and Role Governance Authority (S-6) must be changed. | pass | Platform Security & Network Engineer makes the change under C-5. |
|
||||
| Cryptographic Key Lifecycle and Encryption Controller (S-7) fails at an hour faults are responded to (24x7). | pass | Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable. |
|
||||
| Cryptographic Key Lifecycle and Encryption Controller (S-7) must be changed. | pass | Platform Security & Network Engineer makes the change under C-5. |
|
||||
| Platform Telemetry and Operational Alerting Engine (S-8) fails at an hour faults are responded to (24x7). | pass | Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable. |
|
||||
| Platform Telemetry and Operational Alerting Engine (S-8) must be changed. | pass | Platform Security & Network Engineer makes the change under C-5. |
|
||||
| Financial Governance and Budget Enforcement Monitor (S-9) fails at an hour faults are responded to (24x7). | pass | Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable. |
|
||||
| Financial Governance and Budget Enforcement Monitor (S-9) must be changed. | pass | Platform Security & Network Engineer makes the change under C-5. |
|
||||
| Condition K-1 must be shown to hold: The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit. | pass | Check OC-K1 on C-21 keeps it true. |
|
||||
| Condition K-2 must be shown to hold: The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic. | pass | Check OC-K2 on C-9 keeps it true. |
|
||||
| Condition K-3 must be shown to hold: Data residency is guaranteed within the United Kingdom and European Union. | pass | Check OC-K3 on C-7 keeps it true. |
|
||||
| Condition K-4 must be shown to hold: Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks. | pass | Check OC-K4 on C-16 keeps it true. |
|
||||
| Condition K-5 must be shown to hold: Platform foundation infrastructure maintains measured monthly availability of at least 99.9%. | pass | Check OC-K5 on C-15 keeps it true. |
|
||||
| Condition K-6 must be shown to hold: Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours. | pass | Check OC-K6 on C-1 keeps it true. |
|
||||
| Condition K-7 must be shown to hold: Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour. | pass | Check OC-K7 on C-8 keeps it true. |
|
||||
| Condition K-8 must be shown to hold: Alert notifications trigger operational incident workflows for the 24/7 central platform operations team. | pass | Check OC-K8 on C-2 keeps it true. |
|
||||
| Condition K-9 must be shown to hold: Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off. | pass | Check OC-K9 on C-14 keeps it true. |
|
||||
| Condition K-10 must be shown to hold: Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing. | pass | Check OC-K10 on C-10 keeps it true. |
|
||||
| Condition K-11 must be shown to hold: Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores. | pass | Check OC-K11 on C-10 keeps it true. |
|
||||
| Condition K-12 must be shown to hold: Permissions are continuously rightsized based on IAM Recommender findings. | pass | Check OC-K12 on C-11 keeps it true. |
|
||||
| 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
|
||||
|
||||
No findings: the solution provides what operating it needs.
|
||||
|
||||
Assumed for the customer, and open to change when they answer:
|
||||
|
||||
- `intent.business_outcomes`: {'outcome': 'Continuous, highly available, and low-latency operation of the core payments platform foundation', 'target': '99.9% foundation availability with deterministic low latency', 'id': 'BO-1'}, {'id': 'BO-2', 'target': 'Zero audit non-conformances', 'outcome': 'Continuous compliance with DORA and PCI-DSS v4.0 standards using customer-managed encryption keys and centralised egress inspection'}, {'outcome': 'Automated, secure infrastructure release pipelines enabling workload ingestion within 10 weeks', 'target': 'Operational readiness achieved within 10 weeks', 'id': 'BO-3'}. Derived from workflow request objectives: running core payment processing reliably in Google Cloud, meeting DORA and PCI-DSS v4.0 regulatory standards, and delivering landing zone readiness within 10 weeks.
|
||||
- `intent.exclusions`: Core payment application workload code maintenance and runtime application management, On-premises infrastructure hardware maintenance beyond Cloud Interconnect physical termination. Platform foundation scope excludes application-level core payment workloads and on-premises data centre hardware beyond the Interconnect boundary.
|
||||
- `operations.change_process`: Changes to the platform foundation are deployed through automated GitHub Actions pipelines with mandatory peer reviews and automated policy validation, without a separate manual change advisory board.. Catalogue default aligned with request stating GitHub Actions delivery pipelines: automated pipeline deployment with peer review and automated checks.
|
||||
- `organisation.existing_teams`: {'name': 'Central Platform Operations Team', 'hours': '24x7', 'party': 'provider'}. Catalogue default: all operational roles are newly provided under provider_operated model, with reference to the 24/7 central platform operations team in condition K-8.
|
||||
- `service_management.tooling`: Google Cloud operations suite (Cloud Monitoring, Cloud Logging, and Cloud Alerting) without a separate external ITSM system.. Catalogue default: Cloud provider native operations tooling (Cloud Monitoring, Cloud Logging) integrated with alerting.
|
||||
- `service_levels.priority_1_response_minutes`: 30. Catalogue default response time for Priority 1 critical incidents under 24x7 operational support.
|
||||
- `service_levels.recovery_time_hours`: 4. Catalogue default aligned with condition K-6 specifying a 4-hour recovery time objective (RTO).
|
||||
|
||||
## 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.
|
||||
@@ -0,0 +1,126 @@
|
||||
[
|
||||
{
|
||||
"id": "OR-1",
|
||||
"kind": "service_level",
|
||||
"statement": "Priority 1 critical incidents on platform foundation components are acknowledged and responded to within 30 minutes (as assumed in service_levels.priority_1_response_minutes), 24 hours a day, 7 days a week.",
|
||||
"source": [
|
||||
"operations.support_hours",
|
||||
"service_levels.priority_1_response_minutes"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-2",
|
||||
"kind": "organisation",
|
||||
"statement": "Platform foundation operations are delivered under a provider-operated model where external operational management is provided by the service provider.",
|
||||
"source": [
|
||||
"sourcing.model"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-3",
|
||||
"kind": "organisation",
|
||||
"statement": "Platform operational support and administrative access are conducted exclusively from approved delivery countries: United Kingdom (GB), Poland (PL), and India (IN).",
|
||||
"source": [
|
||||
"sourcing.delivery_countries"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-4",
|
||||
"kind": "compliance",
|
||||
"statement": "Landing zone configuration and operational governance maintain demonstrable alignment with DORA operational resiliency guidelines, PCI-DSS v4.0 perimeter isolation standards, and ISO27001 security standards during external audit.",
|
||||
"source": [
|
||||
"K-1",
|
||||
"compliance.frameworks"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-5",
|
||||
"kind": "service_level",
|
||||
"statement": "The secondary cloud region in europe-west1 is maintained in warm standby operational readiness to receive failover traffic at all times.",
|
||||
"source": [
|
||||
"K-2"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-6",
|
||||
"kind": "compliance",
|
||||
"statement": "Data storage, cryptographic processing, and compliance log retention remain strictly resident within the United Kingdom and European Union.",
|
||||
"source": [
|
||||
"K-3"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-7",
|
||||
"kind": "service_level",
|
||||
"statement": "Platform foundation provisioning, configuration, and operational validation are completed to support core payments engine workload ingestion within 10 weeks.",
|
||||
"source": [
|
||||
"K-4"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-8",
|
||||
"kind": "service_level",
|
||||
"statement": "Platform foundation infrastructure maintains measured monthly availability of at least 99.9%, available 24 hours a day, 7 days a week.",
|
||||
"source": [
|
||||
"K-5",
|
||||
"operations.availability_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-9",
|
||||
"kind": "service_level",
|
||||
"statement": "Platform foundation disaster recovery activation achieves a recovery time objective (RTO) of no more than 4 hours (as assumed in service_levels.recovery_time_hours).",
|
||||
"source": [
|
||||
"K-6",
|
||||
"service_levels.recovery_time_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-10",
|
||||
"kind": "service_level",
|
||||
"statement": "Disaster recovery processes achieve a recovery point objective (RPO) of no more than 1 hour of data loss.",
|
||||
"source": [
|
||||
"K-7"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-11",
|
||||
"kind": "process",
|
||||
"statement": "Platform telemetry alert notifications trigger operational incident workflows immediately upon detection, 24 hours a day, 7 days a week.",
|
||||
"source": [
|
||||
"K-8"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-12",
|
||||
"kind": "process",
|
||||
"statement": "Monthly cloud foundation expenditure does not exceed the agreed target budget allocation without prior operational review and formal sign-off.",
|
||||
"source": [
|
||||
"K-9"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-13",
|
||||
"kind": "service_level",
|
||||
"statement": "Hybrid connectivity between cloud and on-premises environments maintains deterministic low latency suitable for real-time payment transaction processing.",
|
||||
"source": [
|
||||
"K-10"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-14",
|
||||
"kind": "process",
|
||||
"statement": "Deployments and operational workload executions optimize carbon-free energy utilization based on regional carbon-free energy (CFE) scores.",
|
||||
"source": [
|
||||
"K-11"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-15",
|
||||
"kind": "process",
|
||||
"statement": "Access permissions across platform identities are continuously rightsized to least privilege based on automated access findings.",
|
||||
"source": [
|
||||
"K-12"
|
||||
]
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,19 @@
|
||||
flowchart TB
|
||||
subgraph P_1["Customer Platform Team (customer)"]
|
||||
subgraph T_3["Customer Application Teams (stream-aligned team)"]
|
||||
R_6["Customer Stakeholder<br/>GB, lead, business"]
|
||||
end
|
||||
end
|
||||
subgraph P_2["Service Provider (provider)"]
|
||||
subgraph T_1["Central Platform Operations Team (platform team)"]
|
||||
R_1["Platform Operations Engineer<br/>PL, engineer, 24x7"]
|
||||
R_2["Platform Security & Network Engineer<br/>PL, senior, 24x7"]
|
||||
R_3["Platform Reliability Lead<br/>GB, lead, business"]
|
||||
end
|
||||
subgraph T_2["Platform Product & Enablement Team (platform team)"]
|
||||
R_4["Platform Product Manager<br/>GB, lead, business"]
|
||||
R_5["Platform Enablement Engineer<br/>GB, senior, business"]
|
||||
end
|
||||
end
|
||||
T_3 -- "x-as-a-service" --> T_1
|
||||
T_2 -- "facilitating" --> T_3
|
||||
@@ -0,0 +1,219 @@
|
||||
[
|
||||
{
|
||||
"id": "SC-fault-S-1",
|
||||
"scenario": "Resource Hierarchy and Environment Boundary Manager (S-1) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-1",
|
||||
"scenario": "Resource Hierarchy and Environment Boundary Manager (S-1) must be changed.",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-2",
|
||||
"scenario": "Dedicated Private Hybrid Connectivity Gateway (S-2) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-2",
|
||||
"scenario": "Dedicated Private Hybrid Connectivity Gateway (S-2) must be changed.",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-3",
|
||||
"scenario": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-3",
|
||||
"scenario": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) must be changed.",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-4",
|
||||
"scenario": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-4",
|
||||
"scenario": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) must be changed.",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-5",
|
||||
"scenario": "Automated Infrastructure Orchestration and Deployment Engine (S-5) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-5",
|
||||
"passes": true,
|
||||
"path": "Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-5",
|
||||
"scenario": "Automated Infrastructure Orchestration and Deployment Engine (S-5) must be changed.",
|
||||
"about": "S-5",
|
||||
"passes": true,
|
||||
"path": "Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-6",
|
||||
"scenario": "Federated Identity and Role Governance Authority (S-6) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-6",
|
||||
"passes": true,
|
||||
"path": "Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-6",
|
||||
"scenario": "Federated Identity and Role Governance Authority (S-6) must be changed.",
|
||||
"about": "S-6",
|
||||
"passes": true,
|
||||
"path": "Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-7",
|
||||
"scenario": "Cryptographic Key Lifecycle and Encryption Controller (S-7) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-7",
|
||||
"passes": true,
|
||||
"path": "Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-7",
|
||||
"scenario": "Cryptographic Key Lifecycle and Encryption Controller (S-7) must be changed.",
|
||||
"about": "S-7",
|
||||
"passes": true,
|
||||
"path": "Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-8",
|
||||
"scenario": "Platform Telemetry and Operational Alerting Engine (S-8) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-8",
|
||||
"passes": true,
|
||||
"path": "Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-8",
|
||||
"scenario": "Platform Telemetry and Operational Alerting Engine (S-8) must be changed.",
|
||||
"about": "S-8",
|
||||
"passes": true,
|
||||
"path": "Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-9",
|
||||
"scenario": "Financial Governance and Budget Enforcement Monitor (S-9) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-9",
|
||||
"passes": true,
|
||||
"path": "Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-9",
|
||||
"scenario": "Financial Governance and Budget Enforcement Monitor (S-9) must be changed.",
|
||||
"about": "S-9",
|
||||
"passes": true,
|
||||
"path": "Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-1",
|
||||
"scenario": "Condition K-1 must be shown to hold: The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.",
|
||||
"about": "K-1",
|
||||
"passes": true,
|
||||
"path": "Check OC-K1 on C-21 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-2",
|
||||
"scenario": "Condition K-2 must be shown to hold: The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic.",
|
||||
"about": "K-2",
|
||||
"passes": true,
|
||||
"path": "Check OC-K2 on C-9 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-3",
|
||||
"scenario": "Condition K-3 must be shown to hold: Data residency is guaranteed within the United Kingdom and European Union.",
|
||||
"about": "K-3",
|
||||
"passes": true,
|
||||
"path": "Check OC-K3 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-4",
|
||||
"scenario": "Condition K-4 must be shown to hold: Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks.",
|
||||
"about": "K-4",
|
||||
"passes": true,
|
||||
"path": "Check OC-K4 on C-16 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-5",
|
||||
"scenario": "Condition K-5 must be shown to hold: Platform foundation infrastructure maintains measured monthly availability of at least 99.9%.",
|
||||
"about": "K-5",
|
||||
"passes": true,
|
||||
"path": "Check OC-K5 on C-15 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-6",
|
||||
"scenario": "Condition K-6 must be shown to hold: Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours.",
|
||||
"about": "K-6",
|
||||
"passes": true,
|
||||
"path": "Check OC-K6 on C-1 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-7",
|
||||
"scenario": "Condition K-7 must be shown to hold: Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour.",
|
||||
"about": "K-7",
|
||||
"passes": true,
|
||||
"path": "Check OC-K7 on C-8 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-8",
|
||||
"scenario": "Condition K-8 must be shown to hold: Alert notifications trigger operational incident workflows for the 24/7 central platform operations team.",
|
||||
"about": "K-8",
|
||||
"passes": true,
|
||||
"path": "Check OC-K8 on C-2 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-9",
|
||||
"scenario": "Condition K-9 must be shown to hold: Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off.",
|
||||
"about": "K-9",
|
||||
"passes": true,
|
||||
"path": "Check OC-K9 on C-14 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-10",
|
||||
"scenario": "Condition K-10 must be shown to hold: Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing.",
|
||||
"about": "K-10",
|
||||
"passes": true,
|
||||
"path": "Check OC-K10 on C-10 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-11",
|
||||
"scenario": "Condition K-11 must be shown to hold: Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores.",
|
||||
"about": "K-11",
|
||||
"passes": true,
|
||||
"path": "Check OC-K11 on C-10 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-12",
|
||||
"scenario": "Condition K-12 must be shown to hold: Permissions are continuously rightsized based on IAM Recommender findings.",
|
||||
"about": "K-12",
|
||||
"passes": true,
|
||||
"path": "Check OC-K12 on C-11 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-party-P-2",
|
||||
"scenario": "Service Provider cannot be reached.",
|
||||
"about": "P-2",
|
||||
"passes": true,
|
||||
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,401 @@
|
||||
{
|
||||
"kind": "platform_foundation",
|
||||
"stated": {
|
||||
"engagement": {
|
||||
"kind": "platform_foundation"
|
||||
},
|
||||
"intent": {
|
||||
"statement": "We are a UK-regulated payment platform expanding into Google Cloud. We need an\nenterprise-grade landing zone ready in under 10 weeks to support our core payments\nengine. All payment processing must comply with DORA and PCI-DSS v4.0. We have\nexisting on-premises systems that require private, low-latency connectivity over a\n10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and\nGitHub Actions for our delivery pipelines. Security requires that all egress\ntraffic flows through centralised inspection appliances before touching the public\ninternet, and customer data must be encrypted with keys we control."
|
||||
},
|
||||
"solution": {
|
||||
"cloud_provider": "gcp",
|
||||
"items": [
|
||||
{
|
||||
"id": "S-1",
|
||||
"name": "Resource Hierarchy and Environment Boundary Manager",
|
||||
"kind": "governance",
|
||||
"product": "Resource Manager",
|
||||
"source_ref": "C-1",
|
||||
"elements": [
|
||||
"E-1",
|
||||
"E-2",
|
||||
"E-3",
|
||||
"E-4",
|
||||
"E-5",
|
||||
"E-6",
|
||||
"E-7",
|
||||
"E-8",
|
||||
"E-9",
|
||||
"E-10",
|
||||
"E-34",
|
||||
"E-35",
|
||||
"E-36",
|
||||
"E-37",
|
||||
"E-38",
|
||||
"E-50",
|
||||
"E-51",
|
||||
"E-55",
|
||||
"E-60"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-2",
|
||||
"name": "Dedicated Private Hybrid Connectivity Gateway",
|
||||
"kind": "network",
|
||||
"product": "Cloud Interconnect",
|
||||
"source_ref": "C-2",
|
||||
"elements": [
|
||||
"E-11",
|
||||
"E-12",
|
||||
"E-13",
|
||||
"E-14",
|
||||
"E-56",
|
||||
"E-57"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-3",
|
||||
"name": "Centralised Outbound Traffic Inspection and Egress Boundary",
|
||||
"kind": "service",
|
||||
"product": "Palo Alto Networks VM-Series",
|
||||
"source_ref": "C-3",
|
||||
"elements": [
|
||||
"E-15",
|
||||
"E-16",
|
||||
"E-17",
|
||||
"E-18",
|
||||
"E-19",
|
||||
"E-20",
|
||||
"E-47",
|
||||
"E-48",
|
||||
"E-53"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-4",
|
||||
"name": "Centralised Immutable Audit Event and Compliance Log Repository",
|
||||
"kind": "storage",
|
||||
"product": "Cloud Storage",
|
||||
"source_ref": "C-4",
|
||||
"elements": [
|
||||
"E-21",
|
||||
"E-22",
|
||||
"E-39"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-5",
|
||||
"name": "Automated Infrastructure Orchestration and Deployment Engine",
|
||||
"kind": "service",
|
||||
"product": "GitHub Actions",
|
||||
"source_ref": "C-5",
|
||||
"elements": [
|
||||
"E-42",
|
||||
"E-43"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-6",
|
||||
"name": "Federated Identity and Role Governance Authority",
|
||||
"kind": "identity",
|
||||
"product": "IAM Workload Identity Federation",
|
||||
"source_ref": "C-6",
|
||||
"elements": [
|
||||
"E-23",
|
||||
"E-24",
|
||||
"E-25",
|
||||
"E-26",
|
||||
"E-27",
|
||||
"E-45"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-7",
|
||||
"name": "Cryptographic Key Lifecycle and Encryption Controller",
|
||||
"kind": "keys",
|
||||
"product": "Cloud KMS",
|
||||
"source_ref": "C-7",
|
||||
"elements": [
|
||||
"E-28",
|
||||
"E-29",
|
||||
"E-30",
|
||||
"E-31",
|
||||
"E-49",
|
||||
"E-58",
|
||||
"E-59"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-8",
|
||||
"name": "Platform Telemetry and Operational Alerting Engine",
|
||||
"kind": "observability",
|
||||
"product": "Cloud Monitoring",
|
||||
"source_ref": "C-8",
|
||||
"elements": [
|
||||
"E-32",
|
||||
"E-40",
|
||||
"E-41",
|
||||
"E-44",
|
||||
"E-52"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-9",
|
||||
"name": "Financial Governance and Budget Enforcement Monitor",
|
||||
"kind": "billing",
|
||||
"product": "Cloud Billing",
|
||||
"source_ref": "C-9",
|
||||
"elements": [
|
||||
"E-33",
|
||||
"E-46",
|
||||
"E-54"
|
||||
]
|
||||
}
|
||||
],
|
||||
"conditions": [
|
||||
{
|
||||
"id": "K-1",
|
||||
"on": [
|
||||
"S-1",
|
||||
"S-4",
|
||||
"S-7"
|
||||
],
|
||||
"condition": "The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.",
|
||||
"source_ref": "NFR-8"
|
||||
},
|
||||
{
|
||||
"id": "K-2",
|
||||
"on": [
|
||||
"S-1"
|
||||
],
|
||||
"condition": "The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic.",
|
||||
"source_ref": "NFR-9"
|
||||
},
|
||||
{
|
||||
"id": "K-3",
|
||||
"on": [
|
||||
"S-1"
|
||||
],
|
||||
"condition": "Data residency is guaranteed within the United Kingdom and European Union.",
|
||||
"source_ref": "NFR-9"
|
||||
},
|
||||
{
|
||||
"id": "K-4",
|
||||
"on": [
|
||||
"S-5"
|
||||
],
|
||||
"condition": "Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks.",
|
||||
"source_ref": "NFR-10"
|
||||
},
|
||||
{
|
||||
"id": "K-5",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Platform foundation infrastructure maintains measured monthly availability of at least 99.9%.",
|
||||
"source_ref": "NFR-11"
|
||||
},
|
||||
{
|
||||
"id": "K-6",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours.",
|
||||
"source_ref": "NFR-11"
|
||||
},
|
||||
{
|
||||
"id": "K-7",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour.",
|
||||
"source_ref": "NFR-11"
|
||||
},
|
||||
{
|
||||
"id": "K-8",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Alert notifications trigger operational incident workflows for the 24/7 central platform operations team.",
|
||||
"source_ref": "NFR-12"
|
||||
},
|
||||
{
|
||||
"id": "K-9",
|
||||
"on": [
|
||||
"S-9"
|
||||
],
|
||||
"condition": "Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off.",
|
||||
"source_ref": "NFR-13"
|
||||
},
|
||||
{
|
||||
"id": "K-10",
|
||||
"on": [
|
||||
"S-2"
|
||||
],
|
||||
"condition": "Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing.",
|
||||
"source_ref": "NFR-14"
|
||||
},
|
||||
{
|
||||
"id": "K-11",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores.",
|
||||
"source_ref": "NFR-15"
|
||||
},
|
||||
{
|
||||
"id": "K-12",
|
||||
"on": [
|
||||
"S-6"
|
||||
],
|
||||
"condition": "Permissions are continuously rightsized based on IAM Recommender findings.",
|
||||
"source_ref": "DR-OP-3"
|
||||
}
|
||||
],
|
||||
"build": {
|
||||
"duration_days": 36,
|
||||
"customer_owned": [
|
||||
"Order and provision the Interconnect carrier circuits"
|
||||
]
|
||||
}
|
||||
},
|
||||
"operations": {
|
||||
"support_hours": "24x7",
|
||||
"availability_hours": "24x7"
|
||||
},
|
||||
"sourcing": {
|
||||
"model": "provider_operated",
|
||||
"delivery_countries": [
|
||||
"GB",
|
||||
"PL",
|
||||
"IN"
|
||||
]
|
||||
},
|
||||
"compliance": {
|
||||
"frameworks": [
|
||||
"DORA",
|
||||
"ISO27001",
|
||||
"PCI_DSS_v4"
|
||||
]
|
||||
},
|
||||
"commercial": {
|
||||
"currency": "GBP"
|
||||
}
|
||||
},
|
||||
"binding": [
|
||||
"operations.support_hours",
|
||||
"sourcing.model",
|
||||
"sourcing.delivery_countries"
|
||||
],
|
||||
"assumed": [
|
||||
{
|
||||
"field": "intent.business_outcomes",
|
||||
"value": [
|
||||
{
|
||||
"outcome": "Continuous, highly available, and low-latency operation of the core payments platform foundation",
|
||||
"target": "99.9% foundation availability with deterministic low latency",
|
||||
"id": "BO-1"
|
||||
},
|
||||
{
|
||||
"id": "BO-2",
|
||||
"target": "Zero audit non-conformances",
|
||||
"outcome": "Continuous compliance with DORA and PCI-DSS v4.0 standards using customer-managed encryption keys and centralised egress inspection"
|
||||
},
|
||||
{
|
||||
"outcome": "Automated, secure infrastructure release pipelines enabling workload ingestion within 10 weeks",
|
||||
"target": "Operational readiness achieved within 10 weeks",
|
||||
"id": "BO-3"
|
||||
}
|
||||
],
|
||||
"why": "Derived from workflow request objectives: running core payment processing reliably in Google Cloud, meeting DORA and PCI-DSS v4.0 regulatory standards, and delivering landing zone readiness within 10 weeks."
|
||||
},
|
||||
{
|
||||
"field": "intent.exclusions",
|
||||
"value": [
|
||||
"Core payment application workload code maintenance and runtime application management",
|
||||
"On-premises infrastructure hardware maintenance beyond Cloud Interconnect physical termination"
|
||||
],
|
||||
"why": "Platform foundation scope excludes application-level core payment workloads and on-premises data centre hardware beyond the Interconnect boundary."
|
||||
},
|
||||
{
|
||||
"field": "operations.change_process",
|
||||
"value": "Changes to the platform foundation are deployed through automated GitHub Actions pipelines with mandatory peer reviews and automated policy validation, without a separate manual change advisory board.",
|
||||
"why": "Catalogue default aligned with request stating GitHub Actions delivery pipelines: automated pipeline deployment with peer review and automated checks."
|
||||
},
|
||||
{
|
||||
"field": "organisation.existing_teams",
|
||||
"value": [
|
||||
{
|
||||
"name": "Central Platform Operations Team",
|
||||
"hours": "24x7",
|
||||
"party": "provider"
|
||||
}
|
||||
],
|
||||
"why": "Catalogue default: all operational roles are newly provided under provider_operated model, with reference to the 24/7 central platform operations team in condition K-8."
|
||||
},
|
||||
{
|
||||
"field": "service_management.tooling",
|
||||
"value": "Google Cloud operations suite (Cloud Monitoring, Cloud Logging, and Cloud Alerting) without a separate external ITSM system.",
|
||||
"why": "Catalogue default: Cloud provider native operations tooling (Cloud Monitoring, Cloud Logging) integrated with alerting."
|
||||
},
|
||||
{
|
||||
"field": "service_levels.priority_1_response_minutes",
|
||||
"value": 30,
|
||||
"why": "Catalogue default response time for Priority 1 critical incidents under 24x7 operational support."
|
||||
},
|
||||
{
|
||||
"field": "service_levels.recovery_time_hours",
|
||||
"value": 4,
|
||||
"why": "Catalogue default aligned with condition K-6 specifying a 4-hour recovery time objective (RTO)."
|
||||
}
|
||||
],
|
||||
"to_decide": [],
|
||||
"to_ask": [
|
||||
{
|
||||
"field": "metadata.client_name",
|
||||
"prompt": "What is metadata.client_name?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.author",
|
||||
"prompt": "What is metadata.author?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.revision",
|
||||
"prompt": "What is metadata.revision?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "intent.requirements",
|
||||
"prompt": "Which requirements for operations has the customer stated outright?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "solution.inherited_risks",
|
||||
"prompt": "What is already known to be unverified or at risk in the solution?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "operations.monitoring",
|
||||
"prompt": "Which monitoring and alerting is already in place or required?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "organisation.headcount_limit",
|
||||
"prompt": "Is there a limit on the number of people operating this?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "commercial.monthly_run_budget",
|
||||
"prompt": "Is there a monthly budget for operating this, in that currency?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "transition.go_live_date",
|
||||
"prompt": "When must the solution be in operation?",
|
||||
"severity": "LOW"
|
||||
}
|
||||
],
|
||||
"not_applicable": []
|
||||
}
|
||||
@@ -0,0 +1,407 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: case-08-landing-zone
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: architecture:case-08-landing-zone-185426
|
||||
status: BASELINE_LOCKED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We are a UK-regulated payment platform expanding into Google Cloud.
|
||||
We need an
|
||||
|
||||
enterprise-grade landing zone ready in under 10 weeks to support our core payments
|
||||
|
||||
engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have
|
||||
|
||||
existing on-premises systems that require private, low-latency connectivity over
|
||||
a
|
||||
|
||||
10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and
|
||||
|
||||
GitHub Actions for our delivery pipelines. Security requires that all egress
|
||||
|
||||
traffic flows through centralised inspection appliances before touching the public
|
||||
|
||||
internet, and customer data must be encrypted with keys we control.'
|
||||
requirements: ask
|
||||
business_outcomes:
|
||||
- outcome: Continuous, highly available, and low-latency operation of the core payments
|
||||
platform foundation
|
||||
target: 99.9% foundation availability with deterministic low latency
|
||||
id: BO-1
|
||||
- id: BO-2
|
||||
target: Zero audit non-conformances
|
||||
outcome: Continuous compliance with DORA and PCI-DSS v4.0 standards using customer-managed
|
||||
encryption keys and centralised egress inspection
|
||||
- outcome: Automated, secure infrastructure release pipelines enabling workload
|
||||
ingestion within 10 weeks
|
||||
target: Operational readiness achieved within 10 weeks
|
||||
id: BO-3
|
||||
exclusions:
|
||||
- Core payment application workload code maintenance and runtime application management
|
||||
- On-premises infrastructure hardware maintenance beyond Cloud Interconnect physical
|
||||
termination
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Resource Hierarchy and Environment Boundary Manager
|
||||
kind: governance
|
||||
product: Resource Manager
|
||||
source_ref: C-1
|
||||
elements:
|
||||
- E-1
|
||||
- E-2
|
||||
- E-3
|
||||
- E-4
|
||||
- E-5
|
||||
- E-6
|
||||
- E-7
|
||||
- E-8
|
||||
- E-9
|
||||
- E-10
|
||||
- E-34
|
||||
- E-35
|
||||
- E-36
|
||||
- E-37
|
||||
- E-38
|
||||
- E-50
|
||||
- E-51
|
||||
- E-55
|
||||
- E-60
|
||||
- id: S-2
|
||||
name: Dedicated Private Hybrid Connectivity Gateway
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
source_ref: C-2
|
||||
elements:
|
||||
- E-11
|
||||
- E-12
|
||||
- E-13
|
||||
- E-14
|
||||
- E-56
|
||||
- E-57
|
||||
- id: S-3
|
||||
name: Centralised Outbound Traffic Inspection and Egress Boundary
|
||||
kind: service
|
||||
product: Palo Alto Networks VM-Series
|
||||
source_ref: C-3
|
||||
elements:
|
||||
- E-15
|
||||
- E-16
|
||||
- E-17
|
||||
- E-18
|
||||
- E-19
|
||||
- E-20
|
||||
- E-47
|
||||
- E-48
|
||||
- E-53
|
||||
- id: S-4
|
||||
name: Centralised Immutable Audit Event and Compliance Log Repository
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
source_ref: C-4
|
||||
elements:
|
||||
- E-21
|
||||
- E-22
|
||||
- E-39
|
||||
- id: S-5
|
||||
name: Automated Infrastructure Orchestration and Deployment Engine
|
||||
kind: service
|
||||
product: GitHub Actions
|
||||
source_ref: C-5
|
||||
elements:
|
||||
- E-42
|
||||
- E-43
|
||||
- id: S-6
|
||||
name: Federated Identity and Role Governance Authority
|
||||
kind: identity
|
||||
product: IAM Workload Identity Federation
|
||||
source_ref: C-6
|
||||
elements:
|
||||
- E-23
|
||||
- E-24
|
||||
- E-25
|
||||
- E-26
|
||||
- E-27
|
||||
- E-45
|
||||
- id: S-7
|
||||
name: Cryptographic Key Lifecycle and Encryption Controller
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
source_ref: C-7
|
||||
elements:
|
||||
- E-28
|
||||
- E-29
|
||||
- E-30
|
||||
- E-31
|
||||
- E-49
|
||||
- E-58
|
||||
- E-59
|
||||
- id: S-8
|
||||
name: Platform Telemetry and Operational Alerting Engine
|
||||
kind: observability
|
||||
product: Cloud Monitoring
|
||||
source_ref: C-8
|
||||
elements:
|
||||
- E-32
|
||||
- E-40
|
||||
- E-41
|
||||
- E-44
|
||||
- E-52
|
||||
- id: S-9
|
||||
name: Financial Governance and Budget Enforcement Monitor
|
||||
kind: billing
|
||||
product: Cloud Billing
|
||||
source_ref: C-9
|
||||
elements:
|
||||
- E-33
|
||||
- E-46
|
||||
- E-54
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
- S-4
|
||||
- S-7
|
||||
condition: The landing zone configuration aligns with DORA operational resiliency
|
||||
guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.
|
||||
source_ref: NFR-8
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-1
|
||||
condition: The secondary region in europe-west1 operates as a warm standby ready
|
||||
to receive failover traffic.
|
||||
source_ref: NFR-9
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-1
|
||||
condition: Data residency is guaranteed within the United Kingdom and European
|
||||
Union.
|
||||
source_ref: NFR-9
|
||||
- id: K-4
|
||||
'on':
|
||||
- S-5
|
||||
condition: Platform foundation is fully provisioned and validated for core payments
|
||||
engine workload ingestion within 10 weeks.
|
||||
source_ref: NFR-10
|
||||
- id: K-5
|
||||
'on':
|
||||
- S-8
|
||||
condition: Platform foundation infrastructure maintains measured monthly availability
|
||||
of at least 99.9%.
|
||||
source_ref: NFR-11
|
||||
- id: K-6
|
||||
'on':
|
||||
- S-8
|
||||
condition: Disaster recovery activation achieves a recovery time objective (RTO)
|
||||
of 4 hours.
|
||||
source_ref: NFR-11
|
||||
- id: K-7
|
||||
'on':
|
||||
- S-8
|
||||
condition: Disaster recovery processes achieve a recovery point objective (RPO)
|
||||
of 1 hour.
|
||||
source_ref: NFR-11
|
||||
- id: K-8
|
||||
'on':
|
||||
- S-8
|
||||
condition: Alert notifications trigger operational incident workflows for the
|
||||
24/7 central platform operations team.
|
||||
source_ref: NFR-12
|
||||
- id: K-9
|
||||
'on':
|
||||
- S-9
|
||||
condition: Monthly cloud foundation expenditure does not exceed the target allocation
|
||||
without operational sign-off.
|
||||
source_ref: NFR-13
|
||||
- id: K-10
|
||||
'on':
|
||||
- S-2
|
||||
condition: Hybrid connection provides deterministic low latency suitable for real-time
|
||||
payment transaction processing.
|
||||
source_ref: NFR-14
|
||||
- id: K-11
|
||||
'on':
|
||||
- S-8
|
||||
condition: Deployments optimize carbon-free energy utilization based on Google
|
||||
Cloud regional CFE scores.
|
||||
source_ref: NFR-15
|
||||
- id: K-12
|
||||
'on':
|
||||
- S-6
|
||||
condition: Permissions are continuously rightsized based on IAM Recommender findings.
|
||||
source_ref: DR-OP-3
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned:
|
||||
- Order and provision the Interconnect carrier circuits
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Changes to the platform foundation are deployed through automated
|
||||
GitHub Actions pipelines with mandatory peer reviews and automated policy validation,
|
||||
without a separate manual change advisory board.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: provider_operated
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams:
|
||||
- name: Central Platform Operations Team
|
||||
hours: 24x7
|
||||
party: provider
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: Google Cloud operations suite (Cloud Monitoring, Cloud Logging, and Cloud
|
||||
Alerting) without a separate external ITSM system.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 30
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
- ISO27001
|
||||
- PCI_DSS_v4
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: ask
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.business_outcomes
|
||||
statement: 'Assumed intent.business_outcomes is [{''outcome'': ''Continuous, highly
|
||||
available, and low-latency operation of the core payments platform foundation'',
|
||||
''target'': ''99.9% foundation availability with deterministic low latency'',
|
||||
''id'': ''BO-1''}, {''id'': ''BO-2'', ''target'': ''Zero audit non-conformances'',
|
||||
''outcome'': ''Continuous compliance with DORA and PCI-DSS v4.0 standards using
|
||||
customer-managed encryption keys and centralised egress inspection''}, {''outcome'':
|
||||
''Automated, secure infrastructure release pipelines enabling workload ingestion
|
||||
within 10 weeks'', ''target'': ''Operational readiness achieved within 10 weeks'',
|
||||
''id'': ''BO-3''}]. Derived from workflow request objectives: running core payment
|
||||
processing reliably in Google Cloud, meeting DORA and PCI-DSS v4.0 regulatory
|
||||
standards, and delivering landing zone readiness within 10 weeks.'
|
||||
impact_if_invalid: Changes what is measured, and what each measure is for.
|
||||
- id: ASSUMP-02
|
||||
field: intent.exclusions
|
||||
statement: Assumed intent.exclusions is ['Core payment application workload code
|
||||
maintenance and runtime application management', 'On-premises infrastructure hardware
|
||||
maintenance beyond Cloud Interconnect physical termination']. Platform foundation
|
||||
scope excludes application-level core payment workloads and on-premises data centre
|
||||
hardware beyond the Interconnect boundary.
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-03
|
||||
field: operations.change_process
|
||||
statement: 'Assumed operations.change_process is Changes to the platform foundation
|
||||
are deployed through automated GitHub Actions pipelines with mandatory peer reviews
|
||||
and automated policy validation, without a separate manual change advisory board..
|
||||
Catalogue default aligned with request stating GitHub Actions delivery pipelines:
|
||||
automated pipeline deployment with peer review and automated checks.'
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-04
|
||||
field: organisation.existing_teams
|
||||
statement: 'Assumed organisation.existing_teams is [{''name'': ''Central Platform
|
||||
Operations Team'', ''hours'': ''24x7'', ''party'': ''provider''}]. Catalogue default:
|
||||
all operational roles are newly provided under provider_operated model, with reference
|
||||
to the 24/7 central platform operations team in condition K-8.'
|
||||
impact_if_invalid: Changes which Roles are new and which are filled.
|
||||
- id: ASSUMP-05
|
||||
field: service_management.tooling
|
||||
statement: 'Assumed service_management.tooling is Google Cloud operations suite
|
||||
(Cloud Monitoring, Cloud Logging, and Cloud Alerting) without a separate external
|
||||
ITSM system.. Catalogue default: Cloud provider native operations tooling (Cloud
|
||||
Monitoring, Cloud Logging) integrated with alerting.'
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
- id: ASSUMP-06
|
||||
field: service_levels.priority_1_response_minutes
|
||||
statement: Assumed service_levels.priority_1_response_minutes is 30. Catalogue default
|
||||
response time for Priority 1 critical incidents under 24x7 operational support.
|
||||
impact_if_invalid: Changes on-call arrangements and staffing.
|
||||
- id: ASSUMP-07
|
||||
field: service_levels.recovery_time_hours
|
||||
statement: Assumed service_levels.recovery_time_hours is 4. Catalogue default aligned
|
||||
with condition K-6 specifying a 4-hour recovery time objective (RTO).
|
||||
impact_if_invalid: Changes continuity arrangements.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: intent.requirements
|
||||
prompt: Which requirements for operations has the customer stated outright?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: commercial.monthly_run_budget
|
||||
prompt: Is there a monthly budget for operating this, in that currency?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: digested
|
||||
commercial.monthly_run_budget: unknown
|
||||
compliance.frameworks: digested
|
||||
engagement.kind: digested
|
||||
intent.business_outcomes: assumed
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: unknown
|
||||
intent.statement: digested
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: digested
|
||||
metadata.revision: unknown
|
||||
metadata.source: digested
|
||||
operations.availability_hours: digested
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: digested
|
||||
organisation.existing_teams: assumed
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: assumed
|
||||
service_levels.recovery_time_hours: assumed
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: digested
|
||||
solution.build.duration_days: digested
|
||||
solution.cloud_provider: digested
|
||||
solution.conditions: digested
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: digested
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 3
|
||||
answered: 0
|
||||
assumed: 7
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
digested: 13
|
||||
@@ -0,0 +1,119 @@
|
||||
{
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
},
|
||||
"conversion": {
|
||||
"from": "USD",
|
||||
"rate": 0.79,
|
||||
"as_of": "2026-10-13"
|
||||
},
|
||||
"roles": [
|
||||
{
|
||||
"role": "R-1",
|
||||
"name": "Platform Operations Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "PL",
|
||||
"level": "engineer",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 125.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 30777
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"name": "Platform Security & Network Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 185.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 41640
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"name": "Platform Reliability Lead",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20.0,
|
||||
"people": 0.1,
|
||||
"cost_per_month": 2212
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"name": "Platform Product Manager",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 30.0,
|
||||
"people": 0.2,
|
||||
"cost_per_month": 3318
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"name": "Platform Enablement Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "Service Provider",
|
||||
"country": "GB",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 70.0,
|
||||
"people": 0.5,
|
||||
"cost_per_month": 5899
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"name": "Customer Stakeholder",
|
||||
"party": "P-1",
|
||||
"party_name": "Customer Platform Team",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 0.0,
|
||||
"people": 0.0,
|
||||
"cost_per_month": null
|
||||
}
|
||||
],
|
||||
"people": 10.8,
|
||||
"cost_per_month": 83846,
|
||||
"by_party": {
|
||||
"P-2": 83846
|
||||
},
|
||||
"by_country": {
|
||||
"PL": 72417,
|
||||
"GB": 11429
|
||||
},
|
||||
"by_capability": {
|
||||
"C-1": 9849,
|
||||
"C-2": 9849,
|
||||
"C-4": 4924,
|
||||
"C-8": 2462,
|
||||
"C-11": 3693,
|
||||
"C-3": 4502,
|
||||
"C-5": 3376,
|
||||
"C-6": 4502,
|
||||
"C-7": 3376,
|
||||
"C-9": 3376,
|
||||
"C-10": 3376,
|
||||
"C-12": 4502,
|
||||
"C-13": 9003,
|
||||
"C-21": 5627,
|
||||
"C-15": 1106,
|
||||
"C-20": 1106,
|
||||
"C-14": 1106,
|
||||
"C-16": 2212,
|
||||
"C-17": 2528,
|
||||
"C-18": 2528,
|
||||
"C-19": 843
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,664 @@
|
||||
{
|
||||
"parties": [
|
||||
{
|
||||
"kind": "customer",
|
||||
"name": "Customer Platform Team",
|
||||
"id": "P-1"
|
||||
},
|
||||
{
|
||||
"kind": "provider",
|
||||
"name": "Service Provider",
|
||||
"id": "P-2"
|
||||
}
|
||||
],
|
||||
"teams": [
|
||||
{
|
||||
"id": "T-1",
|
||||
"purpose": "24/7 central platform operations and foundation management.",
|
||||
"name": "Central Platform Operations Team",
|
||||
"party": "P-2",
|
||||
"type": "platform"
|
||||
},
|
||||
{
|
||||
"purpose": "Platform product management, enablement, and measurement.",
|
||||
"name": "Platform Product & Enablement Team",
|
||||
"party": "P-2",
|
||||
"id": "T-2",
|
||||
"type": "platform"
|
||||
},
|
||||
{
|
||||
"name": "Customer Application Teams",
|
||||
"type": "stream_aligned",
|
||||
"id": "T-3",
|
||||
"purpose": "Core payments engine development and workload deployment.",
|
||||
"party": "P-1"
|
||||
}
|
||||
],
|
||||
"roles": [
|
||||
{
|
||||
"party": "P-2",
|
||||
"name": "Platform Operations Engineer",
|
||||
"hours": "24x7",
|
||||
"team": "T-1",
|
||||
"level": "engineer",
|
||||
"id": "R-1",
|
||||
"country": "PL"
|
||||
},
|
||||
{
|
||||
"level": "senior",
|
||||
"id": "R-2",
|
||||
"country": "PL",
|
||||
"hours": "24x7",
|
||||
"name": "Platform Security & Network Engineer",
|
||||
"party": "P-2",
|
||||
"team": "T-1"
|
||||
},
|
||||
{
|
||||
"hours": "business",
|
||||
"team": "T-1",
|
||||
"id": "R-3",
|
||||
"name": "Platform Reliability Lead",
|
||||
"party": "P-2",
|
||||
"country": "GB",
|
||||
"level": "lead"
|
||||
},
|
||||
{
|
||||
"name": "Platform Product Manager",
|
||||
"level": "lead",
|
||||
"team": "T-2",
|
||||
"country": "GB",
|
||||
"party": "P-2",
|
||||
"id": "R-4",
|
||||
"hours": "business"
|
||||
},
|
||||
{
|
||||
"level": "senior",
|
||||
"id": "R-5",
|
||||
"team": "T-2",
|
||||
"name": "Platform Enablement Engineer",
|
||||
"hours": "business",
|
||||
"party": "P-2",
|
||||
"country": "GB"
|
||||
},
|
||||
{
|
||||
"party": "P-1",
|
||||
"id": "R-6",
|
||||
"country": "GB",
|
||||
"hours": "business",
|
||||
"team": "T-3",
|
||||
"name": "Customer Stakeholder",
|
||||
"level": "lead"
|
||||
}
|
||||
],
|
||||
"interactions": [
|
||||
{
|
||||
"id": "I-1",
|
||||
"purpose": "Customer teams consume platform foundation services and infrastructure via automated pipelines.",
|
||||
"to": "T-1",
|
||||
"mode": "x_as_a_service",
|
||||
"from": "T-3"
|
||||
},
|
||||
{
|
||||
"mode": "facilitating",
|
||||
"purpose": "Enablement team facilitates customer application teams in adopting pipelines and ingesting workloads.",
|
||||
"from": "T-2",
|
||||
"to": "T-3",
|
||||
"id": "I-2"
|
||||
}
|
||||
],
|
||||
"measures": [
|
||||
{
|
||||
"id": "M-1",
|
||||
"framework": "dora-metrics",
|
||||
"target": "On-demand",
|
||||
"name": "Deployment frequency",
|
||||
"outcome": "BO-3",
|
||||
"measured_by": "C-19",
|
||||
"layer": "outcome"
|
||||
},
|
||||
{
|
||||
"target": "High satisfaction",
|
||||
"framework": "space-framework",
|
||||
"id": "M-2",
|
||||
"name": "Developer satisfaction",
|
||||
"outcome": "BO-3",
|
||||
"measured_by": "C-19",
|
||||
"layer": "guardrail"
|
||||
},
|
||||
{
|
||||
"framework": "devex-framework",
|
||||
"name": "Feedback loops",
|
||||
"id": "M-3",
|
||||
"measured_by": "C-19",
|
||||
"target": "< 10 minutes",
|
||||
"outcome": "BO-3",
|
||||
"layer": "leading"
|
||||
},
|
||||
{
|
||||
"target": "99.9% availability",
|
||||
"outcome": "BO-1",
|
||||
"name": "Platform Availability",
|
||||
"id": "M-4",
|
||||
"layer": "service_level",
|
||||
"measured_by": "C-15"
|
||||
},
|
||||
{
|
||||
"name": "Hybrid Network Latency",
|
||||
"outcome": "BO-1",
|
||||
"id": "M-5",
|
||||
"target": "Deterministic low latency",
|
||||
"layer": "service_level",
|
||||
"measured_by": "C-10"
|
||||
},
|
||||
{
|
||||
"name": "Audit Non-conformances",
|
||||
"outcome": "BO-2",
|
||||
"target": "Zero non-conformances",
|
||||
"measured_by": "C-21",
|
||||
"layer": "service_level",
|
||||
"id": "M-6"
|
||||
}
|
||||
],
|
||||
"responsibilities": [
|
||||
{
|
||||
"role": "R-3",
|
||||
"id": "RS-1-A",
|
||||
"capability": "C-1",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-1",
|
||||
"id": "RS-1-R",
|
||||
"kind": "responsible",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"capability": "C-1",
|
||||
"kind": "consulted",
|
||||
"id": "RS-1-C"
|
||||
},
|
||||
{
|
||||
"capability": "C-2",
|
||||
"kind": "accountable",
|
||||
"id": "RS-2-A",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"id": "RS-2-R",
|
||||
"capability": "C-2",
|
||||
"kind": "responsible",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"id": "RS-2-C",
|
||||
"kind": "consulted",
|
||||
"capability": "C-2",
|
||||
"role": "R-6"
|
||||
},
|
||||
{
|
||||
"capability": "C-3",
|
||||
"id": "RS-3-A",
|
||||
"role": "R-3",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"id": "RS-3-R",
|
||||
"kind": "responsible",
|
||||
"capability": "C-3",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"id": "RS-3-C",
|
||||
"role": "R-6",
|
||||
"kind": "consulted",
|
||||
"capability": "C-3"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"id": "RS-4-A",
|
||||
"kind": "accountable",
|
||||
"capability": "C-4"
|
||||
},
|
||||
{
|
||||
"id": "RS-4-R",
|
||||
"role": "R-1",
|
||||
"capability": "C-4",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"id": "RS-4-C",
|
||||
"role": "R-6",
|
||||
"capability": "C-4"
|
||||
},
|
||||
{
|
||||
"id": "RS-5-A",
|
||||
"capability": "C-5",
|
||||
"role": "R-3",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-5",
|
||||
"id": "RS-5-R",
|
||||
"role": "R-2",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-6",
|
||||
"id": "RS-5-C",
|
||||
"capability": "C-5"
|
||||
},
|
||||
{
|
||||
"capability": "C-6",
|
||||
"id": "RS-6-A",
|
||||
"role": "R-3",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-2",
|
||||
"capability": "C-6",
|
||||
"id": "RS-6-R"
|
||||
},
|
||||
{
|
||||
"capability": "C-6",
|
||||
"role": "R-6",
|
||||
"kind": "consulted",
|
||||
"id": "RS-6-C"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"kind": "accountable",
|
||||
"capability": "C-7",
|
||||
"id": "RS-7-A"
|
||||
},
|
||||
{
|
||||
"capability": "C-7",
|
||||
"id": "RS-7-R",
|
||||
"role": "R-2",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-6",
|
||||
"capability": "C-7",
|
||||
"id": "RS-7-C"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"kind": "accountable",
|
||||
"capability": "C-8",
|
||||
"id": "RS-8-A"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-1",
|
||||
"capability": "C-8",
|
||||
"id": "RS-8-R"
|
||||
},
|
||||
{
|
||||
"id": "RS-8-C",
|
||||
"capability": "C-8",
|
||||
"role": "R-6",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"capability": "C-9",
|
||||
"id": "RS-9-A",
|
||||
"role": "R-3",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-9",
|
||||
"id": "RS-9-R",
|
||||
"kind": "responsible",
|
||||
"role": "R-2"
|
||||
},
|
||||
{
|
||||
"capability": "C-9",
|
||||
"kind": "consulted",
|
||||
"role": "R-6",
|
||||
"id": "RS-9-C"
|
||||
},
|
||||
{
|
||||
"capability": "C-10",
|
||||
"role": "R-3",
|
||||
"kind": "accountable",
|
||||
"id": "RS-10-A"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"kind": "responsible",
|
||||
"id": "RS-10-R",
|
||||
"capability": "C-10"
|
||||
},
|
||||
{
|
||||
"id": "RS-10-C",
|
||||
"capability": "C-10",
|
||||
"role": "R-6",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-11",
|
||||
"id": "RS-11-A",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-1",
|
||||
"capability": "C-11",
|
||||
"id": "RS-11-R"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"id": "RS-11-C",
|
||||
"kind": "consulted",
|
||||
"capability": "C-11"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"id": "RS-12-A",
|
||||
"kind": "accountable",
|
||||
"capability": "C-12"
|
||||
},
|
||||
{
|
||||
"capability": "C-12",
|
||||
"role": "R-2",
|
||||
"kind": "responsible",
|
||||
"id": "RS-12-R"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"capability": "C-12",
|
||||
"role": "R-6",
|
||||
"id": "RS-12-C"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-13",
|
||||
"id": "RS-13-A",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-2",
|
||||
"id": "RS-13-R",
|
||||
"capability": "C-13"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"capability": "C-13",
|
||||
"id": "RS-13-C",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"capability": "C-14",
|
||||
"kind": "accountable",
|
||||
"id": "RS-14-A"
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"capability": "C-14",
|
||||
"id": "RS-14-R",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"id": "RS-14-C",
|
||||
"capability": "C-14",
|
||||
"kind": "consulted",
|
||||
"role": "R-6"
|
||||
},
|
||||
{
|
||||
"id": "RS-15-A",
|
||||
"role": "R-3",
|
||||
"kind": "accountable",
|
||||
"capability": "C-15"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"id": "RS-15-R",
|
||||
"capability": "C-15",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"id": "RS-15-C",
|
||||
"kind": "consulted",
|
||||
"capability": "C-15",
|
||||
"role": "R-6"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"id": "RS-16-A",
|
||||
"capability": "C-16",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"capability": "C-16",
|
||||
"id": "RS-16-R",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"capability": "C-16",
|
||||
"id": "RS-16-C",
|
||||
"role": "R-6",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"id": "RS-17-A",
|
||||
"kind": "accountable",
|
||||
"role": "R-4",
|
||||
"capability": "C-17"
|
||||
},
|
||||
{
|
||||
"capability": "C-17",
|
||||
"kind": "responsible",
|
||||
"role": "R-5",
|
||||
"id": "RS-17-R"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-6",
|
||||
"capability": "C-17",
|
||||
"id": "RS-17-C"
|
||||
},
|
||||
{
|
||||
"id": "RS-18-A",
|
||||
"capability": "C-18",
|
||||
"kind": "accountable",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"id": "RS-18-R",
|
||||
"capability": "C-18",
|
||||
"kind": "responsible",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"capability": "C-18",
|
||||
"id": "RS-18-C",
|
||||
"role": "R-6",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"id": "RS-19-A",
|
||||
"role": "R-4",
|
||||
"kind": "accountable",
|
||||
"capability": "C-19"
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"kind": "responsible",
|
||||
"id": "RS-19-R",
|
||||
"capability": "C-19"
|
||||
},
|
||||
{
|
||||
"capability": "C-19",
|
||||
"id": "RS-19-C",
|
||||
"role": "R-6",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"id": "RS-20-A",
|
||||
"role": "R-3",
|
||||
"kind": "accountable",
|
||||
"capability": "C-20"
|
||||
},
|
||||
{
|
||||
"id": "RS-20-R",
|
||||
"role": "R-3",
|
||||
"kind": "responsible",
|
||||
"capability": "C-20"
|
||||
},
|
||||
{
|
||||
"capability": "C-20",
|
||||
"kind": "consulted",
|
||||
"role": "R-6",
|
||||
"id": "RS-20-C"
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"kind": "accountable",
|
||||
"capability": "C-21",
|
||||
"id": "RS-21-A"
|
||||
},
|
||||
{
|
||||
"id": "RS-21-R",
|
||||
"kind": "responsible",
|
||||
"role": "R-2",
|
||||
"capability": "C-21"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-6",
|
||||
"id": "RS-21-C",
|
||||
"capability": "C-21"
|
||||
}
|
||||
],
|
||||
"checks": [
|
||||
{
|
||||
"source": "K-1",
|
||||
"condition": "Regulatory alignment with DORA and PCI-DSS v4.0 is maintained and verified during external audit with zero non-conformances.",
|
||||
"id": "OC-K1",
|
||||
"on": "C-21"
|
||||
},
|
||||
{
|
||||
"condition": "The europe-west1 secondary region is verified as a warm standby ready to receive failover traffic.",
|
||||
"on": "C-9",
|
||||
"source": "K-2",
|
||||
"id": "OC-K2"
|
||||
},
|
||||
{
|
||||
"source": "K-3",
|
||||
"condition": "Data residency remains strictly within the United Kingdom and European Union boundaries.",
|
||||
"id": "OC-K3",
|
||||
"on": "C-7"
|
||||
},
|
||||
{
|
||||
"on": "C-16",
|
||||
"condition": "Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks.",
|
||||
"id": "OC-K4",
|
||||
"source": "K-4"
|
||||
},
|
||||
{
|
||||
"id": "OC-K5",
|
||||
"condition": "Platform foundation infrastructure maintains measured monthly availability of at least 99.9%.",
|
||||
"on": "C-15",
|
||||
"source": "K-5"
|
||||
},
|
||||
{
|
||||
"on": "C-1",
|
||||
"id": "OC-K6",
|
||||
"condition": "Disaster recovery activation achieves a recovery time objective (RTO) of no more than 4 hours.",
|
||||
"source": "K-6"
|
||||
},
|
||||
{
|
||||
"id": "OC-K7",
|
||||
"on": "C-8",
|
||||
"source": "K-7",
|
||||
"condition": "Disaster recovery achieves a recovery point objective (RPO) of no more than 1 hour of data loss."
|
||||
},
|
||||
{
|
||||
"condition": "Alert notifications trigger operational incident workflows for the 24/7 central platform operations team immediately.",
|
||||
"source": "K-8",
|
||||
"id": "OC-K8",
|
||||
"on": "C-2"
|
||||
},
|
||||
{
|
||||
"condition": "Monthly cloud foundation expenditure does not exceed the agreed target allocation without prior operational review and formal sign-off.",
|
||||
"on": "C-14",
|
||||
"id": "OC-K9",
|
||||
"source": "K-9"
|
||||
},
|
||||
{
|
||||
"id": "OC-K10",
|
||||
"on": "C-10",
|
||||
"condition": "Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing.",
|
||||
"source": "K-10"
|
||||
},
|
||||
{
|
||||
"on": "C-10",
|
||||
"condition": "Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores.",
|
||||
"id": "OC-K11",
|
||||
"source": "K-11"
|
||||
},
|
||||
{
|
||||
"condition": "Permissions are continuously rightsized based on IAM Recommender findings.",
|
||||
"source": "K-12",
|
||||
"on": "C-11",
|
||||
"id": "OC-K12"
|
||||
},
|
||||
{
|
||||
"source": "OR-1",
|
||||
"on": "C-1",
|
||||
"condition": "Priority 1 critical incidents on platform foundation components are acknowledged and responded to within 30 minutes, 24 hours a day, 7 days a week.",
|
||||
"id": "OC-OR1"
|
||||
},
|
||||
{
|
||||
"id": "OC-OR2",
|
||||
"condition": "External operational management is consistently provided by the service provider.",
|
||||
"source": "OR-2",
|
||||
"on": "C-4"
|
||||
},
|
||||
{
|
||||
"on": "C-15",
|
||||
"id": "OC-OR8",
|
||||
"source": "OR-8",
|
||||
"condition": "Platform foundation infrastructure maintains measured monthly availability of at least 99.9%, available 24 hours a day, 7 days a week."
|
||||
},
|
||||
{
|
||||
"source": "OR-3",
|
||||
"condition": "Role operates from an approved delivery country.",
|
||||
"id": "OC-OR3-R1",
|
||||
"on": "R-1"
|
||||
},
|
||||
{
|
||||
"on": "R-2",
|
||||
"condition": "Role operates from an approved delivery country.",
|
||||
"id": "OC-OR3-R2",
|
||||
"source": "OR-3"
|
||||
},
|
||||
{
|
||||
"id": "OC-OR3-R3",
|
||||
"source": "OR-3",
|
||||
"on": "R-3",
|
||||
"condition": "Role operates from an approved delivery country."
|
||||
},
|
||||
{
|
||||
"condition": "Role operates from an approved delivery country.",
|
||||
"source": "OR-3",
|
||||
"on": "R-4",
|
||||
"id": "OC-OR3-R4"
|
||||
},
|
||||
{
|
||||
"condition": "Role operates from an approved delivery country.",
|
||||
"id": "OC-OR3-R5",
|
||||
"on": "R-5",
|
||||
"source": "OR-3"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,264 @@
|
||||
{
|
||||
"dry_run": {
|
||||
"verdict": "pass",
|
||||
"evidence": "31 of 31 scenario walk-throughs pass."
|
||||
},
|
||||
"checks": [
|
||||
{
|
||||
"check": "OC-K1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-21 (regulatory-evidence) exists to compile and retain audit evidence for DORA and PCI-DSS v4.0 assessments. Role R-2 is responsible for it."
|
||||
},
|
||||
{
|
||||
"check": "OC-K2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-9 (service-continuity) is tasked with maintaining runbooks and verifying the europe-west1 secondary region warm standby readiness. Role R-2 is responsible."
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-7 (configuration-management) audits actual environment configurations against data residency boundaries (UK and EU). Role R-2 is responsible.",
|
||||
"check": "OC-K3",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-K4",
|
||||
"evidence": "Capability C-16 (platform-product-management) is responsible for ensuring the platform foundation is provisioned and validated within 10 weeks. Role R-4 is responsible."
|
||||
},
|
||||
{
|
||||
"check": "OC-K5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-15 (service-level-management) is set up to track and report on the 99.9% availability requirement. Role R-3 is responsible."
|
||||
},
|
||||
{
|
||||
"check": "OC-K6",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-1 (incident-management) operates 24x7 and takes responsibility for executing disaster recovery activation within the 4-hour RTO at any time of day. Role R-1 provides the 24x7 coverage."
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-8 (backup-and-recovery) ensures backups meet the 1-hour RPO and handles testing restores. Role R-1 is responsible.",
|
||||
"check": "OC-K7",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "OC-K8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-2 (monitoring-and-alerting) operates 24x7 for immediate response to telemetry signals. Role R-1 provides 24x7 coverage."
|
||||
},
|
||||
{
|
||||
"check": "OC-K9",
|
||||
"evidence": "Capability C-14 (cost-management) monitors foundation spend against agreed budgets and manages sign-offs for anomalies. Role R-4 is responsible.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-K10",
|
||||
"evidence": "Capability C-10 (capacity-and-performance) monitors Dedicated Interconnect latency and overall infrastructure capacity for payment processing performance. Role R-2 is responsible."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-K11",
|
||||
"evidence": "Capability C-10 (capacity-and-performance) oversees optimization of workload placements for carbon-free energy (CFE). Role R-2 is responsible."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-K12",
|
||||
"evidence": "Capability C-11 (access-management) executes continuous identity rightsizing based on automated findings. Role R-1 is responsible."
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-1 (incident-management) explicitly offers 24x7 coverage to acknowledge priority 1 incidents within 30 minutes, supported by the 24x7 R-1 role.",
|
||||
"check": "OC-OR1",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-OR2",
|
||||
"evidence": "Capability C-4 (service-request-fulfilment) represents non-fault operational management by the Service Provider. Sourcing model ensures external operational management."
|
||||
},
|
||||
{
|
||||
"check": "OC-OR8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-15 (service-level-management) tracks and reports on the 99.9% availability requirement on a monthly basis. Role R-3 is responsible."
|
||||
},
|
||||
{
|
||||
"check": "OC-OR3-R1",
|
||||
"evidence": "Role R-1 operates from Poland (PL), which is an approved delivery country.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "OC-OR3-R2",
|
||||
"evidence": "Role R-2 operates from Poland (PL), which is an approved delivery country.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Role R-3 operates from the United Kingdom (GB), which is an approved delivery country.",
|
||||
"check": "OC-OR3-R3"
|
||||
},
|
||||
{
|
||||
"evidence": "Role R-4 operates from the United Kingdom (GB), which is an approved delivery country.",
|
||||
"check": "OC-OR3-R4",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-OR3-R5",
|
||||
"evidence": "Role R-5 operates from the United Kingdom (GB), which is an approved delivery country."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Resource Hierarchy and Environment Boundary Manager (S-1) fails at an hour faults are responded to (24x7). Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Resource Hierarchy and Environment Boundary Manager (S-1) must be changed. Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Dedicated Private Hybrid Connectivity Gateway (S-2) fails at an hour faults are responded to (24x7). Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Dedicated Private Hybrid Connectivity Gateway (S-2) must be changed. Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) fails at an hour faults are responded to (24x7). Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) must be changed. Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) fails at an hour faults are responded to (24x7). Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) must be changed. Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Automated Infrastructure Orchestration and Deployment Engine (S-5) fails at an hour faults are responded to (24x7). Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Automated Infrastructure Orchestration and Deployment Engine (S-5) must be changed. Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-6",
|
||||
"verdict": "pass",
|
||||
"evidence": "Federated Identity and Role Governance Authority (S-6) fails at an hour faults are responded to (24x7). Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-6",
|
||||
"verdict": "pass",
|
||||
"evidence": "Federated Identity and Role Governance Authority (S-6) must be changed. Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-7",
|
||||
"verdict": "pass",
|
||||
"evidence": "Cryptographic Key Lifecycle and Encryption Controller (S-7) fails at an hour faults are responded to (24x7). Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-7",
|
||||
"verdict": "pass",
|
||||
"evidence": "Cryptographic Key Lifecycle and Encryption Controller (S-7) must be changed. Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Platform Telemetry and Operational Alerting Engine (S-8) fails at an hour faults are responded to (24x7). Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Platform Telemetry and Operational Alerting Engine (S-8) must be changed. Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-9",
|
||||
"verdict": "pass",
|
||||
"evidence": "Financial Governance and Budget Enforcement Monitor (S-9) fails at an hour faults are responded to (24x7). Platform Operations Engineer responds under C-1, and Platform Reliability Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-9",
|
||||
"verdict": "pass",
|
||||
"evidence": "Financial Governance and Budget Enforcement Monitor (S-9) must be changed. Platform Security & Network Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-1 must be shown to hold: The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit. Check OC-K1 on C-21 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-2 must be shown to hold: The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic. Check OC-K2 on C-9 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-3 must be shown to hold: Data residency is guaranteed within the United Kingdom and European Union. Check OC-K3 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-4 must be shown to hold: Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks. Check OC-K4 on C-16 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-5 must be shown to hold: Platform foundation infrastructure maintains measured monthly availability of at least 99.9%. Check OC-K5 on C-15 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-6",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-6 must be shown to hold: Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours. Check OC-K6 on C-1 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-7",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-7 must be shown to hold: Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour. Check OC-K7 on C-8 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-8 must be shown to hold: Alert notifications trigger operational incident workflows for the 24/7 central platform operations team. Check OC-K8 on C-2 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-9",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-9 must be shown to hold: Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off. Check OC-K9 on C-14 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-10",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-10 must be shown to hold: Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing. Check OC-K10 on C-10 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-11",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-11 must be shown to hold: Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores. Check OC-K11 on C-10 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-12",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-12 must be shown to hold: Permissions are continuously rightsized based on IAM Recommender findings. Check OC-K12 on C-11 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-party-P-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Service Provider cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
}
|
||||
],
|
||||
"proposed_additions": []
|
||||
}
|
||||
@@ -0,0 +1,187 @@
|
||||
[
|
||||
{
|
||||
"id": "C-1",
|
||||
"catalogue": "incident-management",
|
||||
"serves": ["OR-1", "OR-2", "OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 40,
|
||||
"basis": "Handling service disruptions across all platform items. Provides 30-minute response capability for priority 1 issues 24x7."
|
||||
},
|
||||
{
|
||||
"id": "C-2",
|
||||
"catalogue": "monitoring-and-alerting",
|
||||
"serves": ["OR-1", "OR-2", "OR-3", "OR-8"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 30,
|
||||
"basis": "Configuring, tuning, and maintaining telemetry pipelines and automated alerting rules on a continuous basis."
|
||||
},
|
||||
{
|
||||
"id": "C-3",
|
||||
"catalogue": "problem-management",
|
||||
"serves": ["OR-2"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Post-incident analysis and root cause remediation to protect the 99.9% availability target."
|
||||
},
|
||||
{
|
||||
"id": "C-4",
|
||||
"catalogue": "service-request-fulfilment",
|
||||
"serves": ["OR-12"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Managing non-incident requests from customer teams regarding the foundation environment."
|
||||
},
|
||||
{
|
||||
"id": "C-5",
|
||||
"catalogue": "change-enablement",
|
||||
"serves": ["OR-7", "OR-14"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Reviewing infrastructure changes to ensure DORA, PCI-DSS v4.0, and ISO27001 regulatory compliance."
|
||||
},
|
||||
{
|
||||
"id": "C-6",
|
||||
"catalogue": "release-and-deployment",
|
||||
"serves": ["OR-7", "OR-10"],
|
||||
"items": ["S-5"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 25,
|
||||
"basis": "Operating GitHub Actions CI/CD pipelines to ensure timely deployments and carbon-optimised workload placement."
|
||||
},
|
||||
{
|
||||
"id": "C-7",
|
||||
"catalogue": "configuration-management",
|
||||
"serves": ["OR-6", "OR-14"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Enforcing state definition parity across the active and warm standby regions, and auditing configurations."
|
||||
},
|
||||
{
|
||||
"id": "C-8",
|
||||
"catalogue": "backup-and-recovery",
|
||||
"serves": ["OR-4", "OR-5"],
|
||||
"items": ["S-1", "S-4", "S-7"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Configuring backup policies and regularly rehearsing restoration processes for Cloud Storage, KMS, and foundation state to meet RPO/RTO targets."
|
||||
},
|
||||
{
|
||||
"id": "C-9",
|
||||
"catalogue": "service-continuity",
|
||||
"serves": ["OR-4", "OR-5", "OR-6"],
|
||||
"items": ["S-1", "S-2", "S-3", "S-4", "S-5", "S-6", "S-7", "S-8", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Planning and periodic testing of regional failovers to europe-west1 to validate readiness and timing."
|
||||
},
|
||||
{
|
||||
"id": "C-10",
|
||||
"catalogue": "capacity-and-performance",
|
||||
"serves": ["OR-2", "OR-3"],
|
||||
"items": ["S-1", "S-2", "S-3"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Monitoring and optimising Interconnect bandwidth and firewall VM capacity to guarantee deterministic latency and scaling."
|
||||
},
|
||||
{
|
||||
"id": "C-11",
|
||||
"catalogue": "access-management",
|
||||
"serves": ["OR-11", "OR-13"],
|
||||
"items": ["S-1", "S-6"],
|
||||
"hours": "business", "effort_hours_per_month": 20, "basis": "Continuously applying automated IAM rightsizing recommendations and managing operational access from approved countries."
|
||||
},
|
||||
{
|
||||
"id": "C-12",
|
||||
"catalogue": "vulnerability-and-patch-management",
|
||||
"serves": ["OR-14"],
|
||||
"items": ["S-1", "S-3", "S-6"],
|
||||
"hours": "business", "effort_hours_per_month": 25, "basis": "Identifying and remediating CVEs in the cloud environment and Palo Alto VM-Series firewalls to meet compliance standards."
|
||||
},
|
||||
{
|
||||
"id": "C-13",
|
||||
"catalogue": "security-monitoring-and-response",
|
||||
"serves": ["OR-14", "OR-15"],
|
||||
"items": ["S-1", "S-3", "S-4", "S-6", "S-7"],
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 30,
|
||||
"basis": "Watching for and responding to security misconfigurations, anomalies, and attempts to breach residency or perimeter isolation boundaries around the clock."
|
||||
},
|
||||
{
|
||||
"id": "C-14",
|
||||
"catalogue": "cost-management",
|
||||
"serves": ["OR-9"],
|
||||
"items": ["S-1", "S-9"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 15,
|
||||
"basis": "Monitoring cloud expenditure against allocated budgets, and designing and operating automation to enforce hard financial limits and execution stops."
|
||||
},
|
||||
{
|
||||
"id": "C-15",
|
||||
"catalogue": "service-level-management",
|
||||
"serves": ["OR-1", "OR-2", "OR-3"],
|
||||
"items": ["S-1", "S-2", "S-8"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Aggregating and publishing reporting on 99.9% uptime, 30-minute response times, and network latency commitments."
|
||||
},
|
||||
{
|
||||
"id": "C-16",
|
||||
"catalogue": "platform-product-management",
|
||||
"serves": ["OR-7", "OR-12"],
|
||||
"items": ["S-1", "S-5"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Prioritising features and technical debt to ensure the platform foundation supports the core payments engine developers effectively."
|
||||
},
|
||||
{
|
||||
"id": "C-17",
|
||||
"catalogue": "self-service-and-golden-paths",
|
||||
"serves": ["OR-7", "OR-12"],
|
||||
"items": ["S-1", "S-5"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 30,
|
||||
"basis": "Building reusable Terraform modules and GitHub Actions templates to enable developers to deploy securely by default."
|
||||
},
|
||||
{
|
||||
"id": "C-18",
|
||||
"catalogue": "enablement",
|
||||
"serves": ["OR-7", "OR-12"],
|
||||
"items": ["S-1", "S-5"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 25,
|
||||
"basis": "Working directly with the payments engine team to coach them on the new GCP landing zone and CI/CD pipelines."
|
||||
},
|
||||
{
|
||||
"id": "C-19",
|
||||
"catalogue": "delivery-and-developer-experience-measurement",
|
||||
"serves": ["OR-7", "OR-12"],
|
||||
"items": ["S-1", "S-5", "S-8"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Surveying cognitive load and measuring flow metrics across platform deployment activities."
|
||||
},
|
||||
{
|
||||
"id": "C-20",
|
||||
"catalogue": "supplier-management",
|
||||
"serves": ["OR-12", "OR-13"],
|
||||
"items": ["S-2", "S-3"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 10,
|
||||
"basis": "Managing ongoing relationship and escalations with Interconnect carriers and Palo Alto Networks."
|
||||
},
|
||||
{
|
||||
"id": "C-21",
|
||||
"catalogue": "regulatory-evidence",
|
||||
"serves": ["OR-14", "OR-15"],
|
||||
"items": ["S-1", "S-4", "S-7"],
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 20,
|
||||
"basis": "Continually capturing, preserving, and providing the documented audit evidence required to prove compliance with DORA, PCI-DSS v4.0, and ISO27001 to regulators."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,151 @@
|
||||
{
|
||||
"customer_case": "case-08-landing-zone",
|
||||
"execution_id": "case-02-from-architecture-r3",
|
||||
"session_id": "90a6f5db-fafb-4808-99f3-8c9adba4cbf6",
|
||||
"intent_version": 3,
|
||||
"workflow_request": "We are a UK-regulated payment platform expanding into Google Cloud. We need an\nenterprise-grade landing zone ready in under 10 weeks to support our core payments\nengine. All payment processing must comply with DORA and PCI-DSS v4.0. We have\nexisting on-premises systems that require private, low-latency connectivity over a\n10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and\nGitHub Actions for our delivery pipelines. Security requires that all egress\ntraffic flows through centralised inspection appliances before touching the public\ninternet, and customer data must be encrypted with keys we control.",
|
||||
"baseline": null,
|
||||
"overlay_skills": {},
|
||||
"options": {},
|
||||
"sources": {
|
||||
"execution.json": {
|
||||
"sha256": "8bf269deffc8e4bce474bd8d66959c03b04de01dc137eefaf96ead74b46a5a45",
|
||||
"digested": true
|
||||
},
|
||||
"scope.json": {
|
||||
"sha256": "57dc28ab7397f514ef0e83b292fc2165554ac2b516775c973f4965765a9e905f",
|
||||
"digested": true
|
||||
},
|
||||
"requirements.json": {
|
||||
"sha256": "5aecbef9eaea254fb5123bcc1d107b4a7b7d4d45d60d940464d1fde690d2973d",
|
||||
"digested": true
|
||||
},
|
||||
"recommendations.json": {
|
||||
"sha256": "95958b1a107705280d65c9d088bba57352d1f9fa8e67e89b2b3379f78d91cd24",
|
||||
"digested": true
|
||||
},
|
||||
"components.json": {
|
||||
"sha256": "49e47dbfa90a85d086711eb2ba66370c145f13fd3cd3595c1df1366224db392c",
|
||||
"digested": true
|
||||
},
|
||||
"products.json": {
|
||||
"sha256": "75d51cba319f83000e6f85277b0fb21a7ec02faabac332c5d1800c8f512136db",
|
||||
"digested": true
|
||||
},
|
||||
"target-architecture.json": {
|
||||
"sha256": "40879607aaa7041103d8f4d3ba804df8751d2159aa0ce0977d7d821d35f7608b",
|
||||
"digested": true
|
||||
},
|
||||
"verdicts.json": {
|
||||
"sha256": "75e17da790266e94a6775d90857a9b503cacd62fd55c92be2d7a3435de301853",
|
||||
"digested": true
|
||||
},
|
||||
"work-breakdown.json": {
|
||||
"sha256": "057fd1b0ecd6350a6f9f6101b712a61e78fc10d758a67e785a1dca7e1e674dc3",
|
||||
"digested": true
|
||||
}
|
||||
},
|
||||
"scope": {
|
||||
"status": "BASELINE_LOCKED",
|
||||
"readiness": {
|
||||
"supplied": 3,
|
||||
"answered": 0,
|
||||
"assumed": 7,
|
||||
"unknown": 10,
|
||||
"not_applicable": 0,
|
||||
"digested": 13
|
||||
}
|
||||
},
|
||||
"status": "completed",
|
||||
"warnings": [],
|
||||
"risks": [],
|
||||
"assessment": null,
|
||||
"phases": {
|
||||
"scoping": "approved",
|
||||
"operational_requirements": "approved",
|
||||
"operating_model_design": "approved",
|
||||
"validation": "approved",
|
||||
"packaging": "approved"
|
||||
},
|
||||
"final_document": "operating-model-guide.md",
|
||||
"changes": null,
|
||||
"deliverables": {
|
||||
"operating_scope": {
|
||||
"document": "deliverables/operating_scope.md",
|
||||
"attachments": [
|
||||
"scope.json",
|
||||
"scope.yaml"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operational_requirements": {
|
||||
"document": "deliverables/operational_requirements.md",
|
||||
"attachments": [
|
||||
"operational-requirements.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"capability_model": {
|
||||
"document": "deliverables/capability_model.md",
|
||||
"attachments": [
|
||||
"capabilities.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"target_operating_model": {
|
||||
"document": "deliverables/target_operating_model.md",
|
||||
"attachments": [
|
||||
"findings.json",
|
||||
"organisation.mmd",
|
||||
"staffing.json",
|
||||
"target-operating-model.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"validation_results": {
|
||||
"document": "deliverables/validation_results.md",
|
||||
"attachments": [
|
||||
"scenarios.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"operating_model_guide": {
|
||||
"document": "deliverables/operating_model_guide.md",
|
||||
"attachments": [],
|
||||
"status": "submitted"
|
||||
}
|
||||
},
|
||||
"files": [
|
||||
"capabilities.json",
|
||||
"deliverables/capability_model.md",
|
||||
"deliverables/operating_model_guide.md",
|
||||
"deliverables/operating_scope.md",
|
||||
"deliverables/operational_requirements.md",
|
||||
"deliverables/target_operating_model.md",
|
||||
"deliverables/validation_results.md",
|
||||
"findings.json",
|
||||
"operating-model-guide.md",
|
||||
"operational-requirements.json",
|
||||
"organisation.mmd",
|
||||
"scenarios.json",
|
||||
"scope.json",
|
||||
"scope.yaml",
|
||||
"staffing.json",
|
||||
"target-operating-model.json",
|
||||
"verdicts.json"
|
||||
],
|
||||
"staffing": {
|
||||
"people": 16.9,
|
||||
"cost_per_month": 116409,
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
}
|
||||
},
|
||||
"findings": [],
|
||||
"change_request": null,
|
||||
"capability_sources_verified": false
|
||||
}
|
||||
@@ -0,0 +1 @@
|
||||
[]
|
||||
@@ -0,0 +1,288 @@
|
||||
# Operating model guide: Google Cloud Foundation for Core Payments Engine
|
||||
|
||||
## Summary
|
||||
|
||||
This operating model guide governs the operation of the Google Cloud platform foundation supporting the core payments engine, encompassing the landing zone resource hierarchy, dedicated hybrid Cloud Interconnect connectivity, centralised egress traffic inspection appliances, immutable compliance audit logging, automated deployment pipelines, federated identity authority, customer-managed encryption keys, operational telemetry, and financial budget monitors. The platform operates under a provider-operated sourcing model. The Platform Service Provider delivers platform engineering, telemetry, compliance governance, and security operations from delivery locations in the United Kingdom, Poland, and India. The Customer directs platform strategy and product direction through its platform owner, maintaining internal operations liaison and escalation pathways. External suppliers provide the underlying cloud infrastructure, telecommunications carrier circuits, and inspection appliances under provider supplier management.
|
||||
|
||||
Operational support and infrastructure availability are maintained continuously twenty-four hours a day, seven days a week (24x7) for incident triage, telemetry alerting, and perimeter security response, alongside standard business-hours coverage for release deployment, configuration management, and platform enablement. With all validation checks and scenario walk-throughs passing successfully, the reader should look first at the operational assumptions and regulatory baselines documented in this guide—specifically the critical incident acknowledgement target, disaster recovery recovery objectives, and the rate card pricing status—to ensure formal alignment before operational onboarding.
|
||||
|
||||
### Key figures
|
||||
|
||||
- Operated: 9 Items, with 12 Conditions to keep true.
|
||||
- Faults responded to: 24x7 hours.
|
||||
- Capabilities: 21.
|
||||
- People: 16.9. Cost a month: 116,409 GBP, from rate card version `draft-2026-10-13` (placeholder prices: an illustration).
|
||||
- Scenario walk-throughs: 34 of 34 pass.
|
||||
- Business outcomes: 3, 3 shown by a Measure.
|
||||
- Findings for whoever owns the design: 0.
|
||||
|
||||
## Business outcomes
|
||||
|
||||
**BO-1: Deliver an enterprise-grade Google Cloud landing zone within 10 weeks to enable ingestion and operation of the core payments engine.** Target: Foundation ready in under 10 weeks.
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Deployment Lead Time | outcome | dora-metrics | Under 1 hour | Delivery and developer experience measurement | Platform Engineering Lead |
|
||||
| Developer Friction | leading | devex-framework | Low friction reported in monthly surveys | Delivery and developer experience measurement | Platform Engineering Lead |
|
||||
| Team Satisfaction | guardrail | space-framework | Positive quarterly trend | Delivery and developer experience measurement | Platform Engineering Lead |
|
||||
|
||||
**BO-2: Maintain continuous operational resilience and regulatory compliance with DORA and PCI-DSS v4.0 with platform availability of at least 99.9%.** Target: >=99.9% monthly availability and full regulatory audit alignment.
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Platform Availability | service level | | >=99.9% | Service level management | Platform Engineering Lead |
|
||||
| Time to Restore Service | outcome | dora-metrics | Under 4 hours | Service level management | Platform Engineering Lead |
|
||||
|
||||
**BO-3: Ensure secure, low-latency hybrid transaction transport and zero-trust data protection using customer-managed encryption keys.** Target: Deterministic low-latency 10Gbps interconnect and 100% CMEK lifecycle coverage.
|
||||
|
||||
| Measure | Layer | Framework | Target | Measured by | Answerable |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| Interconnect Latency | service level | | Deterministic low latency (<5ms) | Capacity and performance management | Platform Engineering Lead |
|
||||
| CMEK Lifecycle Coverage | guardrail | | 100% coverage | Regulatory evidence and reporting | Compliance & Governance Analyst |
|
||||
|
||||
## What is operated
|
||||
|
||||
| Item | What it is | Kind | Product | From |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| S-1 | Resource Hierarchy and Environment Boundary Manager | governance | Resource Manager | C-1 |
|
||||
| S-2 | Dedicated Private Hybrid Connectivity Gateway | network | Cloud Interconnect | C-2 |
|
||||
| S-3 | Centralised Outbound Traffic Inspection and Egress Boundary | service | Palo Alto Networks VM-Series | C-3 |
|
||||
| S-4 | Centralised Immutable Audit Event and Compliance Log Repository | storage | Cloud Storage | C-4 |
|
||||
| S-5 | Automated Infrastructure Orchestration and Deployment Engine | service | GitHub Actions | C-5 |
|
||||
| S-6 | Federated Identity and Role Governance Authority | identity | IAM Workload Identity Federation | C-6 |
|
||||
| S-7 | Cryptographic Key Lifecycle and Encryption Controller | keys | Cloud KMS | C-7 |
|
||||
| S-8 | Platform Telemetry and Operational Alerting Engine | observability | Cloud Monitoring | C-8 |
|
||||
| S-9 | Financial Governance and Budget Enforcement Monitor | billing | Cloud Billing | C-9 |
|
||||
|
||||
What must be kept true while it is run:
|
||||
|
||||
| Condition | On | What must hold | From |
|
||||
| --- | --- | --- | --- |
|
||||
| K-1 | S-1, S-4, S-7 | The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit. | NFR-8 |
|
||||
| K-2 | S-1 | The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic. | NFR-9 |
|
||||
| K-3 | S-1 | Data residency is guaranteed within the United Kingdom and European Union. | NFR-9 |
|
||||
| K-4 | S-5 | Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks. | NFR-10 |
|
||||
| K-5 | S-8 | Platform foundation infrastructure maintains measured monthly availability of at least 99.9%. | NFR-11 |
|
||||
| K-6 | S-8 | Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours. | NFR-11 |
|
||||
| K-7 | S-8 | Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour. | NFR-11 |
|
||||
| K-8 | S-8 | Alert notifications trigger operational incident workflows for the 24/7 central platform operations team. | NFR-12 |
|
||||
| K-9 | S-9 | Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off. | NFR-13 |
|
||||
| K-10 | S-2 | Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing. | NFR-14 |
|
||||
| K-11 | S-8 | Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores. | NFR-15 |
|
||||
| K-12 | S-6 | Permissions are continuously rightsized based on IAM Recommender findings. | DR-OP-3 |
|
||||
|
||||
## Operational requirements
|
||||
|
||||
| Requirement | Kind | What must be achieved | From |
|
||||
| --- | --- | --- | --- |
|
||||
| OR-1 | service_level | A Priority 1 fault on any platform foundation Item is acknowledged within 30 minutes (as assumed in service_levels.priority_1_response_minutes), 24 hours a day, 7 days a week. | operations.support_hours, service_levels.priority_1_response_minutes |
|
||||
| OR-2 | service_level | The platform foundation infrastructure maintains measured monthly service availability of at least 99.9%, evaluated over continuous 24x7 operating hours. | K-5, operations.availability_hours |
|
||||
| OR-3 | service_level | The dedicated hybrid interconnect maintains deterministic low network latency suitable for real-time payment transaction processing. | K-10 |
|
||||
| OR-4 | service_level | Disaster recovery activation achieves full operational restoration within a recovery time objective (RTO) of 4 hours (as assumed in service_levels.recovery_time_hours). | K-6, service_levels.recovery_time_hours |
|
||||
| OR-5 | service_level | Disaster recovery failover achieves a recovery point objective (RPO) of no more than 1 hour of operational state or configuration loss. | K-7 |
|
||||
| OR-6 | process | The secondary cloud region in europe-west1 is continuously maintained as an active warm standby ready to receive failover traffic immediately upon activation. | K-2 |
|
||||
| OR-7 | process | The platform foundation is fully provisioned, validated, and ready for core payments engine workload ingestion within 10 weeks of initiation. | K-4 |
|
||||
| OR-8 | process | Platform telemetry alert notifications automatically trigger operational incident response workflows without human delay, maintaining active 24x7 coverage. | K-8 |
|
||||
| OR-9 | process | Monthly cloud foundation consumption expenditure is tracked against allocated budgets and prevented from exceeding limits without documented operational sign-off. | K-9 |
|
||||
| OR-10 | process | Platform foundation deployments and workload placements optimize carbon-free energy utilization based on regional carbon-free energy scores. | K-11 |
|
||||
| OR-11 | process | Access permissions across all foundation environments are continuously audited and rightsized based on automated access recommendations. | K-12 |
|
||||
| OR-12 | organisation | Platform foundation operations and infrastructure maintenance are conducted under a provider-operated delivery model. | sourcing.model |
|
||||
| OR-13 | organisation | All operational management and administrative access to the platform foundation are executed exclusively from delivery locations within the United Kingdom, Poland, and India. | sourcing.delivery_countries |
|
||||
| OR-14 | compliance | Platform foundation configurations and audit mechanisms maintain continuous alignment with DORA operational resiliency guidelines, PCI-DSS v4.0 perimeter isolation standards, and ISO27001 information security controls during external audit. | K-1, compliance.frameworks |
|
||||
| OR-15 | compliance | Data residency for all platform foundation storage, audit logs, and cryptographic keys is guaranteed within the United Kingdom and European Union. | K-3 |
|
||||
|
||||
## Capabilities
|
||||
|
||||
| Capability | What it is | Serves | Covers | Hours | Effort a month |
|
||||
| --- | --- | --- | --- | --- | --- |
|
||||
| C-1 | Incident management | OR-1, OR-2, OR-8 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | 24x7 | 40 h |
|
||||
| C-2 | Monitoring and alerting | OR-1, OR-2, OR-3, OR-8 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | 24x7 | 30 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 | business | 20 h |
|
||||
| C-4 | Service request fulfilment | OR-12 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 20 h |
|
||||
| C-5 | Change enablement | OR-7, OR-14 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 15 h |
|
||||
| C-6 | Release and deployment | OR-7, OR-10 | S-5 | business | 25 h |
|
||||
| C-7 | Configuration management | OR-6, OR-14 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 15 h |
|
||||
| C-8 | Backup and recovery | OR-4, OR-5 | S-1, S-4, S-7 | business | 15 h |
|
||||
| C-9 | Service continuity | OR-4, OR-5, OR-6 | S-1, S-2, S-3, S-4, S-5, S-6, S-7, S-8, S-9 | business | 10 h |
|
||||
| C-10 | Capacity and performance management | OR-2, OR-3 | S-1, S-2, S-3 | business | 15 h |
|
||||
| C-11 | Access management | OR-11, OR-13 | S-1, S-6 | business | 20 h |
|
||||
| C-12 | Vulnerability and patch management | OR-14 | S-1, S-3, S-6 | business | 25 h |
|
||||
| C-13 | Security monitoring and response | OR-14, OR-15 | S-1, S-3, S-4, S-6, S-7 | 24x7 | 30 h |
|
||||
| C-14 | Cost management | OR-9 | S-1, S-9 | business | 15 h |
|
||||
| C-15 | Service level management | OR-1, OR-2, OR-3 | S-1, S-2, S-8 | business | 10 h |
|
||||
| C-16 | Platform product management | OR-7, OR-12 | S-1, S-5 | business | 20 h |
|
||||
| C-17 | Self-service and golden paths | OR-7, OR-12 | S-1, S-5 | business | 30 h |
|
||||
| C-18 | Enablement | OR-7, OR-12 | S-1, S-5 | business | 25 h |
|
||||
| C-19 | Delivery and developer experience measurement | OR-7, OR-12 | S-1, S-5, S-8 | business | 10 h |
|
||||
| C-20 | Supplier management | OR-12, OR-13 | S-2, S-3 | business | 10 h |
|
||||
| C-21 | Regulatory evidence and reporting | OR-14, OR-15 | S-1, S-4, S-7 | business | 20 h |
|
||||
|
||||
## Who does what
|
||||
|
||||
| Role | Party | Country | Level | Hours |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Platform Operations Engineer | Platform Service Provider (provider) | IN | engineer | 24x7 |
|
||||
| Platform Reliability Engineer | Platform Service Provider (provider) | PL | senior | 24x7 |
|
||||
| Security Operations Analyst | Platform Service Provider (provider) | PL | senior | 24x7 |
|
||||
| Platform Automation Engineer | Platform Service Provider (provider) | PL | senior | business |
|
||||
| Platform Engineering Lead | Platform Service Provider (provider) | GB | lead | business |
|
||||
| Compliance & Governance Analyst | Platform Service Provider (provider) | GB | senior | business |
|
||||
| Customer Platform Owner | Customer (customer) | GB | lead | business |
|
||||
| Customer Operations Liaison | Customer (customer) | GB | senior | 24x7 |
|
||||
|
||||
The teams, as Team Topologies names their kinds:
|
||||
|
||||
| Team | Kind | Party | Roles | Purpose |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Cloud Platform Foundation Team | platform | Platform Service Provider | Platform Operations Engineer, Platform Reliability Engineer, Platform Automation Engineer, Platform Engineering Lead | Builds, maintains, and reliably operates the enterprise Google Cloud landing zone. |
|
||||
| Platform Security Team | complicated-subsystem | Platform Service Provider | Security Operations Analyst | Provides 24x7 security monitoring, egress inspection analysis, and vulnerability management. |
|
||||
| Customer Central Platform Operations Team | stream-aligned | Customer | Customer Operations Liaison | Receives incident workflows and serves as the internal operations escalation point. |
|
||||
| Customer Platform Owner Team | stream-aligned | Customer | Customer Platform Owner | Provides business context and sets the strategic direction for the platform. |
|
||||
| Platform Governance Team | enabling | Platform Service Provider | Compliance & Governance Analyst | Ensures continuous regulatory compliance with DORA, PCI-DSS v4.0, and ISO27001. |
|
||||
|
||||
How the teams work together:
|
||||
|
||||
| From | To | Mode | Until | Purpose |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Customer Central Platform Operations Team | Cloud Platform Foundation Team | x-as-a-service | | Customer Central Platform Operations consumes incident workflows and alert notifications from the Provider Cloud Platform Foundation. |
|
||||
| Cloud Platform Foundation Team | Platform Security Team | collaboration | PCI-DSS baseline controls are fully automated and verified by external audit, after which they revert to x_as_a_service. | Jointly establish automated security response runbooks and egress inspection rules for PCI-DSS compliance. |
|
||||
| Platform Governance Team | Cloud Platform Foundation Team | facilitating | | Assisting the platform team in integrating regulatory evidence collection into the automated deployment engine. |
|
||||
|
||||
| Capability | Platform Operations Engineer | Platform Reliability Engineer | Security Operations Analyst | Platform Automation Engineer | Platform Engineering Lead | Compliance & Governance Analyst | Customer Platform Owner | Customer Operations Liaison |
|
||||
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
|
||||
| Incident management (C-1) | | R | | | A | | | C |
|
||||
| Monitoring and alerting (C-2) | R | | | | A | | | C |
|
||||
| Problem management (C-3) | | | | R | A | | | C |
|
||||
| Service request fulfilment (C-4) | | | | R | A | | | C |
|
||||
| Change enablement (C-5) | | | | R | A | R | | C |
|
||||
| Release and deployment (C-6) | | | | R | A | | | C |
|
||||
| Configuration management (C-7) | | | | R | A | | | C |
|
||||
| Backup and recovery (C-8) | | | | R | A | | | C |
|
||||
| Service continuity (C-9) | | R | | | A | | | C |
|
||||
| Capacity and performance management (C-10) | | | | R | A | | | C |
|
||||
| Access management (C-11) | | | A/R | | | | | C |
|
||||
| Vulnerability and patch management (C-12) | | | A/R | | | | | C |
|
||||
| Security monitoring and response (C-13) | | | A/R | | | | | C |
|
||||
| Cost management (C-14) | | | | | A | R | | 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/R | | | 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 Operations Engineer | Platform Service Provider | IN | engineer | 24x7 | 30.0 h | 5.0 | 17,034 GBP |
|
||||
| Platform Reliability Engineer | Platform Service Provider | PL | senior | 24x7 | 50.0 h | 5.0 | 41,640 GBP |
|
||||
| Security Operations Analyst | Platform Service Provider | PL | senior | 24x7 | 75.0 h | 5.0 | 41,640 GBP |
|
||||
| Platform Automation Engineer | Platform Service Provider | PL | senior | business | 177.5 h | 1.2 | 8,063 GBP |
|
||||
| Platform Engineering Lead | Platform Service Provider | GB | lead | business | 25.0 h | 0.2 | 2,765 GBP |
|
||||
| Compliance & Governance Analyst | Platform Service Provider | GB | senior | business | 62.5 h | 0.5 | 5,267 GBP |
|
||||
| Customer Platform Owner | Customer | GB | lead | business | 0.0 h | 0.0 | not priced |
|
||||
| Customer Operations Liaison | Customer | GB | senior | business | 0.0 h | 0.0 | not priced |
|
||||
|
||||
16.9 people in all. Cost a month: 116,409 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 | The landing zone configurations are continuously enforced to align with DORA, PCI-DSS v4.0, and ISO27001 standard baselines. | pass | Capability C-7 provides configuration management, enforcing state definition parity and auditing configurations, and supports ensuring compliance standards like DORA, PCI-DSS v4.0, and ISO27001 are continuously enforced. Role R-4 is responsible for it. |
|
||||
| OC-2 | The europe-west1 secondary region is continuously maintained as an active warm standby. | pass | Capability C-9 handles service continuity, which includes planning and periodic testing of regional failovers, ensuring the secondary region is maintained as an active warm standby. Role R-2 is responsible for it. |
|
||||
| OC-3 | Configuration enforces that all data residency, audit logs, and keys remain strictly within the UK and EU. | pass | Capability C-7 enforces configuration state parity and audits configurations, satisfying the condition that data residency, logs, and keys remain in the UK and EU. |
|
||||
| OC-4 | The foundation platform is verified as fully provisioned and ready for core payments engine workload ingestion within 10 weeks. | pass | Capability C-16 prioritises features and technical debt to ensure the platform foundation supports the payments engine developers effectively, meeting the 10-week provisioning timeframe. R-5 is responsible. |
|
||||
| OC-5 | Continuous telemetry verifies that the platform foundation infrastructure maintains at least 99.9% monthly availability. | pass | Capability C-2 provides continuous monitoring and alerting 24x7, maintaining telemetry pipelines to verify the infrastructure maintains 99.9% availability. |
|
||||
| OC-6 | Disaster recovery failover tests verify that the 4-hour RTO can be met. | pass | Capability C-9 handles disaster recovery failover tests to validate readiness and timing to ensure the 4-hour RTO can be met. |
|
||||
| OC-7 | Backup and restore tests verify that the 1-hour RPO for compliance logs and KMS keys is met. | pass | Capability C-8 rehearses restoration processes for Cloud Storage and KMS to verify the 1-hour RPO is met. |
|
||||
| OC-8 | Alert notifications from platform telemetry automatically trigger incident workflows for the 24x7 central platform operations team without human delay. | pass | Capability C-2 configures and maintains automated alerting rules that trigger workflows to the 24x7 customer central platform operations team (R-8 is consulted). |
|
||||
| OC-9 | Cloud consumption expenditure is tracked against budgets, and automation enforces hard limits that prevent overages without operational sign-off. | pass | Capability C-14 designs and operates automation to enforce hard financial limits and execution stops, tracking cloud consumption against budgets. |
|
||||
| OC-10 | The dedicated hybrid interconnect bandwidth and latency are monitored to ensure deterministic low latency for real-time payments. | pass | Capability C-10 monitors and optimises the dedicated hybrid interconnect bandwidth to guarantee deterministic low latency for real-time payments. |
|
||||
| OC-11 | Workload placements in the deployment pipeline are optimized for carbon-free energy utilization. | pass | Capability C-6 operates the deployment pipelines to ensure timely deployments and carbon-optimised workload placement. |
|
||||
| OC-12 | Access permissions are continuously audited and rightsized based on IAM recommender alerts. | pass | Capability C-11 continuously applies automated IAM rightsizing recommendations and manages access from approved countries. |
|
||||
| OC-13 | A Priority 1 fault on the platform foundation is acknowledged within 30 minutes, at any time of day or night. | pass | Capability C-1 provides 24x7 incident management and 30-minute response capability for Priority 1 faults. |
|
||||
| OC-14 | The platform foundation is led and managed by a provider-operated delivery model. | pass | Role R-5 (Platform Engineering Lead) sits within the Provider (P-2) party, managing and directing the platform strategy and operations. |
|
||||
| OC-15 | Operational management is performed exclusively by staff located in the UK, Poland, or India. | pass | All provider operational staff (R-1, R-2, R-3, R-4, R-5, R-6) are based exclusively in the UK, Poland, or India, fulfilling the sourcing requirement. |
|
||||
| OC-16 | Evidence of continuous alignment with DORA, PCI-DSS v4.0, and ISO27001 is gathered for external audit. | pass | Capability C-21 gathers and preserves documented audit evidence to prove compliance with DORA, PCI-DSS v4.0, and ISO27001 to external regulators. |
|
||||
| OC-17 | The UK and EU data residency guarantee is evidenced for all storage, audit logs, and keys. | pass | Capability C-21 captures, preserves, and provides documented audit evidence to external regulators, which includes proving data residency constraints. |
|
||||
|
||||
Each scenario is generated from the operating model and traced through it by code.
|
||||
|
||||
| Scenario | Result | Path |
|
||||
| --- | --- | --- |
|
||||
| Resource Hierarchy and Environment Boundary Manager (S-1) fails at an hour faults are responded to (24x7). | pass | Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable. |
|
||||
| Resource Hierarchy and Environment Boundary Manager (S-1) must be changed. | pass | Platform Automation Engineer makes the change under C-5. |
|
||||
| Dedicated Private Hybrid Connectivity Gateway (S-2) fails at an hour faults are responded to (24x7). | pass | Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable. |
|
||||
| Dedicated Private Hybrid Connectivity Gateway (S-2) must be changed. | pass | Platform Automation Engineer makes the change under C-5. |
|
||||
| Centralised Outbound Traffic Inspection and Egress Boundary (S-3) fails at an hour faults are responded to (24x7). | pass | Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable. |
|
||||
| Centralised Outbound Traffic Inspection and Egress Boundary (S-3) must be changed. | pass | Platform Automation Engineer makes the change under C-5. |
|
||||
| Centralised Immutable Audit Event and Compliance Log Repository (S-4) fails at an hour faults are responded to (24x7). | pass | Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable. |
|
||||
| Centralised Immutable Audit Event and Compliance Log Repository (S-4) must be changed. | pass | Platform Automation Engineer makes the change under C-5. |
|
||||
| Automated Infrastructure Orchestration and Deployment Engine (S-5) fails at an hour faults are responded to (24x7). | pass | Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable. |
|
||||
| Automated Infrastructure Orchestration and Deployment Engine (S-5) must be changed. | pass | Platform Automation Engineer makes the change under C-5. |
|
||||
| Federated Identity and Role Governance Authority (S-6) fails at an hour faults are responded to (24x7). | pass | Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable. |
|
||||
| Federated Identity and Role Governance Authority (S-6) must be changed. | pass | Platform Automation Engineer makes the change under C-5. |
|
||||
| Cryptographic Key Lifecycle and Encryption Controller (S-7) fails at an hour faults are responded to (24x7). | pass | Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable. |
|
||||
| Cryptographic Key Lifecycle and Encryption Controller (S-7) must be changed. | pass | Platform Automation Engineer makes the change under C-5. |
|
||||
| Platform Telemetry and Operational Alerting Engine (S-8) fails at an hour faults are responded to (24x7). | pass | Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable. |
|
||||
| Platform Telemetry and Operational Alerting Engine (S-8) must be changed. | pass | Platform Automation Engineer makes the change under C-5. |
|
||||
| Financial Governance and Budget Enforcement Monitor (S-9) fails at an hour faults are responded to (24x7). | pass | Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable. |
|
||||
| Financial Governance and Budget Enforcement Monitor (S-9) must be changed. | pass | Platform Automation Engineer makes the change under C-5. |
|
||||
| Condition K-1 must be shown to hold: The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit. | pass | Check OC-1 on C-7 keeps it true. |
|
||||
| Condition K-2 must be shown to hold: The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic. | pass | Check OC-2 on C-9 keeps it true. |
|
||||
| Condition K-3 must be shown to hold: Data residency is guaranteed within the United Kingdom and European Union. | pass | Check OC-3 on C-7 keeps it true. |
|
||||
| Condition K-4 must be shown to hold: Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks. | pass | Check OC-4 on C-16 keeps it true. |
|
||||
| Condition K-5 must be shown to hold: Platform foundation infrastructure maintains measured monthly availability of at least 99.9%. | pass | Check OC-5 on C-2 keeps it true. |
|
||||
| Condition K-6 must be shown to hold: Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours. | pass | Check OC-6 on C-9 keeps it true. |
|
||||
| Condition K-7 must be shown to hold: Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour. | pass | Check OC-7 on C-8 keeps it true. |
|
||||
| Condition K-8 must be shown to hold: Alert notifications trigger operational incident workflows for the 24/7 central platform operations team. | pass | Check OC-8 on C-2 keeps it true. |
|
||||
| Condition K-9 must be shown to hold: Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off. | pass | Check OC-9 on C-14 keeps it true. |
|
||||
| Condition K-10 must be shown to hold: Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing. | pass | Check OC-10 on C-10 keeps it true. |
|
||||
| Condition K-11 must be shown to hold: Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores. | pass | Check OC-11 on C-6 keeps it true. |
|
||||
| Condition K-12 must be shown to hold: Permissions are continuously rightsized based on IAM Recommender findings. | pass | Check OC-12 on C-11 keeps it true. |
|
||||
| Platform Service Provider cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
|
||||
| Google Cloud cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
|
||||
| Network Carrier cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
|
||||
| External Firewall Vendor cannot be reached. | pass | Every Capability it is answerable for has a Role in another Party to turn to. |
|
||||
|
||||
## Findings and open questions
|
||||
|
||||
No findings: the solution provides what operating it needs.
|
||||
|
||||
Assumed for the customer, and open to change when they answer:
|
||||
|
||||
- `intent.business_outcomes`: {'target': 'Foundation ready in under 10 weeks', 'id': 'BO-1', 'outcome': 'Deliver an enterprise-grade Google Cloud landing zone within 10 weeks to enable ingestion and operation of the core payments engine.'}, {'outcome': 'Maintain continuous operational resilience and regulatory compliance with DORA and PCI-DSS v4.0 with platform availability of at least 99.9%.', 'target': '>=99.9% monthly availability and full regulatory audit alignment', 'id': 'BO-2'}, {'target': 'Deterministic low-latency 10Gbps interconnect and 100% CMEK lifecycle coverage', 'id': 'BO-3', 'outcome': 'Ensure secure, low-latency hybrid transaction transport and zero-trust data protection using customer-managed encryption keys.'}. Derived from the workflow request stating the need for an enterprise-grade landing zone ready in under 10 weeks to support the core payments engine, complying with DORA and PCI-DSS v4.0, with secure hybrid connectivity and customer-controlled encryption.
|
||||
- `intent.exclusions`: Core payments engine application-level development, maintenance, and transaction processing logic, On-premises data centre infrastructure and systems beyond the Cloud Interconnect demarcation, Physical telecom carrier circuit ordering and provisioning (customer-owned build item). Derived from engagement kind (platform foundation) and workflow request: application-level workloads, on-prem systems, and physical circuit provisioning are excluded from platform operations.
|
||||
- `operations.change_process`: Automated CI/CD pipelines via GitHub Actions with peer review and automated policy checks; standard operational changes deployed without a separate manual CAB.. Derived from request stating GitHub Actions delivery pipelines and catalogue default guidance.
|
||||
- `organisation.existing_teams`: {'party': 'customer', 'name': 'Central Platform Operations Team', 'hours': '24x7'}. Derived from condition K-8 noting alerting to the 24/7 central platform operations team, alongside provider-operated landing zone model.
|
||||
- `service_management.tooling`: Google Cloud operations suite (Cloud Monitoring and Cloud Logging) integrated with native alerting workflows and GitHub Actions.. Catalogue default guidance leveraging Google Cloud operations suite and GitHub Actions specified in request.
|
||||
- `service_levels.priority_1_response_minutes`: 30. Standard catalogue default for 24x7 critical infrastructure response.
|
||||
- `service_levels.recovery_time_hours`: 4. Matches condition K-6 disaster recovery RTO requirement of 4 hours and catalogue default.
|
||||
|
||||
## 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.
|
||||
@@ -0,0 +1,126 @@
|
||||
[
|
||||
{
|
||||
"id": "OR-1",
|
||||
"kind": "service_level",
|
||||
"statement": "A Priority 1 fault on any platform foundation Item is acknowledged within 30 minutes (as assumed in service_levels.priority_1_response_minutes), 24 hours a day, 7 days a week.",
|
||||
"source": [
|
||||
"operations.support_hours",
|
||||
"service_levels.priority_1_response_minutes"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-2",
|
||||
"kind": "service_level",
|
||||
"statement": "The platform foundation infrastructure maintains measured monthly service availability of at least 99.9%, evaluated over continuous 24x7 operating hours.",
|
||||
"source": [
|
||||
"K-5",
|
||||
"operations.availability_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-3",
|
||||
"kind": "service_level",
|
||||
"statement": "The dedicated hybrid interconnect maintains deterministic low network latency suitable for real-time payment transaction processing.",
|
||||
"source": [
|
||||
"K-10"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-4",
|
||||
"kind": "service_level",
|
||||
"statement": "Disaster recovery activation achieves full operational restoration within a recovery time objective (RTO) of 4 hours (as assumed in service_levels.recovery_time_hours).",
|
||||
"source": [
|
||||
"K-6",
|
||||
"service_levels.recovery_time_hours"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-5",
|
||||
"kind": "service_level",
|
||||
"statement": "Disaster recovery failover achieves a recovery point objective (RPO) of no more than 1 hour of operational state or configuration loss.",
|
||||
"source": [
|
||||
"K-7"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-6",
|
||||
"kind": "process",
|
||||
"statement": "The secondary cloud region in europe-west1 is continuously maintained as an active warm standby ready to receive failover traffic immediately upon activation.",
|
||||
"source": [
|
||||
"K-2"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-7",
|
||||
"kind": "process",
|
||||
"statement": "The platform foundation is fully provisioned, validated, and ready for core payments engine workload ingestion within 10 weeks of initiation.",
|
||||
"source": [
|
||||
"K-4"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-8",
|
||||
"kind": "process",
|
||||
"statement": "Platform telemetry alert notifications automatically trigger operational incident response workflows without human delay, maintaining active 24x7 coverage.",
|
||||
"source": [
|
||||
"K-8"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-9",
|
||||
"kind": "process",
|
||||
"statement": "Monthly cloud foundation consumption expenditure is tracked against allocated budgets and prevented from exceeding limits without documented operational sign-off.",
|
||||
"source": [
|
||||
"K-9"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-10",
|
||||
"kind": "process",
|
||||
"statement": "Platform foundation deployments and workload placements optimize carbon-free energy utilization based on regional carbon-free energy scores.",
|
||||
"source": [
|
||||
"K-11"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-11",
|
||||
"kind": "process",
|
||||
"statement": "Access permissions across all foundation environments are continuously audited and rightsized based on automated access recommendations.",
|
||||
"source": [
|
||||
"K-12"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-12",
|
||||
"kind": "organisation",
|
||||
"statement": "Platform foundation operations and infrastructure maintenance are conducted under a provider-operated delivery model.",
|
||||
"source": [
|
||||
"sourcing.model"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-13",
|
||||
"kind": "organisation",
|
||||
"statement": "All operational management and administrative access to the platform foundation are executed exclusively from delivery locations within the United Kingdom, Poland, and India.",
|
||||
"source": [
|
||||
"sourcing.delivery_countries"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-14",
|
||||
"kind": "compliance",
|
||||
"statement": "Platform foundation configurations and audit mechanisms maintain continuous alignment with DORA operational resiliency guidelines, PCI-DSS v4.0 perimeter isolation standards, and ISO27001 information security controls during external audit.",
|
||||
"source": [
|
||||
"K-1",
|
||||
"compliance.frameworks"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "OR-15",
|
||||
"kind": "compliance",
|
||||
"statement": "Data residency for all platform foundation storage, audit logs, and cryptographic keys is guaranteed within the United Kingdom and European Union.",
|
||||
"source": [
|
||||
"K-3"
|
||||
]
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,32 @@
|
||||
flowchart TB
|
||||
subgraph P_1["Customer (customer)"]
|
||||
subgraph T_3["Customer Central Platform Operations Team (stream-aligned team)"]
|
||||
R_8["Customer Operations Liaison<br/>GB, senior, 24x7"]
|
||||
end
|
||||
subgraph T_4["Customer Platform Owner Team (stream-aligned team)"]
|
||||
R_7["Customer Platform Owner<br/>GB, lead, business"]
|
||||
end
|
||||
end
|
||||
subgraph P_2["Platform Service Provider (provider)"]
|
||||
subgraph T_1["Cloud Platform Foundation Team (platform team)"]
|
||||
R_1["Platform Operations Engineer<br/>IN, engineer, 24x7"]
|
||||
R_2["Platform Reliability Engineer<br/>PL, senior, 24x7"]
|
||||
R_4["Platform Automation Engineer<br/>PL, senior, business"]
|
||||
R_5["Platform Engineering Lead<br/>GB, lead, business"]
|
||||
end
|
||||
subgraph T_2["Platform Security Team (complicated-subsystem team)"]
|
||||
R_3["Security Operations Analyst<br/>PL, senior, 24x7"]
|
||||
end
|
||||
subgraph T_5["Platform Governance Team (enabling team)"]
|
||||
R_6["Compliance & Governance Analyst<br/>GB, senior, business"]
|
||||
end
|
||||
end
|
||||
subgraph P_3["Google Cloud (cloud_provider)"]
|
||||
end
|
||||
subgraph P_4["Network Carrier (supplier)"]
|
||||
end
|
||||
subgraph P_5["External Firewall Vendor (supplier)"]
|
||||
end
|
||||
T_3 -- "x-as-a-service" --> T_1
|
||||
T_1 -- "collaboration until PCI-DSS baseline controls are fully automated and verified by external audit, after which they revert to x_as_a_service." --> T_2
|
||||
T_5 -- "facilitating" --> T_1
|
||||
@@ -0,0 +1,240 @@
|
||||
[
|
||||
{
|
||||
"id": "SC-fault-S-1",
|
||||
"scenario": "Resource Hierarchy and Environment Boundary Manager (S-1) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-1",
|
||||
"scenario": "Resource Hierarchy and Environment Boundary Manager (S-1) must be changed.",
|
||||
"about": "S-1",
|
||||
"passes": true,
|
||||
"path": "Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-2",
|
||||
"scenario": "Dedicated Private Hybrid Connectivity Gateway (S-2) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-2",
|
||||
"scenario": "Dedicated Private Hybrid Connectivity Gateway (S-2) must be changed.",
|
||||
"about": "S-2",
|
||||
"passes": true,
|
||||
"path": "Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-3",
|
||||
"scenario": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-3",
|
||||
"scenario": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) must be changed.",
|
||||
"about": "S-3",
|
||||
"passes": true,
|
||||
"path": "Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-4",
|
||||
"scenario": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-4",
|
||||
"scenario": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) must be changed.",
|
||||
"about": "S-4",
|
||||
"passes": true,
|
||||
"path": "Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-5",
|
||||
"scenario": "Automated Infrastructure Orchestration and Deployment Engine (S-5) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-5",
|
||||
"passes": true,
|
||||
"path": "Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-5",
|
||||
"scenario": "Automated Infrastructure Orchestration and Deployment Engine (S-5) must be changed.",
|
||||
"about": "S-5",
|
||||
"passes": true,
|
||||
"path": "Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-6",
|
||||
"scenario": "Federated Identity and Role Governance Authority (S-6) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-6",
|
||||
"passes": true,
|
||||
"path": "Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-6",
|
||||
"scenario": "Federated Identity and Role Governance Authority (S-6) must be changed.",
|
||||
"about": "S-6",
|
||||
"passes": true,
|
||||
"path": "Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-7",
|
||||
"scenario": "Cryptographic Key Lifecycle and Encryption Controller (S-7) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-7",
|
||||
"passes": true,
|
||||
"path": "Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-7",
|
||||
"scenario": "Cryptographic Key Lifecycle and Encryption Controller (S-7) must be changed.",
|
||||
"about": "S-7",
|
||||
"passes": true,
|
||||
"path": "Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-8",
|
||||
"scenario": "Platform Telemetry and Operational Alerting Engine (S-8) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-8",
|
||||
"passes": true,
|
||||
"path": "Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-8",
|
||||
"scenario": "Platform Telemetry and Operational Alerting Engine (S-8) must be changed.",
|
||||
"about": "S-8",
|
||||
"passes": true,
|
||||
"path": "Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-fault-S-9",
|
||||
"scenario": "Financial Governance and Budget Enforcement Monitor (S-9) fails at an hour faults are responded to (24x7).",
|
||||
"about": "S-9",
|
||||
"passes": true,
|
||||
"path": "Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"id": "SC-change-S-9",
|
||||
"scenario": "Financial Governance and Budget Enforcement Monitor (S-9) must be changed.",
|
||||
"about": "S-9",
|
||||
"passes": true,
|
||||
"path": "Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-1",
|
||||
"scenario": "Condition K-1 must be shown to hold: The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.",
|
||||
"about": "K-1",
|
||||
"passes": true,
|
||||
"path": "Check OC-1 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-2",
|
||||
"scenario": "Condition K-2 must be shown to hold: The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic.",
|
||||
"about": "K-2",
|
||||
"passes": true,
|
||||
"path": "Check OC-2 on C-9 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-3",
|
||||
"scenario": "Condition K-3 must be shown to hold: Data residency is guaranteed within the United Kingdom and European Union.",
|
||||
"about": "K-3",
|
||||
"passes": true,
|
||||
"path": "Check OC-3 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-4",
|
||||
"scenario": "Condition K-4 must be shown to hold: Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks.",
|
||||
"about": "K-4",
|
||||
"passes": true,
|
||||
"path": "Check OC-4 on C-16 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-5",
|
||||
"scenario": "Condition K-5 must be shown to hold: Platform foundation infrastructure maintains measured monthly availability of at least 99.9%.",
|
||||
"about": "K-5",
|
||||
"passes": true,
|
||||
"path": "Check OC-5 on C-2 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-6",
|
||||
"scenario": "Condition K-6 must be shown to hold: Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours.",
|
||||
"about": "K-6",
|
||||
"passes": true,
|
||||
"path": "Check OC-6 on C-9 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-7",
|
||||
"scenario": "Condition K-7 must be shown to hold: Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour.",
|
||||
"about": "K-7",
|
||||
"passes": true,
|
||||
"path": "Check OC-7 on C-8 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-8",
|
||||
"scenario": "Condition K-8 must be shown to hold: Alert notifications trigger operational incident workflows for the 24/7 central platform operations team.",
|
||||
"about": "K-8",
|
||||
"passes": true,
|
||||
"path": "Check OC-8 on C-2 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-9",
|
||||
"scenario": "Condition K-9 must be shown to hold: Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off.",
|
||||
"about": "K-9",
|
||||
"passes": true,
|
||||
"path": "Check OC-9 on C-14 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-10",
|
||||
"scenario": "Condition K-10 must be shown to hold: Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing.",
|
||||
"about": "K-10",
|
||||
"passes": true,
|
||||
"path": "Check OC-10 on C-10 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-11",
|
||||
"scenario": "Condition K-11 must be shown to hold: Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores.",
|
||||
"about": "K-11",
|
||||
"passes": true,
|
||||
"path": "Check OC-11 on C-6 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-condition-K-12",
|
||||
"scenario": "Condition K-12 must be shown to hold: Permissions are continuously rightsized based on IAM Recommender findings.",
|
||||
"about": "K-12",
|
||||
"passes": true,
|
||||
"path": "Check OC-12 on C-11 keeps it true."
|
||||
},
|
||||
{
|
||||
"id": "SC-party-P-2",
|
||||
"scenario": "Platform Service Provider cannot be reached.",
|
||||
"about": "P-2",
|
||||
"passes": true,
|
||||
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"id": "SC-party-P-3",
|
||||
"scenario": "Google Cloud cannot be reached.",
|
||||
"about": "P-3",
|
||||
"passes": true,
|
||||
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"id": "SC-party-P-4",
|
||||
"scenario": "Network Carrier cannot be reached.",
|
||||
"about": "P-4",
|
||||
"passes": true,
|
||||
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"id": "SC-party-P-5",
|
||||
"scenario": "External Firewall Vendor cannot be reached.",
|
||||
"about": "P-5",
|
||||
"passes": true,
|
||||
"path": "Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,402 @@
|
||||
{
|
||||
"kind": "platform_foundation",
|
||||
"stated": {
|
||||
"engagement": {
|
||||
"kind": "platform_foundation"
|
||||
},
|
||||
"intent": {
|
||||
"statement": "We are a UK-regulated payment platform expanding into Google Cloud. We need an\nenterprise-grade landing zone ready in under 10 weeks to support our core payments\nengine. All payment processing must comply with DORA and PCI-DSS v4.0. We have\nexisting on-premises systems that require private, low-latency connectivity over a\n10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and\nGitHub Actions for our delivery pipelines. Security requires that all egress\ntraffic flows through centralised inspection appliances before touching the public\ninternet, and customer data must be encrypted with keys we control."
|
||||
},
|
||||
"solution": {
|
||||
"cloud_provider": "gcp",
|
||||
"items": [
|
||||
{
|
||||
"id": "S-1",
|
||||
"name": "Resource Hierarchy and Environment Boundary Manager",
|
||||
"kind": "governance",
|
||||
"product": "Resource Manager",
|
||||
"source_ref": "C-1",
|
||||
"elements": [
|
||||
"E-1",
|
||||
"E-2",
|
||||
"E-3",
|
||||
"E-4",
|
||||
"E-5",
|
||||
"E-6",
|
||||
"E-7",
|
||||
"E-8",
|
||||
"E-9",
|
||||
"E-10",
|
||||
"E-34",
|
||||
"E-35",
|
||||
"E-36",
|
||||
"E-37",
|
||||
"E-38",
|
||||
"E-50",
|
||||
"E-51",
|
||||
"E-55",
|
||||
"E-60"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-2",
|
||||
"name": "Dedicated Private Hybrid Connectivity Gateway",
|
||||
"kind": "network",
|
||||
"product": "Cloud Interconnect",
|
||||
"source_ref": "C-2",
|
||||
"elements": [
|
||||
"E-11",
|
||||
"E-12",
|
||||
"E-13",
|
||||
"E-14",
|
||||
"E-56",
|
||||
"E-57"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-3",
|
||||
"name": "Centralised Outbound Traffic Inspection and Egress Boundary",
|
||||
"kind": "service",
|
||||
"product": "Palo Alto Networks VM-Series",
|
||||
"source_ref": "C-3",
|
||||
"elements": [
|
||||
"E-15",
|
||||
"E-16",
|
||||
"E-17",
|
||||
"E-18",
|
||||
"E-19",
|
||||
"E-20",
|
||||
"E-47",
|
||||
"E-48",
|
||||
"E-53"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-4",
|
||||
"name": "Centralised Immutable Audit Event and Compliance Log Repository",
|
||||
"kind": "storage",
|
||||
"product": "Cloud Storage",
|
||||
"source_ref": "C-4",
|
||||
"elements": [
|
||||
"E-21",
|
||||
"E-22",
|
||||
"E-39"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-5",
|
||||
"name": "Automated Infrastructure Orchestration and Deployment Engine",
|
||||
"kind": "service",
|
||||
"product": "GitHub Actions",
|
||||
"source_ref": "C-5",
|
||||
"elements": [
|
||||
"E-42",
|
||||
"E-43"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-6",
|
||||
"name": "Federated Identity and Role Governance Authority",
|
||||
"kind": "identity",
|
||||
"product": "IAM Workload Identity Federation",
|
||||
"source_ref": "C-6",
|
||||
"elements": [
|
||||
"E-23",
|
||||
"E-24",
|
||||
"E-25",
|
||||
"E-26",
|
||||
"E-27",
|
||||
"E-45"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-7",
|
||||
"name": "Cryptographic Key Lifecycle and Encryption Controller",
|
||||
"kind": "keys",
|
||||
"product": "Cloud KMS",
|
||||
"source_ref": "C-7",
|
||||
"elements": [
|
||||
"E-28",
|
||||
"E-29",
|
||||
"E-30",
|
||||
"E-31",
|
||||
"E-49",
|
||||
"E-58",
|
||||
"E-59"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-8",
|
||||
"name": "Platform Telemetry and Operational Alerting Engine",
|
||||
"kind": "observability",
|
||||
"product": "Cloud Monitoring",
|
||||
"source_ref": "C-8",
|
||||
"elements": [
|
||||
"E-32",
|
||||
"E-40",
|
||||
"E-41",
|
||||
"E-44",
|
||||
"E-52"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "S-9",
|
||||
"name": "Financial Governance and Budget Enforcement Monitor",
|
||||
"kind": "billing",
|
||||
"product": "Cloud Billing",
|
||||
"source_ref": "C-9",
|
||||
"elements": [
|
||||
"E-33",
|
||||
"E-46",
|
||||
"E-54"
|
||||
]
|
||||
}
|
||||
],
|
||||
"conditions": [
|
||||
{
|
||||
"id": "K-1",
|
||||
"on": [
|
||||
"S-1",
|
||||
"S-4",
|
||||
"S-7"
|
||||
],
|
||||
"condition": "The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.",
|
||||
"source_ref": "NFR-8"
|
||||
},
|
||||
{
|
||||
"id": "K-2",
|
||||
"on": [
|
||||
"S-1"
|
||||
],
|
||||
"condition": "The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic.",
|
||||
"source_ref": "NFR-9"
|
||||
},
|
||||
{
|
||||
"id": "K-3",
|
||||
"on": [
|
||||
"S-1"
|
||||
],
|
||||
"condition": "Data residency is guaranteed within the United Kingdom and European Union.",
|
||||
"source_ref": "NFR-9"
|
||||
},
|
||||
{
|
||||
"id": "K-4",
|
||||
"on": [
|
||||
"S-5"
|
||||
],
|
||||
"condition": "Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks.",
|
||||
"source_ref": "NFR-10"
|
||||
},
|
||||
{
|
||||
"id": "K-5",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Platform foundation infrastructure maintains measured monthly availability of at least 99.9%.",
|
||||
"source_ref": "NFR-11"
|
||||
},
|
||||
{
|
||||
"id": "K-6",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours.",
|
||||
"source_ref": "NFR-11"
|
||||
},
|
||||
{
|
||||
"id": "K-7",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour.",
|
||||
"source_ref": "NFR-11"
|
||||
},
|
||||
{
|
||||
"id": "K-8",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Alert notifications trigger operational incident workflows for the 24/7 central platform operations team.",
|
||||
"source_ref": "NFR-12"
|
||||
},
|
||||
{
|
||||
"id": "K-9",
|
||||
"on": [
|
||||
"S-9"
|
||||
],
|
||||
"condition": "Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off.",
|
||||
"source_ref": "NFR-13"
|
||||
},
|
||||
{
|
||||
"id": "K-10",
|
||||
"on": [
|
||||
"S-2"
|
||||
],
|
||||
"condition": "Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing.",
|
||||
"source_ref": "NFR-14"
|
||||
},
|
||||
{
|
||||
"id": "K-11",
|
||||
"on": [
|
||||
"S-8"
|
||||
],
|
||||
"condition": "Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores.",
|
||||
"source_ref": "NFR-15"
|
||||
},
|
||||
{
|
||||
"id": "K-12",
|
||||
"on": [
|
||||
"S-6"
|
||||
],
|
||||
"condition": "Permissions are continuously rightsized based on IAM Recommender findings.",
|
||||
"source_ref": "DR-OP-3"
|
||||
}
|
||||
],
|
||||
"build": {
|
||||
"duration_days": 36,
|
||||
"customer_owned": [
|
||||
"Order and provision the Interconnect carrier circuits"
|
||||
]
|
||||
}
|
||||
},
|
||||
"operations": {
|
||||
"support_hours": "24x7",
|
||||
"availability_hours": "24x7"
|
||||
},
|
||||
"sourcing": {
|
||||
"model": "provider_operated",
|
||||
"delivery_countries": [
|
||||
"GB",
|
||||
"PL",
|
||||
"IN"
|
||||
]
|
||||
},
|
||||
"compliance": {
|
||||
"frameworks": [
|
||||
"DORA",
|
||||
"ISO27001",
|
||||
"PCI_DSS_v4"
|
||||
]
|
||||
},
|
||||
"commercial": {
|
||||
"currency": "GBP"
|
||||
}
|
||||
},
|
||||
"binding": [
|
||||
"operations.support_hours",
|
||||
"sourcing.model",
|
||||
"sourcing.delivery_countries"
|
||||
],
|
||||
"assumed": [
|
||||
{
|
||||
"field": "intent.business_outcomes",
|
||||
"value": [
|
||||
{
|
||||
"target": "Foundation ready in under 10 weeks",
|
||||
"id": "BO-1",
|
||||
"outcome": "Deliver an enterprise-grade Google Cloud landing zone within 10 weeks to enable ingestion and operation of the core payments engine."
|
||||
},
|
||||
{
|
||||
"outcome": "Maintain continuous operational resilience and regulatory compliance with DORA and PCI-DSS v4.0 with platform availability of at least 99.9%.",
|
||||
"target": ">=99.9% monthly availability and full regulatory audit alignment",
|
||||
"id": "BO-2"
|
||||
},
|
||||
{
|
||||
"target": "Deterministic low-latency 10Gbps interconnect and 100% CMEK lifecycle coverage",
|
||||
"id": "BO-3",
|
||||
"outcome": "Ensure secure, low-latency hybrid transaction transport and zero-trust data protection using customer-managed encryption keys."
|
||||
}
|
||||
],
|
||||
"why": "Derived from the workflow request stating the need for an enterprise-grade landing zone ready in under 10 weeks to support the core payments engine, complying with DORA and PCI-DSS v4.0, with secure hybrid connectivity and customer-controlled encryption."
|
||||
},
|
||||
{
|
||||
"field": "intent.exclusions",
|
||||
"value": [
|
||||
"Core payments engine application-level development, maintenance, and transaction processing logic",
|
||||
"On-premises data centre infrastructure and systems beyond the Cloud Interconnect demarcation",
|
||||
"Physical telecom carrier circuit ordering and provisioning (customer-owned build item)"
|
||||
],
|
||||
"why": "Derived from engagement kind (platform foundation) and workflow request: application-level workloads, on-prem systems, and physical circuit provisioning are excluded from platform operations."
|
||||
},
|
||||
{
|
||||
"field": "operations.change_process",
|
||||
"value": "Automated CI/CD pipelines via GitHub Actions with peer review and automated policy checks; standard operational changes deployed without a separate manual CAB.",
|
||||
"why": "Derived from request stating GitHub Actions delivery pipelines and catalogue default guidance."
|
||||
},
|
||||
{
|
||||
"field": "organisation.existing_teams",
|
||||
"value": [
|
||||
{
|
||||
"party": "customer",
|
||||
"name": "Central Platform Operations Team",
|
||||
"hours": "24x7"
|
||||
}
|
||||
],
|
||||
"why": "Derived from condition K-8 noting alerting to the 24/7 central platform operations team, alongside provider-operated landing zone model."
|
||||
},
|
||||
{
|
||||
"field": "service_management.tooling",
|
||||
"value": "Google Cloud operations suite (Cloud Monitoring and Cloud Logging) integrated with native alerting workflows and GitHub Actions.",
|
||||
"why": "Catalogue default guidance leveraging Google Cloud operations suite and GitHub Actions specified in request."
|
||||
},
|
||||
{
|
||||
"field": "service_levels.priority_1_response_minutes",
|
||||
"value": 30,
|
||||
"why": "Standard catalogue default for 24x7 critical infrastructure response."
|
||||
},
|
||||
{
|
||||
"field": "service_levels.recovery_time_hours",
|
||||
"value": 4,
|
||||
"why": "Matches condition K-6 disaster recovery RTO requirement of 4 hours and catalogue default."
|
||||
}
|
||||
],
|
||||
"to_decide": [],
|
||||
"to_ask": [
|
||||
{
|
||||
"field": "metadata.client_name",
|
||||
"prompt": "What is metadata.client_name?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.author",
|
||||
"prompt": "What is metadata.author?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "metadata.revision",
|
||||
"prompt": "What is metadata.revision?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "intent.requirements",
|
||||
"prompt": "Which requirements for operations has the customer stated outright?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "solution.inherited_risks",
|
||||
"prompt": "What is already known to be unverified or at risk in the solution?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "operations.monitoring",
|
||||
"prompt": "Which monitoring and alerting is already in place or required?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "organisation.headcount_limit",
|
||||
"prompt": "Is there a limit on the number of people operating this?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "commercial.monthly_run_budget",
|
||||
"prompt": "Is there a monthly budget for operating this, in that currency?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "transition.go_live_date",
|
||||
"prompt": "When must the solution be in operation?",
|
||||
"severity": "LOW"
|
||||
}
|
||||
],
|
||||
"not_applicable": []
|
||||
}
|
||||
@@ -0,0 +1,414 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: case-08-landing-zone
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: architecture:case-08-landing-zone-185426
|
||||
status: BASELINE_LOCKED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We are a UK-regulated payment platform expanding into Google Cloud.
|
||||
We need an
|
||||
|
||||
enterprise-grade landing zone ready in under 10 weeks to support our core payments
|
||||
|
||||
engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have
|
||||
|
||||
existing on-premises systems that require private, low-latency connectivity over
|
||||
a
|
||||
|
||||
10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and
|
||||
|
||||
GitHub Actions for our delivery pipelines. Security requires that all egress
|
||||
|
||||
traffic flows through centralised inspection appliances before touching the public
|
||||
|
||||
internet, and customer data must be encrypted with keys we control.'
|
||||
requirements: ask
|
||||
business_outcomes:
|
||||
- target: Foundation ready in under 10 weeks
|
||||
id: BO-1
|
||||
outcome: Deliver an enterprise-grade Google Cloud landing zone within 10 weeks
|
||||
to enable ingestion and operation of the core payments engine.
|
||||
- outcome: Maintain continuous operational resilience and regulatory compliance
|
||||
with DORA and PCI-DSS v4.0 with platform availability of at least 99.9%.
|
||||
target: '>=99.9% monthly availability and full regulatory audit alignment'
|
||||
id: BO-2
|
||||
- target: Deterministic low-latency 10Gbps interconnect and 100% CMEK lifecycle
|
||||
coverage
|
||||
id: BO-3
|
||||
outcome: Ensure secure, low-latency hybrid transaction transport and zero-trust
|
||||
data protection using customer-managed encryption keys.
|
||||
exclusions:
|
||||
- Core payments engine application-level development, maintenance, and transaction
|
||||
processing logic
|
||||
- On-premises data centre infrastructure and systems beyond the Cloud Interconnect
|
||||
demarcation
|
||||
- Physical telecom carrier circuit ordering and provisioning (customer-owned build
|
||||
item)
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Resource Hierarchy and Environment Boundary Manager
|
||||
kind: governance
|
||||
product: Resource Manager
|
||||
source_ref: C-1
|
||||
elements:
|
||||
- E-1
|
||||
- E-2
|
||||
- E-3
|
||||
- E-4
|
||||
- E-5
|
||||
- E-6
|
||||
- E-7
|
||||
- E-8
|
||||
- E-9
|
||||
- E-10
|
||||
- E-34
|
||||
- E-35
|
||||
- E-36
|
||||
- E-37
|
||||
- E-38
|
||||
- E-50
|
||||
- E-51
|
||||
- E-55
|
||||
- E-60
|
||||
- id: S-2
|
||||
name: Dedicated Private Hybrid Connectivity Gateway
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
source_ref: C-2
|
||||
elements:
|
||||
- E-11
|
||||
- E-12
|
||||
- E-13
|
||||
- E-14
|
||||
- E-56
|
||||
- E-57
|
||||
- id: S-3
|
||||
name: Centralised Outbound Traffic Inspection and Egress Boundary
|
||||
kind: service
|
||||
product: Palo Alto Networks VM-Series
|
||||
source_ref: C-3
|
||||
elements:
|
||||
- E-15
|
||||
- E-16
|
||||
- E-17
|
||||
- E-18
|
||||
- E-19
|
||||
- E-20
|
||||
- E-47
|
||||
- E-48
|
||||
- E-53
|
||||
- id: S-4
|
||||
name: Centralised Immutable Audit Event and Compliance Log Repository
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
source_ref: C-4
|
||||
elements:
|
||||
- E-21
|
||||
- E-22
|
||||
- E-39
|
||||
- id: S-5
|
||||
name: Automated Infrastructure Orchestration and Deployment Engine
|
||||
kind: service
|
||||
product: GitHub Actions
|
||||
source_ref: C-5
|
||||
elements:
|
||||
- E-42
|
||||
- E-43
|
||||
- id: S-6
|
||||
name: Federated Identity and Role Governance Authority
|
||||
kind: identity
|
||||
product: IAM Workload Identity Federation
|
||||
source_ref: C-6
|
||||
elements:
|
||||
- E-23
|
||||
- E-24
|
||||
- E-25
|
||||
- E-26
|
||||
- E-27
|
||||
- E-45
|
||||
- id: S-7
|
||||
name: Cryptographic Key Lifecycle and Encryption Controller
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
source_ref: C-7
|
||||
elements:
|
||||
- E-28
|
||||
- E-29
|
||||
- E-30
|
||||
- E-31
|
||||
- E-49
|
||||
- E-58
|
||||
- E-59
|
||||
- id: S-8
|
||||
name: Platform Telemetry and Operational Alerting Engine
|
||||
kind: observability
|
||||
product: Cloud Monitoring
|
||||
source_ref: C-8
|
||||
elements:
|
||||
- E-32
|
||||
- E-40
|
||||
- E-41
|
||||
- E-44
|
||||
- E-52
|
||||
- id: S-9
|
||||
name: Financial Governance and Budget Enforcement Monitor
|
||||
kind: billing
|
||||
product: Cloud Billing
|
||||
source_ref: C-9
|
||||
elements:
|
||||
- E-33
|
||||
- E-46
|
||||
- E-54
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
- S-4
|
||||
- S-7
|
||||
condition: The landing zone configuration aligns with DORA operational resiliency
|
||||
guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.
|
||||
source_ref: NFR-8
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-1
|
||||
condition: The secondary region in europe-west1 operates as a warm standby ready
|
||||
to receive failover traffic.
|
||||
source_ref: NFR-9
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-1
|
||||
condition: Data residency is guaranteed within the United Kingdom and European
|
||||
Union.
|
||||
source_ref: NFR-9
|
||||
- id: K-4
|
||||
'on':
|
||||
- S-5
|
||||
condition: Platform foundation is fully provisioned and validated for core payments
|
||||
engine workload ingestion within 10 weeks.
|
||||
source_ref: NFR-10
|
||||
- id: K-5
|
||||
'on':
|
||||
- S-8
|
||||
condition: Platform foundation infrastructure maintains measured monthly availability
|
||||
of at least 99.9%.
|
||||
source_ref: NFR-11
|
||||
- id: K-6
|
||||
'on':
|
||||
- S-8
|
||||
condition: Disaster recovery activation achieves a recovery time objective (RTO)
|
||||
of 4 hours.
|
||||
source_ref: NFR-11
|
||||
- id: K-7
|
||||
'on':
|
||||
- S-8
|
||||
condition: Disaster recovery processes achieve a recovery point objective (RPO)
|
||||
of 1 hour.
|
||||
source_ref: NFR-11
|
||||
- id: K-8
|
||||
'on':
|
||||
- S-8
|
||||
condition: Alert notifications trigger operational incident workflows for the
|
||||
24/7 central platform operations team.
|
||||
source_ref: NFR-12
|
||||
- id: K-9
|
||||
'on':
|
||||
- S-9
|
||||
condition: Monthly cloud foundation expenditure does not exceed the target allocation
|
||||
without operational sign-off.
|
||||
source_ref: NFR-13
|
||||
- id: K-10
|
||||
'on':
|
||||
- S-2
|
||||
condition: Hybrid connection provides deterministic low latency suitable for real-time
|
||||
payment transaction processing.
|
||||
source_ref: NFR-14
|
||||
- id: K-11
|
||||
'on':
|
||||
- S-8
|
||||
condition: Deployments optimize carbon-free energy utilization based on Google
|
||||
Cloud regional CFE scores.
|
||||
source_ref: NFR-15
|
||||
- id: K-12
|
||||
'on':
|
||||
- S-6
|
||||
condition: Permissions are continuously rightsized based on IAM Recommender findings.
|
||||
source_ref: DR-OP-3
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned:
|
||||
- Order and provision the Interconnect carrier circuits
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Automated CI/CD pipelines via GitHub Actions with peer review and
|
||||
automated policy checks; standard operational changes deployed without a separate
|
||||
manual CAB.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: provider_operated
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams:
|
||||
- party: customer
|
||||
name: Central Platform Operations Team
|
||||
hours: 24x7
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: Google Cloud operations suite (Cloud Monitoring and Cloud Logging) integrated
|
||||
with native alerting workflows and GitHub Actions.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 30
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
- ISO27001
|
||||
- PCI_DSS_v4
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: ask
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.business_outcomes
|
||||
statement: 'Assumed intent.business_outcomes is [{''target'': ''Foundation ready
|
||||
in under 10 weeks'', ''id'': ''BO-1'', ''outcome'': ''Deliver an enterprise-grade
|
||||
Google Cloud landing zone within 10 weeks to enable ingestion and operation of
|
||||
the core payments engine.''}, {''outcome'': ''Maintain continuous operational
|
||||
resilience and regulatory compliance with DORA and PCI-DSS v4.0 with platform
|
||||
availability of at least 99.9%.'', ''target'': ''>=99.9% monthly availability
|
||||
and full regulatory audit alignment'', ''id'': ''BO-2''}, {''target'': ''Deterministic
|
||||
low-latency 10Gbps interconnect and 100% CMEK lifecycle coverage'', ''id'': ''BO-3'',
|
||||
''outcome'': ''Ensure secure, low-latency hybrid transaction transport and zero-trust
|
||||
data protection using customer-managed encryption keys.''}]. Derived from the
|
||||
workflow request stating the need for an enterprise-grade landing zone ready in
|
||||
under 10 weeks to support the core payments engine, complying with DORA and PCI-DSS
|
||||
v4.0, with secure hybrid connectivity and customer-controlled encryption.'
|
||||
impact_if_invalid: Changes what is measured, and what each measure is for.
|
||||
- id: ASSUMP-02
|
||||
field: intent.exclusions
|
||||
statement: 'Assumed intent.exclusions is [''Core payments engine application-level
|
||||
development, maintenance, and transaction processing logic'', ''On-premises data
|
||||
centre infrastructure and systems beyond the Cloud Interconnect demarcation'',
|
||||
''Physical telecom carrier circuit ordering and provisioning (customer-owned build
|
||||
item)'']. Derived from engagement kind (platform foundation) and workflow request:
|
||||
application-level workloads, on-prem systems, and physical circuit provisioning
|
||||
are excluded from platform operations.'
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-03
|
||||
field: operations.change_process
|
||||
statement: Assumed operations.change_process is Automated CI/CD pipelines via GitHub
|
||||
Actions with peer review and automated policy checks; standard operational changes
|
||||
deployed without a separate manual CAB.. Derived from request stating GitHub Actions
|
||||
delivery pipelines and catalogue default guidance.
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-04
|
||||
field: organisation.existing_teams
|
||||
statement: 'Assumed organisation.existing_teams is [{''party'': ''customer'', ''name'':
|
||||
''Central Platform Operations Team'', ''hours'': ''24x7''}]. Derived from condition
|
||||
K-8 noting alerting to the 24/7 central platform operations team, alongside provider-operated
|
||||
landing zone model.'
|
||||
impact_if_invalid: Changes which Roles are new and which are filled.
|
||||
- id: ASSUMP-05
|
||||
field: service_management.tooling
|
||||
statement: Assumed service_management.tooling is Google Cloud operations suite (Cloud
|
||||
Monitoring and Cloud Logging) integrated with native alerting workflows and GitHub
|
||||
Actions.. Catalogue default guidance leveraging Google Cloud operations suite
|
||||
and GitHub Actions specified in request.
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
- id: ASSUMP-06
|
||||
field: service_levels.priority_1_response_minutes
|
||||
statement: Assumed service_levels.priority_1_response_minutes is 30. Standard catalogue
|
||||
default for 24x7 critical infrastructure response.
|
||||
impact_if_invalid: Changes on-call arrangements and staffing.
|
||||
- id: ASSUMP-07
|
||||
field: service_levels.recovery_time_hours
|
||||
statement: Assumed service_levels.recovery_time_hours is 4. Matches condition K-6
|
||||
disaster recovery RTO requirement of 4 hours and catalogue default.
|
||||
impact_if_invalid: Changes continuity arrangements.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: intent.requirements
|
||||
prompt: Which requirements for operations has the customer stated outright?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: commercial.monthly_run_budget
|
||||
prompt: Is there a monthly budget for operating this, in that currency?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: digested
|
||||
commercial.monthly_run_budget: unknown
|
||||
compliance.frameworks: digested
|
||||
engagement.kind: digested
|
||||
intent.business_outcomes: assumed
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: unknown
|
||||
intent.statement: digested
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: digested
|
||||
metadata.revision: unknown
|
||||
metadata.source: digested
|
||||
operations.availability_hours: digested
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: digested
|
||||
organisation.existing_teams: assumed
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: assumed
|
||||
service_levels.recovery_time_hours: assumed
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: digested
|
||||
solution.build.duration_days: digested
|
||||
solution.cloud_provider: digested
|
||||
solution.conditions: digested
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: digested
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 3
|
||||
answered: 0
|
||||
assumed: 7
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
digested: 13
|
||||
@@ -0,0 +1,144 @@
|
||||
{
|
||||
"currency": "GBP",
|
||||
"rate_card": {
|
||||
"name": "rate-card",
|
||||
"version": "draft-2026-10-13",
|
||||
"draft": true
|
||||
},
|
||||
"conversion": {
|
||||
"from": "USD",
|
||||
"rate": 0.79,
|
||||
"as_of": "2026-10-13"
|
||||
},
|
||||
"roles": [
|
||||
{
|
||||
"role": "R-1",
|
||||
"name": "Platform Operations Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Service Provider",
|
||||
"country": "IN",
|
||||
"level": "engineer",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 30.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 17034
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"name": "Platform Reliability Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Service Provider",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 50.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 41640
|
||||
},
|
||||
{
|
||||
"role": "R-3",
|
||||
"name": "Security Operations Analyst",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Service Provider",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"hours": "24x7",
|
||||
"effort_hours_per_month": 75.0,
|
||||
"people": 5.0,
|
||||
"cost_per_month": 41640
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"name": "Platform Automation Engineer",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Service Provider",
|
||||
"country": "PL",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 177.5,
|
||||
"people": 1.2,
|
||||
"cost_per_month": 8063
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"name": "Platform Engineering Lead",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Service Provider",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 25.0,
|
||||
"people": 0.2,
|
||||
"cost_per_month": 2765
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"name": "Compliance & Governance Analyst",
|
||||
"party": "P-2",
|
||||
"party_name": "Platform Service Provider",
|
||||
"country": "GB",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 62.5,
|
||||
"people": 0.5,
|
||||
"cost_per_month": 5267
|
||||
},
|
||||
{
|
||||
"role": "R-7",
|
||||
"name": "Customer Platform Owner",
|
||||
"party": "P-1",
|
||||
"party_name": "Customer",
|
||||
"country": "GB",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 0.0,
|
||||
"people": 0.0,
|
||||
"cost_per_month": null
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"name": "Customer Operations Liaison",
|
||||
"party": "P-1",
|
||||
"party_name": "Customer",
|
||||
"country": "GB",
|
||||
"level": "senior",
|
||||
"hours": "business",
|
||||
"effort_hours_per_month": 0.0,
|
||||
"people": 0.0,
|
||||
"cost_per_month": null
|
||||
}
|
||||
],
|
||||
"people": 16.9,
|
||||
"cost_per_month": 116409,
|
||||
"by_party": {
|
||||
"P-2": 116409
|
||||
},
|
||||
"by_country": {
|
||||
"IN": 17034,
|
||||
"PL": 91343,
|
||||
"GB": 8032
|
||||
},
|
||||
"by_capability": {
|
||||
"C-2": 17034,
|
||||
"C-1": 33312,
|
||||
"C-9": 8328,
|
||||
"C-11": 11104,
|
||||
"C-12": 13880,
|
||||
"C-13": 16656,
|
||||
"C-3": 909,
|
||||
"C-4": 909,
|
||||
"C-5": 973,
|
||||
"C-6": 1136,
|
||||
"C-7": 681,
|
||||
"C-8": 681,
|
||||
"C-10": 681,
|
||||
"C-17": 1363,
|
||||
"C-18": 1136,
|
||||
"C-19": 780,
|
||||
"C-16": 2212,
|
||||
"C-14": 1264,
|
||||
"C-15": 843,
|
||||
"C-20": 843,
|
||||
"C-21": 1685
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,722 @@
|
||||
{
|
||||
"parties": [
|
||||
{
|
||||
"id": "P-1",
|
||||
"kind": "customer",
|
||||
"name": "Customer"
|
||||
},
|
||||
{
|
||||
"id": "P-2",
|
||||
"kind": "provider",
|
||||
"name": "Platform Service Provider"
|
||||
},
|
||||
{
|
||||
"id": "P-3",
|
||||
"kind": "cloud_provider",
|
||||
"name": "Google Cloud"
|
||||
},
|
||||
{
|
||||
"id": "P-4",
|
||||
"kind": "supplier",
|
||||
"name": "Network Carrier"
|
||||
},
|
||||
{
|
||||
"name": "External Firewall Vendor",
|
||||
"kind": "supplier",
|
||||
"id": "P-5"
|
||||
}
|
||||
],
|
||||
"teams": [
|
||||
{
|
||||
"type": "platform",
|
||||
"purpose": "Builds, maintains, and reliably operates the enterprise Google Cloud landing zone.",
|
||||
"party": "P-2",
|
||||
"name": "Cloud Platform Foundation Team",
|
||||
"id": "T-1"
|
||||
},
|
||||
{
|
||||
"id": "T-2",
|
||||
"purpose": "Provides 24x7 security monitoring, egress inspection analysis, and vulnerability management.",
|
||||
"name": "Platform Security Team",
|
||||
"party": "P-2",
|
||||
"type": "complicated_subsystem"
|
||||
},
|
||||
{
|
||||
"purpose": "Receives incident workflows and serves as the internal operations escalation point.",
|
||||
"type": "stream_aligned",
|
||||
"party": "P-1",
|
||||
"name": "Customer Central Platform Operations Team",
|
||||
"id": "T-3"
|
||||
},
|
||||
{
|
||||
"purpose": "Provides business context and sets the strategic direction for the platform.",
|
||||
"name": "Customer Platform Owner Team",
|
||||
"id": "T-4",
|
||||
"type": "stream_aligned",
|
||||
"party": "P-1"
|
||||
},
|
||||
{
|
||||
"type": "enabling",
|
||||
"id": "T-5",
|
||||
"purpose": "Ensures continuous regulatory compliance with DORA, PCI-DSS v4.0, and ISO27001.",
|
||||
"party": "P-2",
|
||||
"name": "Platform Governance Team"
|
||||
}
|
||||
],
|
||||
"roles": [
|
||||
{
|
||||
"level": "engineer",
|
||||
"hours": "24x7",
|
||||
"party": "P-2",
|
||||
"name": "Platform Operations Engineer",
|
||||
"team": "T-1",
|
||||
"id": "R-1",
|
||||
"country": "IN"
|
||||
},
|
||||
{
|
||||
"name": "Platform Reliability Engineer",
|
||||
"team": "T-1",
|
||||
"country": "PL",
|
||||
"party": "P-2",
|
||||
"hours": "24x7",
|
||||
"id": "R-2",
|
||||
"level": "senior"
|
||||
},
|
||||
{
|
||||
"name": "Security Operations Analyst",
|
||||
"id": "R-3",
|
||||
"level": "senior",
|
||||
"team": "T-2",
|
||||
"hours": "24x7",
|
||||
"country": "PL",
|
||||
"party": "P-2"
|
||||
},
|
||||
{
|
||||
"id": "R-4",
|
||||
"name": "Platform Automation Engineer",
|
||||
"team": "T-1",
|
||||
"hours": "business",
|
||||
"party": "P-2",
|
||||
"country": "PL",
|
||||
"level": "senior"
|
||||
},
|
||||
{
|
||||
"name": "Platform Engineering Lead",
|
||||
"id": "R-5",
|
||||
"team": "T-1",
|
||||
"level": "lead",
|
||||
"hours": "business",
|
||||
"party": "P-2",
|
||||
"country": "GB"
|
||||
},
|
||||
{
|
||||
"team": "T-5",
|
||||
"hours": "business",
|
||||
"party": "P-2",
|
||||
"country": "GB",
|
||||
"id": "R-6",
|
||||
"name": "Compliance & Governance Analyst",
|
||||
"level": "senior"
|
||||
},
|
||||
{
|
||||
"hours": "business",
|
||||
"party": "P-1",
|
||||
"level": "lead",
|
||||
"name": "Customer Platform Owner",
|
||||
"id": "R-7",
|
||||
"team": "T-4",
|
||||
"country": "GB"
|
||||
},
|
||||
{
|
||||
"name": "Customer Operations Liaison",
|
||||
"team": "T-3",
|
||||
"hours": "24x7",
|
||||
"country": "GB",
|
||||
"party": "P-1",
|
||||
"level": "senior",
|
||||
"id": "R-8"
|
||||
}
|
||||
],
|
||||
"interactions": [
|
||||
{
|
||||
"mode": "x_as_a_service",
|
||||
"to": "T-1",
|
||||
"from": "T-3",
|
||||
"purpose": "Customer Central Platform Operations consumes incident workflows and alert notifications from the Provider Cloud Platform Foundation.",
|
||||
"id": "I-1"
|
||||
},
|
||||
{
|
||||
"id": "I-2",
|
||||
"mode": "collaboration",
|
||||
"purpose": "Jointly establish automated security response runbooks and egress inspection rules for PCI-DSS compliance.",
|
||||
"from": "T-1",
|
||||
"until": "PCI-DSS baseline controls are fully automated and verified by external audit, after which they revert to x_as_a_service.",
|
||||
"to": "T-2"
|
||||
},
|
||||
{
|
||||
"from": "T-5",
|
||||
"id": "I-3",
|
||||
"mode": "facilitating",
|
||||
"purpose": "Assisting the platform team in integrating regulatory evidence collection into the automated deployment engine.",
|
||||
"to": "T-1"
|
||||
}
|
||||
],
|
||||
"measures": [
|
||||
{
|
||||
"id": "M-1",
|
||||
"target": "Under 1 hour",
|
||||
"measured_by": "C-19",
|
||||
"name": "Deployment Lead Time",
|
||||
"framework": "dora-metrics",
|
||||
"layer": "outcome",
|
||||
"outcome": "BO-1"
|
||||
},
|
||||
{
|
||||
"id": "M-2",
|
||||
"framework": "devex-framework",
|
||||
"target": "Low friction reported in monthly surveys",
|
||||
"name": "Developer Friction",
|
||||
"layer": "leading",
|
||||
"outcome": "BO-1",
|
||||
"measured_by": "C-19"
|
||||
},
|
||||
{
|
||||
"measured_by": "C-19",
|
||||
"framework": "space-framework",
|
||||
"id": "M-3",
|
||||
"name": "Team Satisfaction",
|
||||
"layer": "guardrail",
|
||||
"outcome": "BO-1",
|
||||
"target": "Positive quarterly trend"
|
||||
},
|
||||
{
|
||||
"measured_by": "C-15",
|
||||
"layer": "service_level",
|
||||
"outcome": "BO-2",
|
||||
"id": "M-4",
|
||||
"target": ">=99.9%",
|
||||
"name": "Platform Availability"
|
||||
},
|
||||
{
|
||||
"framework": "dora-metrics",
|
||||
"outcome": "BO-2",
|
||||
"measured_by": "C-15",
|
||||
"name": "Time to Restore Service",
|
||||
"id": "M-5",
|
||||
"layer": "outcome",
|
||||
"target": "Under 4 hours"
|
||||
},
|
||||
{
|
||||
"id": "M-6",
|
||||
"layer": "service_level",
|
||||
"target": "Deterministic low latency (<5ms)",
|
||||
"name": "Interconnect Latency",
|
||||
"outcome": "BO-3",
|
||||
"measured_by": "C-10"
|
||||
},
|
||||
{
|
||||
"outcome": "BO-3",
|
||||
"layer": "guardrail",
|
||||
"target": "100% coverage",
|
||||
"id": "M-7",
|
||||
"name": "CMEK Lifecycle Coverage",
|
||||
"measured_by": "C-21"
|
||||
}
|
||||
],
|
||||
"responsibilities": [
|
||||
{
|
||||
"id": "RS-1",
|
||||
"kind": "accountable",
|
||||
"role": "R-5",
|
||||
"capability": "C-1"
|
||||
},
|
||||
{
|
||||
"capability": "C-1",
|
||||
"role": "R-2",
|
||||
"id": "RS-2",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"capability": "C-1",
|
||||
"kind": "consulted",
|
||||
"id": "RS-3"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"id": "RS-4",
|
||||
"role": "R-5",
|
||||
"capability": "C-2"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"id": "RS-5",
|
||||
"capability": "C-2",
|
||||
"role": "R-1"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"id": "RS-6",
|
||||
"capability": "C-3",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"capability": "C-3",
|
||||
"role": "R-4",
|
||||
"kind": "responsible",
|
||||
"id": "RS-7"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"id": "RS-8",
|
||||
"capability": "C-4",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"kind": "responsible",
|
||||
"id": "RS-9",
|
||||
"capability": "C-4"
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"capability": "C-5",
|
||||
"kind": "accountable",
|
||||
"id": "RS-10"
|
||||
},
|
||||
{
|
||||
"role": "R-4",
|
||||
"kind": "responsible",
|
||||
"capability": "C-5",
|
||||
"id": "RS-11"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-6",
|
||||
"id": "RS-12",
|
||||
"capability": "C-5"
|
||||
},
|
||||
{
|
||||
"capability": "C-6",
|
||||
"kind": "accountable",
|
||||
"id": "RS-13",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"id": "RS-14",
|
||||
"kind": "responsible",
|
||||
"role": "R-4",
|
||||
"capability": "C-6"
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"id": "RS-15",
|
||||
"capability": "C-7",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-7",
|
||||
"role": "R-4",
|
||||
"id": "RS-16",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"id": "RS-17",
|
||||
"capability": "C-8",
|
||||
"role": "R-5",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"id": "RS-18",
|
||||
"role": "R-4",
|
||||
"capability": "C-8"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-9",
|
||||
"id": "RS-19",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"role": "R-2",
|
||||
"id": "RS-20",
|
||||
"kind": "responsible",
|
||||
"capability": "C-9"
|
||||
},
|
||||
{
|
||||
"role": "R-5",
|
||||
"capability": "C-10",
|
||||
"kind": "accountable",
|
||||
"id": "RS-21"
|
||||
},
|
||||
{
|
||||
"capability": "C-10",
|
||||
"role": "R-4",
|
||||
"kind": "responsible",
|
||||
"id": "RS-22"
|
||||
},
|
||||
{
|
||||
"capability": "C-11",
|
||||
"kind": "accountable",
|
||||
"role": "R-3",
|
||||
"id": "RS-23"
|
||||
},
|
||||
{
|
||||
"capability": "C-11",
|
||||
"kind": "responsible",
|
||||
"id": "RS-24",
|
||||
"role": "R-3"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"id": "RS-25",
|
||||
"role": "R-3",
|
||||
"capability": "C-12"
|
||||
},
|
||||
{
|
||||
"id": "RS-26",
|
||||
"role": "R-3",
|
||||
"capability": "C-12",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"id": "RS-27",
|
||||
"role": "R-3",
|
||||
"kind": "accountable",
|
||||
"capability": "C-13"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"role": "R-3",
|
||||
"capability": "C-13",
|
||||
"id": "RS-28"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-14",
|
||||
"role": "R-5",
|
||||
"id": "RS-29"
|
||||
},
|
||||
{
|
||||
"id": "RS-30",
|
||||
"kind": "responsible",
|
||||
"capability": "C-14",
|
||||
"role": "R-6"
|
||||
},
|
||||
{
|
||||
"capability": "C-15",
|
||||
"role": "R-5",
|
||||
"kind": "accountable",
|
||||
"id": "RS-31"
|
||||
},
|
||||
{
|
||||
"role": "R-6",
|
||||
"id": "RS-32",
|
||||
"capability": "C-15",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"id": "RS-33",
|
||||
"capability": "C-16",
|
||||
"role": "R-5",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-16",
|
||||
"id": "RS-34",
|
||||
"kind": "responsible",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"role": "R-7",
|
||||
"capability": "C-16",
|
||||
"kind": "consulted",
|
||||
"id": "RS-35"
|
||||
},
|
||||
{
|
||||
"id": "RS-36",
|
||||
"kind": "accountable",
|
||||
"capability": "C-17",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"capability": "C-17",
|
||||
"role": "R-4",
|
||||
"id": "RS-37",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"capability": "C-18",
|
||||
"role": "R-5",
|
||||
"id": "RS-38",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"id": "RS-39",
|
||||
"capability": "C-18",
|
||||
"kind": "responsible",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"kind": "accountable",
|
||||
"capability": "C-19",
|
||||
"role": "R-5",
|
||||
"id": "RS-40"
|
||||
},
|
||||
{
|
||||
"kind": "responsible",
|
||||
"capability": "C-19",
|
||||
"id": "RS-41",
|
||||
"role": "R-4"
|
||||
},
|
||||
{
|
||||
"id": "RS-42",
|
||||
"role": "R-5",
|
||||
"capability": "C-19",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"id": "RS-43",
|
||||
"kind": "accountable",
|
||||
"capability": "C-20",
|
||||
"role": "R-5"
|
||||
},
|
||||
{
|
||||
"id": "RS-44",
|
||||
"role": "R-6",
|
||||
"capability": "C-20",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"capability": "C-21",
|
||||
"role": "R-6",
|
||||
"id": "RS-45",
|
||||
"kind": "accountable"
|
||||
},
|
||||
{
|
||||
"capability": "C-21",
|
||||
"id": "RS-46",
|
||||
"role": "R-6",
|
||||
"kind": "responsible"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"id": "RS-47",
|
||||
"capability": "C-21",
|
||||
"role": "R-7"
|
||||
},
|
||||
{
|
||||
"id": "RS-48",
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"capability": "C-2"
|
||||
},
|
||||
{
|
||||
"id": "RS-49",
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"capability": "C-3"
|
||||
},
|
||||
{
|
||||
"capability": "C-4",
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-50"
|
||||
},
|
||||
{
|
||||
"id": "RS-51",
|
||||
"capability": "C-5",
|
||||
"role": "R-8",
|
||||
"kind": "consulted"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"capability": "C-6",
|
||||
"id": "RS-52"
|
||||
},
|
||||
{
|
||||
"id": "RS-53",
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"capability": "C-7"
|
||||
},
|
||||
{
|
||||
"capability": "C-8",
|
||||
"kind": "consulted",
|
||||
"role": "R-8",
|
||||
"id": "RS-54"
|
||||
},
|
||||
{
|
||||
"id": "RS-55",
|
||||
"capability": "C-9",
|
||||
"kind": "consulted",
|
||||
"role": "R-8"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-56",
|
||||
"capability": "C-10"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-57",
|
||||
"capability": "C-11"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"capability": "C-12",
|
||||
"id": "RS-58"
|
||||
},
|
||||
{
|
||||
"id": "RS-59",
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"capability": "C-13"
|
||||
},
|
||||
{
|
||||
"id": "RS-60",
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"capability": "C-14"
|
||||
},
|
||||
{
|
||||
"role": "R-8",
|
||||
"kind": "consulted",
|
||||
"id": "RS-61",
|
||||
"capability": "C-15"
|
||||
},
|
||||
{
|
||||
"id": "RS-62",
|
||||
"capability": "C-17",
|
||||
"kind": "consulted",
|
||||
"role": "R-8"
|
||||
},
|
||||
{
|
||||
"capability": "C-18",
|
||||
"kind": "consulted",
|
||||
"role": "R-8",
|
||||
"id": "RS-63"
|
||||
},
|
||||
{
|
||||
"capability": "C-19",
|
||||
"kind": "consulted",
|
||||
"role": "R-8",
|
||||
"id": "RS-64"
|
||||
},
|
||||
{
|
||||
"kind": "consulted",
|
||||
"role": "R-8",
|
||||
"capability": "C-20",
|
||||
"id": "RS-65"
|
||||
}
|
||||
],
|
||||
"checks": [
|
||||
{
|
||||
"on": "C-7",
|
||||
"condition": "The landing zone configurations are continuously enforced to align with DORA, PCI-DSS v4.0, and ISO27001 standard baselines.",
|
||||
"source": "K-1",
|
||||
"id": "OC-1"
|
||||
},
|
||||
{
|
||||
"on": "C-9",
|
||||
"id": "OC-2",
|
||||
"source": "K-2",
|
||||
"condition": "The europe-west1 secondary region is continuously maintained as an active warm standby."
|
||||
},
|
||||
{
|
||||
"source": "K-3",
|
||||
"id": "OC-3",
|
||||
"condition": "Configuration enforces that all data residency, audit logs, and keys remain strictly within the UK and EU.",
|
||||
"on": "C-7"
|
||||
},
|
||||
{
|
||||
"on": "C-16",
|
||||
"id": "OC-4",
|
||||
"source": "K-4",
|
||||
"condition": "The foundation platform is verified as fully provisioned and ready for core payments engine workload ingestion within 10 weeks."
|
||||
},
|
||||
{
|
||||
"on": "C-2",
|
||||
"condition": "Continuous telemetry verifies that the platform foundation infrastructure maintains at least 99.9% monthly availability.",
|
||||
"source": "K-5",
|
||||
"id": "OC-5"
|
||||
},
|
||||
{
|
||||
"source": "K-6",
|
||||
"on": "C-9",
|
||||
"id": "OC-6",
|
||||
"condition": "Disaster recovery failover tests verify that the 4-hour RTO can be met."
|
||||
},
|
||||
{
|
||||
"condition": "Backup and restore tests verify that the 1-hour RPO for compliance logs and KMS keys is met.",
|
||||
"on": "C-8",
|
||||
"source": "K-7",
|
||||
"id": "OC-7"
|
||||
},
|
||||
{
|
||||
"id": "OC-8",
|
||||
"source": "K-8",
|
||||
"condition": "Alert notifications from platform telemetry automatically trigger incident workflows for the 24x7 central platform operations team without human delay.",
|
||||
"on": "C-2"
|
||||
},
|
||||
{
|
||||
"source": "K-9",
|
||||
"id": "OC-9",
|
||||
"condition": "Cloud consumption expenditure is tracked against budgets, and automation enforces hard limits that prevent overages without operational sign-off.",
|
||||
"on": "C-14"
|
||||
},
|
||||
{
|
||||
"id": "OC-10",
|
||||
"on": "C-10",
|
||||
"source": "K-10",
|
||||
"condition": "The dedicated hybrid interconnect bandwidth and latency are monitored to ensure deterministic low latency for real-time payments."
|
||||
},
|
||||
{
|
||||
"on": "C-6",
|
||||
"condition": "Workload placements in the deployment pipeline are optimized for carbon-free energy utilization.",
|
||||
"id": "OC-11",
|
||||
"source": "K-11"
|
||||
},
|
||||
{
|
||||
"condition": "Access permissions are continuously audited and rightsized based on IAM recommender alerts.",
|
||||
"on": "C-11",
|
||||
"source": "K-12",
|
||||
"id": "OC-12"
|
||||
},
|
||||
{
|
||||
"id": "OC-13",
|
||||
"on": "C-1",
|
||||
"source": "OR-1",
|
||||
"condition": "A Priority 1 fault on the platform foundation is acknowledged within 30 minutes, at any time of day or night."
|
||||
},
|
||||
{
|
||||
"on": "C-21",
|
||||
"source": "OR-14",
|
||||
"id": "OC-16",
|
||||
"condition": "Evidence of continuous alignment with DORA, PCI-DSS v4.0, and ISO27001 is gathered for external audit."
|
||||
},
|
||||
{
|
||||
"id": "OC-17",
|
||||
"source": "OR-15",
|
||||
"condition": "The UK and EU data residency guarantee is evidenced for all storage, audit logs, and keys.",
|
||||
"on": "C-21"
|
||||
},
|
||||
{
|
||||
"on": "R-5",
|
||||
"condition": "The platform foundation is led and managed by a provider-operated delivery model.",
|
||||
"source": "OR-12",
|
||||
"id": "OC-14"
|
||||
},
|
||||
{
|
||||
"id": "OC-15",
|
||||
"source": "OR-13",
|
||||
"condition": "Operational management is performed exclusively by staff located in the UK, Poland, or India.",
|
||||
"on": "R-2"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,264 @@
|
||||
{
|
||||
"dry_run": {
|
||||
"verdict": "pass",
|
||||
"evidence": "34 of 34 scenario walk-throughs pass."
|
||||
},
|
||||
"checks": [
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-7 provides configuration management, enforcing state definition parity and auditing configurations, and supports ensuring compliance standards like DORA, PCI-DSS v4.0, and ISO27001 are continuously enforced. Role R-4 is responsible for it.",
|
||||
"check": "OC-1"
|
||||
},
|
||||
{
|
||||
"check": "OC-2",
|
||||
"evidence": "Capability C-9 handles service continuity, which includes planning and periodic testing of regional failovers, ensuring the secondary region is maintained as an active warm standby. Role R-2 is responsible for it.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-7 enforces configuration state parity and audits configurations, satisfying the condition that data residency, logs, and keys remain in the UK and EU.",
|
||||
"verdict": "pass",
|
||||
"check": "OC-3"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-4",
|
||||
"evidence": "Capability C-16 prioritises features and technical debt to ensure the platform foundation supports the payments engine developers effectively, meeting the 10-week provisioning timeframe. R-5 is responsible."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-2 provides continuous monitoring and alerting 24x7, maintaining telemetry pipelines to verify the infrastructure maintains 99.9% availability.",
|
||||
"check": "OC-5"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-6",
|
||||
"evidence": "Capability C-9 handles disaster recovery failover tests to validate readiness and timing to ensure the 4-hour RTO can be met."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-7",
|
||||
"evidence": "Capability C-8 rehearses restoration processes for Cloud Storage and KMS to verify the 1-hour RPO is met."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-2 configures and maintains automated alerting rules that trigger workflows to the 24x7 customer central platform operations team (R-8 is consulted).",
|
||||
"check": "OC-8"
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-14 designs and operates automation to enforce hard financial limits and execution stops, tracking cloud consumption against budgets.",
|
||||
"check": "OC-9",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "OC-10",
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-10 monitors and optimises the dedicated hybrid interconnect bandwidth to guarantee deterministic low latency for real-time payments."
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-6 operates the deployment pipelines to ensure timely deployments and carbon-optimised workload placement.",
|
||||
"check": "OC-11"
|
||||
},
|
||||
{
|
||||
"check": "OC-12",
|
||||
"evidence": "Capability C-11 continuously applies automated IAM rightsizing recommendations and manages access from approved countries.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "Capability C-1 provides 24x7 incident management and 30-minute response capability for Priority 1 faults.",
|
||||
"check": "OC-13"
|
||||
},
|
||||
{
|
||||
"evidence": "Role R-5 (Platform Engineering Lead) sits within the Provider (P-2) party, managing and directing the platform strategy and operations.",
|
||||
"verdict": "pass",
|
||||
"check": "OC-14"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "OC-15",
|
||||
"evidence": "All provider operational staff (R-1, R-2, R-3, R-4, R-5, R-6) are based exclusively in the UK, Poland, or India, fulfilling the sourcing requirement."
|
||||
},
|
||||
{
|
||||
"evidence": "Capability C-21 gathers and preserves documented audit evidence to prove compliance with DORA, PCI-DSS v4.0, and ISO27001 to external regulators.",
|
||||
"check": "OC-16",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "OC-17",
|
||||
"evidence": "Capability C-21 captures, preserves, and provides documented audit evidence to external regulators, which includes proving data residency constraints.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Resource Hierarchy and Environment Boundary Manager (S-1) fails at an hour faults are responded to (24x7). Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Resource Hierarchy and Environment Boundary Manager (S-1) must be changed. Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Dedicated Private Hybrid Connectivity Gateway (S-2) fails at an hour faults are responded to (24x7). Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Dedicated Private Hybrid Connectivity Gateway (S-2) must be changed. Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) fails at an hour faults are responded to (24x7). Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Outbound Traffic Inspection and Egress Boundary (S-3) must be changed. Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) fails at an hour faults are responded to (24x7). Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Centralised Immutable Audit Event and Compliance Log Repository (S-4) must be changed. Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Automated Infrastructure Orchestration and Deployment Engine (S-5) fails at an hour faults are responded to (24x7). Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Automated Infrastructure Orchestration and Deployment Engine (S-5) must be changed. Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-6",
|
||||
"verdict": "pass",
|
||||
"evidence": "Federated Identity and Role Governance Authority (S-6) fails at an hour faults are responded to (24x7). Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-6",
|
||||
"verdict": "pass",
|
||||
"evidence": "Federated Identity and Role Governance Authority (S-6) must be changed. Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-7",
|
||||
"verdict": "pass",
|
||||
"evidence": "Cryptographic Key Lifecycle and Encryption Controller (S-7) fails at an hour faults are responded to (24x7). Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-7",
|
||||
"verdict": "pass",
|
||||
"evidence": "Cryptographic Key Lifecycle and Encryption Controller (S-7) must be changed. Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Platform Telemetry and Operational Alerting Engine (S-8) fails at an hour faults are responded to (24x7). Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Platform Telemetry and Operational Alerting Engine (S-8) must be changed. Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-fault-S-9",
|
||||
"verdict": "pass",
|
||||
"evidence": "Financial Governance and Budget Enforcement Monitor (S-9) fails at an hour faults are responded to (24x7). Platform Reliability Engineer responds under C-1, and Platform Engineering Lead is answerable."
|
||||
},
|
||||
{
|
||||
"check": "SC-change-S-9",
|
||||
"verdict": "pass",
|
||||
"evidence": "Financial Governance and Budget Enforcement Monitor (S-9) must be changed. Platform Automation Engineer makes the change under C-5."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-1",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-1 must be shown to hold: The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit. Check OC-1 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-2 must be shown to hold: The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic. Check OC-2 on C-9 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-3 must be shown to hold: Data residency is guaranteed within the United Kingdom and European Union. Check OC-3 on C-7 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-4 must be shown to hold: Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks. Check OC-4 on C-16 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-5 must be shown to hold: Platform foundation infrastructure maintains measured monthly availability of at least 99.9%. Check OC-5 on C-2 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-6",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-6 must be shown to hold: Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours. Check OC-6 on C-9 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-7",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-7 must be shown to hold: Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour. Check OC-7 on C-8 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-8",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-8 must be shown to hold: Alert notifications trigger operational incident workflows for the 24/7 central platform operations team. Check OC-8 on C-2 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-9",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-9 must be shown to hold: Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off. Check OC-9 on C-14 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-10",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-10 must be shown to hold: Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing. Check OC-10 on C-10 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-11",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-11 must be shown to hold: Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores. Check OC-11 on C-6 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-condition-K-12",
|
||||
"verdict": "pass",
|
||||
"evidence": "Condition K-12 must be shown to hold: Permissions are continuously rightsized based on IAM Recommender findings. Check OC-12 on C-11 keeps it true."
|
||||
},
|
||||
{
|
||||
"check": "SC-party-P-2",
|
||||
"verdict": "pass",
|
||||
"evidence": "Platform Service Provider cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"check": "SC-party-P-3",
|
||||
"verdict": "pass",
|
||||
"evidence": "Google Cloud cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"check": "SC-party-P-4",
|
||||
"verdict": "pass",
|
||||
"evidence": "Network Carrier cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
},
|
||||
{
|
||||
"check": "SC-party-P-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "External Firewall Vendor cannot be reached. Every Capability it is answerable for has a Role in another Party to turn to."
|
||||
}
|
||||
],
|
||||
"proposed_additions": []
|
||||
}
|
||||
@@ -0,0 +1,15 @@
|
||||
# Intent 1: case-08-landing-zone
|
||||
|
||||
- Recorded: 2026-10-21T21:30:39+00:00
|
||||
- Execution: `case-02-from-architecture-r1`
|
||||
|
||||
## What the customer wants
|
||||
|
||||
We are a UK-regulated payment platform expanding into Google Cloud. We need an
|
||||
enterprise-grade landing zone ready in under 10 weeks to support our core payments
|
||||
engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have
|
||||
existing on-premises systems that require private, low-latency connectivity over a
|
||||
10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and
|
||||
GitHub Actions for our delivery pipelines. Security requires that all egress
|
||||
traffic flows through centralised inspection appliances before touching the public
|
||||
internet, and customer data must be encrypted with keys we control.
|
||||
@@ -0,0 +1,406 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: case-08-landing-zone
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: architecture:case-08-landing-zone-185426
|
||||
status: APPROVED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We are a UK-regulated payment platform expanding into Google Cloud.
|
||||
We need an
|
||||
|
||||
enterprise-grade landing zone ready in under 10 weeks to support our core payments
|
||||
|
||||
engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have
|
||||
|
||||
existing on-premises systems that require private, low-latency connectivity over
|
||||
a
|
||||
|
||||
10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and
|
||||
|
||||
GitHub Actions for our delivery pipelines. Security requires that all egress
|
||||
|
||||
traffic flows through centralised inspection appliances before touching the public
|
||||
|
||||
internet, and customer data must be encrypted with keys we control.'
|
||||
requirements: ask
|
||||
business_outcomes:
|
||||
- outcome: Enterprise landing zone ready to ingest core payments engine workloads
|
||||
within 10 weeks
|
||||
id: BO-1
|
||||
target: Workload ready within 10 weeks
|
||||
- outcome: Continuous operational resilience and regulatory compliance under DORA
|
||||
and PCI-DSS v4.0
|
||||
target: Zero audit non-conformances and >= 99.9% platform availability
|
||||
id: BO-2
|
||||
- id: BO-3
|
||||
target: Continuous 10Gbps dedicated interconnect availability with centralized
|
||||
inspection
|
||||
outcome: Secure, deterministic low-latency hybrid connectivity supporting real-time
|
||||
payment transactions
|
||||
exclusions:
|
||||
- Application workload code, payment engine business logic, and database-level transaction
|
||||
data management
|
||||
- Physical data centre hosting, hardware maintenance, and on-premises network infrastructure
|
||||
- Corporate Entra ID user identity lifecycle management outside Google Cloud federation
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Resource Hierarchy and Environment Boundary Manager
|
||||
kind: governance
|
||||
product: Resource Manager
|
||||
source_ref: C-1
|
||||
elements:
|
||||
- E-1
|
||||
- E-2
|
||||
- E-3
|
||||
- E-4
|
||||
- E-5
|
||||
- E-6
|
||||
- E-7
|
||||
- E-8
|
||||
- E-9
|
||||
- E-10
|
||||
- E-34
|
||||
- E-35
|
||||
- E-36
|
||||
- E-37
|
||||
- E-38
|
||||
- E-50
|
||||
- E-51
|
||||
- E-55
|
||||
- E-60
|
||||
- id: S-2
|
||||
name: Dedicated Private Hybrid Connectivity Gateway
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
source_ref: C-2
|
||||
elements:
|
||||
- E-11
|
||||
- E-12
|
||||
- E-13
|
||||
- E-14
|
||||
- E-56
|
||||
- E-57
|
||||
- id: S-3
|
||||
name: Centralised Outbound Traffic Inspection and Egress Boundary
|
||||
kind: service
|
||||
product: Palo Alto Networks VM-Series
|
||||
source_ref: C-3
|
||||
elements:
|
||||
- E-15
|
||||
- E-16
|
||||
- E-17
|
||||
- E-18
|
||||
- E-19
|
||||
- E-20
|
||||
- E-47
|
||||
- E-48
|
||||
- E-53
|
||||
- id: S-4
|
||||
name: Centralised Immutable Audit Event and Compliance Log Repository
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
source_ref: C-4
|
||||
elements:
|
||||
- E-21
|
||||
- E-22
|
||||
- E-39
|
||||
- id: S-5
|
||||
name: Automated Infrastructure Orchestration and Deployment Engine
|
||||
kind: service
|
||||
product: GitHub Actions
|
||||
source_ref: C-5
|
||||
elements:
|
||||
- E-42
|
||||
- E-43
|
||||
- id: S-6
|
||||
name: Federated Identity and Role Governance Authority
|
||||
kind: identity
|
||||
product: IAM Workload Identity Federation
|
||||
source_ref: C-6
|
||||
elements:
|
||||
- E-23
|
||||
- E-24
|
||||
- E-25
|
||||
- E-26
|
||||
- E-27
|
||||
- E-45
|
||||
- id: S-7
|
||||
name: Cryptographic Key Lifecycle and Encryption Controller
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
source_ref: C-7
|
||||
elements:
|
||||
- E-28
|
||||
- E-29
|
||||
- E-30
|
||||
- E-31
|
||||
- E-49
|
||||
- E-58
|
||||
- E-59
|
||||
- id: S-8
|
||||
name: Platform Telemetry and Operational Alerting Engine
|
||||
kind: observability
|
||||
product: Cloud Monitoring
|
||||
source_ref: C-8
|
||||
elements:
|
||||
- E-32
|
||||
- E-40
|
||||
- E-41
|
||||
- E-44
|
||||
- E-52
|
||||
- id: S-9
|
||||
name: Financial Governance and Budget Enforcement Monitor
|
||||
kind: billing
|
||||
product: Cloud Billing
|
||||
source_ref: C-9
|
||||
elements:
|
||||
- E-33
|
||||
- E-46
|
||||
- E-54
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
- S-4
|
||||
- S-7
|
||||
condition: The landing zone configuration aligns with DORA operational resiliency
|
||||
guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.
|
||||
source_ref: NFR-8
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-1
|
||||
condition: The secondary region in europe-west1 operates as a warm standby ready
|
||||
to receive failover traffic.
|
||||
source_ref: NFR-9
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-1
|
||||
condition: Data residency is guaranteed within the United Kingdom and European
|
||||
Union.
|
||||
source_ref: NFR-9
|
||||
- id: K-4
|
||||
'on':
|
||||
- S-5
|
||||
condition: Platform foundation is fully provisioned and validated for core payments
|
||||
engine workload ingestion within 10 weeks.
|
||||
source_ref: NFR-10
|
||||
- id: K-5
|
||||
'on':
|
||||
- S-8
|
||||
condition: Platform foundation infrastructure maintains measured monthly availability
|
||||
of at least 99.9%.
|
||||
source_ref: NFR-11
|
||||
- id: K-6
|
||||
'on':
|
||||
- S-8
|
||||
condition: Disaster recovery activation achieves a recovery time objective (RTO)
|
||||
of 4 hours.
|
||||
source_ref: NFR-11
|
||||
- id: K-7
|
||||
'on':
|
||||
- S-8
|
||||
condition: Disaster recovery processes achieve a recovery point objective (RPO)
|
||||
of 1 hour.
|
||||
source_ref: NFR-11
|
||||
- id: K-8
|
||||
'on':
|
||||
- S-8
|
||||
condition: Alert notifications trigger operational incident workflows for the
|
||||
24/7 central platform operations team.
|
||||
source_ref: NFR-12
|
||||
- id: K-9
|
||||
'on':
|
||||
- S-9
|
||||
condition: Monthly cloud foundation expenditure does not exceed the target allocation
|
||||
without operational sign-off.
|
||||
source_ref: NFR-13
|
||||
- id: K-10
|
||||
'on':
|
||||
- S-2
|
||||
condition: Hybrid connection provides deterministic low latency suitable for real-time
|
||||
payment transaction processing.
|
||||
source_ref: NFR-14
|
||||
- id: K-11
|
||||
'on':
|
||||
- S-8
|
||||
condition: Deployments optimize carbon-free energy utilization based on Google
|
||||
Cloud regional CFE scores.
|
||||
source_ref: NFR-15
|
||||
- id: K-12
|
||||
'on':
|
||||
- S-6
|
||||
condition: Permissions are continuously rightsized based on IAM Recommender findings.
|
||||
source_ref: DR-OP-3
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned:
|
||||
- Order and provision the Interconnect carrier circuits
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Automated infrastructure-as-code deployment via GitHub Actions pipelines
|
||||
with automated linting, security scans, and peer review approvals without a manual
|
||||
CAB.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: provider_operated
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams: []
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: Google Cloud operations suite (Cloud Monitoring, Cloud Logging) integrated
|
||||
with provider operational incident and alerting management systems.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 30
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
- ISO27001
|
||||
- PCI_DSS_v4
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: ask
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.business_outcomes
|
||||
statement: 'Assumed intent.business_outcomes is [{''outcome'': ''Enterprise landing
|
||||
zone ready to ingest core payments engine workloads within 10 weeks'', ''id'':
|
||||
''BO-1'', ''target'': ''Workload ready within 10 weeks''}, {''outcome'': ''Continuous
|
||||
operational resilience and regulatory compliance under DORA and PCI-DSS v4.0'',
|
||||
''target'': ''Zero audit non-conformances and >= 99.9% platform availability'',
|
||||
''id'': ''BO-2''}, {''id'': ''BO-3'', ''target'': ''Continuous 10Gbps dedicated
|
||||
interconnect availability with centralized inspection'', ''outcome'': ''Secure,
|
||||
deterministic low-latency hybrid connectivity supporting real-time payment transactions''}].
|
||||
Derived from the workflow request specifying rapid 10-week landing zone delivery,
|
||||
DORA and PCI-DSS v4.0 compliance, and deterministic hybrid connectivity.'
|
||||
impact_if_invalid: Changes what is measured, and what each measure is for.
|
||||
- id: ASSUMP-02
|
||||
field: intent.exclusions
|
||||
statement: 'Assumed intent.exclusions is [''Application workload code, payment engine
|
||||
business logic, and database-level transaction data management'', ''Physical data
|
||||
centre hosting, hardware maintenance, and on-premises network infrastructure'',
|
||||
''Corporate Entra ID user identity lifecycle management outside Google Cloud federation''].
|
||||
Assumed from platform foundation scope: excludes application-level payment processing
|
||||
logic, physical on-premises hardware maintenance, and end-user identity administration
|
||||
beyond cloud federation.'
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-03
|
||||
field: operations.change_process
|
||||
statement: Assumed operations.change_process is Automated infrastructure-as-code
|
||||
deployment via GitHub Actions pipelines with automated linting, security scans,
|
||||
and peer review approvals without a manual CAB.. Assumed based on catalogue default
|
||||
and stated use of GitHub Actions delivery pipelines.
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-04
|
||||
field: organisation.existing_teams
|
||||
statement: 'Assumed organisation.existing_teams is []. Assumed catalogue default:
|
||||
no existing customer operational roles carry forward into the platform foundation;
|
||||
operations are delivered under a provider-operated model.'
|
||||
impact_if_invalid: Changes which Roles are new and which are filled.
|
||||
- id: ASSUMP-05
|
||||
field: service_management.tooling
|
||||
statement: Assumed service_management.tooling is Google Cloud operations suite (Cloud
|
||||
Monitoring, Cloud Logging) integrated with provider operational incident and alerting
|
||||
management systems.. Assumed based on catalogue default and solution item S-8
|
||||
(Cloud Monitoring).
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
- id: ASSUMP-06
|
||||
field: service_levels.priority_1_response_minutes
|
||||
statement: Assumed service_levels.priority_1_response_minutes is 30. Assumed catalogue
|
||||
default of 30 minutes for critical incident response.
|
||||
impact_if_invalid: Changes on-call arrangements and staffing.
|
||||
- id: ASSUMP-07
|
||||
field: service_levels.recovery_time_hours
|
||||
statement: Assumed service_levels.recovery_time_hours is 4. Derived from solution
|
||||
condition K-6 specifying a disaster recovery RTO of 4 hours, matching catalogue
|
||||
default.
|
||||
impact_if_invalid: Changes continuity arrangements.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: intent.requirements
|
||||
prompt: Which requirements for operations has the customer stated outright?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: commercial.monthly_run_budget
|
||||
prompt: Is there a monthly budget for operating this, in that currency?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: digested
|
||||
commercial.monthly_run_budget: unknown
|
||||
compliance.frameworks: digested
|
||||
engagement.kind: digested
|
||||
intent.business_outcomes: assumed
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: unknown
|
||||
intent.statement: digested
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: digested
|
||||
metadata.revision: unknown
|
||||
metadata.source: digested
|
||||
operations.availability_hours: digested
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: digested
|
||||
organisation.existing_teams: assumed
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: assumed
|
||||
service_levels.recovery_time_hours: assumed
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: digested
|
||||
solution.build.duration_days: digested
|
||||
solution.cloud_provider: digested
|
||||
solution.conditions: digested
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: digested
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 3
|
||||
answered: 0
|
||||
assumed: 7
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
digested: 13
|
||||
@@ -0,0 +1,10 @@
|
||||
intent:
|
||||
business_outcomes: decide
|
||||
run:
|
||||
pre_approved: true
|
||||
sourcing:
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
model: provider_operated
|
||||
@@ -0,0 +1,79 @@
|
||||
[
|
||||
{
|
||||
"id": "C-1",
|
||||
"name": "Resource Hierarchy and Environment Boundary Manager",
|
||||
"requirements": [
|
||||
"FR-1",
|
||||
"NFR-1",
|
||||
"NFR-8",
|
||||
"NFR-9"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-2",
|
||||
"name": "Dedicated Private Hybrid Connectivity Gateway",
|
||||
"requirements": [
|
||||
"FR-2",
|
||||
"NFR-3",
|
||||
"NFR-14"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-3",
|
||||
"name": "Centralised Outbound Traffic Inspection and Egress Boundary",
|
||||
"requirements": [
|
||||
"FR-3",
|
||||
"NFR-2",
|
||||
"NFR-4"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-4",
|
||||
"name": "Centralised Immutable Audit Event and Compliance Log Repository",
|
||||
"requirements": [
|
||||
"FR-4",
|
||||
"NFR-7",
|
||||
"NFR-8"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-5",
|
||||
"name": "Automated Infrastructure Orchestration and Deployment Engine",
|
||||
"requirements": [
|
||||
"FR-5",
|
||||
"NFR-10"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-6",
|
||||
"name": "Federated Identity and Role Governance Authority",
|
||||
"requirements": [
|
||||
"FR-6",
|
||||
"NFR-5"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-7",
|
||||
"name": "Cryptographic Key Lifecycle and Encryption Controller",
|
||||
"requirements": [
|
||||
"NFR-6",
|
||||
"NFR-8"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-8",
|
||||
"name": "Platform Telemetry and Operational Alerting Engine",
|
||||
"requirements": [
|
||||
"NFR-11",
|
||||
"NFR-12",
|
||||
"NFR-15"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-9",
|
||||
"name": "Financial Governance and Budget Enforcement Monitor",
|
||||
"requirements": [
|
||||
"NFR-13"
|
||||
]
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,140 @@
|
||||
{
|
||||
"customer_case": "case-08-landing-zone",
|
||||
"execution_id": "case-08-landing-zone-185426",
|
||||
"session_id": "cdd6bfe7-2bd8-44af-8e15-9dcfa869eb84",
|
||||
"intent_version": 1,
|
||||
"workflow_request": "We are a UK-regulated payment platform expanding into Google Cloud. We need an\nenterprise-grade landing zone ready in under 10 weeks to support our core payments\nengine. All payment processing must comply with DORA and PCI-DSS v4.0. We have\nexisting on-premises systems that require private, low-latency connectivity over a\n10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and\nGitHub Actions for our delivery pipelines. Security requires that all egress\ntraffic flows through centralised inspection appliances before touching the public\ninternet, and customer data must be encrypted with keys we control.",
|
||||
"baseline": null,
|
||||
"overlay_skills": {},
|
||||
"terraform_modules": false,
|
||||
"scope": {
|
||||
"status": "BASELINE_LOCKED",
|
||||
"readiness": {
|
||||
"supplied": 44,
|
||||
"answered": 0,
|
||||
"assumed": 12,
|
||||
"unknown": 4,
|
||||
"not_applicable": 3
|
||||
}
|
||||
},
|
||||
"delivery_plan": {
|
||||
"work_packages": 9,
|
||||
"activities": 15,
|
||||
"working_days": 36.0,
|
||||
"weeks": 7.2,
|
||||
"team_size": 3,
|
||||
"window_weeks": 10,
|
||||
"within_window": true,
|
||||
"critical_path": [
|
||||
"A-6",
|
||||
"A-10",
|
||||
"A-13",
|
||||
"A-14",
|
||||
"A-15"
|
||||
]
|
||||
},
|
||||
"status": "completed",
|
||||
"warnings": [],
|
||||
"risks": [],
|
||||
"assessment": {
|
||||
"recommendations_quality": {
|
||||
"specific": 0.91,
|
||||
"actionable": 0.79,
|
||||
"trade_offs": 0.95,
|
||||
"traceable": 0.73
|
||||
},
|
||||
"mean": 0.84,
|
||||
"meets_bar": true
|
||||
},
|
||||
"phases": {
|
||||
"scoping": "approved",
|
||||
"requirements_discovery": "approved",
|
||||
"solution_architecture": "approved",
|
||||
"solution_implementation": "approved",
|
||||
"solution_validation": "approved",
|
||||
"packaging": "approved"
|
||||
},
|
||||
"solution_guide": "solution-architecture-guide.md",
|
||||
"customer_questions": "customer-questions.md",
|
||||
"changes": null,
|
||||
"deliverables": {
|
||||
"scope": {
|
||||
"document": "deliverables/scope.md",
|
||||
"attachments": [
|
||||
"scope.json",
|
||||
"scope.yaml"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"requirements": {
|
||||
"document": "deliverables/requirements.md",
|
||||
"attachments": [
|
||||
"requirements.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"technical_decomposition": {
|
||||
"document": "deliverables/technical_decomposition.md",
|
||||
"attachments": [
|
||||
"components.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"product_selection": {
|
||||
"document": "deliverables/product_selection.md",
|
||||
"attachments": [
|
||||
"products.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"design_recommendations": {
|
||||
"document": "deliverables/design_recommendations.md",
|
||||
"attachments": [
|
||||
"recommendations.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"target_architecture": {
|
||||
"document": "deliverables/target_architecture.md",
|
||||
"attachments": [
|
||||
"architecture.mmd",
|
||||
"target-architecture.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"architecture_description": {
|
||||
"document": "deliverables/architecture_description.md",
|
||||
"attachments": [],
|
||||
"status": "submitted"
|
||||
},
|
||||
"deployment_guidance": {
|
||||
"document": "deliverables/deployment_guidance.md",
|
||||
"attachments": [
|
||||
"implementation.json",
|
||||
"terraform/main.tf",
|
||||
"terraform/variables.tf",
|
||||
"terraform/versions.tf"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"validation_results": {
|
||||
"document": "deliverables/validation_results.md",
|
||||
"attachments": [
|
||||
"verdicts.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"work_breakdown": {
|
||||
"document": "deliverables/work_breakdown.md",
|
||||
"attachments": [
|
||||
"work-breakdown.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"solution_guide": {
|
||||
"document": "deliverables/solution_guide.md",
|
||||
"attachments": [],
|
||||
"status": "submitted"
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,38 @@
|
||||
[
|
||||
{
|
||||
"component": "C-1",
|
||||
"product": "Resource Manager"
|
||||
},
|
||||
{
|
||||
"component": "C-2",
|
||||
"product": "Cloud Interconnect"
|
||||
},
|
||||
{
|
||||
"component": "C-3",
|
||||
"product": "Palo Alto Networks VM-Series"
|
||||
},
|
||||
{
|
||||
"component": "C-4",
|
||||
"product": "Cloud Storage"
|
||||
},
|
||||
{
|
||||
"component": "C-5",
|
||||
"product": "GitHub Actions"
|
||||
},
|
||||
{
|
||||
"component": "C-6",
|
||||
"product": "IAM Workload Identity Federation"
|
||||
},
|
||||
{
|
||||
"component": "C-7",
|
||||
"product": "Cloud KMS"
|
||||
},
|
||||
{
|
||||
"component": "C-8",
|
||||
"product": "Cloud Monitoring"
|
||||
},
|
||||
{
|
||||
"component": "C-9",
|
||||
"product": "Cloud Billing"
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,248 @@
|
||||
[
|
||||
{
|
||||
"id": "DR-SEC-1",
|
||||
"pillar": "security",
|
||||
"text": "Implement a VPC Service Controls perimeter around all Cardholder Data Environment (CDE) projects and the centralized audit log buckets.",
|
||||
"components": [
|
||||
"C-1",
|
||||
"C-4"
|
||||
],
|
||||
"conditions": [
|
||||
"A VPC Service Controls perimeter encloses the CDE and audit log projects.",
|
||||
"The VPC Service Controls perimeter restricts ingress and egress to authorized traffic."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SEC-2",
|
||||
"pillar": "security",
|
||||
"text": "Apply Organization Policy constraints to disable default network creation, deny external IPs, prohibit service account key creation, and restrict resource locations.",
|
||||
"components": [
|
||||
"C-1"
|
||||
],
|
||||
"conditions": [
|
||||
"The compute.skipDefaultNetworkCreation constraint is enforced.",
|
||||
"The compute.vmExternalIpAccess constraint is enforced to deny all.",
|
||||
"The iam.disableServiceAccountKeyCreation constraint is enforced.",
|
||||
"The gcp.resourceLocations constraint restricts resources to europe-west2 and europe-west1."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SEC-3",
|
||||
"pillar": "security",
|
||||
"text": "Enable Confidential Computing on the payment engine Compute Engine instances to encrypt data in-use.",
|
||||
"components": [],
|
||||
"conditions": [
|
||||
"Confidential Computing is enabled on the core payment engine Compute Engine instances."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SEC-4",
|
||||
"pillar": "security",
|
||||
"text": "Deploy Sensitive Data Protection (Cloud DLP) inspection templates to detect and mask PAN data.",
|
||||
"components": [
|
||||
"C-4"
|
||||
],
|
||||
"conditions": [
|
||||
"Sensitive Data Protection (Cloud DLP) inspection templates are configured to detect and mask PAN data."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SEC-5",
|
||||
"pillar": "security",
|
||||
"text": "Enable Security Command Center at the organization level with Event and Container Threat Detection.",
|
||||
"components": [
|
||||
"C-1",
|
||||
"C-8"
|
||||
],
|
||||
"conditions": [
|
||||
"Security Command Center is activated at the organization level.",
|
||||
"Event Threat Detection and Container Threat Detection are enabled in SCC."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SEC-6",
|
||||
"pillar": "security",
|
||||
"text": "Implement event-driven automated responses using Eventarc and Cloud Run functions for SCC findings.",
|
||||
"components": [
|
||||
"C-8"
|
||||
],
|
||||
"conditions": [
|
||||
"Eventarc is configured to route high-severity SCC findings.",
|
||||
"Cloud Run functions are configured to execute automated remediation on Eventarc triggers."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-REL-1",
|
||||
"pillar": "reliability",
|
||||
"text": "Provision redundant Dedicated Cloud Interconnect circuits across distinct physical edge colocation facilities, terminating on redundant Cloud Routers with BFD.",
|
||||
"components": [
|
||||
"C-2"
|
||||
],
|
||||
"conditions": [
|
||||
"Dedicated Cloud Interconnect circuits are provisioned across redundant edge colocation facilities.",
|
||||
"Cloud Interconnects terminate on redundant Cloud Routers in each region.",
|
||||
"Bidirectional Forwarding Detection (BFD) is enabled on the Cloud Router BGP sessions."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-REL-2",
|
||||
"pillar": "reliability",
|
||||
"text": "Deploy Palo Alto VM-Series firewalls in a regional Managed Instance Group across at least three zones, fronted by an Internal Passthrough Network Load Balancer.",
|
||||
"components": [
|
||||
"C-3"
|
||||
],
|
||||
"conditions": [
|
||||
"Palo Alto VM-Series firewalls are deployed in a regional Managed Instance Group (MIG) across at least three zones.",
|
||||
"An Internal Passthrough Network Load Balancer routes traffic to the VM-Series MIG.",
|
||||
"Health checks are configured on the internal load balancer to probe firewall health."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-REL-3",
|
||||
"pillar": "reliability",
|
||||
"text": "Provision dedicated regional Cloud KMS key rings in both europe-west2 and europe-west1, granting workload identity service accounts Decrypter roles on both.",
|
||||
"components": [
|
||||
"C-7",
|
||||
"C-6"
|
||||
],
|
||||
"conditions": [
|
||||
"Regional Cloud KMS key rings are provisioned in both europe-west2 and europe-west1.",
|
||||
"Workload Identity Federation service accounts are granted Decrypter roles on both regional key sets."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-REL-4",
|
||||
"pillar": "reliability",
|
||||
"text": "Configure the Cloud Storage buckets for audit logging as Dual-Region spanning europe-west2 and europe-west1.",
|
||||
"components": [
|
||||
"C-4"
|
||||
],
|
||||
"conditions": [
|
||||
"Audit log Cloud Storage buckets are configured as Dual-Region spanning europe-west2 and europe-west1."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-REL-5",
|
||||
"pillar": "reliability",
|
||||
"text": "Isolate the Terraform state of the primary region from the standby region using multi-region Cloud Storage buckets with Object Versioning.",
|
||||
"components": [
|
||||
"C-5"
|
||||
],
|
||||
"conditions": [
|
||||
"Terraform state for primary and standby regions is decoupled into separate failure domains.",
|
||||
"Terraform state is stored in multi-region Cloud Storage buckets with Object Versioning enabled."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-OP-1",
|
||||
"pillar": "operational-excellence",
|
||||
"text": "Integrate Policy-as-Code validation into the GitHub Actions pull request workflows.",
|
||||
"components": [
|
||||
"C-5"
|
||||
],
|
||||
"conditions": [
|
||||
"GitHub Actions workflows include automated Policy-as-Code validation steps prior to deployment execution."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-OP-2",
|
||||
"pillar": "operational-excellence",
|
||||
"text": "Establish explicit Service Level Indicators (SLIs) and configure multi-burn-rate alerting policies in Cloud Monitoring.",
|
||||
"components": [
|
||||
"C-8"
|
||||
],
|
||||
"conditions": [
|
||||
"Service Level Objectives (SLOs) and SLIs are defined in Cloud Monitoring Service Monitoring.",
|
||||
"Multi-burn-rate alerting policies are configured based on the SLO error budget."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-OP-3",
|
||||
"pillar": "operational-excellence",
|
||||
"text": "Activate the IAM Recommender to continuously evaluate role bindings.",
|
||||
"components": [
|
||||
"C-6"
|
||||
],
|
||||
"conditions": [
|
||||
"IAM Recommender is activated on the foundation projects."
|
||||
],
|
||||
"outside_code": [
|
||||
"Permissions are continuously rightsized based on IAM Recommender findings."
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "DR-COST-1",
|
||||
"pillar": "cost-optimization",
|
||||
"text": "Enforce a mandatory labeling taxonomy through Organization Policies and export granular billing data to BigQuery.",
|
||||
"components": [
|
||||
"C-9",
|
||||
"C-1"
|
||||
],
|
||||
"conditions": [
|
||||
"Cloud Billing export to BigQuery is enabled.",
|
||||
"A mandatory labeling taxonomy is enforced via Organization Policy Service tags."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-COST-2",
|
||||
"pillar": "cost-optimization",
|
||||
"text": "Implement Cloud Storage Object Lifecycle Management to transition logs to Nearline storage after 30 days and to Coldline or Archive storage after 90 days.",
|
||||
"components": [
|
||||
"C-4"
|
||||
],
|
||||
"conditions": [
|
||||
"Object Lifecycle Management rules transition Cloud Storage objects to Nearline storage after 30 days.",
|
||||
"Object Lifecycle Management rules transition Cloud Storage objects to Coldline or Archive storage after 90 days."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-PERF-1",
|
||||
"pillar": "performance-optimization",
|
||||
"text": "Configure Cloud Routers with regional dynamic routing to localize egress traffic within the warm standby region.",
|
||||
"components": [
|
||||
"C-2"
|
||||
],
|
||||
"conditions": [
|
||||
"Cloud Routers are configured with regional dynamic routing mode."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-PERF-2",
|
||||
"pillar": "performance-optimization",
|
||||
"text": "Instrument the deployment with OpenTelemetry exporting to Cloud Trace, and use Cloud Profiler on the compute instances.",
|
||||
"components": [
|
||||
"C-8"
|
||||
],
|
||||
"conditions": [
|
||||
"OpenTelemetry tracing is configured to export to Cloud Trace.",
|
||||
"Cloud Profiler agents are enabled on the core payments engine instances."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SUST-1",
|
||||
"pillar": "sustainability",
|
||||
"text": "Implement a Pilot Light warm standby by maintaining active data replication while scaling the standby compute instances to a minimal baseline.",
|
||||
"components": [],
|
||||
"conditions": [
|
||||
"Secondary region compute instances are scaled to a minimal baseline (Pilot Light) configuration during normal operations."
|
||||
],
|
||||
"outside_code": []
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,280 @@
|
||||
[
|
||||
{
|
||||
"id": "FR-1",
|
||||
"kind": "functional",
|
||||
"text": "The platform foundation isolates development, staging, and production environments across distinct Google Cloud projects and resource folders.",
|
||||
"from": [
|
||||
"REQ-02"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "FR-2",
|
||||
"kind": "functional",
|
||||
"text": "The platform foundation establishes private bidirectional network connectivity between Google Cloud and on-premises core payment systems over Cloud Interconnect.",
|
||||
"from": [
|
||||
"REQ-03"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "FR-3",
|
||||
"kind": "functional",
|
||||
"text": "The platform foundation routes all outbound internet-bound traffic from workload spoke networks through centralised network security inspection appliances.",
|
||||
"from": [
|
||||
"REQ-03"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "FR-4",
|
||||
"kind": "functional",
|
||||
"text": "The platform foundation captures and exports all administrative and data access audit logs across environments into a centralised, tamper-resistant log repository.",
|
||||
"from": [
|
||||
"REQ-02"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "FR-5",
|
||||
"kind": "functional",
|
||||
"text": "The platform foundation provisions and manages all cloud infrastructure as code via automated CI/CD pipelines executing validated pull request workflows.",
|
||||
"from": [
|
||||
"REQ-01"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "FR-6",
|
||||
"kind": "functional",
|
||||
"text": "The platform foundation federates corporate identity for single sign-on and enforces least-privilege role-based access control for platform administrators and application squads.",
|
||||
"from": [
|
||||
"REQ-04"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-1",
|
||||
"kind": "non_functional",
|
||||
"text": "Environments are partitioned into development, staging, and production tiers, enforcing corp_workload controls on lower environments and pci_regulated_workload controls on production.",
|
||||
"conditions": [
|
||||
"Separate projects or folders exist for development, staging, and production environment tiers.",
|
||||
"Production environments enforce pci_regulated_workload archetype security controls.",
|
||||
"Development and staging environments enforce corp_workload archetype security controls."
|
||||
],
|
||||
"outside_code": [],
|
||||
"from": [
|
||||
"REQ-02",
|
||||
"governance.environment_tiers"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-2",
|
||||
"kind": "non_functional",
|
||||
"text": "Network connectivity is structured as a Shared VPC hub-and-spoke topology with zero direct internet ingress to workload subnets.",
|
||||
"conditions": [
|
||||
"A Shared VPC host project is connected to service projects across environment tiers.",
|
||||
"Workload subnets have private Google access enabled and no external public IP addresses assigned.",
|
||||
"Ingress firewall rules deny uninspected public internet traffic to workload subnets."
|
||||
],
|
||||
"outside_code": [],
|
||||
"from": [
|
||||
"REQ-02",
|
||||
"networking.topology",
|
||||
"networking.exposure"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-3",
|
||||
"kind": "non_functional",
|
||||
"text": "Hybrid connectivity to on-premises core payment systems is enabled via a 10Gbps Dedicated Cloud Interconnect.",
|
||||
"conditions": [
|
||||
"Dedicated Cloud Interconnect connections are configured for hybrid connectivity.",
|
||||
"Cloud Interconnect capacity is provisioned at 10Gbps bandwidth.",
|
||||
"Interconnect VLAN attachments are associated with Cloud Routers in the Shared VPC hub."
|
||||
],
|
||||
"outside_code": [],
|
||||
"from": [
|
||||
"REQ-03",
|
||||
"networking.hybrid_connectivity.enabled",
|
||||
"networking.hybrid_connectivity.type",
|
||||
"networking.hybrid_connectivity.bandwidth_gbps"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-4",
|
||||
"kind": "non_functional",
|
||||
"text": "All outbound internet traffic from workload spokes is forced through centralised inspection appliances deployed in the hub network.",
|
||||
"conditions": [
|
||||
"Inspection appliance instances are deployed in a centralised hub network.",
|
||||
"Custom VPC route tables direct 0.0.0.0/0 egress traffic from spokes to the centralised inspection appliance instances or internal load balancer."
|
||||
],
|
||||
"outside_code": [],
|
||||
"from": [
|
||||
"REQ-03",
|
||||
"networking.egress_control.model"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-5",
|
||||
"kind": "non_functional",
|
||||
"text": "Administrative access is authenticated via Entra ID single sign-on, and delivery pipelines authenticate via Workload Identity Federation without stored service account keys.",
|
||||
"conditions": [
|
||||
"Workload Identity Federation pools and providers are configured for GitHub Actions authentication.",
|
||||
"IAM bindings grant roles to federated GitHub Actions identities without downloadable service account keys.",
|
||||
"Corporate single sign-on is configured with Entra ID as the identity source of truth."
|
||||
],
|
||||
"outside_code": [],
|
||||
"from": [
|
||||
"REQ-04",
|
||||
"governance.identity_source_of_truth",
|
||||
"governance.pipeline_authentication"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-6",
|
||||
"kind": "non_functional",
|
||||
"text": "Customer confidential data is encrypted at rest using customer-managed encryption keys with a 90-day rotation schedule.",
|
||||
"conditions": [
|
||||
"Cloud KMS customer-managed encryption keys are configured for infrastructure resources storing confidential data.",
|
||||
"Cloud KMS keys have an automated rotation period set to 90 days (7776000s)."
|
||||
],
|
||||
"outside_code": [],
|
||||
"from": [
|
||||
"REQ-04",
|
||||
"compliance.encryption.type",
|
||||
"compliance.encryption.key_rotation_days"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-7",
|
||||
"kind": "non_functional",
|
||||
"text": "Audit logs across all environments are retained for 365 days in a storage bucket protected by an immutable retention policy.",
|
||||
"conditions": [
|
||||
"An organization-level or project-level log sink exports audit logs to a centralised Cloud Storage bucket.",
|
||||
"The centralised audit log storage bucket specifies a retention period of 365 days (31536000 seconds).",
|
||||
"The centralised audit log storage bucket has retention policy locking enabled to prevent modification or early deletion."
|
||||
],
|
||||
"outside_code": [],
|
||||
"from": [
|
||||
"REQ-02",
|
||||
"compliance.audit_logging.retention_days",
|
||||
"compliance.audit_logging.immutable_retention_policy"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-8",
|
||||
"kind": "non_functional",
|
||||
"text": "The platform foundation enforces DORA, ISO27001, and PCI-DSS v4.0 regulatory baselines and protects confidential data classification.",
|
||||
"conditions": [
|
||||
"Organization policy constraints enforce perimeter isolation and restrict unauthenticated resource sharing.",
|
||||
"IAM policies restrict access to confidential data resources to authorized service identities and roles."
|
||||
],
|
||||
"outside_code": [
|
||||
"The landing zone configuration aligns with DORA operational resiliency guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit."
|
||||
],
|
||||
"from": [
|
||||
"REQ-02",
|
||||
"compliance.frameworks",
|
||||
"compliance.data_classification"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-9",
|
||||
"kind": "non_functional",
|
||||
"text": "Platform foundation resources are provisioned across europe-west2 (primary) and europe-west1 (secondary) in a warm standby model, restricting data residency to the UK and EU.",
|
||||
"conditions": [
|
||||
"Primary landing zone network and foundation resources are provisioned in europe-west2.",
|
||||
"Secondary landing zone network and foundation standby resources are provisioned in europe-west1.",
|
||||
"Resource location organization policies restrict resource and data storage locations to europe-west2 and europe-west1."
|
||||
],
|
||||
"outside_code": [
|
||||
"The secondary region in europe-west1 operates as a warm standby ready to receive failover traffic.",
|
||||
"Data residency is guaranteed within the United Kingdom and European Union."
|
||||
],
|
||||
"from": [
|
||||
"REQ-02",
|
||||
"estate.regions.primary",
|
||||
"estate.regions.secondary",
|
||||
"estate.regions.resiliency_tier",
|
||||
"estate.data_residency"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-10",
|
||||
"kind": "non_functional",
|
||||
"text": "The platform foundation landing zone is delivered and operational for workload ingestion within 10 weeks.",
|
||||
"conditions": [
|
||||
"All landing zone foundation resources are codified in modular Terraform configurations."
|
||||
],
|
||||
"outside_code": [
|
||||
"Platform foundation is fully provisioned and validated for core payments engine workload ingestion within 10 weeks."
|
||||
],
|
||||
"from": [
|
||||
"REQ-01"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-11",
|
||||
"kind": "non_functional",
|
||||
"text": "The platform foundation maintains 99.9% availability with a 4-hour recovery time objective (RTO) and a 1-hour recovery point objective (RPO).",
|
||||
"conditions": [
|
||||
"Regional networking and core management services are deployed across at least three zones in the primary region."
|
||||
],
|
||||
"outside_code": [
|
||||
"Platform foundation infrastructure maintains measured monthly availability of at least 99.9%.",
|
||||
"Disaster recovery activation achieves a recovery time objective (RTO) of 4 hours.",
|
||||
"Disaster recovery processes achieve a recovery point objective (RPO) of 1 hour."
|
||||
],
|
||||
"from": [
|
||||
"REQ-02"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-12",
|
||||
"kind": "non_functional",
|
||||
"text": "Platform operations monitoring and alerting are implemented using Google Cloud Operations Suite with 24/7 alerting capabilities.",
|
||||
"conditions": [
|
||||
"Cloud Monitoring workspaces and notification channels are configured for the platform foundation.",
|
||||
"Alert policies are configured for Interconnect link degradation, appliance health, and egress routing failures."
|
||||
],
|
||||
"outside_code": [
|
||||
"Alert notifications trigger operational incident workflows for the 24/7 central platform operations team."
|
||||
],
|
||||
"from": []
|
||||
},
|
||||
{
|
||||
"id": "NFR-13",
|
||||
"kind": "non_functional",
|
||||
"text": "Infrastructure costs are tracked against a monthly budget of 25,000 GBP with automated alerting.",
|
||||
"conditions": [
|
||||
"A Cloud Billing budget is configured for the foundation projects with currency set to GBP.",
|
||||
"Budget alert thresholds are configured at 50%, 80%, 90%, and 100% of the 25,000 GBP monthly budget."
|
||||
],
|
||||
"outside_code": [
|
||||
"Monthly cloud foundation expenditure does not exceed the target allocation without operational sign-off."
|
||||
],
|
||||
"from": []
|
||||
},
|
||||
{
|
||||
"id": "NFR-14",
|
||||
"kind": "non_functional",
|
||||
"text": "Hybrid networking provides dedicated 10Gbps unthrottled throughput with minimal latency between Google Cloud and on-premises core systems.",
|
||||
"conditions": [
|
||||
"Cloud Routers configured for Interconnect advertise non-overlapping RFC 1918 BGP routes.",
|
||||
"Dedicated Interconnect VLAN attachments are configured with dedicated 10Gbps bandwidth allocation."
|
||||
],
|
||||
"outside_code": [
|
||||
"Hybrid connection provides deterministic low latency suitable for real-time payment transaction processing."
|
||||
],
|
||||
"from": [
|
||||
"REQ-03"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "NFR-15",
|
||||
"kind": "non_functional",
|
||||
"text": "Landing zone resources are deployed in Google Cloud regions with strong low-carbon energy ratings.",
|
||||
"conditions": [
|
||||
"Foundation resources are constrained to europe-west2 (London) and europe-west1 (Belgium) regions."
|
||||
],
|
||||
"outside_code": [
|
||||
"Deployments optimize carbon-free energy utilization based on Google Cloud regional CFE scores."
|
||||
],
|
||||
"from": []
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,233 @@
|
||||
{
|
||||
"kind": "platform_foundation",
|
||||
"stated": {
|
||||
"engagement": {
|
||||
"kind": "platform_foundation"
|
||||
},
|
||||
"intent": {
|
||||
"statement": "We are a UK-regulated payment platform expanding into Google Cloud. We need an\nenterprise-grade landing zone ready in under 10 weeks to support our core payments\nengine. All payment processing must comply with DORA and PCI-DSS v4.0. We have\nexisting on-premises systems that require private, low-latency connectivity over a\n10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and\nGitHub Actions for our delivery pipelines. Security requires that all egress\ntraffic flows through centralised inspection appliances before touching the public\ninternet, and customer data must be encrypted with keys we control.\n",
|
||||
"requirements": [
|
||||
{
|
||||
"id": "REQ-01",
|
||||
"category": "Timeline",
|
||||
"statement": "Platform foundation must be ready for workload ingestion within 10 weeks."
|
||||
},
|
||||
{
|
||||
"id": "REQ-02",
|
||||
"category": "Compliance",
|
||||
"statement": "Must achieve DORA resiliency alignment and PCI-DSS v4.0 perimeter isolation."
|
||||
},
|
||||
{
|
||||
"id": "REQ-03",
|
||||
"category": "Networking",
|
||||
"statement": "10Gbps on-premises hybrid connectivity; centralised inspection appliances for egress."
|
||||
},
|
||||
{
|
||||
"id": "REQ-04",
|
||||
"category": "Identity and security",
|
||||
"statement": "Workload identity federation with GitHub Actions; Entra ID single sign-on; customer-managed encryption keys."
|
||||
}
|
||||
],
|
||||
"exclusions": [
|
||||
"Application container deployment; workloads are managed by application squads.",
|
||||
"An active-active secondary region in phase 1; warm standby is acceptable."
|
||||
]
|
||||
},
|
||||
"estate": {
|
||||
"cloud_provider": "gcp",
|
||||
"mode": "greenfield",
|
||||
"regions": {
|
||||
"primary": "europe-west2",
|
||||
"secondary": "europe-west1",
|
||||
"resiliency_tier": "warm_standby"
|
||||
},
|
||||
"data_residency": "United Kingdom and European Union",
|
||||
"existing_systems": "On-premises payment systems that stay in place and connect over the interconnect."
|
||||
},
|
||||
"workload": {
|
||||
"availability": {
|
||||
"hours": "always"
|
||||
}
|
||||
},
|
||||
"compliance": {
|
||||
"industry": "financial_services",
|
||||
"frameworks": [
|
||||
"DORA",
|
||||
"ISO27001",
|
||||
"PCI_DSS_v4"
|
||||
],
|
||||
"data_classification": "confidential",
|
||||
"encryption": {
|
||||
"type": "cmek",
|
||||
"key_rotation_days": 90
|
||||
},
|
||||
"audit_logging": {
|
||||
"retention_days": 365,
|
||||
"immutable_retention_policy": true
|
||||
}
|
||||
},
|
||||
"networking": {
|
||||
"exposure": "internal_only",
|
||||
"topology": "shared_vpc_hub_and_spoke",
|
||||
"hybrid_connectivity": {
|
||||
"enabled": true,
|
||||
"type": "cloud_interconnect",
|
||||
"bandwidth_gbps": 10
|
||||
},
|
||||
"egress_control": {
|
||||
"model": "centralized_appliance"
|
||||
}
|
||||
},
|
||||
"governance": {
|
||||
"identity_source_of_truth": "Entra ID",
|
||||
"pipeline_authentication": "workload identity federation",
|
||||
"environment_tiers": [
|
||||
{
|
||||
"name": "development",
|
||||
"archetype": "corp_workload"
|
||||
},
|
||||
{
|
||||
"name": "staging",
|
||||
"archetype": "corp_workload"
|
||||
},
|
||||
{
|
||||
"name": "production",
|
||||
"archetype": "pci_regulated_workload"
|
||||
}
|
||||
]
|
||||
},
|
||||
"operations": {
|
||||
"operating_model": "central platform team brokering access for application squads",
|
||||
"support_hours": "always"
|
||||
},
|
||||
"delivery": {
|
||||
"window_weeks": 10,
|
||||
"commercial_model": "fixed_price_milestone",
|
||||
"iac_tooling": "terraform",
|
||||
"ci_cd": "GitHub Actions",
|
||||
"team_size": 3,
|
||||
"working_days_per_week": 5
|
||||
},
|
||||
"cost": {
|
||||
"currency": "GBP"
|
||||
}
|
||||
},
|
||||
"binding": [
|
||||
"estate.regions.primary",
|
||||
"estate.regions.secondary",
|
||||
"estate.regions.resiliency_tier",
|
||||
"estate.data_residency",
|
||||
"compliance.frameworks",
|
||||
"compliance.data_classification",
|
||||
"compliance.encryption.type",
|
||||
"compliance.encryption.key_rotation_days",
|
||||
"compliance.audit_logging.retention_days",
|
||||
"compliance.audit_logging.immutable_retention_policy",
|
||||
"networking.exposure",
|
||||
"networking.topology",
|
||||
"networking.hybrid_connectivity.enabled",
|
||||
"networking.hybrid_connectivity.type",
|
||||
"networking.hybrid_connectivity.bandwidth_gbps",
|
||||
"networking.egress_control.model",
|
||||
"governance.identity_source_of_truth",
|
||||
"governance.pipeline_authentication",
|
||||
"governance.environment_tiers"
|
||||
],
|
||||
"assumed": [
|
||||
{
|
||||
"field": "intent.success_criteria",
|
||||
"value": [
|
||||
"Platform foundation ready for workload ingestion within 10 weeks",
|
||||
"Compliance achieved with DORA and PCI-DSS v4.0 requirements",
|
||||
"Hybrid connectivity established via 10Gbps Dedicated Interconnect",
|
||||
"Centralised egress inspection operational",
|
||||
"Identity federation and CMEK security controls implemented"
|
||||
],
|
||||
"why": "Assumed standard success criteria based on delivery within 10 weeks and compliance with DORA and PCI-DSS v4.0."
|
||||
},
|
||||
{
|
||||
"field": "workload.availability.target",
|
||||
"value": "99.9%",
|
||||
"why": "Assumed 99.9% availability target for platform foundation infrastructure aligned with warm standby secondary region."
|
||||
},
|
||||
{
|
||||
"field": "workload.availability.recovery_time",
|
||||
"value": "4 hours",
|
||||
"why": "Assumed 4 hours recovery time objective (RTO) for platform foundation services in warm standby."
|
||||
},
|
||||
{
|
||||
"field": "workload.availability.recovery_point",
|
||||
"value": "1 hour",
|
||||
"why": "Assumed 1 hour recovery point objective (RPO) for platform foundation configuration and state."
|
||||
},
|
||||
{
|
||||
"field": "networking.egress_control.appliance_vendor",
|
||||
"value": "Palo Alto Networks VM-Series",
|
||||
"why": "Assumed Palo Alto Networks VM-Series as enterprise inspection appliance for centralized egress control."
|
||||
},
|
||||
{
|
||||
"field": "networking.cidr_allocations",
|
||||
"value": "RFC 1918 non-overlapping IP allocation (10.0.0.0/16 partitioned across environments) sized for growth",
|
||||
"why": "Assumed RFC 1918 non-overlapping IP allocation (10.0.0.0/16 partitioned across environments) sized for growth."
|
||||
},
|
||||
{
|
||||
"field": "operations.monitoring",
|
||||
"value": "Google Cloud Operations Suite with availability and error alerting",
|
||||
"why": "Assumed native Google Cloud Operations Suite (Cloud Monitoring and Cloud Logging) with availability and error alerting."
|
||||
},
|
||||
{
|
||||
"field": "operations.change_process",
|
||||
"value": "GitHub Actions pull request workflow with automated Terraform plan validation and peer review",
|
||||
"why": "Assumed GitHub Actions pull request workflow with automated Terraform plan validation and peer approval."
|
||||
},
|
||||
{
|
||||
"field": "integrations",
|
||||
"value": [
|
||||
{
|
||||
"criticality": "critical",
|
||||
"direction": "bidirectional",
|
||||
"name": "On-premises core payment systems"
|
||||
}
|
||||
],
|
||||
"why": "Assumed integration with existing on-premises core payment systems via Dedicated Interconnect."
|
||||
},
|
||||
{
|
||||
"field": "cost.monthly_budget",
|
||||
"value": 25000,
|
||||
"why": "Assumed indicative monthly foundation infrastructure budget of 25000 GBP for 10Gbps interconnect, inspection appliances, and core services."
|
||||
},
|
||||
{
|
||||
"field": "constraints.products_required",
|
||||
"value": [],
|
||||
"why": "No mandated third-party products beyond stated tooling (GCP, Terraform, GitHub Actions, Entra ID)."
|
||||
},
|
||||
{
|
||||
"field": "constraints.products_forbidden",
|
||||
"value": [],
|
||||
"why": "No forbidden products specified."
|
||||
}
|
||||
],
|
||||
"to_decide": [],
|
||||
"to_ask": [
|
||||
{
|
||||
"field": "metadata.engagement_reference",
|
||||
"prompt": "What is metadata.engagement_reference?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "delivery.target_start_date",
|
||||
"prompt": "When should work start?",
|
||||
"severity": "LOW"
|
||||
},
|
||||
{
|
||||
"field": "constraints.other",
|
||||
"prompt": "What is constraints.other?",
|
||||
"severity": "LOW"
|
||||
}
|
||||
],
|
||||
"not_applicable": [
|
||||
"workload.users.count",
|
||||
"workload.users.peak_concurrent",
|
||||
"workload.users.who"
|
||||
]
|
||||
}
|
||||
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,529 @@
|
||||
{
|
||||
"dry_run": {
|
||||
"evidence": "Success! The configuration is valid.",
|
||||
"verdict": "pass"
|
||||
},
|
||||
"checks": [
|
||||
{
|
||||
"check": "K-1",
|
||||
"evidence": "display_name = \"Dev Folder\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-2",
|
||||
"evidence": "display_name = \"Staging Folder\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-3",
|
||||
"evidence": "display_name = \"Production Folder\""
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "tag_value = google_tags_tag_value.corp_workload.id",
|
||||
"check": "K-4"
|
||||
},
|
||||
{
|
||||
"check": "K-5",
|
||||
"verdict": "pass",
|
||||
"evidence": "host_project = google_compute_shared_vpc_host_project.hub.project"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "host_project = google_compute_shared_vpc_host_project.hub.project",
|
||||
"check": "K-6"
|
||||
},
|
||||
{
|
||||
"check": "K-7",
|
||||
"evidence": "host_project = google_compute_shared_vpc_host_project.hub.project",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "private_ip_google_access = true",
|
||||
"check": "K-8"
|
||||
},
|
||||
{
|
||||
"check": "K-9",
|
||||
"evidence": "private_ip_google_access = true",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-10",
|
||||
"evidence": "direction = \"INGRESS\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-11",
|
||||
"verdict": "pass",
|
||||
"evidence": "protocol = \"all\""
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "source_ranges = [\"0.0.0.0/0\"]",
|
||||
"check": "K-12"
|
||||
},
|
||||
{
|
||||
"check": "K-13",
|
||||
"evidence": "type = \"DEDICATED\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "type = \"DEDICATED\"",
|
||||
"verdict": "pass",
|
||||
"check": "K-14"
|
||||
},
|
||||
{
|
||||
"check": "K-15",
|
||||
"verdict": "pass",
|
||||
"evidence": "bandwidth = \"BPS_10G\""
|
||||
},
|
||||
{
|
||||
"evidence": "bandwidth = \"BPS_10G\"",
|
||||
"verdict": "pass",
|
||||
"check": "K-16"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "router = google_compute_router.primary.id",
|
||||
"check": "K-17"
|
||||
},
|
||||
{
|
||||
"evidence": "network = google_compute_network.hub.id",
|
||||
"verdict": "pass",
|
||||
"check": "K-18"
|
||||
},
|
||||
{
|
||||
"check": "K-19",
|
||||
"evidence": "dest_range = \"0.0.0.0/0\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-20",
|
||||
"evidence": "next_hop_ilb = google_compute_forwarding_rule.palo_alto_ilb.id"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-21",
|
||||
"evidence": "issuer_uri = \"https://token.actions.githubusercontent.com\""
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-22",
|
||||
"evidence": "member = \"principalSet://iam.googleapis.com/${google_iam_workload_identity_pool.wif_pool.name}/attribute.repository/my-org/my-repo\""
|
||||
},
|
||||
{
|
||||
"evidence": "idp_metadata_xml = \"<EntityDescriptor></EntityDescriptor>\"",
|
||||
"verdict": "pass",
|
||||
"check": "K-23"
|
||||
},
|
||||
{
|
||||
"evidence": "purpose = \"ENCRYPT_DECRYPT\"",
|
||||
"verdict": "pass",
|
||||
"check": "K-24"
|
||||
},
|
||||
{
|
||||
"check": "K-25",
|
||||
"evidence": "purpose = \"ENCRYPT_DECRYPT\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-26",
|
||||
"verdict": "pass",
|
||||
"evidence": "rotation_period = \"7776000s\""
|
||||
},
|
||||
{
|
||||
"check": "K-27",
|
||||
"evidence": "rotation_period = \"7776000s\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "destination = \"storage.googleapis.com/${google_storage_bucket.audit_logs.name}\"",
|
||||
"verdict": "pass",
|
||||
"check": "K-28"
|
||||
},
|
||||
{
|
||||
"check": "K-29",
|
||||
"verdict": "pass",
|
||||
"evidence": "retention_period = 31536000"
|
||||
},
|
||||
{
|
||||
"check": "K-30",
|
||||
"verdict": "pass",
|
||||
"evidence": "is_locked = true"
|
||||
},
|
||||
{
|
||||
"evidence": "restricted_services = [\"compute.googleapis.com\"]",
|
||||
"verdict": "pass",
|
||||
"check": "K-31"
|
||||
},
|
||||
{
|
||||
"check": "K-32",
|
||||
"evidence": "role = \"roles/cloudkms.cryptoKeyEncrypterDecrypter\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-33",
|
||||
"evidence": "region = \"europe-west2\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-34",
|
||||
"verdict": "pass",
|
||||
"evidence": "region = \"europe-west2\""
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-35",
|
||||
"evidence": "region = \"europe-west1\""
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "constraint = \"gcp.resourceLocations\"",
|
||||
"check": "K-36"
|
||||
},
|
||||
{
|
||||
"check": "K-37",
|
||||
"verdict": "pass",
|
||||
"evidence": "values = [\"in:europe-west2\", \"in:europe-west1\"]"
|
||||
},
|
||||
{
|
||||
"check": "K-38",
|
||||
"evidence": "project = var.project_id",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "distribution_policy_zones = [\"europe-west2-a\", \"europe-west2-b\", \"europe-west2-c\"]",
|
||||
"check": "K-39"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-40",
|
||||
"evidence": "notification_channels = [google_monitoring_notification_channel.email.name]"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "condition_threshold is defined",
|
||||
"check": "K-41"
|
||||
},
|
||||
{
|
||||
"evidence": "currency_code = \"GBP\"",
|
||||
"check": "K-42",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "threshold_percent includes 0.5, 0.8, 0.9, 1.0",
|
||||
"check": "K-43"
|
||||
},
|
||||
{
|
||||
"check": "K-44",
|
||||
"verdict": "pass",
|
||||
"evidence": "units = \"25000\""
|
||||
},
|
||||
{
|
||||
"evidence": "advertise_mode = \"CUSTOM\"",
|
||||
"verdict": "pass",
|
||||
"check": "K-45"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "advertise_mode = \"CUSTOM\"",
|
||||
"check": "K-46"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "bandwidth = \"BPS_10G\"",
|
||||
"check": "K-47"
|
||||
},
|
||||
{
|
||||
"evidence": "bandwidth = \"BPS_10G\"",
|
||||
"verdict": "pass",
|
||||
"check": "K-48"
|
||||
},
|
||||
{
|
||||
"check": "K-49",
|
||||
"verdict": "pass",
|
||||
"evidence": "values = [\"in:europe-west2\", \"in:europe-west1\"]"
|
||||
},
|
||||
{
|
||||
"evidence": "resources = [\"projects/${var.prod_project_id}\", \"projects/${var.project_id}\"]",
|
||||
"check": "K-50",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-51",
|
||||
"evidence": "ingress_policies and egress_policies are configured"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "constraint = \"compute.skipDefaultNetworkCreation\"",
|
||||
"check": "K-52"
|
||||
},
|
||||
{
|
||||
"evidence": "enforced = true",
|
||||
"verdict": "pass",
|
||||
"check": "K-53"
|
||||
},
|
||||
{
|
||||
"check": "K-54",
|
||||
"evidence": "constraint = \"compute.vmExternalIpAccess\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "all = true",
|
||||
"check": "K-55"
|
||||
},
|
||||
{
|
||||
"evidence": "constraint = \"iam.disableServiceAccountKeyCreation\"",
|
||||
"check": "K-56",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-57",
|
||||
"evidence": "enforced = true",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-58",
|
||||
"evidence": "constraint = \"gcp.resourceLocations\""
|
||||
},
|
||||
{
|
||||
"evidence": "values = [\"in:europe-west2\", \"in:europe-west1\"]",
|
||||
"verdict": "pass",
|
||||
"check": "K-59"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-60",
|
||||
"evidence": "enable_confidential_compute = true"
|
||||
},
|
||||
{
|
||||
"check": "K-61",
|
||||
"evidence": "name = \"CREDIT_CARD_NUMBER\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-62",
|
||||
"evidence": "event_data_content_type = \"application/json\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "attribute = \"type\", value = \"google.cloud.securitycenter.finding.v1.saved\"",
|
||||
"check": "K-63",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "event_type = \"google.cloud.securitycenter.finding.v1.saved\"",
|
||||
"verdict": "pass",
|
||||
"check": "K-64"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "interconnect = var.interconnect_1_url",
|
||||
"check": "K-65"
|
||||
},
|
||||
{
|
||||
"evidence": "interconnect = var.interconnect_2_url",
|
||||
"verdict": "pass",
|
||||
"check": "K-66"
|
||||
},
|
||||
{
|
||||
"check": "K-67",
|
||||
"evidence": "router = google_compute_router.primary.id",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-68",
|
||||
"evidence": "session_initialization_mode = \"ACTIVE\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-69",
|
||||
"evidence": "distribution_policy_zones = [\"europe-west2-a\", \"europe-west2-b\", \"europe-west2-c\"]"
|
||||
},
|
||||
{
|
||||
"evidence": "load_balancing_scheme = \"INTERNAL\"",
|
||||
"check": "K-70",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "health_checks = [google_compute_health_check.palo_alto_ilb_hc.id]",
|
||||
"verdict": "pass",
|
||||
"check": "K-71"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-72",
|
||||
"evidence": "location = \"europe-west2\""
|
||||
},
|
||||
{
|
||||
"evidence": "location = \"europe-west1\"",
|
||||
"check": "K-73",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "role = \"roles/cloudkms.cryptoKeyDecrypter\"",
|
||||
"verdict": "pass",
|
||||
"check": "K-74"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "data_locations = [\"EUROPE-WEST1\", \"EUROPE-WEST2\"]",
|
||||
"check": "K-75"
|
||||
},
|
||||
{
|
||||
"check": "K-76",
|
||||
"verdict": "pass",
|
||||
"evidence": "name = \"${var.project_id}-tfstate-primary\""
|
||||
},
|
||||
{
|
||||
"evidence": "name = \"${var.project_id}-tfstate-secondary\"",
|
||||
"check": "K-77",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "enabled = true",
|
||||
"check": "K-78",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-79",
|
||||
"evidence": "enabled = true",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "goal = 0.999",
|
||||
"verdict": "pass",
|
||||
"check": "K-80"
|
||||
},
|
||||
{
|
||||
"evidence": "filter = \"select_slo_burn_rate(\\\"${google_monitoring_slo.platform_slo.name}\\\", 3600s)\"",
|
||||
"verdict": "pass",
|
||||
"check": "K-81"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-82",
|
||||
"evidence": "service = \"recommender.googleapis.com\""
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "age = 30",
|
||||
"check": "K-83"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-84",
|
||||
"evidence": "type = \"SetStorageClass\", storage_class = \"NEARLINE\""
|
||||
},
|
||||
{
|
||||
"check": "K-85",
|
||||
"verdict": "pass",
|
||||
"evidence": "age = 90"
|
||||
},
|
||||
{
|
||||
"check": "K-86",
|
||||
"evidence": "type = \"SetStorageClass\", storage_class = \"ARCHIVE\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-87",
|
||||
"evidence": "routing_mode = \"REGIONAL\""
|
||||
},
|
||||
{
|
||||
"evidence": "min_replicas = 1",
|
||||
"check": "K-88",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "short_name = \"environment\"",
|
||||
"check": "K-89",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-90",
|
||||
"evidence": "destination = \"bigquery.googleapis.com/...\""
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-91",
|
||||
"evidence": "tag_value = google_tags_tag_value.pci_regulated.id"
|
||||
},
|
||||
{
|
||||
"check": "K-92",
|
||||
"evidence": "check_interval_sec = 5",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-93",
|
||||
"evidence": "disabled = false"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"check": "K-94",
|
||||
"evidence": "disabled = false"
|
||||
},
|
||||
{
|
||||
"evidence": "display_name = \"Platform Custom Service\"",
|
||||
"check": "K-95",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-96",
|
||||
"verdict": "pass",
|
||||
"evidence": "base_instance_name = \"palo-alto-secondary\""
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "session_initialization_mode = \"ACTIVE\"",
|
||||
"check": "K-97"
|
||||
},
|
||||
{
|
||||
"evidence": "min_receive_interval = 100",
|
||||
"check": "K-99",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"check": "K-100",
|
||||
"verdict": "pass",
|
||||
"evidence": "min_receive_interval = 100"
|
||||
},
|
||||
{
|
||||
"check": "K-101",
|
||||
"evidence": "role = \"roles/cloudkms.cryptoKeyDecrypter\"",
|
||||
"verdict": "pass"
|
||||
},
|
||||
{
|
||||
"evidence": "tag_value = google_tags_tag_value.corp_workload.id",
|
||||
"verdict": "pass",
|
||||
"check": "K-102"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "router = google_compute_router.primary.id",
|
||||
"check": "K-103"
|
||||
},
|
||||
{
|
||||
"verdict": "pass",
|
||||
"evidence": "min_transmit_interval = 100",
|
||||
"check": "K-104"
|
||||
},
|
||||
{
|
||||
"check": "K-105",
|
||||
"evidence": "min_transmit_interval = 100",
|
||||
"verdict": "pass"
|
||||
}
|
||||
],
|
||||
"proposed_additions": []
|
||||
}
|
||||
@@ -0,0 +1,332 @@
|
||||
{
|
||||
"work_packages": [
|
||||
{
|
||||
"id": "WP-0",
|
||||
"name": "Platform Foundation",
|
||||
"parent": null,
|
||||
"elements": [],
|
||||
"scope": "The complete enterprise-grade landing zone.",
|
||||
"produces": [
|
||||
"an operational landing zone"
|
||||
],
|
||||
"skills": [
|
||||
"cloud architecture"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "WP-1",
|
||||
"name": "Automated Infrastructure Orchestration",
|
||||
"parent": "WP-0",
|
||||
"elements": [
|
||||
"E-42",
|
||||
"E-43"
|
||||
],
|
||||
"scope": "CI/CD orchestration, state management, and API enablement.",
|
||||
"produces": [
|
||||
"Terraform state buckets for primary and secondary regions"
|
||||
],
|
||||
"skills": [
|
||||
"cloud engineering"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "WP-2",
|
||||
"name": "Federated Identity and Role Governance",
|
||||
"parent": "WP-0",
|
||||
"elements": [
|
||||
"E-23",
|
||||
"E-24",
|
||||
"E-25",
|
||||
"E-26",
|
||||
"E-27",
|
||||
"E-45"
|
||||
],
|
||||
"scope": "Authentication for delivery pipelines and workforce SSO.",
|
||||
"produces": [
|
||||
"Workload Identity Federation for GitHub Actions and Entra ID SSO"
|
||||
],
|
||||
"skills": [
|
||||
"identity and access management"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "WP-3",
|
||||
"name": "Resource Hierarchy and Environment Boundary",
|
||||
"parent": "WP-0",
|
||||
"elements": [
|
||||
"E-1",
|
||||
"E-2",
|
||||
"E-3",
|
||||
"E-4",
|
||||
"E-5",
|
||||
"E-6",
|
||||
"E-7",
|
||||
"E-8",
|
||||
"E-9",
|
||||
"E-10",
|
||||
"E-34",
|
||||
"E-35",
|
||||
"E-36",
|
||||
"E-37",
|
||||
"E-38",
|
||||
"E-50",
|
||||
"E-51",
|
||||
"E-55",
|
||||
"E-60"
|
||||
],
|
||||
"scope": "Google Cloud resource hierarchy, shared VPC projects, networking, and organization policies.",
|
||||
"produces": [
|
||||
"Folders, projects, networking, and organization policies ensuring isolation"
|
||||
],
|
||||
"skills": [
|
||||
"cloud engineering",
|
||||
"network engineering"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "WP-4",
|
||||
"name": "Cryptographic Key Lifecycle",
|
||||
"parent": "WP-0",
|
||||
"elements": [
|
||||
"E-28",
|
||||
"E-29",
|
||||
"E-30",
|
||||
"E-31",
|
||||
"E-49",
|
||||
"E-58",
|
||||
"E-59"
|
||||
],
|
||||
"scope": "Customer-managed encryption keys (CMEK) and cryptographic isolation.",
|
||||
"produces": [
|
||||
"Primary and secondary KMS key rings and crypto keys with IAM bindings"
|
||||
],
|
||||
"skills": [
|
||||
"security engineering"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "WP-5",
|
||||
"name": "Audit, Compliance, and Financial Governance",
|
||||
"parent": "WP-0",
|
||||
"elements": [
|
||||
"E-21",
|
||||
"E-22",
|
||||
"E-33",
|
||||
"E-39",
|
||||
"E-46",
|
||||
"E-54"
|
||||
],
|
||||
"scope": "Immutable compliance logs, DLP templates, and budget enforcement.",
|
||||
"produces": [
|
||||
"Immutable audit log storage, billing budgets, and DLP inspection templates"
|
||||
],
|
||||
"skills": [
|
||||
"cloud engineering",
|
||||
"finops"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "WP-6",
|
||||
"name": "Centralised Outbound Traffic Inspection",
|
||||
"parent": "WP-0",
|
||||
"elements": [
|
||||
"E-15",
|
||||
"E-16",
|
||||
"E-17",
|
||||
"E-18",
|
||||
"E-19",
|
||||
"E-20",
|
||||
"E-47",
|
||||
"E-48",
|
||||
"E-53"
|
||||
],
|
||||
"scope": "Egress inspection and threat prevention using Palo Alto VM-Series.",
|
||||
"produces": [
|
||||
"Palo Alto VM-Series firewalls with internal load balancing and egress routing"
|
||||
],
|
||||
"skills": [
|
||||
"network security engineering"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "WP-7",
|
||||
"name": "Dedicated Private Hybrid Connectivity",
|
||||
"parent": "WP-0",
|
||||
"elements": [
|
||||
"E-11",
|
||||
"E-12",
|
||||
"E-13",
|
||||
"E-14",
|
||||
"E-56",
|
||||
"E-57"
|
||||
],
|
||||
"scope": "Dedicated Interconnect termination and dynamic BGP routing.",
|
||||
"produces": [
|
||||
"Primary and secondary Cloud Routers with Dedicated Interconnect VLAN attachments"
|
||||
],
|
||||
"skills": [
|
||||
"network engineering"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "WP-8",
|
||||
"name": "Platform Telemetry and Operational Alerting",
|
||||
"parent": "WP-0",
|
||||
"elements": [
|
||||
"E-32",
|
||||
"E-40",
|
||||
"E-41",
|
||||
"E-44",
|
||||
"E-52"
|
||||
],
|
||||
"scope": "SLO tracking, multi-burn-rate alerting, and SCC automated remediation.",
|
||||
"produces": [
|
||||
"SLOs, alerting policies, and SCC automated remediation functions"
|
||||
],
|
||||
"skills": [
|
||||
"site reliability engineering"
|
||||
]
|
||||
}
|
||||
],
|
||||
"activities": [
|
||||
{
|
||||
"id": "A-1",
|
||||
"work_package": "WP-1",
|
||||
"name": "Enable Google Cloud APIs",
|
||||
"days": 0.5,
|
||||
"after": []
|
||||
},
|
||||
{
|
||||
"id": "A-2",
|
||||
"work_package": "WP-1",
|
||||
"name": "Setup CI/CD Pipeline and State Buckets",
|
||||
"days": 1,
|
||||
"after": [
|
||||
"A-1"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-3",
|
||||
"work_package": "WP-2",
|
||||
"name": "Configure Workload Identity and Entra ID SSO",
|
||||
"days": 1.5,
|
||||
"after": [
|
||||
"A-2"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-4",
|
||||
"work_package": "WP-3",
|
||||
"name": "Provision Resource Hierarchy and Enforce Org Policies",
|
||||
"days": 2.5,
|
||||
"after": [
|
||||
"A-3"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-5",
|
||||
"work_package": "WP-3",
|
||||
"name": "Provision Hub and Spoke VPC Networks",
|
||||
"days": 2,
|
||||
"after": [
|
||||
"A-4"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-6",
|
||||
"work_package": "WP-7",
|
||||
"name": "Order and provision the Interconnect carrier circuits",
|
||||
"days": 30,
|
||||
"owner": "customer",
|
||||
"assumption": "The customer manages the carrier's lead time and physical cross-connects.",
|
||||
"after": []
|
||||
},
|
||||
{
|
||||
"id": "A-7",
|
||||
"work_package": "WP-4",
|
||||
"name": "Configure Cloud KMS and Key Rings",
|
||||
"days": 1.5,
|
||||
"after": [
|
||||
"A-4"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-8",
|
||||
"work_package": "WP-5",
|
||||
"name": "Set up Audit Logging, DLP, and Billing Budgets",
|
||||
"days": 2,
|
||||
"after": [
|
||||
"A-4"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-9",
|
||||
"work_package": "WP-6",
|
||||
"name": "Deploy Palo Alto Egress Firewall Appliances",
|
||||
"days": 5,
|
||||
"after": [
|
||||
"A-5"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-10",
|
||||
"work_package": "WP-7",
|
||||
"name": "Configure Cloud Routers and Terminate BGP over Interconnect",
|
||||
"days": 3,
|
||||
"after": [
|
||||
"A-5",
|
||||
"A-6"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-11",
|
||||
"work_package": "WP-3",
|
||||
"name": "Implement VPC Service Controls",
|
||||
"days": 2,
|
||||
"after": [
|
||||
"A-5",
|
||||
"A-7",
|
||||
"A-8"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-12",
|
||||
"work_package": "WP-8",
|
||||
"name": "Deploy Platform Telemetry, SLOs, and SCC Auto-remediation",
|
||||
"days": 2.5,
|
||||
"after": [
|
||||
"A-8",
|
||||
"A-11"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-13",
|
||||
"work_package": "WP-1",
|
||||
"name": "Run validation in development environment",
|
||||
"days": 1,
|
||||
"after": [
|
||||
"A-9",
|
||||
"A-10",
|
||||
"A-12"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-14",
|
||||
"work_package": "WP-1",
|
||||
"name": "Run validation in staging environment",
|
||||
"days": 1,
|
||||
"after": [
|
||||
"A-13"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "A-15",
|
||||
"work_package": "WP-1",
|
||||
"name": "Run validation in production environment",
|
||||
"days": 1,
|
||||
"after": [
|
||||
"A-14"
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,15 @@
|
||||
# Intent 2: case-08-landing-zone
|
||||
|
||||
- Recorded: 2026-10-21T22:19:12+00:00
|
||||
- Execution: `case-02-from-architecture-r2`
|
||||
|
||||
## What the customer wants
|
||||
|
||||
We are a UK-regulated payment platform expanding into Google Cloud. We need an
|
||||
enterprise-grade landing zone ready in under 10 weeks to support our core payments
|
||||
engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have
|
||||
existing on-premises systems that require private, low-latency connectivity over a
|
||||
10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and
|
||||
GitHub Actions for our delivery pipelines. Security requires that all egress
|
||||
traffic flows through centralised inspection appliances before touching the public
|
||||
internet, and customer data must be encrypted with keys we control.
|
||||
@@ -0,0 +1,407 @@
|
||||
schema_version: 1
|
||||
metadata:
|
||||
customer_case: case-08-landing-zone
|
||||
client_name: ask
|
||||
author: ask
|
||||
revision: ask
|
||||
source: architecture:case-08-landing-zone-185426
|
||||
status: BASELINE_LOCKED
|
||||
engagement:
|
||||
kind: platform_foundation
|
||||
intent:
|
||||
statement: 'We are a UK-regulated payment platform expanding into Google Cloud.
|
||||
We need an
|
||||
|
||||
enterprise-grade landing zone ready in under 10 weeks to support our core payments
|
||||
|
||||
engine. All payment processing must comply with DORA and PCI-DSS v4.0. We have
|
||||
|
||||
existing on-premises systems that require private, low-latency connectivity over
|
||||
a
|
||||
|
||||
10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and
|
||||
|
||||
GitHub Actions for our delivery pipelines. Security requires that all egress
|
||||
|
||||
traffic flows through centralised inspection appliances before touching the public
|
||||
|
||||
internet, and customer data must be encrypted with keys we control.'
|
||||
requirements: ask
|
||||
business_outcomes:
|
||||
- outcome: Continuous, highly available, and low-latency operation of the core payments
|
||||
platform foundation
|
||||
target: 99.9% foundation availability with deterministic low latency
|
||||
id: BO-1
|
||||
- id: BO-2
|
||||
target: Zero audit non-conformances
|
||||
outcome: Continuous compliance with DORA and PCI-DSS v4.0 standards using customer-managed
|
||||
encryption keys and centralised egress inspection
|
||||
- outcome: Automated, secure infrastructure release pipelines enabling workload
|
||||
ingestion within 10 weeks
|
||||
target: Operational readiness achieved within 10 weeks
|
||||
id: BO-3
|
||||
exclusions:
|
||||
- Core payment application workload code maintenance and runtime application management
|
||||
- On-premises infrastructure hardware maintenance beyond Cloud Interconnect physical
|
||||
termination
|
||||
solution:
|
||||
cloud_provider: gcp
|
||||
items:
|
||||
- id: S-1
|
||||
name: Resource Hierarchy and Environment Boundary Manager
|
||||
kind: governance
|
||||
product: Resource Manager
|
||||
source_ref: C-1
|
||||
elements:
|
||||
- E-1
|
||||
- E-2
|
||||
- E-3
|
||||
- E-4
|
||||
- E-5
|
||||
- E-6
|
||||
- E-7
|
||||
- E-8
|
||||
- E-9
|
||||
- E-10
|
||||
- E-34
|
||||
- E-35
|
||||
- E-36
|
||||
- E-37
|
||||
- E-38
|
||||
- E-50
|
||||
- E-51
|
||||
- E-55
|
||||
- E-60
|
||||
- id: S-2
|
||||
name: Dedicated Private Hybrid Connectivity Gateway
|
||||
kind: network
|
||||
product: Cloud Interconnect
|
||||
source_ref: C-2
|
||||
elements:
|
||||
- E-11
|
||||
- E-12
|
||||
- E-13
|
||||
- E-14
|
||||
- E-56
|
||||
- E-57
|
||||
- id: S-3
|
||||
name: Centralised Outbound Traffic Inspection and Egress Boundary
|
||||
kind: service
|
||||
product: Palo Alto Networks VM-Series
|
||||
source_ref: C-3
|
||||
elements:
|
||||
- E-15
|
||||
- E-16
|
||||
- E-17
|
||||
- E-18
|
||||
- E-19
|
||||
- E-20
|
||||
- E-47
|
||||
- E-48
|
||||
- E-53
|
||||
- id: S-4
|
||||
name: Centralised Immutable Audit Event and Compliance Log Repository
|
||||
kind: storage
|
||||
product: Cloud Storage
|
||||
source_ref: C-4
|
||||
elements:
|
||||
- E-21
|
||||
- E-22
|
||||
- E-39
|
||||
- id: S-5
|
||||
name: Automated Infrastructure Orchestration and Deployment Engine
|
||||
kind: service
|
||||
product: GitHub Actions
|
||||
source_ref: C-5
|
||||
elements:
|
||||
- E-42
|
||||
- E-43
|
||||
- id: S-6
|
||||
name: Federated Identity and Role Governance Authority
|
||||
kind: identity
|
||||
product: IAM Workload Identity Federation
|
||||
source_ref: C-6
|
||||
elements:
|
||||
- E-23
|
||||
- E-24
|
||||
- E-25
|
||||
- E-26
|
||||
- E-27
|
||||
- E-45
|
||||
- id: S-7
|
||||
name: Cryptographic Key Lifecycle and Encryption Controller
|
||||
kind: keys
|
||||
product: Cloud KMS
|
||||
source_ref: C-7
|
||||
elements:
|
||||
- E-28
|
||||
- E-29
|
||||
- E-30
|
||||
- E-31
|
||||
- E-49
|
||||
- E-58
|
||||
- E-59
|
||||
- id: S-8
|
||||
name: Platform Telemetry and Operational Alerting Engine
|
||||
kind: observability
|
||||
product: Cloud Monitoring
|
||||
source_ref: C-8
|
||||
elements:
|
||||
- E-32
|
||||
- E-40
|
||||
- E-41
|
||||
- E-44
|
||||
- E-52
|
||||
- id: S-9
|
||||
name: Financial Governance and Budget Enforcement Monitor
|
||||
kind: billing
|
||||
product: Cloud Billing
|
||||
source_ref: C-9
|
||||
elements:
|
||||
- E-33
|
||||
- E-46
|
||||
- E-54
|
||||
conditions:
|
||||
- id: K-1
|
||||
'on':
|
||||
- S-1
|
||||
- S-4
|
||||
- S-7
|
||||
condition: The landing zone configuration aligns with DORA operational resiliency
|
||||
guidelines and PCI-DSS v4.0 perimeter isolation standards during external audit.
|
||||
source_ref: NFR-8
|
||||
- id: K-2
|
||||
'on':
|
||||
- S-1
|
||||
condition: The secondary region in europe-west1 operates as a warm standby ready
|
||||
to receive failover traffic.
|
||||
source_ref: NFR-9
|
||||
- id: K-3
|
||||
'on':
|
||||
- S-1
|
||||
condition: Data residency is guaranteed within the United Kingdom and European
|
||||
Union.
|
||||
source_ref: NFR-9
|
||||
- id: K-4
|
||||
'on':
|
||||
- S-5
|
||||
condition: Platform foundation is fully provisioned and validated for core payments
|
||||
engine workload ingestion within 10 weeks.
|
||||
source_ref: NFR-10
|
||||
- id: K-5
|
||||
'on':
|
||||
- S-8
|
||||
condition: Platform foundation infrastructure maintains measured monthly availability
|
||||
of at least 99.9%.
|
||||
source_ref: NFR-11
|
||||
- id: K-6
|
||||
'on':
|
||||
- S-8
|
||||
condition: Disaster recovery activation achieves a recovery time objective (RTO)
|
||||
of 4 hours.
|
||||
source_ref: NFR-11
|
||||
- id: K-7
|
||||
'on':
|
||||
- S-8
|
||||
condition: Disaster recovery processes achieve a recovery point objective (RPO)
|
||||
of 1 hour.
|
||||
source_ref: NFR-11
|
||||
- id: K-8
|
||||
'on':
|
||||
- S-8
|
||||
condition: Alert notifications trigger operational incident workflows for the
|
||||
24/7 central platform operations team.
|
||||
source_ref: NFR-12
|
||||
- id: K-9
|
||||
'on':
|
||||
- S-9
|
||||
condition: Monthly cloud foundation expenditure does not exceed the target allocation
|
||||
without operational sign-off.
|
||||
source_ref: NFR-13
|
||||
- id: K-10
|
||||
'on':
|
||||
- S-2
|
||||
condition: Hybrid connection provides deterministic low latency suitable for real-time
|
||||
payment transaction processing.
|
||||
source_ref: NFR-14
|
||||
- id: K-11
|
||||
'on':
|
||||
- S-8
|
||||
condition: Deployments optimize carbon-free energy utilization based on Google
|
||||
Cloud regional CFE scores.
|
||||
source_ref: NFR-15
|
||||
- id: K-12
|
||||
'on':
|
||||
- S-6
|
||||
condition: Permissions are continuously rightsized based on IAM Recommender findings.
|
||||
source_ref: DR-OP-3
|
||||
build:
|
||||
duration_days: 36
|
||||
customer_owned:
|
||||
- Order and provision the Interconnect carrier circuits
|
||||
inherited_risks: ask
|
||||
operations:
|
||||
support_hours: 24x7
|
||||
availability_hours: 24x7
|
||||
change_process: Changes to the platform foundation are deployed through automated
|
||||
GitHub Actions pipelines with mandatory peer reviews and automated policy validation,
|
||||
without a separate manual change advisory board.
|
||||
monitoring: ask
|
||||
sourcing:
|
||||
model: provider_operated
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
organisation:
|
||||
existing_teams:
|
||||
- name: Central Platform Operations Team
|
||||
hours: 24x7
|
||||
party: provider
|
||||
headcount_limit: ask
|
||||
service_management:
|
||||
tooling: Google Cloud operations suite (Cloud Monitoring, Cloud Logging, and Cloud
|
||||
Alerting) without a separate external ITSM system.
|
||||
service_levels:
|
||||
priority_1_response_minutes: 30
|
||||
recovery_time_hours: 4
|
||||
compliance:
|
||||
frameworks:
|
||||
- DORA
|
||||
- ISO27001
|
||||
- PCI_DSS_v4
|
||||
commercial:
|
||||
currency: GBP
|
||||
monthly_run_budget: ask
|
||||
transition:
|
||||
go_live_date: ask
|
||||
run:
|
||||
pre_approved: true
|
||||
overlay_skills: ask
|
||||
inferred_assumptions:
|
||||
- id: ASSUMP-01
|
||||
field: intent.business_outcomes
|
||||
statement: 'Assumed intent.business_outcomes is [{''outcome'': ''Continuous, highly
|
||||
available, and low-latency operation of the core payments platform foundation'',
|
||||
''target'': ''99.9% foundation availability with deterministic low latency'',
|
||||
''id'': ''BO-1''}, {''id'': ''BO-2'', ''target'': ''Zero audit non-conformances'',
|
||||
''outcome'': ''Continuous compliance with DORA and PCI-DSS v4.0 standards using
|
||||
customer-managed encryption keys and centralised egress inspection''}, {''outcome'':
|
||||
''Automated, secure infrastructure release pipelines enabling workload ingestion
|
||||
within 10 weeks'', ''target'': ''Operational readiness achieved within 10 weeks'',
|
||||
''id'': ''BO-3''}]. Derived from workflow request objectives: running core payment
|
||||
processing reliably in Google Cloud, meeting DORA and PCI-DSS v4.0 regulatory
|
||||
standards, and delivering landing zone readiness within 10 weeks.'
|
||||
impact_if_invalid: Changes what is measured, and what each measure is for.
|
||||
- id: ASSUMP-02
|
||||
field: intent.exclusions
|
||||
statement: Assumed intent.exclusions is ['Core payment application workload code
|
||||
maintenance and runtime application management', 'On-premises infrastructure hardware
|
||||
maintenance beyond Cloud Interconnect physical termination']. Platform foundation
|
||||
scope excludes application-level core payment workloads and on-premises data centre
|
||||
hardware beyond the Interconnect boundary.
|
||||
impact_if_invalid: Changes which Capabilities are designed.
|
||||
- id: ASSUMP-03
|
||||
field: operations.change_process
|
||||
statement: 'Assumed operations.change_process is Changes to the platform foundation
|
||||
are deployed through automated GitHub Actions pipelines with mandatory peer reviews
|
||||
and automated policy validation, without a separate manual change advisory board..
|
||||
Catalogue default aligned with request stating GitHub Actions delivery pipelines:
|
||||
automated pipeline deployment with peer review and automated checks.'
|
||||
impact_if_invalid: Changes change enablement and release.
|
||||
- id: ASSUMP-04
|
||||
field: organisation.existing_teams
|
||||
statement: 'Assumed organisation.existing_teams is [{''name'': ''Central Platform
|
||||
Operations Team'', ''hours'': ''24x7'', ''party'': ''provider''}]. Catalogue default:
|
||||
all operational roles are newly provided under provider_operated model, with reference
|
||||
to the 24/7 central platform operations team in condition K-8.'
|
||||
impact_if_invalid: Changes which Roles are new and which are filled.
|
||||
- id: ASSUMP-05
|
||||
field: service_management.tooling
|
||||
statement: 'Assumed service_management.tooling is Google Cloud operations suite
|
||||
(Cloud Monitoring, Cloud Logging, and Cloud Alerting) without a separate external
|
||||
ITSM system.. Catalogue default: Cloud provider native operations tooling (Cloud
|
||||
Monitoring, Cloud Logging) integrated with alerting.'
|
||||
impact_if_invalid: Changes tooling and the processes written for it.
|
||||
- id: ASSUMP-06
|
||||
field: service_levels.priority_1_response_minutes
|
||||
statement: Assumed service_levels.priority_1_response_minutes is 30. Catalogue default
|
||||
response time for Priority 1 critical incidents under 24x7 operational support.
|
||||
impact_if_invalid: Changes on-call arrangements and staffing.
|
||||
- id: ASSUMP-07
|
||||
field: service_levels.recovery_time_hours
|
||||
statement: Assumed service_levels.recovery_time_hours is 4. Catalogue default aligned
|
||||
with condition K-6 specifying a 4-hour recovery time objective (RTO).
|
||||
impact_if_invalid: Changes continuity arrangements.
|
||||
discovery_gaps:
|
||||
- field: metadata.client_name
|
||||
prompt: What is metadata.client_name?
|
||||
severity: LOW
|
||||
- field: metadata.author
|
||||
prompt: What is metadata.author?
|
||||
severity: LOW
|
||||
- field: metadata.revision
|
||||
prompt: What is metadata.revision?
|
||||
severity: LOW
|
||||
- field: intent.requirements
|
||||
prompt: Which requirements for operations has the customer stated outright?
|
||||
severity: LOW
|
||||
- field: solution.inherited_risks
|
||||
prompt: What is already known to be unverified or at risk in the solution?
|
||||
severity: LOW
|
||||
- field: operations.monitoring
|
||||
prompt: Which monitoring and alerting is already in place or required?
|
||||
severity: LOW
|
||||
- field: organisation.headcount_limit
|
||||
prompt: Is there a limit on the number of people operating this?
|
||||
severity: LOW
|
||||
- field: commercial.monthly_run_budget
|
||||
prompt: Is there a monthly budget for operating this, in that currency?
|
||||
severity: LOW
|
||||
- field: transition.go_live_date
|
||||
prompt: When must the solution be in operation?
|
||||
severity: LOW
|
||||
- field: run.overlay_skills
|
||||
prompt: Which overlay Skills should this Execution load?
|
||||
severity: LOW
|
||||
provenance:
|
||||
commercial.currency: digested
|
||||
commercial.monthly_run_budget: unknown
|
||||
compliance.frameworks: digested
|
||||
engagement.kind: digested
|
||||
intent.business_outcomes: assumed
|
||||
intent.exclusions: assumed
|
||||
intent.requirements: unknown
|
||||
intent.statement: digested
|
||||
metadata.author: unknown
|
||||
metadata.client_name: unknown
|
||||
metadata.customer_case: digested
|
||||
metadata.revision: unknown
|
||||
metadata.source: digested
|
||||
operations.availability_hours: digested
|
||||
operations.change_process: assumed
|
||||
operations.monitoring: unknown
|
||||
operations.support_hours: digested
|
||||
organisation.existing_teams: assumed
|
||||
organisation.headcount_limit: unknown
|
||||
run.overlay_skills: unknown
|
||||
run.pre_approved: supplied
|
||||
service_levels.priority_1_response_minutes: assumed
|
||||
service_levels.recovery_time_hours: assumed
|
||||
service_management.tooling: assumed
|
||||
solution.build.customer_owned: digested
|
||||
solution.build.duration_days: digested
|
||||
solution.cloud_provider: digested
|
||||
solution.conditions: digested
|
||||
solution.inherited_risks: unknown
|
||||
solution.items: digested
|
||||
sourcing.delivery_countries: supplied
|
||||
sourcing.model: supplied
|
||||
transition.go_live_date: unknown
|
||||
readiness:
|
||||
supplied: 3
|
||||
answered: 0
|
||||
assumed: 7
|
||||
unknown: 10
|
||||
not_applicable: 0
|
||||
digested: 13
|
||||
@@ -0,0 +1,10 @@
|
||||
intent:
|
||||
business_outcomes: decide
|
||||
run:
|
||||
pre_approved: true
|
||||
sourcing:
|
||||
delivery_countries:
|
||||
- GB
|
||||
- PL
|
||||
- IN
|
||||
model: provider_operated
|
||||
@@ -0,0 +1,79 @@
|
||||
[
|
||||
{
|
||||
"id": "C-1",
|
||||
"name": "Resource Hierarchy and Environment Boundary Manager",
|
||||
"requirements": [
|
||||
"FR-1",
|
||||
"NFR-1",
|
||||
"NFR-8",
|
||||
"NFR-9"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-2",
|
||||
"name": "Dedicated Private Hybrid Connectivity Gateway",
|
||||
"requirements": [
|
||||
"FR-2",
|
||||
"NFR-3",
|
||||
"NFR-14"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-3",
|
||||
"name": "Centralised Outbound Traffic Inspection and Egress Boundary",
|
||||
"requirements": [
|
||||
"FR-3",
|
||||
"NFR-2",
|
||||
"NFR-4"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-4",
|
||||
"name": "Centralised Immutable Audit Event and Compliance Log Repository",
|
||||
"requirements": [
|
||||
"FR-4",
|
||||
"NFR-7",
|
||||
"NFR-8"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-5",
|
||||
"name": "Automated Infrastructure Orchestration and Deployment Engine",
|
||||
"requirements": [
|
||||
"FR-5",
|
||||
"NFR-10"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-6",
|
||||
"name": "Federated Identity and Role Governance Authority",
|
||||
"requirements": [
|
||||
"FR-6",
|
||||
"NFR-5"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-7",
|
||||
"name": "Cryptographic Key Lifecycle and Encryption Controller",
|
||||
"requirements": [
|
||||
"NFR-6",
|
||||
"NFR-8"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-8",
|
||||
"name": "Platform Telemetry and Operational Alerting Engine",
|
||||
"requirements": [
|
||||
"NFR-11",
|
||||
"NFR-12",
|
||||
"NFR-15"
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "C-9",
|
||||
"name": "Financial Governance and Budget Enforcement Monitor",
|
||||
"requirements": [
|
||||
"NFR-13"
|
||||
]
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,140 @@
|
||||
{
|
||||
"customer_case": "case-08-landing-zone",
|
||||
"execution_id": "case-08-landing-zone-185426",
|
||||
"session_id": "cdd6bfe7-2bd8-44af-8e15-9dcfa869eb84",
|
||||
"intent_version": 1,
|
||||
"workflow_request": "We are a UK-regulated payment platform expanding into Google Cloud. We need an\nenterprise-grade landing zone ready in under 10 weeks to support our core payments\nengine. All payment processing must comply with DORA and PCI-DSS v4.0. We have\nexisting on-premises systems that require private, low-latency connectivity over a\n10Gbps dedicated interconnect. We use Entra ID for corporate single sign-on and\nGitHub Actions for our delivery pipelines. Security requires that all egress\ntraffic flows through centralised inspection appliances before touching the public\ninternet, and customer data must be encrypted with keys we control.",
|
||||
"baseline": null,
|
||||
"overlay_skills": {},
|
||||
"terraform_modules": false,
|
||||
"scope": {
|
||||
"status": "BASELINE_LOCKED",
|
||||
"readiness": {
|
||||
"supplied": 44,
|
||||
"answered": 0,
|
||||
"assumed": 12,
|
||||
"unknown": 4,
|
||||
"not_applicable": 3
|
||||
}
|
||||
},
|
||||
"delivery_plan": {
|
||||
"work_packages": 9,
|
||||
"activities": 15,
|
||||
"working_days": 36.0,
|
||||
"weeks": 7.2,
|
||||
"team_size": 3,
|
||||
"window_weeks": 10,
|
||||
"within_window": true,
|
||||
"critical_path": [
|
||||
"A-6",
|
||||
"A-10",
|
||||
"A-13",
|
||||
"A-14",
|
||||
"A-15"
|
||||
]
|
||||
},
|
||||
"status": "completed",
|
||||
"warnings": [],
|
||||
"risks": [],
|
||||
"assessment": {
|
||||
"recommendations_quality": {
|
||||
"specific": 0.91,
|
||||
"actionable": 0.79,
|
||||
"trade_offs": 0.95,
|
||||
"traceable": 0.73
|
||||
},
|
||||
"mean": 0.84,
|
||||
"meets_bar": true
|
||||
},
|
||||
"phases": {
|
||||
"scoping": "approved",
|
||||
"requirements_discovery": "approved",
|
||||
"solution_architecture": "approved",
|
||||
"solution_implementation": "approved",
|
||||
"solution_validation": "approved",
|
||||
"packaging": "approved"
|
||||
},
|
||||
"solution_guide": "solution-architecture-guide.md",
|
||||
"customer_questions": "customer-questions.md",
|
||||
"changes": null,
|
||||
"deliverables": {
|
||||
"scope": {
|
||||
"document": "deliverables/scope.md",
|
||||
"attachments": [
|
||||
"scope.json",
|
||||
"scope.yaml"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"requirements": {
|
||||
"document": "deliverables/requirements.md",
|
||||
"attachments": [
|
||||
"requirements.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"technical_decomposition": {
|
||||
"document": "deliverables/technical_decomposition.md",
|
||||
"attachments": [
|
||||
"components.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"product_selection": {
|
||||
"document": "deliverables/product_selection.md",
|
||||
"attachments": [
|
||||
"products.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"design_recommendations": {
|
||||
"document": "deliverables/design_recommendations.md",
|
||||
"attachments": [
|
||||
"recommendations.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"target_architecture": {
|
||||
"document": "deliverables/target_architecture.md",
|
||||
"attachments": [
|
||||
"architecture.mmd",
|
||||
"target-architecture.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"architecture_description": {
|
||||
"document": "deliverables/architecture_description.md",
|
||||
"attachments": [],
|
||||
"status": "submitted"
|
||||
},
|
||||
"deployment_guidance": {
|
||||
"document": "deliverables/deployment_guidance.md",
|
||||
"attachments": [
|
||||
"implementation.json",
|
||||
"terraform/main.tf",
|
||||
"terraform/variables.tf",
|
||||
"terraform/versions.tf"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"validation_results": {
|
||||
"document": "deliverables/validation_results.md",
|
||||
"attachments": [
|
||||
"verdicts.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"work_breakdown": {
|
||||
"document": "deliverables/work_breakdown.md",
|
||||
"attachments": [
|
||||
"work-breakdown.json"
|
||||
],
|
||||
"status": "submitted"
|
||||
},
|
||||
"solution_guide": {
|
||||
"document": "deliverables/solution_guide.md",
|
||||
"attachments": [],
|
||||
"status": "submitted"
|
||||
}
|
||||
}
|
||||
}
|
||||
@@ -0,0 +1,38 @@
|
||||
[
|
||||
{
|
||||
"component": "C-1",
|
||||
"product": "Resource Manager"
|
||||
},
|
||||
{
|
||||
"component": "C-2",
|
||||
"product": "Cloud Interconnect"
|
||||
},
|
||||
{
|
||||
"component": "C-3",
|
||||
"product": "Palo Alto Networks VM-Series"
|
||||
},
|
||||
{
|
||||
"component": "C-4",
|
||||
"product": "Cloud Storage"
|
||||
},
|
||||
{
|
||||
"component": "C-5",
|
||||
"product": "GitHub Actions"
|
||||
},
|
||||
{
|
||||
"component": "C-6",
|
||||
"product": "IAM Workload Identity Federation"
|
||||
},
|
||||
{
|
||||
"component": "C-7",
|
||||
"product": "Cloud KMS"
|
||||
},
|
||||
{
|
||||
"component": "C-8",
|
||||
"product": "Cloud Monitoring"
|
||||
},
|
||||
{
|
||||
"component": "C-9",
|
||||
"product": "Cloud Billing"
|
||||
}
|
||||
]
|
||||
@@ -0,0 +1,248 @@
|
||||
[
|
||||
{
|
||||
"id": "DR-SEC-1",
|
||||
"pillar": "security",
|
||||
"text": "Implement a VPC Service Controls perimeter around all Cardholder Data Environment (CDE) projects and the centralized audit log buckets.",
|
||||
"components": [
|
||||
"C-1",
|
||||
"C-4"
|
||||
],
|
||||
"conditions": [
|
||||
"A VPC Service Controls perimeter encloses the CDE and audit log projects.",
|
||||
"The VPC Service Controls perimeter restricts ingress and egress to authorized traffic."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SEC-2",
|
||||
"pillar": "security",
|
||||
"text": "Apply Organization Policy constraints to disable default network creation, deny external IPs, prohibit service account key creation, and restrict resource locations.",
|
||||
"components": [
|
||||
"C-1"
|
||||
],
|
||||
"conditions": [
|
||||
"The compute.skipDefaultNetworkCreation constraint is enforced.",
|
||||
"The compute.vmExternalIpAccess constraint is enforced to deny all.",
|
||||
"The iam.disableServiceAccountKeyCreation constraint is enforced.",
|
||||
"The gcp.resourceLocations constraint restricts resources to europe-west2 and europe-west1."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SEC-3",
|
||||
"pillar": "security",
|
||||
"text": "Enable Confidential Computing on the payment engine Compute Engine instances to encrypt data in-use.",
|
||||
"components": [],
|
||||
"conditions": [
|
||||
"Confidential Computing is enabled on the core payment engine Compute Engine instances."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SEC-4",
|
||||
"pillar": "security",
|
||||
"text": "Deploy Sensitive Data Protection (Cloud DLP) inspection templates to detect and mask PAN data.",
|
||||
"components": [
|
||||
"C-4"
|
||||
],
|
||||
"conditions": [
|
||||
"Sensitive Data Protection (Cloud DLP) inspection templates are configured to detect and mask PAN data."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SEC-5",
|
||||
"pillar": "security",
|
||||
"text": "Enable Security Command Center at the organization level with Event and Container Threat Detection.",
|
||||
"components": [
|
||||
"C-1",
|
||||
"C-8"
|
||||
],
|
||||
"conditions": [
|
||||
"Security Command Center is activated at the organization level.",
|
||||
"Event Threat Detection and Container Threat Detection are enabled in SCC."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SEC-6",
|
||||
"pillar": "security",
|
||||
"text": "Implement event-driven automated responses using Eventarc and Cloud Run functions for SCC findings.",
|
||||
"components": [
|
||||
"C-8"
|
||||
],
|
||||
"conditions": [
|
||||
"Eventarc is configured to route high-severity SCC findings.",
|
||||
"Cloud Run functions are configured to execute automated remediation on Eventarc triggers."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-REL-1",
|
||||
"pillar": "reliability",
|
||||
"text": "Provision redundant Dedicated Cloud Interconnect circuits across distinct physical edge colocation facilities, terminating on redundant Cloud Routers with BFD.",
|
||||
"components": [
|
||||
"C-2"
|
||||
],
|
||||
"conditions": [
|
||||
"Dedicated Cloud Interconnect circuits are provisioned across redundant edge colocation facilities.",
|
||||
"Cloud Interconnects terminate on redundant Cloud Routers in each region.",
|
||||
"Bidirectional Forwarding Detection (BFD) is enabled on the Cloud Router BGP sessions."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-REL-2",
|
||||
"pillar": "reliability",
|
||||
"text": "Deploy Palo Alto VM-Series firewalls in a regional Managed Instance Group across at least three zones, fronted by an Internal Passthrough Network Load Balancer.",
|
||||
"components": [
|
||||
"C-3"
|
||||
],
|
||||
"conditions": [
|
||||
"Palo Alto VM-Series firewalls are deployed in a regional Managed Instance Group (MIG) across at least three zones.",
|
||||
"An Internal Passthrough Network Load Balancer routes traffic to the VM-Series MIG.",
|
||||
"Health checks are configured on the internal load balancer to probe firewall health."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-REL-3",
|
||||
"pillar": "reliability",
|
||||
"text": "Provision dedicated regional Cloud KMS key rings in both europe-west2 and europe-west1, granting workload identity service accounts Decrypter roles on both.",
|
||||
"components": [
|
||||
"C-7",
|
||||
"C-6"
|
||||
],
|
||||
"conditions": [
|
||||
"Regional Cloud KMS key rings are provisioned in both europe-west2 and europe-west1.",
|
||||
"Workload Identity Federation service accounts are granted Decrypter roles on both regional key sets."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-REL-4",
|
||||
"pillar": "reliability",
|
||||
"text": "Configure the Cloud Storage buckets for audit logging as Dual-Region spanning europe-west2 and europe-west1.",
|
||||
"components": [
|
||||
"C-4"
|
||||
],
|
||||
"conditions": [
|
||||
"Audit log Cloud Storage buckets are configured as Dual-Region spanning europe-west2 and europe-west1."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-REL-5",
|
||||
"pillar": "reliability",
|
||||
"text": "Isolate the Terraform state of the primary region from the standby region using multi-region Cloud Storage buckets with Object Versioning.",
|
||||
"components": [
|
||||
"C-5"
|
||||
],
|
||||
"conditions": [
|
||||
"Terraform state for primary and standby regions is decoupled into separate failure domains.",
|
||||
"Terraform state is stored in multi-region Cloud Storage buckets with Object Versioning enabled."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-OP-1",
|
||||
"pillar": "operational-excellence",
|
||||
"text": "Integrate Policy-as-Code validation into the GitHub Actions pull request workflows.",
|
||||
"components": [
|
||||
"C-5"
|
||||
],
|
||||
"conditions": [
|
||||
"GitHub Actions workflows include automated Policy-as-Code validation steps prior to deployment execution."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-OP-2",
|
||||
"pillar": "operational-excellence",
|
||||
"text": "Establish explicit Service Level Indicators (SLIs) and configure multi-burn-rate alerting policies in Cloud Monitoring.",
|
||||
"components": [
|
||||
"C-8"
|
||||
],
|
||||
"conditions": [
|
||||
"Service Level Objectives (SLOs) and SLIs are defined in Cloud Monitoring Service Monitoring.",
|
||||
"Multi-burn-rate alerting policies are configured based on the SLO error budget."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-OP-3",
|
||||
"pillar": "operational-excellence",
|
||||
"text": "Activate the IAM Recommender to continuously evaluate role bindings.",
|
||||
"components": [
|
||||
"C-6"
|
||||
],
|
||||
"conditions": [
|
||||
"IAM Recommender is activated on the foundation projects."
|
||||
],
|
||||
"outside_code": [
|
||||
"Permissions are continuously rightsized based on IAM Recommender findings."
|
||||
]
|
||||
},
|
||||
{
|
||||
"id": "DR-COST-1",
|
||||
"pillar": "cost-optimization",
|
||||
"text": "Enforce a mandatory labeling taxonomy through Organization Policies and export granular billing data to BigQuery.",
|
||||
"components": [
|
||||
"C-9",
|
||||
"C-1"
|
||||
],
|
||||
"conditions": [
|
||||
"Cloud Billing export to BigQuery is enabled.",
|
||||
"A mandatory labeling taxonomy is enforced via Organization Policy Service tags."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-COST-2",
|
||||
"pillar": "cost-optimization",
|
||||
"text": "Implement Cloud Storage Object Lifecycle Management to transition logs to Nearline storage after 30 days and to Coldline or Archive storage after 90 days.",
|
||||
"components": [
|
||||
"C-4"
|
||||
],
|
||||
"conditions": [
|
||||
"Object Lifecycle Management rules transition Cloud Storage objects to Nearline storage after 30 days.",
|
||||
"Object Lifecycle Management rules transition Cloud Storage objects to Coldline or Archive storage after 90 days."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-PERF-1",
|
||||
"pillar": "performance-optimization",
|
||||
"text": "Configure Cloud Routers with regional dynamic routing to localize egress traffic within the warm standby region.",
|
||||
"components": [
|
||||
"C-2"
|
||||
],
|
||||
"conditions": [
|
||||
"Cloud Routers are configured with regional dynamic routing mode."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-PERF-2",
|
||||
"pillar": "performance-optimization",
|
||||
"text": "Instrument the deployment with OpenTelemetry exporting to Cloud Trace, and use Cloud Profiler on the compute instances.",
|
||||
"components": [
|
||||
"C-8"
|
||||
],
|
||||
"conditions": [
|
||||
"OpenTelemetry tracing is configured to export to Cloud Trace.",
|
||||
"Cloud Profiler agents are enabled on the core payments engine instances."
|
||||
],
|
||||
"outside_code": []
|
||||
},
|
||||
{
|
||||
"id": "DR-SUST-1",
|
||||
"pillar": "sustainability",
|
||||
"text": "Implement a Pilot Light warm standby by maintaining active data replication while scaling the standby compute instances to a minimal baseline.",
|
||||
"components": [],
|
||||
"conditions": [
|
||||
"Secondary region compute instances are scaled to a minimal baseline (Pilot Light) configuration during normal operations."
|
||||
],
|
||||
"outside_code": []
|
||||
}
|
||||
]
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user