About the Automotive Cybersecurity Dashboard

An evidence-based research environment that connects automotive cybersecurity threats to observable external evidence.

A risk analysis describes what could happen. Connecting threats to observable evidence makes the risk tangible, examinable and open to challenge.

From risk register to evidence-based analysis

The dashboard is built around a Threat Register rather than around individual data feeds. The register provides the analytical structure; external evidence provides the material against which individual threats can be examined.

Instead of presenting a risk assessment as a static end product, the dashboard makes the relationship between a threat and its supporting or potentially relevant evidence navigable. Each threat can be opened as a dossier containing the available evidence, its correlation with the threat, and items that still require expert review.

The Threat Register at the centre

Different evidence sources describe different parts of the cybersecurity landscape. The Threat Register brings those sources together around the risk question. In addition to observable external evidence, threats can now be related to applicable regulatory requirements and analytical regulatory mappings. This keeps evidence, risk analysis and regulatory traceability connected without treating correlation or regulatory relevance as proof of compliance.

Threat Register
CVEs Papers Repositories Signals Incidents Assessments Narratives
UN R155 requirements Annex 5 analytical candidates Regulatory Hub
Accepted evidence Review candidates Evidence gaps Expert review

The Regulatory Hub complements this threat-level traceability by explaining the wider regulatory frameworks, official sources, expert views and unresolved regulatory questions.

Evidence sources

No single source type gives a complete view. The dashboard combines deliberately different forms of public evidence.

CVEs

Publicly documented vulnerabilities that provide concrete technical evidence about affected products, components and software.

Academic papers

Research, experiments and analyses that add technical depth, validation and emerging knowledge.

GitHub repositories

Public tooling, implementations, demonstrators and security research connected to automotive attack surfaces.

Signals

Developments that may indicate a change in the threat landscape or deserve continued monitoring.

Incidents

Observed events and reported real-world cases that help connect analytical threats with operational reality.

Assessments

Authoritative public analyses, investigations and policy or security assessments relevant to individual threats.

Narratives

Synthesis across multiple signals and evidence items, intended to expose wider patterns rather than isolated observations.

Accepted evidence and review candidates

Automated correlation helps identify relationships between evidence and threats, but the dashboard deliberately distinguishes stronger matches from candidates that still need assessment.

Accepted evidence

Evidence whose relationship with the specific threat meets the configured acceptance criteria.

Review candidate

Potentially relevant evidence that should be examined before the relationship is treated as accepted.

Evidence strength and correlation status answer different questions. A strong or authoritative source can still be only a review candidate for a particular threat.

Correlation is not proof

Evidence is correlated with threats using technical characteristics and contextual indicators such as terminology, assets, protocols, attack vectors and impacts. A higher correlation indicates a stronger relationship according to the analytical model; it does not by itself prove that a threat has materialised or that a source supports every aspect of that threat.

Likewise, the absence of matched evidence does not demonstrate the absence of a threat, and a large volume of evidence does not automatically make a threat more severe or more likely.

Cross-domain by design

Modern vehicle cybersecurity does not stop at the vehicle boundary. Connected vehicles depend on external digital and physical infrastructure, and risks can therefore cross traditional sector and supervisory boundaries.

Vehicle↔Charging infrastructure↔Backend / cloud↔Telecommunications↔Energy infrastructure↔Digital services

This cross-domain perspective is intentional: an adjacent system can be relevant to an automotive threat even when that system is governed, operated or supervised elsewhere.

What this dashboard is

  • A research and analytical environment.
  • A way to make the relationship between risks and external evidence transparent and traceable.
  • A mechanism for exposing evidence gaps and candidates requiring expert review.
  • A continuously extensible view of the automotive cybersecurity landscape.

What this dashboard is not

  • It is not a vulnerability scanner.
  • It is not an automated risk decision system.
  • It does not replace expert assessment or professional judgement.
  • Correlation scores should not be interpreted as proof, probability or risk scores.

Update cycle

The underlying evidence collections are refreshed daily. Evidence is correlated with the Threat Register and the dashboard is republished weekly. This separates continuous evidence collection from the periodic publication of a stable analytical view.

Latest data collection Not yet available
Latest correlation Not yet available
Latest publication Not yet available

Update timestamps are loaded from the dashboard status record.

Research prototype

This dashboard is a research and analytical prototype. Its purpose is to explore how automotive cybersecurity risk analysis can become more evidence-driven, transparent and continuously examinable.

The underlying datasets, correlation rules and analytical methods can evolve as new evidence becomes available. The value of the environment therefore lies not only in individual findings, but also in traceability: users can move from a threat to the evidence behind it and judge that relationship themselves.

Transparency, traceability and expert judgement remain central.

Version & contact

Release information and contact details for the Automotive Cybersecurity Dashboard research prototype.

Version 0.6.0
Released 11 November 2026
Contact Contact NCRC

Any questions or suggestions? Feel free to reach out.

Release notes

0.6.0 - 2026-12-11

UN R155 regulatory traceability

  • Promoted the UN R155 review baseline into the production Threat Register.
  • Added threat-level R155 requirement relevance and Annex 5 analytical candidates to the 69 Threat Register pages.
  • Preserved generated mappings as review candidates rather than automatic compliance conclusions.
  • Added explicit handling for threats with no direct mapping and for post-production cybersecurity support relevance.

Regulatory Hub

  • Added a dedicated Regulatory Hub covering UN R155, UN R156 and the EU Cyber Resilience Act (CRA).
  • Added direct access to official regulatory sources and annexes.
  • Added separate presentation layers for Official Regulation, NCRC Explanation, Expert View and Open Regulatory Question.
  • Added the Type Approved Zone, CRA Zone and Grey Zone as clearly labelled expert-analysis concepts.
  • Added automotive ecosystem scope topics covering vehicle categories, supply chains, software, embedded hardware, tools, infrastructure, aftermarket products and digital services.

Public expert names and affiliations are withheld while internal provenance is retained.

Navigation

  • Added Regulatory consistently to the main navigation across the dashboard sections.

0.5.0 - 2026-11-11

  • Improved automotive CVE relevance classification.
  • Added GitHub remediation evidence analysis.
  • Reduced false-positive OEM and supplier name matching.

0.4.0 - 2026-07-11

  • Improved automotive relevance classification.
  • Added daily data generation
  • Added weekly matching
  • Added Signals, Narratives

0.3.0 - 2026-31-10

  • Complete overhaul Threat Register as central point
  • Evidence-based Threat Register with traceable relationships between threats and supporting evidence.
  • Integrated CVE, GitHub repository, academic paper, signal and incident evidence.
  • Automated evidence correlation with separate accepted-evidence and expert-review workflows.
  • Cross-domain analysis including vehicle systems, charging infrastructure, backend services, telecommunications and energy infrastructure.
  • Automotive CVE relevance filtering with contextual validation of OEM, supplier and technology matches.