Management of supplier and service-provider dependencies
R155 references: 5.1.1(a) / 7.2.2.5 / 7.3.2
Candidate generated from title/description evidence, optionally supported by category fields; expert review required.
T-069 ยท Critical Infrastructure and National Security
Threat analysis
A shared cloud platform, software component, communication provider, update service, supplier, credential, or other dependency is compromised or fails, causing several vehicle fleets or mobility providers to be disrupted at the same time. It emphasizes that the threat is defined by a single point of dependency causing simultaneous, cross-organization disruption, rather than an isolated supplier or fleet incident.
"CATASTROPHIC" economic and territorial impacts are credible if one shared provider, component, key, architecture or update path simultaneously disrupts several OEMs, fleets or vital mobility providers. Physical and societal effects may be very serious.
Shared dependencies are common, but catastrophic disruption requires a highly concentrated dependency, widespread use, limited independent fallback of different domains, and a compromise or failure capable of affecting several organizations simultaneously. In the next 5 years, this could lead to a Unlikely scenario.
T-001 covers large-scale disruption; T-031/T-033 supply-chain risk; T-049 fleet-scale underestimation; T-052/T-055 external dependencies; T-056 support failure. T-069 explicitly assesses correlated concentration risk across them.
External Evidence
CVEs, academic research, strategic signals, real-world incidents and authoritative assessments from the correlation pipeline, plus public repositories from the existing evidence pipeline.
No CVEs, papers, signals, incidents, assessments or repositories currently meet the configured correlation criteria. Absence of matched evidence does not demonstrate absence of the threat.
Technical surfaces: -
Terms: single point of failure, shared dependency, supply chain
CVE, paper, signal, incident, assessment and narrative correlations are generated by correlate_evidence.py. Repository mappings remain sourced from the existing evidence pipeline.
Regulatory traceability
NCRC review-baseline mapping of T-069 to UN R155 requirements and Annex 5. Analytical traceability only, not a determination of compliance, non-compliance or legal effect.
R155 coverage: Cross-cutting / Shared dependency / single point of failure
Protected high-level baseline / cross-cutting.
Main-text R155 CSMS, vehicle-type and type-approval relations. Expert review required.
R155 references: 5.1.1(a) / 7.2.2.5 / 7.3.2
Candidate generated from title/description evidence, optionally supported by category fields; expert review required.
R155 references: 7.3.3
Candidate generated from title/description evidence, optionally supported by category fields; expert review required.
Analytical candidate relationships from the promoted review baseline.
NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.
NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.
NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.
NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.
NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.