Crisam Logo
  • CRISAM®
    CRISAM®
    • What is CRISAM®?
    • Method
    • Content
    • Customers
    • Academy
    • Webinars
    • Events
  • Areas of application
    Areas of application
    • Information Security Management
    • Integrated Risk Management
    • ESG
    • CRISAM® AI
    • Data Protection Management
    • Audit Management
    • Compliance Management
    • Business Continuity Management
    • Tax Compliance Management System
    • Project Risk Management
    • Legal Register
    • Conflicts of Interest Software
    • CRISAM® Legal Hold Software
  • Industries
    Industries
    • Automotive
    • Energy
    • Manufacturing
    • Financial Services
    • Retail
    • Real Estate & Construction
    • Healthcare
    • Broadcasting & Telecommunications
    • Technology
    • Transport & Logistics
  • More
    More
    • Download Center
    • CRISAM® Academy
    • Webinars
    • News
    • Jobs
    • CRISAM® Partners
    • Trust Center
    • Contact
  • en
    • en-gb
    • de
Request
  • Language
    • en-gb
    • de
  • CRISAM®
    • What is CRISAM®?
    • Method
    • Content
    • Customers
    • Academy
    • Webinars
    • Events
  • Areas of application
    • Information Security Management
    • Integrated Risk Management
    • ESG
    • CRISAM® AI
    • Data Protection Management
    • Audit Management
    • Compliance Management
    • Business Continuity Management
    • Tax Compliance Management System
    • Project Risk Management
    • Legal Register
    • Conflicts of Interest Software
    • CRISAM® Legal Hold Software
  • Industries
    • Automotive
    • Energy
    • Manufacturing
    • Financial Services
    • Retail
    • Real Estate & Construction
    • Healthcare
    • Broadcasting & Telecommunications
    • Technology
    • Transport & Logistics
  • More
    • Download Center
    • CRISAM® Academy
    • Webinars
    • News
    • Jobs
    • CRISAM® Partners
    • Trust Center
    • Contact
  • Request
Short answer Lifecycle Triggers Requirements Implementation Comparison Getting started FAQ
Regulations and frameworks

Implementing ISO/SAE 21434: cybersecurity across the entire vehicle lifecycle

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

Book a demo View requirements
CRISAM®Sample values
☰Zulieferer AG/ Automotive Security
DASHBOARDS, compliance level per phase
Concept
88 %
Development
72 %
Production
63 %
Operations and maintenance
49 %
85Building blocks in the Knowledge Pack
47Components in scope
31Open measures
12Suppliers involved
Cybersecurity risks per component
ComponentInterfaceGrossNet
Telematics unitCellularvery highhigh
Central control unitVehicle bushighmedium
Charging interfaceexternalhighmedium
Diagnostic accessWorkshopmediumlow
Short answer

What is ISO/SAE 21434?

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.

StandardISO/SAE 21434:2021
EditionFirst edition, 31 August 2021
SubjectCybersecurity engineering
CoverageEntire lifecycle
The lifecycle

Five phases that extend beyond the start of production

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.

Phase 1

Concept

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.

Phase 2

Development

The goals are translated into requirements, architecture and tests. This makes cybersecurity a development task rather than a final check.

Phase 3

Production

Manufacturing also contributes to cybersecurity: keys, configurations and access must be implemented in series production the way they were planned.

Phase 4

Operations and maintenance

Some vulnerabilities only become visible in the field. Reported vulnerabilities must be assessed and handled for as long as the vehicle is in operation.

Phase 5

Decommissioning

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.

Triggers

Who works according to ISO/SAE 21434

Manufacturers and suppliers along the same supply chain. The standard is voluntary, but it is regularly required in the supply chain.

Typical triggers

  • A customer requires evidence of cybersecurity engineering for a component
  • An audit according to the guidelines for cybersecurity engineering audits is coming up
  • A new vehicle project is starting and the cybersecurity goals are still missing
  • Threat analysis and risk assessment start from scratch in every project, without a common basis
  • Vulnerability reports from the field go to support instead of to development
  • The evidence sits in project folders instead of being assigned to the components

Why the supply chain matters so much here

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.

What comes after the start of production

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.

What the standard is not

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.

Requirements

What cybersecurity engineering means in day-to-day work

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.
Implementation

Cybersecurity engineering in CRISAM®, step by step

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.

CRISAM®Sample values
☰Zulieferer AG/ Automotive Security
47Components in scope
63Interfaces
12Suppliers involved
5Assessments open
SCOPE, components and interfaces
ComponentOriginInterfaceCriticalityAssessment
Telematics unitSupplier ACellularhighcompleted
Central control unitinternalVehicle bushighcompleted
Charging interfaceSupplier Bexternalhighin progress
Diagnostic accessinternalWorkshopmediumcompleted
InfotainmentSupplier CBluetooth, Wi-Fimediumin progress
Chassis sensorsSupplier DVehicle buslowopen
Components by criticality
Very highHighMediumLowVery low

The wizard guides you through the assessment. The function determines what an attacker could achieve, and from that the level of risk.

CRISAM®Sample values
✕Zulieferer AG/ Automotive Security
ScopeThreatsGoalsSuppliersFieldReports
←Assess threat

Threat and assessment

COMPONENT
Telematics unit
INTERFACE
Cellular
ATTACK PATH
remote
ASSESSMENT METHOD
qualitative
POTENTIAL IMPACT
Impairment of a driving function
AFFECTED GOALS
Integrity of control commands, confidentiality of vehicle data
DESCRIPTION
The unit is permanently reachable and can pass commands on to the vehicle bus
OWNER
Head of Development
NEXT REVIEW
31 Mar 2027
From function to threat

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 twice

A component that can be reached remotely carries different weight than one that someone can only get to in the workshop.

Same methodology along the chain

If manufacturers and suppliers assess differently, the overall statement cannot be consolidated.

AssessmentNEXT

Cybersecurity goals are derived from the threats, and requirements from the goals. It remains visible which threat is behind which requirement.

CRISAM®Sample values
☰Zulieferer AG/ Automotive Security
94Threats assessed
38Goals derived
122Requirements
31Open measures
GOALS, from threat to requirement
ThreatComponentGrossMeasuresNetReviewed
Inject commands remotelyTelematics unitvery high4 implementedhigh4 Sep 2026
Manipulate the charging processCharging interfacehigh3 implementedmedium4 Sep 2026
Read out vehicle dataInfotainmenthigh2 implementedmedium21 Aug 2026
Misuse diagnostic accessDiagnostic accessmedium3 implementedlow21 Aug 2026
Falsify sensor dataChassis sensorsmedium1 implementedlowopen
Install software without authorizationCentral control unithigh4 implementedlow12 Jun 2026
Requirements per phase
ConceptDevelopmentProductionOperationsEnd

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.

CRISAM®Sample values
☰Zulieferer AG/ Automotive Security
Requests to subject matter owners and suppliers12 entries
AllOpenPartialCompleteOverdue
Cybersecurity evidence, telematics unitSupplier A
Component31 Jul 2026complete
Evidence, charging interfaceSupplier B
Component31 Oct 2026partial
Interface description, infotainmentSupplier C
Interface30 Nov 2026partial
Handling of vulnerability reportsSupplier D
Process31 Dec 2026open
Key management in manufacturingProduction
Process30 Jun 2026complete
Evidence, chassis sensorsSupplier D
Component31 Jan 2027open
123›

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.

CRISAM®Sample values
☰Zulieferer AG/ Automotive Security
23Reports in the period
6Rated relevant
4Measures derived
2Assessments open
FIELD, vulnerabilities and consequence
ReportComponentSourceRatingConsequence
Vulnerability in a radio libraryTelematics unitSupplierrelevantMeasure in progress
Faulty certificate validationCharging interfaceResearchrelevantMeasure open
Open debug access in one batchControl unitProductionrelevantcompleted
Indication of a side channelInfotainmentResearchnot relevantdocumented
Report without reliable detailsunclearexternalopenAssessment open
Open items
ItemEffectOwner
Two reports without a completed assessmentGap in the evidence for the fieldProduct Security
One supplier without a reporting channel for vulnerabilitiesReports reach development latePurchasing

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.

CRISAM®Sample values
☰Zulieferer AG/ Automotive Security
Cybersecurity engineering evidenceAs of Q3 2026
Concept
Development
Production
Operations and maintenance
requiredachieved
DocumentContentAs ofOwnerStatus
Scope description47 components, 63 interfaces4 Sep 2026Developmentcomplete
Threat analysis94 threats with assessment4 Sep 2026Product Securitycomplete
Cybersecurity goals38 goals linked to a threat4 Sep 2026Developmentpartial
Supplier evidence12 requests, responses documentedongoingPurchasingpartial
Vulnerability handling23 reports with ratingongoingProduct Securityunder review
Measures register31 open items with deadlineongoingDepartmentspartial
Development

Scope, cybersecurity goals, requirements, architecture and tests.

Product security

Threat analysis, vulnerabilities from the field, assessment and handling.

Purchasing and supplier management

Requests, evidence and reporting channels at suppliers.

Quality and audit

Internal audits, customer inquiries, support for external audits.

Multi-Compliance

Four automotive requirements, one data set

The automotive industry places high demands on information security, supply chain compliance and audit readiness. In CRISAM®, you collect the necessary information only once.

Four frameworks in one model

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 path to the TISAX label

The required Information Security Assessment can be generated, exported and imported directly from CRISAM®. Learn more on the TISAX page.

The same structure as in the ISMS

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.

85 building blocks as a starting point

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.

Comparison

ISO/SAE 21434, UN R 155 and TISAX

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

Why the effort does not triple

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.

Getting started

How to get started with CRISAM®

The first step depends on where you stand today.

Starting point A

Every project assesses on its own

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.

Starting point B

Supplier evidence arrives by email

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.

Starting point C

There is no tracking after the start of production

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.

Book a demo
Frequently asked questions

Frequently asked questions about ISO/SAE 21434

  • 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.

References

Sources and status

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.

  • International Organization for Standardization, ISO/SAE 21434:2021, title, first edition dated 31 August 2021, lifecycle and status of the systematic reviewStandard
  • International Organization for Standardization, Cybersecurity in cars, purpose and coverage of the standardStandard
  • International Organization for Standardization, ISO/PAS 5112:2022, guidelines for auditing cybersecurity engineering, with the note that elements of the Cyber Security Management System are based on the processes of ISO/SAE 21434Audit

The information reflects the status of the sources listed as of the review date stated above.

Next step

Claiming secure development is easy. The evidence is the real work.

In the demo, we walk through your case: scope, threats and goals, requirements per phase, supplier requests and the evidence for customers and auditors.

Book a demo

No risk - let's just stay in touch!

Green phone icon for getting in touch.
Phone

+43 732 601 216-0

Green envelope icon representing email.
E-Mail

office@crisam.net

Green paper plane icon representing sending an email.
Newsletter

Register now

CRISAM GRC Software
Darstellung eines Trends im Risikomanagement

CALPANA business consulting GmbH

Blumauerstr. 45-47

4020 Linz, Austria

+43 732 601 216-0 sales@crisam.net

CALPANA business consulting Deutschland GmbH

Paul-Dessau-Str. 1

22761 Hamburg, Germany

+49 (40) 35 98 29 21 sales@crisam.net

CALPANA business consulting GmbH

Blumauerstr. 45-47

4020 Linz, Austria

+43 732 601 216-0 sales@crisam.net

CALPANA business consulting Deutschland GmbH

Paul-Dessau-Str. 1

22761 Hamburg, Germany

+49 (40) 35 98 29 21 sales@crisam.net
CRISAM®
  • What is CRISAM?
  • CRISAM® Method
  • CRISAM® Content
  • Customers
  • Academy
  • Webinars
  • Events
  • CRISAM® Academy
Operational area
  • Integrated Risk Management
  • Information Security Management
  • CRISAM® AI
  • ESG
  • Data Protection Management
  • Audit Management
  • Compliance Management
  • Business Continuity Management
  • Tax Compliance Management System
  • Project Risk Management
  • Legal Register
  • Conflicts of Interest Software
  • CRISAM® Legal Hold Software
Industries
  • Automotive
  • Energy
  • Manufacturing
  • Financial Services
  • Healthcare
  • Retail
  • Real Estate & Construction
  • Broadcasting & Telecommunications
  • Technology
  • Transport & Logistics
More
  • Download Center
  • CRISAM® Academy
  • Webinars
  • CRISAM® Partners
  • Jobs
  • News
  • Trust Center
  • Contact

© 2026 CALPANA business consulting GmbH. All rights reserved.

  • Imprint
  • Privacy
  • Trustcenter
linkedin
xing
Chartis Research Category LeaderChartis RiskTech Quadrant® for GRC Analytics 2025

You complete your registration on the next page. Unsubscribe at any time.

Please enter a valid email address.

Solutions

  • Risk management
  • Information & Cyber Security (ISMS)
  • Internal control system
  • Compliance Management
  • All solutions

Platform

  • Platform overview
  • CRISAM® AI
  • Reporting
  • Standards and frameworks

Resources

  • Success Stories
  • News
  • Webinars
  • Events
  • Careers

Kontakt

  • Österreich+43 732 601 216-0
  • Deutschland+49 40 35 98 29 21
  • E-Mailoffice@crisam.net
Live-Demo buchen

© 2026 CALPANA business consulting GmbH. All rights reserved.

CALPANA business consulting GmbH, Blumauerstraße 45-47, 4020 Linz, Österreich

CALPANA business consulting Deutschland GmbH, Paul-Dessau-Straße 1, 22761 Hamburg, Deutschland

  • Legal notice
  • Privacy
  • Trust Center
  • Cookie settings
  • GGovernanceStrategy & objectives

    • Strategic Management
    • Lean Management Systems
    • GRC Twins
    • Decision Intelligence
    • Policy Management

    Overview

    All solutions on one platform

    View all solutions

    RRiskRisk & resilience

    • Integrated Risk Management (IRM)
    • Project Risk Management
    • Information & Cyber Security (ISMS)
    • Business Continuity Management (BCM)
    • Supply Chain Security

    New: AI governance

    AI Governed Autonomy

    Steer and evidence critical AI decisions without slowing AI down.

    Explore the framework

    CComplianceCompliance & regulation

    • Legal Register
    • Data Protection Management
    • AI Management System
    • ESG Management
    • Internal Control System (ICS)
    • Audit Management
    • Compliance Management
    • Tax Compliance (TCMS)
    • Legal Hold
    • Conflicts of Interest
  • Features

    • CRISAM® platform overview
    • Reporting
    • Integrations
    • CRISAM® Method
    • Content
    • Onboarding & implementation
    • Trust Center

    Regulations & frameworks

    • DORA
    • NIS2
    • ISO/IEC 27001
    • GDPR
    • EU AI Act
    • CSRD
    • TISAX
    • ISO 22301
    All standards and frameworks covered

    Featured

    CRISAM® AI

    AI Risk Intelligence and AI Risk Assistance detect risks early and suggest measures.

    Discover CRISAM® AI
  • Industries

    • Financial services
    • Healthcare
    • Energy & utilities
    • Public sector
    • Automotive
    • Manufacturing
    • Transport & logistics
    • Retail & consumer goods
    • Real estate & construction
    • Broadcasting & telecommunications
    • Technology

    Teams

    • Risk management
    • CFO & CRO
    • CISOs & ISMS owners
    • CIO
    • Compliance
    • Internal audit & ICS
    • Data protection officers
    • ESG & sustainability
    • AI officers

    Customers

    • Success Stories

    Success Story

    Vossloh

    Vossloh

    How Vossloh AG introduced CRISAM® GRC to meet the requirements of IDW PS 340 (revised).

    Read the story
  • About CRISAM®

    • About us
    • Careers
    • Contact

    Partners

    • CRISAM® partners
    • CALPANA consulting
    • Become a partner
  • Resources

    • News
    • Download center
    • Academy

    Events

    • Events
    • Webinars

    Next date

    Corporate Risk Minds Europe 2026

    23 to 24 November 2026, Hotel Okura, Amsterdam

    Book an appointment
EN DE Login
Book a live demo
  • DE
Book a live demo
#RISK Meet CRISAM® at #RISK Expo Europe, ExCeL London, 10 to 11 November, Stand 13. Learn more
Corporate Risk Minds Europe 2026 Meet CRISAM® at Corporate Risk Minds Europe, stand 4, Hotel Okura Amsterdam, 23 to 24 November. Learn more