← Threat Register

T-068 · Critical Infrastructure and National Security

Compromise of connected road and traffic-management infrastructure affecting vehicles

Risk: High ReviewReview candidates available3 review candidatesRegulatory

Threat analysis

Analysis / Description

A cyberattack on traffic signals, lane-control systems, roadside units, tunnel systems or central traffic-management platforms could create unsafe traffic conditions, provide false information to vehicles and disrupt road-network operations.

Assessment

Primary domain
Infrastructure
Secondary domains
Vehicle; Society
Affects
Infrastructure, Vehicle, Society
Impact
Severe (score 5)
Probability
Medium (score 3)
Source
NHTSA 2022; ENISA Transport Threat Landscape

Impact rationale

"CATASTROPHIC" physical-safety impact is credible if traffic signals, lane controls, tunnels, roadside units or infrastructure-to-vehicle messages are manipulated across a wide area, creating conflicting movements and multiple fatal collisions. Economic and territorial effects may be very serious.

Likelihood rationale

Connected road infrastructure may contain remotely accessible, long-lived or insufficiently segmented systems. A successful regional attack is plausible within five years, but broad safety consequences require access to operational controls, coordinated manipulation and failure of the last resort "local fail-safe" or manual override controls.

Risk rationale

T-002 and T-004 cover charging and V2G; T-006 critical-infrastructure targeting and T-035/T-054 communications. T-068 fills the connected road and traffic-management asset boundary.

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-068
0
Accepted CVEs
0
Accepted Papers
0
Accepted Signals
0
Accepted Incidents
0
Accepted Assessments
0
Accepted Narratives
0
Repositories
3
Review Candidates
No review candidates

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

3 items
Repository review
Correlation0.42

Electroop — OCPP & OCPI EV charging platform (CPMS, eMSP, card payment at the station)

Plausible match requiring review between github:electroop-engineering/electroop-ev-charging-platform and T-068: structured overlap in assets: road_infrastructure; protocols: v2g; specific rules: repository_multi_axis_technical; shared terms: campaign, platforms, unit, cloud, charging, area, management.

road_infrastructurev2gcampaignplatformsunitcloudchargingareamanagement
Technical correlation details
Evidence identifier
github:electroop-engineering/electroop-ev-charging-platform
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, protocols
Rules fired
repository_multi_axis_technical
Lexical0.01
Features0.11
Assets0.20
Protocols0.33
Attack vectors0.00
Impacts0.00
Rule contribution0.03
Context penalty0.00
Generic penalty0.00
Final score0.42
Repository review
Correlation0.42

EVSE ID Generator

Plausible match requiring review between github:lex/evse-id-generator and T-068: structured overlap in assets: road_infrastructure; protocols: v2g; specific rules: repository_multi_axis_technical; shared terms: charging, infrastructure.

road_infrastructurev2gcharginginfrastructure
Technical correlation details
Evidence identifier
github:lex/evse-id-generator
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, protocols
Rules fired
repository_multi_axis_technical
Lexical0.01
Features0.11
Assets0.17
Protocols0.33
Attack vectors0.00
Impacts0.00
Rule contribution0.03
Context penalty0.00
Generic penalty0.00
Final score0.42
Repository review
Correlation0.42

Securing-Data-in-Connected-Vehicles-V2X

Plausible match requiring review between github:youssefclayb/securing-data-in-connected-vehicles-v2x and T-068: structured overlap in assets: vehicle_intelligence; protocols: v2x; specific rules: repository_multi_axis_technical; shared terms: analysis, v2x, connected.

vehicle_intelligencev2xanalysisconnected
Technical correlation details
Evidence identifier
github:youssefclayb/securing-data-in-connected-vehicles-v2x
Evidence type
Repository
Evidence strength
Strongly relevant technical repository
Confidence
low
Matched axes
assets, protocols
Rules fired
repository_multi_axis_technical
Lexical0.03
Features0.15
Assets0.20
Protocols0.50
Attack vectors0.00
Impacts0.00
Rule contribution0.03
Context penalty0.00
Generic penalty0.00
Final score0.42
How evidence was matched to this threat

Technical surfaces: V2X
Terms: traffic management, traffic light, roadside unit, rsu, intelligent transportation
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-068 to UN R155 requirements and Annex 5. Analytical traceability only, not a determination of compliance, non-compliance or legal effect.

RDW BASELINE

R155 coverage: Cross-cutting / Connected road and traffic-management infrastructure

Protected high-level baseline / cross-cutting.

R155 REQUIREMENT RELEVANCE

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

No main-text R155 requirement relation was generated for this threat.
ANNEX 5 ANALYTICAL CANDIDATES

Analytical candidate relationships from the promoted review baseline.

5Mappings
5Review
reviewAnnex 5score 0.66
Part A / Table A1 / Ref 16.1

Manipulation of functions designed to remotely operate vehicle systems

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

manipulationremotely
Corresponding mitigations (1)
B / - / M20 Security controls are applied to systems with remote access
reviewAnnex 5score 0.65
Part A / Table A1 / Ref 29.2

Circumvention of network separation to gain control

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

controlcouldnetworkthat
Corresponding mitigations (1)
B / - / M23 Cybersecurity best practices are followed for software/hardware development, system design/integration, with appropriate testing
reviewAnnex 5score 0.62
Part A / Table A1 / Ref 5.1

Communication channels permit code injection

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

Corresponding mitigations (2)
B / - / M10 Vehicle verifies authenticity and integrity of messages it receives
B / - / M6 Security by design minimises risk
reviewAnnex 5score 0.62
Part A / Table A1 / Ref 5.3

Communication channels permit overwrite 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.

Corresponding mitigations (1)
B / - / M7 Access-control techniques and designs protect system data/code
reviewAnnex 5score 0.62
Part A / Table A1 / Ref 32.1

Physical manipulation or replacement of electronic hardware or sensor inputs

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

couldmanipulationphysicalthat
Corresponding mitigations (1)
B / - / M9 Measures prevent and detect unauthorized access