Contents

TARA — Threat Analysis and Risk Assessment

The core method of automotive cybersecurity: find what is worth protecting, how it can be attacked, how bad and how likely that is — and decide what to do about it.

Why it exists

Security budgets are finite. The TARA makes protection decisions traceable: which assets need which controls, and which risks are accepted.

What it consists of

  1. Asset identification — e.g. brake commands, firmware, keys, personal data — and the property to protect (integrity, confidentiality, availability).
  2. Damage scenarios — consequences rated for safety, financial, operational and privacy impact.
  3. Threat scenarios — what an attacker would do to cause the damage.
  4. Attack path analysis — how they get from an entry point (telematics, OBD, Bluetooth) to the asset.
  5. Attack feasibility — rated by factors such as elapsed time, expertise, knowledge of the item, window of opportunity and equipment.
  6. Risk value from impact and feasibility.
  7. Risk treatment — avoid, reduce, share or accept. Reductions become cybersecurity goals and requirements.
TARA from assets to cybersecurity goals
AssetsIdentify assets and properties to protect
Damage and threatsRate damage impact; identify threat scenarios
Attack pathsAnalyse paths and rate attack feasibility
Risk valueCombine impact and attack feasibility
Risk treatmentAvoid, reduce, share or accept
Cybersecurity goalsDerive goals and requirements for risk reduction

Simplified TARA flow; risk reduction leads to cybersecurity goals and requirements, and the analysis is refined as the design changes.

Best practices

  • Start early on the architecture, then refine as design details become known.
  • Reuse threat catalogues and attack-path libraries, but check them against the concrete design.
  • Keep the TARA alive: update it for new vulnerabilities and changes.

Common pitfalls

  • TARAs so generic that they produce no concrete requirements.
  • Rating feasibility without considering remote, scalable attacks.

What it means for your discipline

  • Cybersecurity Core

    Leads the TARA and derives cybersecurity goals, claims and requirements.

  • E/E architecture Core

    Provides the item definition — functions, interfaces, data flows — that the TARA analyses; changes the architecture when risks are too high.

  • Functional safety Partial

    Safety-related damage scenarios link the TARA to the HARA; both analyses must be consistent.

  • Networks & communication Partial

    Network topology and interfaces determine attack paths and their feasibility.

  • Base software Partial

    Receives cybersecurity requirements (e.g. SecOC on specific messages) that come out of the TARA.

  • Software update & OTA Partial

    Contributes update-specific assets and attack paths, including tampered packages, compromised campaign infrastructure and unauthorised rollback; implements the resulting update security requirements.

No direct stake: HPC & application software · Hardware & silicon · Diagnostics & lifecycle

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Security services — Implements authentication, access control, cryptography and intrusion detection requirements derived from assessed attack paths.
  • Secure boot chain · TEE — Enforces firmware authenticity and boot integrity requirements derived from threats to executable software.
  • OTA client · UCM — Implements update authenticity and rollback protection requirements derived from update attack scenarios.
MCU-based ECU · AUTOSAR Classic
  • Communication — Applies SecOC protection to messages identified by the TARA as requiring authenticity and freshness.
  • Memory · crypto · WdgM — Provides cryptographic services and protected persistent storage where derived cybersecurity requirements require them.
  • Flash bootloader · secure boot — Verifies firmware authenticity and enforces programming restrictions derived from firmware tampering threats.
  • Diagnostics — Restricts sensitive diagnostic services according to authentication and authorisation requirements derived from diagnostic attack paths.