rv-2026-0387Submitted by Jonas Weber of Drives Services Digital28 Aug 2026Google Cloud, scored under CIS Controls v8.1 and Northwind’s own standardsmatched to Internal API behind Apigee at 88%read from warranty-claims-api-lld-v2.1.pdf and warranty-claims-api-architecture.png
| Maps to | |||||||||
|---|---|---|---|---|---|---|---|---|---|
16.10 | Apply Secure Design Principles in Application ArchitecturesThe service runs as the deployment account, which can redeploy itself and administer the database | Application | Security | PR.PS-06 | High | Fail | Missing 2 cited, none proving it is built | Drives Services Digital | 27 Sept 2026 |
6.3 | Require MFA for Externally-Exposed ApplicationsMFA for partner portal users depends on an identity provider the document does not describe | Identity | Security | PR.AA-03 | Medium | Fail | Missing 3 cited, none proving it is built | Identity Engineering | 27 Oct 2026 |
COST-4 | Spend is visible and attributedNo budget, alert or cost attribution | Cost | Cost | GCP Architecture Framework | Medium | Fail | Missing | Cloud Platform Engineering | 27 Oct 2026 |
MBSS-1 | The design names the baselines it is built to4 baselines apply and none is named in the design | Estate fit | Estate fit | MBSS baselines | Medium | Fail | Missing | Cyber Security | 27 Oct 2026 |
PERF-4 | Scaling bounds are definedNo scaling bounds are stated | Performance | Performance | GCP Architecture Framework | Medium | Fail | Missing | Drives Services Digital | 27 Oct 2026 |
REL-5 | Dependencies fail without taking the application downA call to SAP S/4HANA has no stated failure behaviour | Reliability | Reliability | GCP Architecture Framework | Medium | Fail | Missing | Drives Services Digital | 27 Oct 2026 |
OPS-4 | Runbooks exist for the likely failuresNo runbooks are referenced | Operations | Operations | GCP Architecture Framework | Low | Fail | Missing | Cloud Platform Engineering | 26 Nov 2026 |
3.10 | Encrypt Sensitive Data in TransitEvery hop carrying claim data is encrypted, including the database session | Data | Security | PR.DS-02 | Low | Pass | Data Platform Engineering | — | |
3.11 | Encrypt Sensitive Data at RestClaim data at rest is encrypted with a customer-managed key, beyond what Confidential data requires | Data | Security | PR.DS-01 | Low | Pass | Data Platform Engineering | — | |
3.12 | Segment Data Processing and Storage Based on SensitivityThe claims database and its key sit inside the motion-services perimeter | Data | Security | PR.IR-01 · PR.DS-01 | Low | Pass | Data Platform Engineering | — | |
6.5 | Require MFA for Administrative AccessProject administration is limited to one group with security-key 2-Step Verification | Identity | Security | PR.AA-03 · PR.AA-05 | Low | Pass | Identity Engineering | — | |
8.9 | Centralize Audit LogsAudit logs leave the project through the organisation sink | Logging | Security | PR.PS-04 | Low | Pass | Cyber Security | — | |
11.4 | Establish and Maintain an Isolated Instance of Recovery DataBackups are held in a separate project with independent IAM and a recent restore test | Resilience | Security | PR.DS-11 | Low | Pass | Cloud Platform Engineering | — | |
12.2 | Establish and Maintain a Secure Network ArchitecturePrivate database connectivity and a documented two-subnet zone model | Network | Security | PR.IR-01 | Low | Pass | Network Engineering | — | |
13.10 | Perform Application Layer FilteringApigee and Cloud Armor filter every request at the application layer | Network | Security | PR.IR-01 · DE.CM-01 | Low | Pass | Network Engineering | — | |
AP-1 | Shared databaseNo shared database | Design pattern | Reliability | Design patterns | Low | Pass | Not assessed | Drives Services Digital | — |
AP-2 | Third party in the data pathNo third party on the request path | Design pattern | Reliability | Design patterns | Low | Pass | Not assessed | Drives Services Digital | — |
AP-3 | One identity for every workloadWorkload identities are separated | Design pattern | Operations | Design patterns | Low | Pass | Not assessed | Cloud Platform Engineering | — |
AP-4 | Snowflake environmentThe environment is reproducible | Design pattern | Operations | Design patterns | Low | Pass | Cloud Platform Engineering | — | |
CAT-1 | Every service is in the catalogue and permittedAll 9 services are in the catalogue and permitted | Estate fit | Estate fit | Service catalogue | Low | Pass | Not assessed | Cyber Security | — |
CAT-2 | Conditional services are used on their terms9 conditional services are used within their terms | Estate fit | Estate fit | Service catalogue | Low | Pass | Not assessed | Cyber Security | — |
CAT-3 | Nothing depends on a service that is going awayNothing in the design is retiring or unassessed | Estate fit | Estate fit | Service catalogue | Low | Pass | Not assessed | Cyber Security | — |
CAT-4 | Data is held only where its class is permittedEvery store is assessed for the class it holds | Estate fit | Estate fit | Service catalogue | Low | Pass | Not assessed | Cyber Security | — |
COST-1 | Capacity follows demandNothing runs when nothing is happening | Cost | Cost | GCP Architecture Framework | Low | Pass | Not assessed | Cloud Platform Engineering | — |
COST-3 | Traffic that leaves is accounted forTraffic leaving the estate is accounted for | Cost | Cost | GCP Architecture Framework | Low | Pass | Cloud Platform Engineering | — | |
OPS-1 | Infrastructure is defined as codeThe environment is defined as code | Operations | Operations | GCP Architecture Framework | Low | Pass | Cloud Platform Engineering | — | |
OPS-2 | Releases are staged and reversibleReleases are staged and can be withdrawn | Operations | Operations | GCP Architecture Framework | Low | Pass | Cloud Platform Engineering | — | |
OPS-3 | Monitoring reaches a personAlerts reach a named rota | Operations | Operations | GCP Architecture Framework | Low | Pass | Cloud Platform Engineering | — | |
PERF-1 | Latency and throughput targets are statedThe design states what it is built to serve | Performance | Performance | GCP Architecture Framework | Low | Pass | Drives Services Digital | — | |
REL-1 | No single point of failure on the critical pathThe data tier survives the loss of a zone | Reliability | Reliability | GCP Architecture Framework | Low | Pass | Drives Services Digital | — | |
REL-2 | Recovery objectives are statedRecovery objectives are stated | Reliability | Reliability | GCP Architecture Framework | Low | Pass | Drives Services Digital | — | |
REL-3 | Recovery is tested, not assumedA restore has been performed and timed | Reliability | Reliability | GCP Architecture Framework | Low | Pass | Drives Services Digital | — |