TISAX® · VDA ISA · ENX
TISAX® Certification for US Suppliers: What Your German Customer Is Asking For
A German OEM or Tier-1 sends you a development contract, and somewhere in the purchasing terms it says "TISAX label required before data exchange". Most US companies have never heard of it. This page explains what TISAX is, which assessment your customer actually expects and how to get there without building a second security program.
What is TISAX?
TISAX stands for Trusted Information Security Assessment Exchange. German car makers created it so that a supplier is assessed once and every OEM accepts the same result, instead of each customer sending its own auditors. The requirements come from the VDA ISA, a catalogue of information security, prototype protection and data protection controls maintained by the German Association of the Automotive Industry.
Buyers and engineers often say "TISAX certification". Formally it is an assessment with a label, not an ISO-style certificate, and ENX expects companies to describe it that way in public. In practice the question behind both terms is the same: can your customer send you confidential drawings, software or prototype parts?
Who needs TISAX certification?
TISAX is not a law. It becomes mandatory through the contract. Typical triggers for US and Asian companies:
- A development or engineering contract with a German OEM or Tier-1 that includes CAD data, specifications or source code.
- Software, AI models or cloud services that process vehicle or customer data for the OEM.
- Prototype parts, test vehicles or pre-launch events at your site.
- An existing supply relationship where the customer has started to block data exchange until a label is available.
Your customer decides which assessment objectives you need, based on how sensitive its data is. Ask for the exact objectives in writing before you register. That one email saves more money than any other step.
Assessment levels and labels
The label your customer asks for determines the assessment level, and the level determines effort and cost.
| Assessment level | How it works | Typical use |
|---|---|---|
| AL1 | Self-assessment only, no external verification | Internal baseline; customers do not accept it for supplier qualification |
| AL2 | Accredited audit provider checks your self-assessment and evidence, usually through remote interviews | High protection need, for example confidential development data |
| AL3 | In-depth assessment, normally with on-site verification | Very high protection need (strictly confidential data) and most prototype protection objectives |
Labels describe what was assessed: information with high or very high protection need, availability, prototype protection (parts, vehicles, events) and data protection. A label always belongs to a defined scope, usually one site. Shared IT, cloud services and remote workers that touch customer data are part of that scope.
The TISAX process step by step
- Clarify objectives. Get the required labels from your customer in writing.
- Register with ENX. Define your scope and assessment objectives in the ENX portal. Plan at least eight weeks before the audit date.
- Self-assessment. Rate every applicable VDA ISA control in the official Excel catalogue. The target is maturity level 3: documented, approved and demonstrably lived.
- Close gaps. Policies alone score nothing. Auditors want evidence that a process runs: access reviews, training records, incident tickets, restore tests.
- Choose an audit provider. Any provider accredited by ENX. Compare at least three quotes, availability and language.
- Assessment. One to five auditor days, depending on level, sites and scope.
- Corrective actions. Findings have to be closed within nine months of the initial assessment.
- Label and sharing. ENX publishes the result, and you share it with your customers in the portal.
Assessments ordered from 1 January 2027 use the new catalogue ISA2027. If your assessment falls into 2027, prepare against the new version.
Timeline and cost
Preparation typically takes three to nine months. With a working ISO 27001 ISMS you are at the short end. Starting from scratch, plan six to nine months. The bottleneck is rarely writing documents. It is producing evidence that the processes run.
Total cost usually lies between EUR 8,000 and EUR 35,000 or more. It has three parts: ENX registration fees, which ENX invoices separately; the audit provider's fee, driven by level, sites and scope; and the remediation work, internal or with consultants, such as rolling out MFA, penetration tests and policy work. A tight, well-designed scope is the strongest lever on all three.
TISAX vs. ISO 27001 vs. SOC 2
| ISO 27001 | SOC 2 | TISAX | |
|---|---|---|---|
| Result | Certificate | Attestation report | Label in the ENX portal |
| Accepted by German OEMs instead of TISAX | No | No | Yes |
| Reusable for TISAX | Large parts of policies, risk process and evidence | Access, change management and encryption evidence | |
| Automotive specifics | None | None | Prototype protection, customer-driven classification, maturity rating |
Our approach for companies with ISO 27001 or SOC 2: map what you already have to the VDA ISA and build only the missing part inside your existing program, with one risk method and one document register.
ISO/SAE 21434 and UNECE R155
If you deliver vehicle software, control units or connected services, your customer will soon ask for a second thing: product cybersecurity. Car makers need a cybersecurity management system under UNECE R155 for type approval, and they pass the requirements of ISO/SAE 21434 down to their suppliers.
The difference in two sentences: TISAX protects your customer's information inside your company. ISO/SAE 21434 protects the vehicle and its software against attacks over its whole life. Many suppliers need both, and both can run on the same management system.
How MLYK helps
Michael Kirsch has worked in information security for 26 years, with stations at BMW, KPMG and Novartis. Since 2017 he has guided more than 100 TISAX and ISO 27001 audits with a 100% pass rate and written two books on TISAX. We work remotely from Prague, in English, and know both sides of the table: what the German customer expects and how a US or Asian company actually runs.
- Gap analysis against the VDA ISA, starting from your ISO 27001 or SOC 2 evidence.
- Scope design and ENX registration that match your customer's objectives.
- Preparation and audit support until the label is published.
Frequently asked questions
Is TISAX mandatory?
Not by law. German OEMs and many Tier-1 suppliers make specific TISAX labels a contractual condition, often before any confidential data is exchanged.
How long is a TISAX label valid?
Three years. There are no annual surveillance audits, so start the re-assessment six to nine months before the label expires.
Can the assessment be done remotely from the US?
AL2 assessments are usually carried out remotely. AL3 normally requires on-site verification at the assessed location, wherever it is.
Can sites in the US or Asia get TISAX labels?
Yes. TISAX is international. You need an eligible scope and an accredited audit provider that covers your location and language.
Does ISO 27001 or SOC 2 replace TISAX?
No. Both give you a strong foundation and reusable evidence, but your customer expects a TISAX result in the ENX portal.
What does TISAX certification cost?
Usually between EUR 8,000 and EUR 35,000 or more in total, depending on assessment level, number of sites, scope and the gaps you need to close.
Sources
- ENX Association: TISAX and TISAX Participant Handbook
- VDA ISA 6 and ISA2027 (applies to assessments ordered from 1 January 2027)
- ISO/SAE 21434:2021 Road vehicles, cybersecurity engineering; UN Regulation No. 155
- More answers: TISAX® FAQ with 76 questions
As of November 2026. Figures for duration and cost are ranges from our projects, not quotes. TISAX® is a registered trademark of the ENX Association. MLYK Consulting s.r.o. is not an accredited TISAX® audit provider.