The standard does not treat cybersecurity as a final check, but as part of development, from concept to decommissioning and across the entire supply chain. In practice, the open question is therefore rarely what needs to be done, but where the evidence for it is kept.
As of: 23 September 2026
| Component | Interface | Gross | Net |
|---|---|---|---|
| Telematics unit | Cellular | ||
| Central control unit | Vehicle bus | ||
| Charging interface | external | ||
| Diagnostic access | Workshop |
ISO/SAE 21434 is the standard for cybersecurity engineering for road vehicles. According to the International Organization for Standardization, it addresses the cybersecurity perspective in the engineering of electrical and electronic systems in road vehicles. The standard defines terms, objectives, requirements and guidelines for cybersecurity engineering so that the same understanding applies across the entire supply chain.
It covers the entire lifecycle of these systems, from concept through development and production to operations, maintenance and decommissioning. It is an engineering standard, not a management system with certification.
Cybersecurity does not end with release. What happens after the start of production is just as much a part of it as the concept before it.
What the system does, where it can be attacked and which cybersecurity goals follow from that. This is where it is decided what will be developed at all later on.
The goals are translated into requirements, architecture and tests. This makes cybersecurity a development task rather than a final check.
Manufacturing also contributes to cybersecurity: keys, configurations and access must be implemented in series production the way they were planned.
Some vulnerabilities only become visible in the field. Reported vulnerabilities must be assessed and handled for as long as the vehicle is in operation.
The end of the lifecycle is part of it too: access is revoked, keys and data are handled securely and responsibilities are ended in an orderly way.
The phases reflect the description of the International Organization for Standardization. We do not reproduce clause numbers, requirement numbers or work products, because the full text of the standard is subject to a fee. According to ISO, ISO/SAE 21434 has been under systematic review since 15 Jul 2026.
Manufacturers and suppliers along the same supply chain. The standard is voluntary, but it is regularly required in the supply chain.
According to ISO, the standard defines terms, objectives, requirements and guidelines so that the same understanding applies across the entire supply chain. This is exactly where the first problems arise in practice: if manufacturers and suppliers assess differently, no reliable overall statement can be made.
According to ISO, cybersecurity issues should be considered in every phase of the development process and in the field. For vehicles that are in use for ten years and longer, this is the longest part of the work.
ISO/SAE 21434 is not a management system with a certificate. An auditable management system is required by UN Regulation No. 155 with its Cyber Security Management System, which builds on the same processes.
Eight points along the lifecycle. They are easy to understand but hard to prove when the evidence is scattered.
| Requirement | Phase | What matters | How you map it in CRISAM® |
|---|---|---|---|
| Organize cybersecurity | Cross-phase | Responsibilities, rules and competencies must be defined before the first project, not emerge while it is underway | The integrated Automotive Knowledge Pack provides over 85 building blocks and more than 650 control objectives that serve as the basis for your own structure. |
| Define the scope | Concept | Which components, interfaces and functions are considered and which are explicitly not | Structures are modeled flexibly. Components and interfaces are captured as objects in the same model as risks and measures. |
| Analyze threats | Concept | The function determines what an attacker could achieve. Only from this are the cybersecurity goals derived | Risks can be identified and assessed in a structured way using wizards, qualitatively or quantitatively, depending on maturity. |
| Show the effect of measures | Development | It must be clear how high a risk is without and with the implemented measures | Risks are assessed in a gross and net view. Measures are planned, implemented and monitored with workflow support. |
| Involve suppliers | Development | A large share of the components comes from suppliers. Without a shared understanding in the supply chain, the overall statement is not reliable | Information can be collected in a targeted, decentralized way from the responsible subject matter owners. This reduces the effort for baseline audits, reviews and supplier inquiries. |
| Secure the transition to series production | Production | What was developed must also be implemented that way in manufacturing. Configurations and access must be documented | Requirements and evidence are assigned to the same objects as in development, every open item with an owner and a deadline. |
| Handle vulnerabilities | Operations | Reports from the field must be assessed in a traceable way for as long as the vehicle is in operation | Incidents and vulnerabilities are documented in a structured way, and the resulting measures run through the same workflows. |
| Maintain evidence | Cross-phase | In audits and customer inquiries, it is not only the result that counts, but also the path that led to it | Dashboards show compliance status, deviations and measures. Reports for audits and customer inquiries as well as export functions for assessments and audits are available. |
From the scope to the documents that a customer or an auditor receives.
At the start, you define what is considered. Components, interfaces and functions are modeled as objects so that every assessment can later be assigned to a specific object.
| Component | Origin | Interface | Criticality | Assessment |
|---|---|---|---|---|
| Telematics unit | Supplier A | Cellular | completed | |
| Central control unit | internal | Vehicle bus | completed | |
| Charging interface | Supplier B | external | in progress | |
| Diagnostic access | internal | Workshop | completed | |
| Infotainment | Supplier C | Bluetooth, Wi-Fi | in progress | |
| Chassis sensors | Supplier D | Vehicle bus | open |
The wizard guides you through the assessment. The function determines what an attacker could achieve, and from that the level of risk.
What a component can do determines what an attacker could achieve. That is why the assessment starts with the function, not with the technology.
Reachability counts twiceA component that can be reached remotely carries different weight than one that someone can only get to in the workshop.
Same methodology along the chainIf manufacturers and suppliers assess differently, the overall statement cannot be consolidated.
Cybersecurity goals are derived from the threats, and requirements from the goals. It remains visible which threat is behind which requirement.
| Threat | Component | Gross | Measures | Net | Reviewed |
|---|---|---|---|---|---|
| Inject commands remotely | Telematics unit | 4 implemented | 4 Sep 2026 | ||
| Manipulate the charging process | Charging interface | 3 implemented | 4 Sep 2026 | ||
| Read out vehicle data | Infotainment | 2 implemented | 21 Aug 2026 | ||
| Misuse diagnostic access | Diagnostic access | 3 implemented | 21 Aug 2026 | ||
| Falsify sensor data | Chassis sensors | 1 implemented | open | ||
| Install software without authorization | Central control unit | 4 implemented | 12 Jun 2026 |
A large share of the evidence sits with suppliers. Requests are sent out decentrally and evaluated centrally. Spreadsheets no longer have to be merged manually.
The longest phase begins after the start of production. Reports from the field are assessed and assigned to the affected component, not to a project folder.
| Report | Component | Source | Rating | Consequence |
|---|---|---|---|---|
| Vulnerability in a radio library | Telematics unit | Supplier | Measure in progress | |
| Faulty certificate validation | Charging interface | Research | Measure open | |
| Open debug access in one batch | Control unit | Production | completed | |
| Indication of a side channel | Infotainment | Research | documented | |
| Report without reliable details | unclear | external | Assessment open |
| Item | Effect | Owner |
|---|---|---|
| Two reports without a completed assessment | Gap in the evidence for the field | Product Security |
| One supplier without a reporting channel for vulnerabilities | Reports reach development late | Purchasing |
At the end, you hand over the status per phase to customers or auditors with the associated documents, including the documentation of how they were created.
| Document | Content | As of | Owner | Status |
|---|---|---|---|---|
| Scope description | 47 components, 63 interfaces | 4 Sep 2026 | Development | |
| Threat analysis | 94 threats with assessment | 4 Sep 2026 | Product Security | |
| Cybersecurity goals | 38 goals linked to a threat | 4 Sep 2026 | Development | |
| Supplier evidence | 12 requests, responses documented | ongoing | Purchasing | |
| Vulnerability handling | 23 reports with rating | ongoing | Product Security | |
| Measures register | 31 open items with deadline | ongoing | Departments |
Scope, cybersecurity goals, requirements, architecture and tests.
Threat analysis, vulnerabilities from the field, assessment and handling.
Requests, evidence and reporting channels at suppliers.
Internal audits, customer inquiries, support for external audits.
The automotive industry places high demands on information security, supply chain compliance and audit readiness. In CRISAM®, you collect the necessary information only once.
In addition to TISAX, requirements from UN R 155 and 156, ISO/SAE 21434 and IATF 16949 can be mapped and evaluated in a structured way.
The required Information Security Assessment can be generated, exported and imported directly from CRISAM®. Learn more on the TISAX page.
The automotive extension is connected to ISMS, data protection, internal control system, audit and risk management. If you work according to ISO 27001, you already have the basic structure.
The integrated Automotive Knowledge Pack provides over 85 building blocks and more than 650 control objectives. This means you do not have to build your own structure from scratch.
The three are often mentioned together, although they serve different purposes. ISO/SAE 21434 describes how vehicle systems are developed securely. UN Regulation No. 155 requires a management system for cybersecurity whose elements, according to ISO, are based on the processes of ISO/SAE 21434. TISAX answers a third question: how securely a company handles its partners' information.
| Criterion | ISO/SAE 21434 | UN R 155 | TISAX |
|---|---|---|---|
| Type | International standard, first edition dated 31 August 2021 | Regulation of the United Nations Economic Commission for Europe | Assessment and exchange mechanism of the German Association of the Automotive Industry (VDA) |
| Subject | Cybersecurity engineering for electrical and electronic systems | Cybersecurity and a Cyber Security Management System | Information security within the company and toward partners |
| Addressee | Manufacturers and suppliers along the development chain | Vehicle manufacturers, indirectly their suppliers | Companies in the automotive industry and their service providers |
| Binding nature | Voluntary, but regularly required in the supply chain | Binding where the regulation is applied | Voluntary, but regularly expected in contracts |
| Relationship | Provides the processes | According to ISO, elements of the management system are based on these processes | Its own catalog, with overlaps in organization and evidence |
| The end result | Evidence of cybersecurity engineering, auditable according to the ISO guidelines from 2022 | A certificate for the management system | A label that is shared with partners via the platform |
| Mapping in CRISAM® | As requirements and risks on components and interfaces | Via the same objects, supplemented by the management system view | Via the Automotive Knowledge Pack, with export of the assessment |
All three concern the same objects: components, interfaces, suppliers, measures and evidence. If you keep them in three separate repositories, you maintain the same information three times and have to explain deviations in the audit. In a shared model, you answer the same question only once. You can find an overview of all frameworks under Standards and frameworks.
The first step depends on where you stand today.
Then you start with a common basis. The integrated Automotive Knowledge Pack provides over 85 building blocks and more than 650 control objectives that the projects align with.
Then the focus is on decentralized requests. Information can be collected in a targeted way from the responsible subject matter owners, which reduces the effort for baseline audits, reviews and supplier inquiries.
Then the field phase is the next step. Vulnerabilities and the resulting measures are assigned to the component, not to a project folder that will be closed at some point.
For this you need the CRISAM® GRC Platform, the CRISAM® ISMS Module and the Automotive Knowledge Pack. In the demo, we discuss your starting point and show which of these you already have in place.
ISO/SAE 21434 is the standard for cybersecurity engineering for road vehicles. According to the International Organization for Standardization, it addresses the cybersecurity perspective in the engineering of electrical and electronic systems in road vehicles. The standard defines terms, objectives, requirements and guidelines for cybersecurity engineering so that the same understanding applies across the entire supply chain.
The first edition was published on 31 August 2021. According to ISO, the standard has been under systematic review since 15 Jul 2026, as is scheduled at regular intervals for international standards.
The three are often mentioned together, although they serve different purposes. ISO/SAE 21434 describes how vehicle systems are developed securely. UN Regulation No. 155 requires a management system for cybersecurity whose elements, according to ISO, are based on the processes of ISO/SAE 21434. TISAX answers a third question: how securely a company handles its partners' information.
According to ISO, the entire lifecycle of the electrical and electronic systems in the vehicle, from concept through development and production to operations, maintenance and decommissioning. Cybersecurity issues should be considered in every phase of the development process and in the field.
The standard is an engineering standard and not a management system with certification. For auditing, there is a separate ISO guideline from 2022 on auditing cybersecurity engineering. An auditable management system, by contrast, is required by UN Regulation No. 155.
Because a large share of the components comes from suppliers. According to ISO, the standard defines terms, objectives, requirements and guidelines so that the same understanding applies across the entire supply chain. If manufacturers and suppliers assess differently, the overall statement cannot be consolidated.
In CRISAM®, information can be collected in a targeted, decentralized way from the responsible subject matter owners. This significantly reduces the effort for baseline audits, reviews and supplier inquiries, because responses from spreadsheets and emails no longer have to be merged manually.
What matters is whether component, threat, measure and evidence are linked in a shared model. CRISAM® maps and evaluates the requirements from VDA TISAX as well as from UN R 155 and 156, ISO/SAE 21434 and IATF 16949 in a structured way, identifies compliance gaps and deviations, and provides more than 85 building blocks and over 650 control objectives through the integrated Automotive Knowledge Pack.
The information about the standard on this page comes from the following sources. The full text is subject to a fee, which is why no clause or requirement numbers are reproduced.
The information reflects the status of the sources listed as of the review date stated above.
In the demo, we walk through your case: scope, threats and goals, requirements per phase, supplier requests and the evidence for customers and auditors.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Embedded Content. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information