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
- Asset identification — e.g. brake commands, firmware, keys, personal data — and the property to protect (integrity, confidentiality, availability).
- Damage scenarios — consequences rated for safety, financial, operational and privacy impact.
- Threat scenarios — what an attacker would do to cause the damage.
- Attack path analysis — how they get from an entry point (telematics, OBD, Bluetooth) to the asset.
- Attack feasibility — rated by factors such as elapsed time, expertise, knowledge of the item, window of opportunity and equipment.
- Risk value from impact and feasibility.
- Risk treatment — avoid, reduce, share or accept. Reductions become cybersecurity goals and requirements.
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.