Two lab technicians in safety glasses testing medical-device equipment, one at a computer and one adjusting an instrument rack

Medical & regulated devices

TISAX (automotive supply chain information security assessment), explained

Last updated:

TISAX (Trusted Information Security Assessment Exchange) runs assessments across three escalating assessment levels (AL1-AL3) and scores individual controls on a 0-5 maturity scale, with the resulting label valid for three years — it is the information security assessment system most automotive OEMs now expect their suppliers to hold, run by the ENX Association and built on the VDA ISA (Information Security Assessment) questionnaire that the German Association of the Automotive Industry (VDA) publishes. Rather than every OEM auditing every supplier separately, TISAX lets a supplier get assessed once and share the resulting label with multiple customers through the ENX Portal — the standard answer, in the automotive supply chain, to "has this vendor's information security actually been checked."

Process rules below come from ENX's own pages and the TISAX Participant Handbook (version 2.8, dated 2025-03-13); control wording comes from the VDA ISA 6.0.3 workbook that ENX hosts. The handbook's screenshots still show ISA version 5, so where the catalogues differ, the catalogue text wins.

Key takeaways

  • Process rules below come from ENX's own pages and the TISAX Participant Handbook (version 2.8, dated 2025-03-13); control wording comes from the VDA ISA 6.0.3 workbook that ENX hosts.
  • One point device makers often miss: TISAX assesses the organization and its locations — how a supplier protects the OEM's information, prototypes and personal data — not the security of the product it ships.
  • Selection — the supplier picks an ENX-contracted audit provider.
  • The assessment level follows from the assessment objectives an OEM asks for, not from a free choice.

What does TISAX actually assess, and why does it exist?

Per ENX's own page, TISAX "was developed to create a standardized and scalable approach to information security in the automotive industry," covering the protection of "design data, production information, customer information, prototypes, and intellectual property" that flows between OEMs and their supplier base. The scheme is maintained through industry collaboration — ENX states it is "continuously developed by automotive manufacturers, suppliers, and audit providers working together in expert groups and committees" — rather than being a fixed standard an outside body wrote once and left alone. The actual assessment content is the separate VDA ISA catalogue, which ENX describes as serving as the requirements framework for assessments; TISAX itself is the governance, process and label-exchange layer sitting on top of that catalogue.

One point device makers often miss: TISAX assesses the organization and its locations — how a supplier protects the OEM's information, prototypes and personal data — not the security of the product it ships. An ECU or telematics unit with weak firmware can come from a site with a perfect TISAX label. Product cybersecurity is a separate track, covered below.

How does a TISAX assessment run, from registration to shared results?

ENX's page describes the process in four stages:

  1. Registration— the supplier registers as a TISAX participant and defines at least one assessment scope: which locations, and which assessment objectives (for example confidentiality of OEM data or protection of prototypes). The handbook (§4.3.2.2) warns that "other TISAX participants only accept assessment results based on the standard scope description," so a custom scope rarely helps.
  2. Selection— the supplier picks an ENX-contracted audit provider. ENX publishes the list of audit providers; per the handbook, "only audit providers that we contracted can conduct TISAX assessments."
  3. Assessment— a self-assessment against the VDA ISA questionnaire plus, depending on the assessment level, an external check.
  4. Exchange— results go into the ENX Portal, where the label is valid for three years and is shared only with partners the supplier selects. ENX states that "results are not publicly available."

Which assessment objective and level does your contract need?

The assessment level follows from the assessment objectives an OEM asks for, not from a free choice. The handbook (§4.3.3.1) states: "There are currently twelve TISAX assessment objectives," and its Table 5 maps each to a level:

Assessment objective (label) What it covers Assessment level
Info high / Info very high Information with high / very high protection needs (selectable only until 31 March 2024) AL 2 / AL 3
Confidential / Strictly confidential Confidentiality, high / very high AL 2 / AL 3
High availability / Very high availability Availability, high / very high AL 2 / AL 3
Proto parts Protection of prototype parts and components AL 3
Proto vehicles Protection of prototype vehicles AL 3
Test vehicles Handling of test vehicles AL 2
Proto events Prototypes during events and film or photo shoots AL 2
Data / Special data GDPR Art. 28 processing / with Art. 9 special categories AL 2 / AL 3

The levels themselves differ in rigor, not in requirements:

  • AL1 — the auditor only checks that a self-assessment exists. The handbook says AL1 results "have a low trust level and are thus not used in TISAX," so no label comes from it.
  • AL2 — "a plausibility check on your self-assessment," with evidence review and an interview, usually remote.
  • AL2.5 — the handbook's name for a full remote assessment instead of the plausibility check; it eases a later upgrade to AL3.
  • AL3 — a full assessment including on-site activities.

"Higher assessment levels always include lower assessment levels," and a scope is assessed at the highest level any of its objectives implies. A supplier that stores prototype ECUs for an OEM therefore lands at AL3 for the whole scope, even if its other objectives are AL2.

How is the result scored: maturity level 3 per question?

Each Information Security and Prototype Protection control is scored on a maturity scale; the handbook's Table 10 quotes the ISA's informal descriptions:

Level Name Meaning in short
0 Incomplete A process is not available, not followed or not suitable
1 Performed An undocumented or incompletely documented process is followed
2 Managed Process followed; documentation and implementation evidence available
3 Established A standard process integrated into the overall system, used sustainably over an extended period
4 Predictable Effectiveness monitored with key figures and limit values
5 Optimizing Continual improvement actively advanced by dedicated resources

Per handbook §5.2.4.2, "the ISA defines a 'target maturity level' of 3 for each question." Scores do not average out: "you can't compensate for a maturity level of '2' for one question with a maturity level of '4' for the other." The overall rule (§5.2.4.5) works on a result score cut back to the target: more than 10% below the maximum gives "minor non-conform," more than 30% below gives "major non-conform."

Inside each control, the ISA 6 workbook separates "must" requirements ("strict requirements without any exemptions") from "should" requirements, which must be implemented unless there is "a valid justification for non-compliance," plus extra requirements for high and very high protection needs. The Data Protection catalogue has no maturity-level column; its sheet uses an "Assessment" column instead.

What happens if the assessment finds gaps?

A minor non-conform result does not end the process. The supplier submits a corrective action plan, and per handbook §5.4.9 implementation periods are capped at three, six or nine months depending on the justification and evidence given, with nine months as the maximum. With a "minor non-conform" overall result, the supplier receives temporary TISAX labels, which "can be valid for up to nine months after the closing meeting of the initial assessment"; a follow-up assessment within that window converts them. The handbook states that temporary labels "are equal to permanent TISAX labels" apart from their shorter validity. A major non-conform result gives no label until the follow-up closes the gaps.

Which VDA ISA controls land on engineering and firmware teams?

Most of the ISA reads like an IT and facilities checklist, but several controls reach into R&D. The table quotes the ISA 6.0.3 workbook (download from the ENX Portal):

ISA 6 control Wording (excerpt) What an engineering team typically shows
1.3.4 Approved software "The types of software such as firmware, operating systems, applications, libraries, device drivers to be managed are determined"; "Software versions and patch levels are known" Inventory of tools and libraries in the build and test environment, with versions
1.6.1 Event reporting "An externally accessible way to report security events exists and is communicated" A published security contact that external parties can use
5.2.2 Environment separation "A segmentation is implemented based on the results of risk analysis" Separate networks and accounts for development, test benches and production
5.2.5 Vulnerabilities Vulnerability information "is gathered … and evaluated (e.g. Common Vulnerability Scoring System CVSS)" A process that tracks CVEs for systems in use and records patch decisions
5.3.1 Security in development For very high protection needs, "the security of purpose built software or significantly customized software is tested (e.g. penetration testing)" Security requirements in specifications; test records for in-house tools
6.1.1 Contractors For high protection needs, "proof is provided that the information security level of the supplier is adequate" TISAX labels or audit evidence from sub-suppliers that receive OEM data
8.x Prototype protection Security areas, visitor management, image recording, transport and storage "in accordance with customer requirements" Locked lab areas for prototype ECUs, camera rules, logged hand-overs

Note the scope of 1.3.4 and 5.2.5: they concern the supplier's own IT systems, but the same SBOM and CVE-tracking habits produce product evidence an OEM asks for under its cybersecurity contract.

Which catalogue applies: ISA 6.0.3 or ISA2027?

Per ENX's portal downloads page, ISA 6.0.3 (dated 2024-04-25) has applied to assessments starting after 1 April 2024. A successor catalogue, ISA2027.1 (dated 2026-07-01), is published on the same page as the basis for "TISAX Assessments ordered in 2027"; "assessments ordered before 2027-01-01 can still be performed with ISA6." The same page states that "the final date to open an initial assessment under ISA6 is March 2027."

ENX's ISA2027 announcement explains the new naming: future catalogues "will generally be published in summer and become effective on January 1st of the following year," and labels keep "a validity period of up to three years." It also lists changes that matter to suppliers: stricter assurance for very high protection needs ("a TISAX label, an equivalent third-party assessment, or an appropriate supplier audit"), prototype controls consolidated into two domains with new requirements on traceability and disposal, and "clarified mappings to ISA/IEC 62443." The order date, not the newest publication, decides which catalogue an assessment uses.

Is TISAX the same as ISO/IEC 27001, IEC 62443 or an R155 CSMS audit?

No. TISAX runs on its own VDA ISA questionnaire rather than certifying against a general management-system standard — it is not the same instrument as ISO/IEC 27001 certification, though organizations that already run an ISO/IEC 27001 ISMS typically find substantial overlap (the workbook lists ISO/IEC 27001:2022 references per control) and can reuse much of that documentation. For industrial-automation products, TISAX does not substitute for IEC 62443-4-1 or IEC 62443-4-2.

For vehicle cybersecurity, the relevant regulation is UN R155, with engineering requirements in ISO/SAE 21434. ENX runs a separate scheme for that: ENX VCS, described as "a harmonized ISO/SAE 21434 based scheme for the independent third party audit of the Vehicle Cybersecurity Management System (V‑CSMS) of cybersecurity relevant automotive suppliers." ENX states that companies seeking ENX VCS audits "must hold a valid TISAX label covering their Information Security Management System (ISMS)," so TISAX becomes the entry ticket, not the substitute. Software update processes sit in a third track again (ISO 24089); regulated sectors such as medical devices show the same split between site security and product security.

Worked example: an ECU supplier with an OEM prototype contract

Synthetic example, not a real company. A 300-person supplier builds body-control ECUs at one German site. An OEM's request for quotation asks for TISAX labels "Strictly confidential" and "Proto parts" before CAD data and pre-series hardware are shared.

  1. LevelBoth objectives imply AL 3 (Table 5), so the scope is AL3 with on-site activities.
  2. CatalogueThe assessment is ordered in November 2026, so ISA 6.0.3 applies; an order in February 2027 would use ISA2027.
  3. Gap runThe quality lead runs the ISA workbook internally. Engineering scores 2 on 5.2.2: the HIL test benches share a flat network with office laptops. Lab access for prototype ECUs (8.x) has no visitor log.
  4. FixesThe team segments the bench network, adds badge access and a visitor book to the prototype lab, and records the library and toolchain versions on build servers for 1.3.4.
  5. ResultThe audit finds one remaining minor gap in event reporting (1.6.1). The overall result is "minor non-conform," temporary labels are issued with a three-month corrective action, and a follow-up converts them.
  6. Product trackSeparately, the OEM's cybersecurity interface agreement asks for an SBOM and vulnerability status for the ECU firmware, which TISAX does not cover.

What are the common pitfalls?

  • Assuming AL2 is enough for prototype work. Proto parts and Proto vehicles imply AL3; check the objectives in the OEM request.
  • Averaging scores. A level 4 on one question does not lift a level 2 on another.
  • Writing policies without using them. Level 3 needs evidence "that the process has been used sustainably and actively over an extended period."
  • Preparing against the wrong catalogue. Check the order date against the 1 January 2027 cutover.
  • Treating the label as product security evidence. OEM cybersecurity contracts under R155 ask for product evidence that TISAX does not produce.
  • Custom scopes. Partners only accept the standard scope.

Where do you start?

  1. Read the OEM request for named assessment objectives, then look them up in Table 5 — the level follows from them.
  2. Run the ISA workbook internally firstAL1 gives no label, but the self-assessment is the input to every higher level.
  3. Target maturity level 3 on every applicable question, with records that show the process in use.
  4. Check your order date against the ISA 6.0.3 / ISA2027 cutoverbefore preparing evidence.
  5. Map ISO/IEC 27001 documentation explicitlyto ISA control numbers rather than submitting it unchanged.

SoftWSP does not perform TISAX assessments. It helps with the product-security evidence that sits next to them: SoftWSP extracts a CycloneDX 1.6 SBOM from a firmware image (see the firmware SBOM guide), matches its components against NVD, CISA KEV, FIRST EPSS and CISA ICS advisories, and drafts a cited report that an engineer reviews before it is sent — useful for the version and vulnerability records behind controls such as 1.3.4 and 5.2.5, and for the SBOM an OEM asks for. See Device & Firmware Security.

This guide draws on ENX's TISAX pages, the TISAX Participant Handbook 2.8 and the VDA ISA 6.0.3 workbook, with NRI Secure and Schellman as secondary explanations. It is not a substitute for the VDA ISA catalogue itself or for compliance or legal advice.

Put this guide to work

Frequently asked questions

What is TISAX, and who runs it?

TISAX (Trusted Information Security Assessment Exchange) is an information security assessment system for the automotive industry, governed by the ENX Association. Per ENX's own page, it "was developed to create a standardized and scalable approach to information security in the automotive industry" and is "continuously developed by automotive manufacturers, suppliers, and audit providers working together in expert groups and committees." The assessment questions themselves come from a separate but linked document: the VDA ISA (Information Security Assessment) catalogue, which ENX maintains and the German Association of the Automotive Industry (VDA) publishes.

What do the AL1, AL2 and AL3 assessment levels mean?

They are escalating levels of verification rigor, not escalating sets of requirements. Per ENX and independent secondary reporting, AL1 is self-assessment only, using the VDA ISA questionnaire, with no external auditor and no TISAX label issued — it functions mainly as an internal gap-finding tool before a real assessment. AL2 adds a remote plausibility check: an ENX-approved auditor reviews the self-assessment's supporting evidence and conducts an interview, typically by video call, and does issue a TISAX label; per Table 5 of ENX's TISAX Participant Handbook, six of the twelve assessment objectives imply AL2. AL3 is a full on-site audit — evidence review, interviews and a physical site visit — reserved for very high protection needs, such as strictly confidential OEM data or unreleased prototypes: the same table maps the Proto parts and Proto vehicles objectives to AL3, while Test vehicles and Proto events imply AL2.

How does the 0-5 maturity scale work, and what score do you need to pass?

Separately from the AL1-3 assessment level, each individual VDA ISA control is scored on a capability-maturity scale from 0 to 5, modeled on CMMI-style process maturity: roughly, 0 (no process exists), 1 (ad-hoc, unstructured), 2 (defined in advance and tracked with assigned responsibility), 3 (standardized, documented and consistently applied, called "Established"), 4 (measured with quantitative metrics), and 5 (subject to continuous, data-driven improvement). The VDA ISA catalogue separates requirements into "must" and "should" categories inside each control. Per ENX's TISAX Participant Handbook (version 2.8), the ISA defines a target maturity level of 3 for each question, a higher score on one question cannot compensate for a lower one on another, and a result score more than 10% below the maximum gives a "minor non-conform" result (more than 30% below: "major non-conform"). The authoritative requirement text lives in the VDA ISA catalogue itself, available from the ENX Portal.

What is ISA2027, and does it replace the current VDA ISA catalogue?

Yes, on a defined timeline. Per ENX's own portal downloads page, the current catalogue is ISA 6.0.3 (dated 2024-04-25), applicable to assessments starting after 1 April 2024. The VDA published a successor catalogue, ISA2027.1, dated 2026-07-01 on the same ENX downloads page, which the page states will be "the basis of TISAX Assessments ordered in 2027"; assessments ordered before 1 January 2027 can still use ISA 6. ENX's own page further states that the final date to open an initial assessment under the ISA 6 catalogue is March 2027, after which ISA2027 becomes the only active version. A supplier commissioning an assessment now should check which catalogue version its specific order date falls under rather than assume the newest-published catalogue automatically applies.

Sources

  1. ENX Association: TISAX overview — governance, VDA ISA basis, process stages, label sharing via the ENX Portal
  2. ENX Portal: Downloads — VDA ISA catalogue versions (ISA 6.0.3, ISA2027.1, redline changes, applicable assessment date ranges)
  3. NRI Secure: What Is TISAX? The Complete Guide to Automotive Information Security Assessments (AL1/AL2/AL3 definitions, 0-5 maturity scale, label validity period)
  4. Schellman: TISAX Self-Assessment Guide (accredited-assessor perspective on the self-assessment and plausibility-check process)
  5. ENX Association: TISAX Participant Handbook, version 2.8 (2025-03-13): assessment objectives, Table 5 assessment levels, target maturity level, result thresholds, temporary labels
  6. VDA ISA 6.0.3 catalogue (Excel), hosted on the ENX Portal: control questions and requirements
  7. ENX Association: ISA page (annual ISA versions, final month for initial assessments under the former version)
  8. ENX Association: ISA2027 news (2026-07-01): versioning by year, annual cycle, supplier and prototype changes
  9. ENX Association: TISAX audit providers
  10. ENX Association: ENX VCS, ISO/SAE 21434-based audit of a supplier's vehicle cybersecurity management system
Was this guide helpful?

In this cluster

TISAX (automotive supply chain information security assessment), explained