TISAX Preparation Guide: VDA ISA, Scope and Evidence

If TISAX preparation starts with the wrong objective, the wrong scope or the wrong ISA version, months are lost. Steps, evidence and pitfalls from the customer request to the label.
Technical summary
Technology
TISAX, VDA ISA 6 / ISA2027
Topic
Assessment preparation
Level
Start
In this article9 sections

A customer has asked you for a “TISAX label”, and all you have is an email. This is where most preparation goes wrong: work starts without asking about the objective, the scope is drawn by guesswork, and nobody checks which ISA version you’ll be assessed against. Then months of work turn out to have been done for an objective the customer didn’t want. Which assessment objectives are required, which locations are in scope, and which ISA version will the assessment use? Don’t write a single policy until these three questions are answered in writing.

What TISAX is, and what it isn’t

TISAX (Trusted Information Security Assessment Exchange) is an assessment and result-sharing mechanism based on VDA’s information security question catalog (VDA ISA) and run by ENX. It isn’t a certificate; it’s a system for sharing the result (label) of an assessment carried out by ENX-approved assessment providers with customers. For how it relates to ISO 27001, see the differences between TISAX and ISO 27001 guide.

The practical consequence of this distinction: the label isn’t given to “your company” but to a specific scope and specific assessment objectives. On the ENX portal, the customer sees for which objectives, at which location and with what result you were assessed. A label obtained for the wrong objective means, in the customer’s eyes, no label.

Step 1 — Clarify the customer request in writing

Ask the customer for the following in writing: the required assessment objectives (high or very high protection needs for information security, prototype protection objectives, data protection), the target date and which location(s) must be in scope. The objectives determine the assessment level (AL2 or AL3) and therefore the depth of preparation.

Assessment level Method (summary) Typical use
AL2 Plausibility check of the self-assessment and evidence, mostly through remote interviews High protection needs
AL3 Comprehensive review, on-site assessment Very high protection needs, Proto parts and Proto vehicles

A situation you may run into is the request arriving from the purchasing department as a vague sentence: “Do you have TISAX?” That sentence isn’t a specification. Ask the customer’s information security or supplier management function for the list of objectives; most OEMs already define this in the supplier portal or a contract annex. If prototype objectives are requested, the work goes far beyond office IT: security areas, visitor management, photography rules and transport processes come into play.

Step 2 — Determine the scope and version

The TISAX assessment scope is usually set according to ENX’s standard scope definition and includes all relevant processes at the selected locations. A note on the version: assessments ordered during 2026 are carried out with VDA ISA 6, and those ordered on or after 1 January 2027 with ISA2027, published by VDA on 1 July 2026. For details, see the ISA2027 transition guide.

When the standard scope says “all relevant processes”, areas many organizations count as outside come in: the production network, a shared server room, the identity system managed by central IT, machine suppliers who do remote maintenance. If a location is in scope, everything that touches information at that location is in scope. Draw the line from the network diagram and data flows, not from the org chart.

The version timeline also directly affects planning. If you start the gap analysis without deciding when you’ll place the order, you risk working with the wrong catalog. If the preparation period runs into the end of the year, take the ISA2027 changes into account from the start.

Step 3 — Gap analysis and maturity measurement

VDA ISA defines maturity levels (0–5) for each control; the general target level in TISAX assessments is 3 (established process). In the gap analysis, three questions are answered for each control: Who’s responsible? How is it applied? What evidence can show it? Filling in the self-assessment optimistically is the most common problem; a control with no evidence shouldn’t be marked as 3.

Read level 3 like this in practice: the process is written, communicated to the people concerned, applied, and there’s a record that it’s applied. An access review with a written policy but no records isn’t level 3. Nor is a backup process that has records but lives only in one person’s head. In the gap analysis, sit down with the owner who can show at least one concrete piece of evidence (screenshot, record, report) for each control on the spot; an answer of “we have it, I’ll find it” should be counted as a gap.

Step 4 — Maturing: processes, documents, technical controls

  • ISMS framework: Policy, roles, risk management, document management.
  • Identity and access: User lifecycle, privileged access, MFA, periodic review.
  • Operations: Backup, malware protection, patching, logging, network segregation.
  • Suppliers: Assessment, confidentiality agreements, supply chain requirements.
  • Incidents and continuity: Incident management, business continuity, crisis communication.
  • Prototype protection (if relevant): Security areas, access, transport, tests and events, photography and visitor rules.

The most time-consuming work at this stage isn’t writing documents; it’s getting technical controls to actually work. Closing a leaver’s account the same day, separating admin accounts from everyday accounts, making backups independent of the domain and restorable, and putting remote maintenance access through a request–approval–record flow: these take weeks. You can write the policy in a day. You can’t build the practice in a day.

Our suggested order: identity and access first, then backup and logging, then supplier and incident processes. If there’s a prototype protection objective, physical measures (badge access, cameras, enclosed areas, cover and transport rules) should be started in parallel, as they require purchasing and construction time.

Step 5 — Evidence file and rehearsal

Before the assessment, evidence is indexed for each control: policy, procedure, system screen, record. Then a rehearsal is held in the assessment format. Gathering evidence in one place, such as SharePoint, noticeably shortens the assessment; see SharePoint evidence management.

Name the evidence folders by ISA control number; make each item’s date, owner and validity period visible. In the rehearsal, give the assessor role to someone from outside the organization, or at least someone distant from the topic. The control owner must be able to open and explain their own evidence in five minutes. If they can’t, they won’t be able to on assessment day either.

Step 6 — Assessment and corrective actions

The assessment provider reports findings; a corrective action plan is prepared for the findings, carried out within the period set by the provider and verified with a follow-up assessment. Labels are published on the ENX portal and shared with the customer. According to ENX, labels are valid for a maximum of three years.

In the corrective action plan, write the root cause, action, owner and date for each finding. “The procedure will be updated” isn’t an action on its own; a record showing the procedure is applied will also be requested. The work doesn’t end once the label is obtained: controls continuing to work throughout the three-year period is the foundation of the renewal assessment.

The most common preparation mistakes

  1. Starting work without knowing the objective the customer wants.
  2. Filling in the self-assessment with high scores and no evidence.
  3. Assuming the production network and supplier maintenance access are out of scope.
  4. Leaving physical controls in prototype areas to the last week.
  5. Booking the assessment before the maturing work is complete.

A short pre-preparation checklist:

  • Has a written list of objectives and a target date been received from the customer?
  • Have the in-scope locations and the systems at those locations been marked on the network diagram?
  • Has the applicable ISA version been determined from the order date?
  • Has an owner been assigned to each control, and can at least one piece of evidence be shown?
  • Has a rehearsal been held and have the gaps it found been closed?

Eretek isn’t an ENX-approved TISAX assessment provider and doesn’t issue TISAX labels. This guide is for general information; ENX’s official documents should be taken as the basis for current rules.

Frequently asked questions

How do we choose an assessment provider?

From the list of approved assessment providers published by ENX, based on language, location, schedule and proposal terms. Your consultant must not have an independence conflict with the assessment provider.

When does the label become visible to the customer?

Once the assessment is complete and the results are published on the ENX portal, the customer can see them according to the sharing permission you give.

We have several locations; do they all need to be assessed?

It depends on the customer’s request and at which locations customer information is processed. The scope is set together with ENX rules and the customer’s requirements.

To plan your preparation, take a look at our TISAX Consulting and Assessment Preparation service, or, as a first step, the VDA ISA gap analysis.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles