EnCo ASE TARA

EnCo ASE TARA for ISO/SAE 21434 & ISO 24882: Threat Analysis and Risk Assessment for Road Vehicles and Agricultural Machinery

Perform Threat Analysis and Risk Assessment (TARA) according to ISO/SAE 21434 for road vehicles and ISO 24882 for agricultural machinery, tractors and earth-moving machinery – in one integrated engineering environment with multi-user collaboration and audit-ready documentation.

ISO/SAE 21434 Road Vehicles
ISO 24882 Agricultural Machinery
Integrated Engineering Data
Request a Free TARA Demo

No obligation · Personal consultation · Fast response

The Challenge: Two Standards, One TARA Process

ISO/SAE 21434 defines cybersecurity engineering for road vehicles and is the technical basis for the Cybersecurity Management System (CSMS) required by UN Regulation No. 155. ISO 24882 (currently ISO/DIS 24882) transfers this approach to agricultural machinery, tractors and earth-moving machinery, where telematics, ISOBUS, remote diagnostics and autonomous functions create new attack surfaces – with a direct link to the EU Cyber Resilience Act and the EU Machinery Regulation. Both standards require a documented Threat Analysis and Risk Assessment (TARA) that is kept up to date across the whole product lifecycle.

The problem: Spreadsheet-based TARAs are hard to keep consistent, cannot be traced to requirements and system design, and have to be rebuilt for every variant, audit or additional standard.

EnCo ASE TARA manages the complete analysis in one database, so one method with standard-specific rating schemes covers ISO/SAE 21434 and ISO 24882.

ISO/SAE 21434 and ISO 24882 at a Glance

Both standards follow the same engineering logic: identify assets, describe damage and threat scenarios, rate impact and attack feasibility, determine the risk and decide on its treatment. They differ in the products they cover, the rating criteria and the regulations behind them.

Road vehicles

ISO/SAE 21434:2021

Cybersecurity engineering for the electrical and electronic systems of road vehicles, their components and interfaces.

  • Applies to passenger cars, trucks, buses, motorcycles and their suppliers (OEM, Tier 1, Tier 2)
  • TARA methods in Clause 15: asset identification, threat scenarios, impact rating, attack path analysis, attack feasibility, risk value and risk treatment
  • Impact is rated for safety, financial, operational and privacy damage
  • Technical basis for the Cybersecurity Management System (CSMS) under UN Regulation No. 155
Agricultural machinery, tractors and earth-moving machinery

ISO 24882 (ISO/DIS 24882)

Product cybersecurity for the E/E systems of agricultural machinery, tractors and earth-moving machinery over the whole lifecycle – from concept and development to production, operation, maintenance and decommissioning.

  • Developed by ISO/TC 23/SC 19, currently a Draft International Standard
  • Builds on the principles of ISO/SAE 21434 with evaluation criteria adapted to mobile work machines
  • Addresses connected functions such as telematics, ISOBUS implements, remote diagnostics and automation
  • Links product cybersecurity to the EU Cyber Resilience Act and explains the relationship to the EU Machinery Regulation, ISO/SAE 21434 and IEC 62443

Core TARA Capabilities for ISO/SAE 21434 and ISO 24882

From assets and damage scenarios to threat scenarios, attack paths, risk values and treatment decisions, EnCo ASE provides everything required to develop and maintain structured TARAs for road vehicles and mobile work machines.

01

Assets & Damage Scenarios

Identify assets and describe the damage scenarios that matter for your item – whether it is a vehicle ECU or a tractor control unit.

  • Identify assets and their cybersecurity properties (confidentiality, integrity, availability)
  • Describe damage scenarios for road users, operators, fleet owners and other stakeholders
  • Rate impact in categories such as safety, financial, operational and privacy
  • Keep asset information connected with the system model
02

Threat Scenarios & Attack Paths

Analyze how damage scenarios can be caused and how attacks could be realized via vehicle networks, telematics, diagnostics or implement interfaces.

  • Derive threat scenarios for assets and cybersecurity properties
  • Model attack paths and rate attack feasibility (attack potential, CVSS or attack vector based)
  • Reduce effort with transferable attack paths
  • Connect threat scenarios with attack tree analysis
03

Risk Determination & Treatment

Evaluate risks and define how your organization responds to them.

  • Determine risk values from impact and attack feasibility
  • Apply predefined and project specific risk calculation models
  • Decide risk treatment – avoid, reduce, share or retain – and derive cybersecurity goals
  • Track treatment decisions and their implementation
04

Standard-Specific Rating Schemes & Catalogs

Run the TARA with the rating scheme your standard and your customers expect – without rebuilding the analysis.

  • Configure impact categories, feasibility criteria and risk matrices to match ISO/SAE 21434 or ISO 24882
  • Customizable choice lists for project and customer specific requirements
  • Reusable catalogs for assets, threat scenarios and measures
  • Consistent results as evidence for CSMS audits and CRA documentation
05

Review, Reporting & Documentation

Keep TARA information structured and available for audits, CSMS assessments and product documentation.

  • Work with review workflows and dashboards
  • Version projects and compare analysis states
  • Generate reports and cybersecurity documentation with the Report Designer
  • Keep results accessible for engineering teams, assessors and auditors

Who Is EnCo ASE TARA Designed For?

Automotive OEMs & Suppliers

To perform ISO/SAE 21434 TARAs for ECUs, vehicle functions and complete vehicles and to provide evidence for the CSMS under UN R155.

Manufacturers of Agricultural & Mobile Work Machinery

To prepare for ISO 24882 and the EU Cyber Resilience Act with a structured TARA for tractors, implements and earth-moving machinery.

Cybersecurity Managers & Assessors

For consistent, traceable and audit-ready cybersecurity documentation across projects, variants and standards.

TARA Workflow Based on ISO/SAE 21434 and ISO 24882

EnCo ASE TARA supports your team throughout the complete threat analysis and risk assessment process defined in ISO/SAE 21434 and adopted by ISO 24882 – from asset identification and threat scenarios to risk determination and treatment decisions.

01

Item Definition &
Assets

Define the item and identify assets with their cybersecurity properties

02

Damage
Scenarios

Describe damage scenarios and rate their impact

03

Threat
Scenarios

Identify threat scenarios for assets and cybersecurity properties

04

Attack Path
Analysis

Analyze attack paths and rate attack feasibility

05

Risk
Determination

Determine risk values from impact and attack feasibility

06

Risk
Treatment

Decide risk treatment and derive cybersecurity goals

07

Documentation &
Review

Document results and support review and release workflows

EnCo ASE TARA guides you through the complete TARA methodology of ISO/SAE 21434 and ISO 24882 with integrated data, reuse of engineering knowledge and real time collaboration.

Integrated Engineering. Connected TARA.

EnCo ASE connects TARA with requirements, system structures and additional security analyses so engineering information can be reused, traced and maintained across the development process.

Requirements

Connect requirements and relevant engineering information directly with the TARA.

System Design

Reuse system structures, interfaces and engineering relationships within the analysis.

Core Analysis

TARA

Develop structured TARAs using connected engineering data instead of isolated information.

Attack Trees

Analyze attack paths in more detail with connected attack tree analysis.

Cybersecurity Goals

Derive cybersecurity goals and requirements from risk treatment decisions.

Reporting

Use structured engineering data to create consistent reports and project documentation.

End to End Traceability

Maintain relationships between requirements, system elements, assets, threat scenarios and downstream analyses.

Reuse Engineering Knowledge

Use existing information across analyses and projects instead of maintaining the same engineering knowledge multiple times.

Consistent Engineering Data

Work with connected data rather than isolated documents and reduce inconsistencies between engineering disciplines.

TARA becomes part of the engineering model. EnCo ASE allows teams to connect analysis data across requirements, system design and security engineering instead of managing TARA as an isolated document.

Connect TARA with Your Engineering Toolchain

Import existing engineering information, exchange structured TARA data and export results for further use across your development environment. EnCo ASE helps integrate TARA into established engineering workflows instead of creating another isolated data source.

Bring Data In

Import

Bring existing engineering and analysis information into EnCo ASE and use available project data as the foundation for further analysis.

Data Exchange

Exchange structured engineering information between EnCo ASE and other systems while preserving relevant relationships within your workflow.

Engineering Data EnCo ASE TARA
Use Data Beyond TARA

Export

Export TARA information and analysis results for documentation, communication and further use in your engineering environment.

Toolchain Integration

Connect TARA activities with surrounding engineering processes and keep information available where your teams need it.

Use Existing Data

Build on engineering information that already exists instead of recreating it manually inside the TARA.

Reduce Duplicate Work

Exchange and reuse structured information across engineering activities and reduce unnecessary manual data transfer.

Keep Engineering Connected

Integrate TARA into the wider development process and maintain connections between relevant engineering information.

Your TARA does not have to live in isolation. EnCo ASE helps you move engineering information into, through and out of the TARA process while keeping it connected to your wider engineering environment.

Technical Overview

Key technical capabilities of EnCo ASE TARA at a glance.

Methodology

ISO/SAE 21434 & ISO 24882
Threat Analysis & Risk Assessment

Risk Models

Predefined & Project Specific
Risk Calculation

Collaboration

Multi User
Engineering

Knowledge Reuse

Catalogs &
Transferable Attack Paths

Engineering Integration

Requirements, System Design
& Attack Trees

Data Exchange

Import, Export &
Excel Reporting

Ready to Improve Your TARA Workflow?

See how EnCo ASE TARA supports your engineering team with a structured TARA workflow for ISO/SAE 21434 and ISO 24882, integrated engineering data and efficient knowledge reuse.

Request a Free Demo
No obligation · Personal consultation · Fast response

FAQ – Frequently Asked Questions about TARA, ISO/SAE 21434 & ISO 24882

Answers to common questions about Threat Analysis and Risk Assessment, the two standards and EnCo ASE TARA.

What is a TARA (Threat Analysis and Risk Assessment)?

A TARA is the systematic cybersecurity risk assessment of a product. It identifies assets, describes damage and threat scenarios, analyzes attack paths, rates impact and attack feasibility, determines risk values and documents the risk treatment decisions. ISO/SAE 21434 defines the TARA methods for road vehicles, and ISO 24882 adopts the same approach for agricultural machinery, tractors and earth-moving machinery.

What is the difference between ISO/SAE 21434 and ISO 24882?

ISO/SAE 21434:2021 covers cybersecurity engineering for road vehicles and is the technical basis for the CSMS required by UN Regulation No. 155. ISO 24882 applies the same engineering principles to agricultural machinery, tractors and earth-moving machinery, with evaluation criteria adapted to mobile work machines and a direct link to the EU Cyber Resilience Act. ISO 24882 is currently a Draft International Standard (ISO/DIS 24882).

Is ISO 24882 already published?

Not yet. ISO 24882 is being developed by ISO/TC 23/SC 19 and is currently at the Draft International Standard stage. Many manufacturers already align their processes with the draft, because the EU Cyber Resilience Act and the EU Machinery Regulation require product cybersecurity independently of the final publication of the standard.

Does EnCo ASE TARA support ISO/SAE 21434?

Yes. The TARA module follows the methodology of ISO/SAE 21434 for road vehicle cybersecurity engineering, including asset identification, damage and threat scenarios, impact rating, attack feasibility rating, risk determination and risk treatment decisions.

Can EnCo ASE TARA be used for ISO 24882?

Yes. Because ISO 24882 follows the TARA logic of ISO/SAE 21434, the same workflow applies. Impact categories, attack feasibility criteria and risk matrices can be configured per project, so the analysis can follow the adapted evaluation criteria of ISO 24882 for tractors, implements and earth-moving machinery.

How does TARA relate to UN R155 and the CSMS?

UN Regulation No. 155 requires vehicle manufacturers to operate a certified Cybersecurity Management System (CSMS) and to demonstrate the risk assessment for each vehicle type. A documented TARA according to ISO/SAE 21434 is the accepted way to provide this evidence. EnCo ASE keeps the TARA versioned, reviewed and traceable so it can be presented to the approval authority.

Which regulations drive cybersecurity for agricultural machinery?

The EU Cyber Resilience Act sets horizontal cybersecurity requirements for products with digital elements, and the EU Machinery Regulation 2023/1230 adds protection against corruption for the safety functions of machinery. ISO 24882 translates these requirements into an engineering process for agricultural machinery, tractors and earth-moving machinery.

Can risk calculation be adapted to our organization?

Yes. EnCo ASE TARA provides predefined risk calculation models and also supports project specific models, customizable choice lists and catalogs, so the analysis matches your internal cybersecurity process and the standard you work with.

Can multiple engineers work on a TARA at the same time?

Yes. TARA projects are stored in a central database and support multi user collaboration, change history and review workflows, so distributed teams can work on the same analysis without exchanging files.

How is TARA connected with requirements, system design and attack trees?

Assets and analysis elements can be connected with requirements and system structures in EnCo ASE. Threat scenarios and attack paths can be analyzed in more detail with the integrated Attack Tree Analysis module, and cybersecurity goals derived in the TARA can be managed as requirements for downstream development.

Can existing TARA knowledge be reused in new projects?

Yes. Catalogs, transferable attack paths and versioned projects make it possible to reuse existing analysis knowledge and compare project versions instead of starting every TARA from scratch – also across road vehicle and agricultural machinery projects.

Does EnCo ASE support TARA reporting and documentation?

Yes. TARA data can be documented with the integrated Report Designer and exported for communication with customers, assessors and auditors, including Excel based reporting.

Why use EnCo ASE TARA instead of Excel?

Spreadsheets become hard to maintain as items, assets and threat scenarios grow and change. A database driven TARA tool keeps relationships consistent, supports collaboration and versioning, and reduces manual effort when the analysis needs to be updated for a new variant, a new standard or an audit.