Cybersecurity Compliance Supply chain SMEs

TISAX for automotive suppliers: what it is, what is assessed and how to prepare

Quick summary

Summary

  • TISAX is the mechanism the automotive industry uses to share the results of information security assessments. ENX Association runs it and it is based on the VDA ISA catalogue, published by the VDA, the German Association of the Automotive Industry.
  • The outcome is labels with an assessment level (AL 2 or AL 3) that you share with your customers from the ENX portal. An ISO/IEC 27001 certificate does not replace them.
  • What is assessed depends on the assessment objectives you declare: confidential information, availability, prototypes or data protection. Each one carries a minimum level.
  • A label is valid for three years. The ENX handbook recommends starting the renewal at least a year ahead.
  • VDA ISA2027 has been published and becomes mandatory for new assessments and renewals from 2027. Valid labels keep their validity. Confirm the transition rules with your audit provider before you order anything.
  • Preparing the scope and the evidence before requesting the assessment reduces the non-conformities that could have been avoided.

Status as of 18 November 2026.

What TISAX is

TISAX stands for Trusted Information Security Assessment Exchange. It started in the German automotive industry so that a supplier would not have to go through a different security audit for every customer: it is assessed once against a common standard and the result is shared with whoever the supplier authorises. The VDA publishes the catalogue of requirements, the VDA ISA, and ENX Association runs the portal where scopes are registered and results are exchanged.

It is not an ISO certificate and no certification body issues it. The assessment is carried out by an audit provider approved by ENX, which delivers a report, and the result is recorded in the portal as labels that can be shared with customers. The catalogue builds on ISO/IEC 27001, so a management system already built on that standard helps a great deal, but an ISO/IEC 27001 certificate is not equivalent to a TISAX label.

Will you be asked for it?

No law requires TISAX. It is asked for by the manufacturers that have adopted it as a procurement requirement and, by extension, by some first-tier suppliers further down their own chain. There is no public list of who requires it, so the way to find out is to ask each customer in writing for three things: which assessment objectives they need, at what level and by what date.

Galicia has an automotive cluster with a manufacturing plant in Vigo and suppliers spread along the Atlantic corridor. Since each customer decides whether to ask for it and with what scope, it cannot be assumed that a Galician supplier is subject to it or at which level. If it has been mentioned in passing, it is worth clarifying before it shows up as a condition of an order.

What is assessed: the assessment objectives

When you register the scope you choose one or more assessment objectives, and each objective has a minimum level attached. The ENX participant handbook (version 2.8, dated 13 March 2025) lists twelve. Two of them, “Info high” and “Info very high”, can no longer be selected since April 2024 and are replaced by “Confidential” and “Strictly confidential”. These remain:

GroupAssessment objective (ENX name)Level
InformationConfidentialAL 2
InformationStrictly confidentialAL 3
AvailabilityHigh availabilityAL 2
AvailabilityVery high availabilityAL 3
PrototypesProto partsAL 3
PrototypesProto vehiclesAL 3
PrototypesTest vehiclesAL 2
PrototypesProto eventsAL 2
Data protectionDataAL 2
Data protectionSpecial dataAL 3

Declare only the objectives your customer needs. Every additional objective widens what has to be demonstrated, and with it the time and the cost. If the customer asks for a level 3 objective, such as strictly confidential information, the assessment of that objective will be at level 3.

AL 2, AL 2.5 and AL 3: what the auditor does

  • AL 2. The auditor carries out a plausibility check of your self-assessment: reviews evidence and interviews the person responsible for information security, normally by web conference. An on-site visit is optional and has to be requested.
  • AL 2.5. An optional variant that is formally evaluated as AL 2 but carried out as a full remote verification, without the on-site activities. It allows a later upgrade to AL 3 with moderate effort.
  • AL 3. A comprehensive verification: documents and evidence, planned and unplanned interviews, observation of local conditions and processes, and an on-site visit. If going on site is temporarily impossible, a video-supported remote assessment is allowed, which is recorded as a minor non-conformity and requires an on-site follow-up assessment.

The handbook sums up the difference with two verbs: in AL 2 the auditor checks that something exists and looks right, and in AL 3 that it is what it claims to be. A higher level includes the requirements of the lower one. The results of an AL 2 assessment cannot be used as a basis to upgrade to AL 3, which is why AL 2.5 exists as an option.

The VDA ISA is the spreadsheet with the requirements that are assessed. It is organised in modules: information security, prototype protection and data protection. Until now the version in force was 6.0.3, published by ENX in April 2024.

In July 2026 the VDA published the next generation of the catalogue, which is no longer numbered by version and is named by year instead: VDA ISA2027. DQS, an audit provider, published an analysis of it that same month. Its main points:

  • ISA2027 becomes mandatory from early 2027 for initial assessments and renewals.
  • Valid labels keep their validity period. ISA2027 starts to matter at your next assessment or renewal.
  • The information security module has 43 revised controls, most of them to clarify the wording, and a few requirements move from recommendation to obligation. Examples it cites: defining and testing a crisis plan, and fixing vulnerabilities within a defined timeframe.
  • Prototype protection is reduced to two labels: Prototype Protection Basic (AL 2) and Prototype Protection Facilities (AL 3).
What still needs confirming

DQS warned that its articles were preliminary because ENX had not yet published the document that sets the transition rules, the TISAX ACAR. I have also not been able to check how the current prototype labels map to the new ones. Before ordering an assessment, ask your audit provider which version of the catalogue applies to your order.

The process step by step

  1. Registration on the ENX portal. You create the account, provide the participant details and accept the general terms. This is the contract with ENX.
  2. Scope registration. You give the name, the locations and the assessment objectives. The scope of the assessment must match the scope of your information security management system. ENX validates it and assigns the participant ID and the Scope ID.
  3. Choosing the audit provider. You request quotes from providers approved by ENX. The Scope ID is required to order the assessment. This is the second contract.
  4. Assessment. At level 2 or 3 depending on the objectives, with a report that records the result.
  5. Closing non-conformities. If the overall result is “minor non-conformity”, a temporary label is issued. Non-conformities must be fixed within a maximum of nine months from the closing meeting.
  6. Sharing the result. Once the provider has submitted the result and the fee has been paid, the scope moves to “Active” status and you can share it with your customers from the portal.
  7. Renewal every three years.

Label validity and renewal

In general a label is valid for three years from the end of the assessment. It can be shorter if the scope changes significantly, for example with a relocation or a new location. A temporary label lasts up to nine months from the closing meeting of the initial assessment. If the non-conformities are not fixed within that period, no label is issued and a new initial assessment has to be carried out.

To renew you must register a new scope before approaching the provider, because it can only start an assessment with a new Scope ID. The handbook recommends starting at least a year before the labels expire.

How to prepare without overspending

  1. Talk to your customer. Assessment objectives, level, date and whether they accept the scope you propose. Ask for it in writing.
  2. Define the scope with judgement. The sites, processes and systems that touch the customer’s information. A smaller scope is cheaper, but it has to match your management system and cover what the customer expects.
  3. Self-assess with the official catalogue before you contract. At AL 2 the self-assessment is the basis of the auditor’s check, so scoring each control with its evidence is work that is not wasted.
  4. Close the gaps in order. Policies and roles, access management, logging, vulnerability management, backups, continuity and supplier management. The requirements that ISA2027 tightens, such as a tested crisis plan and timeframes for fixing vulnerabilities, are worth having in place even if your assessment falls under the previous version.
  5. Gather evidence an auditor can see. Approved and communicated policies, access lists with their review, logs, test reports, minutes.
  6. Choose the level with the future in mind. If you are likely to be asked for AL 3 later, AL 2.5 lets you upgrade with little effort, and a regular AL 2 assessment does not.

Common mistakes

  • Starting when the customer’s deadline arrives. You have to register the scope, request quotes, be assessed and close findings. With a renewal you also have to start before the label expires.
  • A scope that does not match the management system or that the customer does not accept. It is discovered late and forces you to redo the registration.
  • Declaring objectives nobody asked for. Each one adds requirements.
  • Treating the self-assessment as paperwork. At AL 2 it is the basis of the auditor’s work, and an optimistic self-assessment shows as soon as the evidence is requested.
  • Forgetting your own suppliers. The catalogue has supplier management requirements, and ISA2027 broadens “IT suppliers” to “IT service providers”. If you do not have a supplier assessment process, that part is left without evidence. The Basic VRM Form maps its questions to TISAX (VDA ISA), among other frameworks.
  • Letting the label expire. Renewing needs a new Scope ID and provider time.

Frequently asked questions

Is TISAX mandatory?

No law requires it. It is a contractual requirement set by each customer. If a customer asks for it, you must meet it to keep working with them, but another customer may not ask for it.

Does my ISO/IEC 27001 certificate count?

It does not replace the TISAX label, which is the result of an assessment against the VDA ISA catalogue. It helps because the catalogue builds on that standard and many controls will already be in place, but the assessment still has to be carried out.

How much does it cost?

There is no single price. There are ENX fees and the audit provider’s fee, which depends on the scope, the level, the number of locations and the objectives. Request written quotes from several approved providers on the same scope so that they are comparable. To understand where the price of an audit in general comes from, there is the article on how much a cybersecurity audit costs.

How long does it take?

It depends on your starting point, the scope and the audit provider’s calendar. One data point from the handbook: non-conformities must be fixed within a maximum of nine months from the closing meeting. With that in mind, plan in months rather than weeks, and start before the deadline your customer gives you.

I already have a label. What does ISA2027 change for me?

According to DQS, your label keeps its validity. ISA2027 will be the catalogue for your next assessment or renewal, so it is worth starting to close the differences beforehand. Confirm with your audit provider which version will apply when you place the order.

Can ACBSEC carry out my TISAX assessment?

The official assessment is carried out by an audit provider approved by ENX. The groundwork, which consists of the gap analysis against the catalogue, defining the scope and preparing the evidence, is the kind of service I offer as part of the cybersecurity audit, which is not a certification audit.

Any questions, I am here. No fluff.

Sources

ENXTISAX Participant Handbook, version 2.8, 13 March 2025 · TISAX at ENX · ENX frequently asked questions · ENX news

VDA ISA catalogueVDA · information security · DQS · ISA 2027: what is changing (17 July 2026) · DQS · ISA 2027 information security module, control by control (21 July 2026)

Content last reviewed on 18 November 2026, using the sources consulted that day. The ENX handbook cited is version 2.8; a newer one may exist. The transition rules to ISA2027 were pending an ENX document when the cited analyses were published: confirm them with your audit provider.

Keep reading

Has your customer asked you for TISAX?

Before you order the assessment, it helps to know where you stand

I do the groundwork: a gap analysis against the VDA ISA catalogue, the scope and the objectives you really need, a closure plan and the evidence in order. The official assessment is carried out by an audit provider approved by ENX.

Tell me what your customer asked for and where you are, and I will tell you what I would do. I answer personally, no fluff and no strings attached.

Let's talk about your case →