TISAX compliance means passing an information security assessment against the VDA ISA catalogue, carried out by an audit provider approved by the ENX Association, and sharing the result with the automotive customers who ask for it. What you get is a set of labels that are valid for three years. If a carmaker or a tier 1 supplier has written to say “we need TISAX”, this is what they are asking for.
What TISAX is and who is behind it
TISAX (Trusted Information Security Assessment Exchange) was created to give the automotive industry a common way of assessing the information security of its partners. It is governed by the ENX Association, which approves the audit providers and oversees the quality of assessments, according to the ENX FAQs. The requirements catalogue, the VDA ISA (Information Security Assessment), is published by the VDA, the German Association of the Automotive Industry.
The current version of the catalogue is 6.0, applicable since 1 April 2024, according to the VDA’s page. ISA2027 was published on 1 July 2026, and the ENX announcement says it applies to all assessments ordered from 1 January 2027. From now on there will be a new catalogue every summer, taking effect on the following 1 January, and each version will be named after the year it becomes mandatory. One of the changes in ISA2027: prototype protection, which had five groups of controls, is reduced to two domains, organisational requirements and physical and environmental security.
What gets assessed falls into three areas: information security, prototype protection and data protection. Each control is rated on a maturity scale from 0 to 5 (incomplete, performed, managed, established, predictable and optimising), and the ENX participant handbook sets a target maturity level of 3 for every question. Put another way: having the control in place is not enough, it has to be established as a process.
An assessment, even if everyone says “TISAX certification”
In procurement and in contracts you will see “TISAX certification” and “TISAX certificate”. Technically, it is neither. The ENX handbook is blunt about it: if you are wondering whether there is a certificate to hang on the wall, there isn’t, because the result is exchanged in a standardised way. What you receive is an assessment report and a set of labels, and only the parties you authorise on the ENX portal can see them.
The labels are what you are really being asked for. Confidential, Strictly confidential, High availability, Proto parts and Data are some of them, and each one comes with a fixed assessment level: AL2, usually reviewed by video call, or AL3, with the auditor on your premises. If a document mentions “Info high” or “Info very high”, those are old names that can no longer be selected.
Who needs it
According to ENX, the catalogue is used by suppliers and service providers in the automotive supply chain, and some participants have made it a mandatory requirement for many of their suppliers. It is not a legal obligation: it comes through the contract, because your customer requires it before sharing sensitive information, parts in development or personal data with you.
In TISAX, everyone who registers is a “participant”. The active participant is the one that is assessed and shares the result; the passive participant is the one that asks for it and receives it. The same company can play both roles: a tier 1 supplier is assessed for its carmaker and, at the same time, requires TISAX from its own suppliers. That is why the request moves down the chain, and why the requirement travels with the customer, not with the country.
The steps, from registration to exchange
ENX sums up the process as registration, assessment and exchange. In practice, those three steps contain a few more:
- Registration on the ENX portal. You register your company as a participant along with at least one assessment scope. The registration fee is based on the locations included and is separate from what the auditor charges you.
- Scope. You decide which locations are included. The ENX standard scope is the recommended one and the one accepted by all participants.
- Self-assessment. You fill in the VDA ISA catalogue control by control, with its maturity level and the evidence behind it. This is the basis the auditor works from.
- Choosing the audit provider. Only those on the official ENX list are valid. You can ask all of them for a quote.
- Assessment. At AL2, the auditor checks the plausibility of your self-assessment, asks for evidence and interviews the people in charge. At AL3, they carry out a full verification at your locations.
- Corrective actions. If there are deviations, you submit a plan. No action may take longer than nine months, and with a minor non-conformity result you receive temporary labels in the meantime.
- Report and labels. The audit provider gives you the official report and, if you pass the assessment, the labels.
- Exchange. You share the result through the ENX portal with the partners you choose.
TISAX and ISO 27001
They are similar, but they are not the same. According to ENX, the VDA ISA stays aligned with ISO/IEC 27001, and ISA2027 revises the mappings to the 2022 version and removes the references to the 2013 one. If you already have a management system based on ISO 27001, a good part of your policies, risk analysis and controls will carry over.
The most practical difference is the scope. The ENX handbook explains it like this: in ISO 27001 the audit scope has to match the scope of your management system, and you define it fairly freely. In TISAX the assessment scope is set for you and can be smaller than that of your management system, but always within it. And an ISO 27001 certificate does not give you labels: labels only come from a TISAX assessment carried out by an audit provider approved by ENX.
As we see it, anyone coming from ISO 27001 has the information security part done and finds the new work in two places: maturity level 3 control by control and, if the customer asks for them, the prototype labels, which have no equivalent in the ISO standard.
Renewal every three years
Final labels are valid for three years, or less if something significant in the scope changes, such as moving a location. They are not extended: to keep them, you go through the process again with a new scope. The handbook advises starting the renewal at least a year before they expire. For your next assessment you will get whichever catalogue is current when you order it, and from 2027 that catalogue changes every year. Labels already issued remain fully valid.
Where we would start
First, ask the customer in writing which labels they need and by when. Without that you don’t know whether you are heading for AL2 or AL3, and a single AL3 label takes the whole assessment to AL3, with the auditor on site. Don’t add labels “just in case”.
Second, an honest self-assessment before calling any auditor, using the catalogue that will apply to you: if you are going to order the assessment in 2027, do it straight away with ISA2027, because doing it with version 6 and repeating it in January is wasted work. Every control below 3 or without evidence is a task with an owner and a date.
That is what the GlobalSuite® TISAX module is for: the VDA ISA self-assessment with each control’s maturity against the target, the scope with the labels each customer asks for by location, the action plan with owners and dates, and the prototype protection evidence kept apart from the rest. If you already manage ISO 27001 in GlobalSuite®, assets, risks and controls are shared. If you would like to see it with your own case, get in touch.
Official sources: TISAX on the ENX website, TISAX participant handbook (version 2.8), TISAX FAQs, approved audit providers, VDA ISA2027 announcement and VDA, information security.





