← Threat Register

T-058 · AI, Software Supply Chains, and External Services

Compromise or disruption of vehicle-related backend and cloud services

Risk: High ReviewReview candidates available5 review candidates1 paperRegulatory

Threat analysis

Analysis / Description

Encryption, destructive malware or data-extortion can disable fleet, backend, charging, roadside or mobility services and may delay transport, logistics and emergency operations. Sub-level threats from Annex 5 for this threat includes back end servers used as a means to attack a vehicle or extract data, services from back end server being disrupted, affecting the operation of a vehicle and vehicle data held on back end servers being lost or compromised.

Assessment

Primary domain
Infrastructure
Secondary domains
Vehicle
Affects
Infrastructure, Vehicle
Impact
High (score 4)
Probability
High (score 3)
Source
UNECE R155, Annex 5, 4.3.1.

Impact rationale

"VERY SERIOUS" impact may arise where a trusted backend is used to issue commands, distribute software, expose data or remove services across a large vehicle population. Physical safety, economic activity, daily mobility and Dutch digital-space integrity may all be affected.

Likelihood rationale

Backend and cloud services are continuously exposed and attractive to attackers. A successful compromise is plausible within five years, but widespread vehicle or mobility impact requires privileged access and failure of multiple security and recovery controls.

Risk rationale

T-011 covers outages, T-033 supply-chain attacks, T-047 vehicle-behaviour manipulation and T-052 external-service dependency. T-058 adds the backend as the initiating vehicle attack surface.

External Evidence

Evidence supporting this threat

CVEs, academic research, strategic signals, real-world incidents and authoritative assessments from the correlation pipeline, plus public repositories from the existing evidence pipeline.

T-058
0
Accepted CVEs
0
Accepted Papers
0
Accepted Signals
0
Accepted Incidents
0
Accepted Assessments
0
Accepted Narratives
0
Repositories
5
Review Candidates
1 papers

Evidence strength describes the quality or authority of the source. Correlation status describes the automated relationship with this specific threat. Review status does not mean that the source itself is weak.

Evidence Requiring Review

5 items
Repository review
Correlation0.48

Automotive Security Glossary

Plausible match requiring review between github:automotive-security/automotive-security-glossary and T-058: structured overlap in assets: backend_cloud, supply_chain, vehicle_intelligence; attack_vectors: ai_assisted, denial_of_service; impacts: availability, integrity; specific rules: remote_oem_critical_function_access, backend_services, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: outages, privileged, distribute, controls., attackers., surface., lost, api.

backend_cloudsupply_chainvehicle_intelligenceai_assisteddenial_of_serviceavailabilityintegrityoutagesprivilegeddistribute
Technical correlation details
Evidence identifier
github:automotive-security/automotive-security-glossary
Evidence type
Repository
Evidence strength
Directly relevant technical repository
Confidence
low
Matched axes
assets, attack_vectors, impacts
Rules fired
remote_oem_critical_function_access, backend_services, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.02
Features0.18
Assets0.27
Protocols0.00
Attack vectors0.20
Impacts0.40
Rule contribution0.33
Context penalty0.00
Generic penalty0.00
Final score0.48
Repository review
Correlation0.48

Architecture

Plausible match requiring review between github:evtivity/evtivity-csms and T-058: structured overlap in assets: backend_cloud; attack_vectors: ai_assisted; impacts: availability; specific rules: remote_oem_critical_function_access, backend_services, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match; shared terms: adds, api, daily, activity, commands, backend, operations., recovery.

backend_cloudai_assistedavailabilityaddsapidailyactivitycommandsbackendoperations.
Technical correlation details
Evidence identifier
github:evtivity/evtivity-csms
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, attack_vectors, impacts
Rules fired
remote_oem_critical_function_access, backend_services, repository_rule_and_feature, repository_multi_axis_technical, repository_strong_structured_match
Lexical0.01
Features0.15
Assets0.17
Protocols0.00
Attack vectors0.25
Impacts0.33
Rule contribution0.33
Context penalty0.00
Generic penalty0.00
Final score0.48
Research review
Correlation0.43

Secure and Resilient EV Charging Infrastructure Using Hyperledger Fabric Smart Contracts in Smart Cities

Plausible match requiring review between doi:10.68159/e051170849 and T-058: structured overlap in assets: backend_cloud; attack_vectors: denial_of_service; impacts: integrity; specific rules: remote_oem_critical_function_access, backend_services; shared terms: malware, daily, expose, affecting, activity, commands, emergency, widespread.

backend_clouddenial_of_serviceintegritymalwaredailyexposeaffectingactivitycommandsemergency
Technical correlation details
Evidence identifier
doi:10.68159/e051170849
Evidence type
Research
Evidence strength
Conceptual or methodological
Confidence
low
Matched axes
assets, attack_vectors, impacts
Rules fired
remote_oem_critical_function_access, backend_services
Lexical0.03
Features0.14
Assets0.17
Protocols0.00
Attack vectors0.20
Impacts0.33
Rule contribution0.33
Context penalty0.00
Generic penalty0.00
Final score0.43
Repository review
Correlation0.42

Next-Gen-Security-Enhanced-DDoS-Attack-Detection-for-Autonomous-Vehicles-in-6G-Networks

Plausible match requiring review between github:j-b-mugundh/next-gen-security_enhanced-ddos-attack-detection-for-autonomous-vehicles-in-6g-networks and T-058: structured overlap in attack_vectors: ai_assisted, denial_of_service; impacts: availability; specific rules: repository_multi_axis_technical; shared terms: continuously, five, includes, mobility, service, impact, access, threats.

ai_assisteddenial_of_serviceavailabilitycontinuouslyfiveincludesmobilityserviceimpactaccess
Technical correlation details
Evidence identifier
github:j-b-mugundh/next-gen-security_enhanced-ddos-attack-detection-for-autonomous-vehicles-in-6g-networks
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
attack_vectors, impacts
Rules fired
repository_multi_axis_technical
Lexical0.02
Features0.20
Assets0.00
Protocols0.00
Attack vectors0.67
Impacts0.50
Rule contribution0.03
Context penalty0.00
Generic penalty0.00
Final score0.42
Repository review
Correlation0.40

AutoTARA

Plausible match requiring review between github:hackproof/autotara and T-058: structured overlap in assets: backend_cloud; specific rules: backend_services, repository_rule_and_feature; shared terms: api, backend, server, language, services, service, threat, threats.

backend_cloudapibackendserverlanguageservicesservicethreatthreatsdevelopment
Technical correlation details
Evidence identifier
github:hackproof/autotara
Evidence type
Repository
Evidence strength
Directly relevant technical repository
Confidence
low
Matched axes
assets
Rules fired
backend_services, repository_rule_and_feature
Lexical0.02
Features0.06
Assets0.25
Protocols0.00
Attack vectors0.00
Impacts0.00
Rule contribution0.18
Context penalty0.00
Generic penalty0.00
Final score0.40
How evidence was matched to this threat

Technical surfaces: Backend / Cloud, Telematics
Terms: backend, cloud, api
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

UN Regulation No. 155

NCRC review-baseline mapping of T-058 to UN R155 requirements and Annex 5. Analytical traceability only, not a determination of compliance, non-compliance or legal effect.

RDW BASELINE

R155 coverage: 4.3.1 / Vehicle-related backend servers

Protected high-level baseline / direct.

R155 REQUIREMENT RELEVANCE

Main-text R155 CSMS, vehicle-type and type-approval relations. Expert review required.

reviewvehicle type

Exhaustive vehicle-type risk assessment including external systems and other relevant risks

R155 references: 7.3.3

Candidate generated from title/description evidence, optionally supported by category fields; expert review required.

ANNEX 5 ANALYTICAL CANDIDATES

Analytical candidate relationships from the promoted review baseline.

5Mappings
5Review
reviewAnnex 5score 0.70
Part A / Table A1 / Ref 1.3

Unauthorized physical access to the server

NCRC rationale: Threat register explicitly identifies Annex 5 area 4.3.1.

accessbackphysicalserverserversthreats
Corresponding mitigations (1)
C / - / M8 System design and access control prevent unauthorized access to personal or system-critical data
reviewAnnex 5score 0.70
Part A / Table A1 / Ref 3.4

Unauthorized physical access to the server

NCRC rationale: Threat register explicitly identifies Annex 5 area 4.3.1.

accessbackphysicalserverserversthreats
Corresponding mitigations (1)
C / - / M8 System design and access control prevent unauthorized access to personal or system-critical data
reviewAnnex 5score 0.66
Part A / Table A1 / Ref 7.2

Gaining unauthorized access to files or data

NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.

accessthreats
Corresponding mitigations (1)
B / - / M8 System design and access control prevent unauthorized access to personal or system-critical data
reviewAnnex 5score 0.66
Part A / Table A1 / Ref 19.2

Unauthorized access to owner privacy information

NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.

accessthreats
Corresponding mitigations (1)
B / - / M8 System design and access control prevent unauthorized access to personal or system-critical data
reviewAnnex 5score 0.66
Part A / Table A1 / Ref 5.2

Communication channels permit manipulation of vehicle-held data/code

NCRC rationale: Candidate generated from shared technical concepts, an attack-path bridge, or multiple non-generic terms; expert review required.

heldmanipulationthreats
Corresponding mitigations (1)
B / - / M7 Access-control techniques and designs protect system data/code