TISAX Preparation Process and Technical Evidence

How do you prepare for a TISAX assessment? Process steps, the difference between assessment objectives and levels, VDA ISA and examples of technical evidence requested in the assessment.
In this article5 sections

Where companies get stuck most in TISAX preparation isn’t writing policies but showing evidence of implementation. In the automotive industry, an OEM or large supplier may ask its business partners to prove their information security level through TISAX (Trusted Information Security Assessment Exchange). TISAX is an assessment and result-sharing mechanism managed by the ENX Association; the assessment is based on the VDA ISA (Information Security Assessment) question catalog. Below we explain the process and, in particular, technical evidence preparation.

Note: Eretek doesn’t issue TISAX labels. Assessments are carried out by assessment providers accredited by ENX; this guide focuses on the preparation process.

Main steps of the process

  1. Clarify the requirement: Find out in writing which assessment objectives (e.g. information confidentiality, availability, prototype protection, data protection) and which level your customer requires.
  2. Define the scope: The locations and processes to be assessed.
  3. Registration on the ENX portal: The company and the assessment are registered, and an assessment provider is selected.
  4. Self-assessment and gap analysis: Current maturity is scored against the VDA ISA question catalog.
  5. Improvement: Missing controls are implemented and evidence is prepared.
  6. Assessment: Depending on the selected level, a document review, remote or on-site assessment is carried out.
  7. Corrective actions and result: Findings are closed; labels are shared on the ENX platform. According to the ENX participant handbook, the assessment result is valid for three years.

Mistakes made in the first two steps

The most expensive mistake is assuming what the customer wants based on verbal information. A “we need TISAX” request says nothing on its own; if the objective, level and location don’t come in writing, either work is done for a scope wider than necessary or the label the customer expects doesn’t come out at the end of the assessment. Keep the request letter from purchasing or quality and the wording on the customer’s supplier portal.

In scoping, what’s often forgotten is every place the information is processed. Customer drawings may be not only in the engineering department but also in the quality office, on a terminal on the production floor, in a cloud-based shared folder and on a supplier engineer’s laptop. Draw the scope boundary by looking at the information flow, not the org chart.

Assessment levels

In TISAX, assessment levels (Assessment Level) determine the depth of the review. AL1 is a self-assessment and doesn’t provide a label; AL2 is generally based on document review and interviews, and AL3 on a comprehensive on-site review. Which level is required depends on the protection needs of the information processed and the customer’s request.

As the level rises, the auditor’s question changes from “does this control exist?” to “show me that this control works.” At AL2, the assessment mostly proceeds through a plausibility check of the self-assessment, evidence review and interviews; the assessment provider decides which evidence counts as sufficient. At AL3, the auditor may ask you to open the screen and show that the account of a recently departed employee really is closed. Prepare accordingly. Documents alone aren’t enough.

Prototype protection objectives also cover non-IT areas such as physical security, visitor management, photography rules and prototype transport processes. If these objectives are required, facility management and logistics teams should be included in the preparation from the start.

Changes with VDA ISA 6

Version 6 of VDA ISA brought the catalog more in line with the ISO/IEC 27001:2022 structure, and ENX announced changes to the label structure along with it. ENX publications should be taken as the basis for the current label list and transition rules.

The practical consequence: don’t keep working on a self-assessment file made with an old catalog version. Confirm at registration which catalog version the assessment provider will use, and do the gap analysis on that version.

Technical evidence frequently requested in the audit

Control area Example evidence
Asset management Up-to-date hardware, software and information asset inventory, with owners
Access control Access request and approval records, periodic access review minutes, MFA configuration
Identity management Onboarding/offboarding processes and records of closed accounts
Logging and monitoring Log sources, retention period, records showing that alarms were reviewed
Backup Backup policy, record of the latest restore test
Vulnerability management Scan reports, patching times, exception records
Network security Network diagram, segmentation, firewall rule review record
Supplier management Supplier assessments and security clauses in contracts
Incident management Incident procedure, incident records, exercise report

Where evidence falls short

Inventory: A list kept in Excel and last updated a year ago doesn’t count as evidence in an audit. You need to show that the inventory is fed from a source (endpoint management, Active Directory, a network discovery tool) and that it has owners. Being unable to find a device picked at random by the auditor in the inventory is a typical finding.

Logging: Saying “we have a SIEM” isn’t enough. Which sources send logs, how long they’re retained, and who reviewed an alarm and when must be recorded. Logs nobody looks at produce no evidence.

Backup: The auditor asks less about the backup policy and more about the date, scope and result of the latest restore test. An untested backup isn’t a backup.

Firewall: Most companies have no record showing the rule base is reviewed periodically. Every rule should have an owner and a business justification, and unused rules should be removed with the date noted.

Practical recommendations

  • Prepare an evidence matrix that answers up front, for each control, the question “which document or screen will we show?”
  • Fix the implementation first instead of writing policies; the auditor wants to see evidence of implementation.
  • For manufacturing suppliers, access to the production network and vendor maintenance connections are frequently questioned.
  • If there’s also an ISO/IEC 27001 goal, address the common controls in a single effort.

An evidence matrix is a simple table: catalog question, control owner, current state, name and location of the evidence, last update date. This table is the main list in the team’s hands on assessment day; when the auditor asks a question, it’s clear who opens which screen. Most of the preparation time goes into filling in this table.

On the production side, machine vendors’ remote maintenance connections are a separate topic. A machine connecting through its own modem or a permanently open remote desktop tool is an uncontrolled entry into the in-scope network. Inventory these connections, move them to a remote access point with MFA and logging, and keep them closed when not in use.

There’s also the human side. In interviews, the auditor talks not only to the IT manager but also to HR, purchasing and production managers. These people need to be able to explain in their own words the confidentiality commitment in onboarding and the security check in supplier selection. If the person who wrote the procedure and the person who applies it are different, do a short rehearsal before the interview; a manager who can’t explain their own process lowers the value of a well-written document.

Time is granted for findings after the assessment, but don’t plan to use that time to close major gaps. Leave the remaining time for small fixes.

To plan the preparation process together, see our TISAX Consulting page; for an ISO goal, ISO 27001 Consulting and ISMS Setup; for the risk side, Risk Assessment; and for logging evidence, SIEM and Security Logs.

Support

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

Contact form
[email protected]

Eretek Cybersecurity

Firewall, VPN, endpoint security and threat prevention. We reduce the attack surface and measure and report the risks.

Knowledge Center

Other articles