How to Import Work Items from a Document into Azure DevOps
Azure DevOps only imports CSV files. See how native CSV...
Modern cars are simply computers on wheels having several hundred ECUs interlinked across vehicle systems, sensors, communication interfaces, cloud services, mobile applications, and over-the-air (OTA) update channels. That connectivity creates new ways for attackers to reach vehicle functions and data.
In order to address this issue, the teams follow the ISO/SAE 21434:2021 standard, which describes how organizations determine their cybersecurity risks and design, implement, and assess cybersecurity during the lifecycle of the vehicle. This also helps in complying with UNECE R155 that specifies cybersecurity management and vehicle type approval requirements for the markets that have implemented the regulation.
This guide will help you to comprehend why automotive cybersecurity is essential, some common issues faced while implementing cybersecurity, and how to practically handle the security risks in the automotive domain.
What ISO 21434 is: the automotive cybersecurity engineering standard and its seven TARA modules.
Why vehicles need engineering rules: connected ECUs, fleet-wide risk, and the role of UNECE R155.
The trace chain: how TARA flows to cybersecurity goals, requirements, and verification.
Where programs go wrong: poor traceability, siloed teams, supplier handoffs, and late evidence.
Managing it in Azure DevOps: bidirectional traceability, baselines, and organized audit evidence.
ISO and SAE International issued ISO/SAE 21434:2021. Its title is “Road vehicles Cybersecurity engineering,” and it was released in August 2021. It defines engineering requirements for managing cybersecurity risks in the electrical and electronic systems of road vehicles.
Usually, the standard deals with the management of processes from conception up to product development, manufacturing, operations, maintenance, and decommissioning, as well as cybersecurity management at organizational and project levels within all those stages.
A central method in the standard is Threat Analysis and Risk Assessment (TARA). Clause 15 defines seven TARA modules:
These modules can be applied at different points in the lifecycle, and their outputs become part of the wider cybersecurity work products.
So you can think about it this way:
ISO 21434 = How should we manage automotive cybersecurity?
But not:
ISO 21434 = Which cybersecurity product should we install?
A modern car is no longer a closed mechanical system. It has ECUs, mobile apps, cellular connections, cloud services, Bluetooth, diagnostics, and over-the-air updates. Each connection adds another point that attackers could try to exploit. A weakness in one system can also affect other parts of the vehicle.
The bigger concern is scale. A software flaw in one vehicle may not stay limited to one vehicle. If the same software or ECU is used across thousands of cars, the same weakness can affect an entire fleet. That can turn a technical issue into a safety concern, a costly recall, and a serious business problem.
This is why cybersecurity cannot be treated as a final testing step. Teams need to identify what needs protection, assess how it could be attacked, define cybersecurity goals, and turn those goals into clear requirements. Those requirements then need to be implemented and tested.
The difficult part is keeping all of this connected. When a TARA identifies a serious risk, engineers should be able to trace that risk to the related goal, requirement, test, and evidence. ISO 21434 provides the framework for managing this work, while UNECE R155 has made cybersecurity management part of vehicle type approval in markets where the regulation applies.
How TARA (Threat Analysis Risk Assessment) works is quite straightforward; first, identify critical components in the vehicle, secondly, consider ways that a hacker might exploit these components, third, evaluate the potential impact of the attack, fourth, assess the likelihood of the event, and finally, determine how to proceed. The procedure described above feeds directly into all other requirements of the standard as outlined below.
| Stage | What It Produces | Traces To |
|---|---|---|
| TARA (Clause 15) | Assets, threat scenarios, attack paths, and risk values | Risks that justify cybersecurity goals |
| Cybersecurity Goals (Clause 9) | Top-level security objectives for the item | Back to TARA risks and forward to requirements |
| Cybersecurity Requirements (Clause 10) | Verifiable requirements allocated to the architecture | Back to goals and forward to verification |
| Verification & Validation (Clause 13) | Tests and results proving each requirement | Each requirement to its evidence |
| Cybersecurity Case | The complete argument and supporting evidence | The full chain in both directions |
The key principle is traceability. A cybersecurity risk identified through TARA should connect to a cybersecurity goal, then to specific requirements, and finally to verification tests and evidence.
This link must work in both directions. Teams should be able to trace a test back to the requirement, goal, and risk it addresses, while also tracing each identified risk forward to the requirements and tests that manage it.
For instance, if the risk of unauthorized access to the vehicle’s interface is involved, then it will result in an authentication process and further test if the authentication process succeeds or not. This clear sequence of events helps in finding out what areas are lacking and also gives evidence to the auditors.
The adoption of the ISO/SAE 21434 standard may be complicated by the fact that cybersecurity activities are distributed among various teams, software, and vendors. The primary issues here will be associated with data linking and synchronization.
Common to both is the problem of maintaining linkage between risk, requirement, test, and evidence over the lifecycle of the vehicle.
ISO/SAE 21434 requires the tracing of cybersecurity threats, objectives, requirements, and validation. For teams working inside Azure DevOps, requirements management tools like Modern Requirements4DevOps help to build a single source of truth for creating all development and cybersecurity-related requirements and ensure traceability in the same place.
Such characteristics can be utilized by automotive engineering teams when executing the ISO 21434 cybersecurity engineering process. If you want to learn more about how Modern Requirements can help you with automotive requirements management, please visit automotive requirements management.
Want to simplify ISO 21434 requirements management? Start a 30-day free trial of Modern Requirements4DevOps.
Since ISO 21434 is a voluntary industry standard, it is effectively required by law with UNECE R155 for the ISO 21434- based implementation and certification of CSMS.
ISO 21434 is the information security standard for the automotive industry that will help you meet the compliance requirements defined by R155.
These work products include the TARA report, cybersecurity requirements, test results, and cybersecurity case, which document the cybersecurity activities performed.
HARA is the analysis of safety risk because of failures and accidents, while TARA is the risk analysis of cybersecurity due to attacks.
It applies only to systems developed after August 2021. Moreover, it could be applied to other needs associated with cybersecurity regarding new or revised automobiles.
Azure DevOps only imports CSV files. See how native CSV...
Small banks spend 3x more of their budget on compliance....
DORA auditors now want proof, not policies. See what evidence...
End-to-end requirements management in Azure DevOps.
AI-powered assistance for DevOps workflows.
Autonomous AI agents for DevOps execution.
Compliance management, built into Azure DevOps.
Real-time data sync across tools and systems.