GUIDE · MANUFACTURING OT

TISAX step by step: from assessment level to label

This guide walks you through the TISAX route, the information security assessment scheme used across the automotive supply chain. By the end you will know how to work out which level is being asked of you, how to define the scope, which mistakes to avoid, and what the first step is to prepare for the assessment.

Updated october 2026
6 min read
Altovar Technical Editorial Team

1. What TISAX is and why it is requested

TISAX is an information security assessment scheme created for the automotive supply chain. It allows a company to demonstrate to its customers, through an assessment carried out by an independent body, that its processes and systems protect the data shared in projects. Instead of subjecting every supplier to different questionnaires, the sector uses a common reference, so the same result can be read by several customers.

Suppliers are often asked for it because their customers must demonstrate the security of the supply chain. If you work on components, designs or technical data for a manufacturer, the request is likely to arrive in the contract or during a selection process. Check with the customer which assessment level and which scope they expect, because the requirement varies greatly from one manufacturer to another.

2. Before you start

Before you move, clarify three things. The first is the assessment level required by the customer: the levels increase in depth and rigour, and the wrong level wastes time and money. The second is the scope, that is, which sites, processes and systems are included in the assessment. The third is who in your team holds the information, because the work requires real documents, procedures and records, not just verbal statements.

  • Assessment level required in writing by the customer
  • List of sites, processes and systems involved
  • An internal manager with authority over the processes
  • List of data shared with customers and its classification

3. The route, step by step

The route is linear in substance, although each step takes time. The safest method is not to skip the self-assessment, because it highlights gaps before the assessor finds them. The steps are these, to be done in order and with intermediate checks that remain documented. Do not skip any step: each phase provides the elements for the next. Even a short phase deserves a written check.

Do not assume that the time required is linear. Technical corrections may require purchases or changes to systems, and the assessor may ask for clarifications. Ask the assessor and the customer what the timelines and procedural costs are, because they vary widely depending on the scope and the starting position, and get the forecast in writing.

  1. Ask the customer for the assessment level and the exact scope.
  2. Carry out a first self-assessment of the scope, control by control.
  3. Reconstruct the evidence: procedures, records, access and training.
  4. Identify the gaps and plan the corrections, with owners and deadlines.
  5. Select an independent assessor, verifying their credentials.
  6. Take part in the assessment, answering with documents and not only with words.
  7. Obtain the result and share it with customers through the channel the scheme provides.

4. The most common mistakes

The first mistake is defining the scope too narrowly, excluding a site or system that nevertheless handles customer data. The assessor will notice, and the result will not cover what is needed. The second is preparing documents that describe processes as they should be, without anyone actually following them. The third is treating the certification of your IT provider as your own, when the scheme concerns your organisation and the processes that run it.

A fourth mistake is treating TISAX as a project with an end date. The label has a validity period, and customers expect processes to remain in order between one assessment and the next. Appoint a manager who updates the evidence and reports changes, such as new systems, new suppliers or new sites, before they become a problem. Ask your customer whether they consider a corrective plan with intermediate dates acceptable.

5. How to maintain the result

The most useful work for the future is to make the evidence routine. Up-to-date procedures, access records, periodic checks and staff training must be part of day-to-day work, not a rush before the assessment. When a scope, a customer or a system changes, assess straight away whether the label still holds or whether an update is needed, and tell the customer without waiting for them to ask.

A practical way to maintain the result is an internal review, planned with the same care as the assessment. At a frequency set by the manager, a small group re-examines the main evidence, checks that procedures are genuinely used and reports gaps. The result is a record of continuous controls, which makes it simpler to answer each new customer request.

6. How to get started

This week, ask your customer or purchasing manager in writing which assessment level and which scope they expect. If they do not know, ask for the reference of their supplier security requirement. Without this answer you cannot plan anything seriously, nor estimate costs and timelines. If the customer cannot answer, it is a signal to raise in the commercial conversation.

Then choose an internal manager and have them do a first review of the list of processes and systems involved. The result will be a map of the scope and a list of open questions. With that map you can decide whether to carry out the self-assessment in-house or with a consultant, and how much time to dedicate to it in the following weeks. Involve those who run the systems too, because they know where the data actually sits.

Frequently Asked Questions

Is TISAX a standard or a label?

The scheme is based on information security controls defined for the automotive sector and concludes with an assessment. The result is made available as a label that customers can verify. It is not a law, but many manufacturers require it from their suppliers. Ask the customer whether they expect the full scheme or only a specific level.

How long does the route take?

It depends on the required level, the scope, the initial state of security and the availability of people. A reliable estimate cannot be given without a self-assessment. Ask the assessor and the customer to state in writing the phases and the points where the time could extend.

Can I do everything myself?

The self-assessment can be done in-house, but the assessment itself must be carried out by an independent body. A consultant can help you interpret the controls and prepare the evidence, but cannot replace the assessment. Choose whoever helps you based on their experience in the automotive sector.

Does the scope include my suppliers' suppliers?

It depends on how the data is handled. If one of your sub-suppliers processes customer data, the matter must be considered within the scope or in the controls over the chain. Check with the customer how they want sub-suppliers to be treated and document the agreements with them.

What changes if I buy a new system?

A system change can alter the scope and the evidence. Assess whether the new system handles data covered by the assessment and whether the controls still hold. Update the list of systems and inform the customer when the change affects shared data, before putting it into production.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →