When an automotive customer asks “do you have a TISAX label?”, many companies send their ISO/IEC 27001 certificate. The request isn’t met. The two frameworks are often mentioned together, even used interchangeably; yet their purposes, assessment methods and outcomes differ. Below we explain the differences and how to prepare for both goals with the same work.
Quick comparison
| Item | ISO/IEC 27001 | TISAX |
|---|---|---|
| What is it? | International standard for an information security management system (ISMS) | An automotive-specific assessment and result-sharing mechanism |
| Governed by | ISO / IEC | ENX Association |
| Reference | Clauses of the standard (4–10) and the 93 controls in Annex A (2022 version) | VDA ISA question catalog |
| Scope | The ISMS scope defined by the organization | Assessment objectives and locations |
| Result | A certificate from an accredited certification body | A label shared on the ENX platform |
| Visibility | The certificate can be shared with anyone | Results are shared with participants the company authorizes |
| Validity | 3-year cycle, annual surveillance audits | Labels generally 3 years |
The key difference: a management system versus a maturity assessment
ISO/IEC 27001 verifies that the organization has established and operates information security as a management system (context, leadership, risk assessment, internal audit, management review, continual improvement). TISAX, on the other hand, assesses the maturity level of the controls in the VDA ISA catalog and industry-specific requirements (e.g. prototype protection). That’s why an ISO 27001 certificate makes TISAX preparation easier but doesn’t automatically mean a TISAX label.
The difference is easy to see at the audit table. An ISO auditor asks about your risk assessment, your Statement of Applicability (SoA), and your internal audit and management review records; you can exclude Annex A controls based on the risk outcome as long as there’s a justification. A TISAX assessor, on the other hand, looks at the maturity level for each question in VDA ISA. The catalog has a scale from 0 to 5, and the target level is usually 3: the process is defined, documented and actually applied. If a procedure is written but there’s no evidence it’s applied, the level drops.
Scope logic also works differently. In ISO 27001, the organization draws the scope itself, and it’s possible to keep that scope narrow. In TISAX, the scope is a standard scope defined by ENX; you choose the assessment objectives (for example, information with high or very high protection needs, prototype parts, data protection) and the locations. A common mistake is limiting the ISO scope to a single office and noticing late that the production site and prototype warehouse also fall within the TISAX scope.
Assessment level
In TISAX, the assessment level (Assessment Level) isn’t determined by you but by the assessment objective. For high protection needs, AL2 applies; at this level, the assessment is mostly done remotely through documents and interviews. For very high protection needs, AL3 applies; it’s a more detailed review done on site. In prototype protection the level varies by objective: according to the table in the ENX participant handbook, the prototype parts (Proto parts) and prototype vehicles (Proto vehicles) objectives are AL3, while test vehicles (Test vehicles) and events and shootings (Proto events) are AL2. Verify the current mapping in the handbook. Which objective is needed is determined by your customer’s request. Don’t open a registration without finding out in writing which label the customer expects.
The process from registration to label roughly works like this: registration and scope definition on the ENX portal, self-assessment against VDA ISA, the initial assessment with an authorized assessment provider, a corrective action plan for any findings and, if needed, a follow-up assessment. The label isn’t published until the findings are closed. On the ISO side, the certification audit runs in two stages: the first stage reviews documentation and readiness, and the second stage reviews that the system is actually operated. After the certificate is issued, a surveillance audit is carried out every year.
In both processes, the most time-consuming part isn’t writing documents. It’s accumulating evidence of implementation. If a management review has been done only once, the claim of “continual improvement” is weak. If an access review was planned but never done, the maturity level doesn’t reach 3. Set the schedule accordingly: after processes are put in place, they should run for at least a few months and produce records.
Which one do you need?
- If your automotive customer requires a TISAX label, an ISO 27001 certificate alone doesn’t meet that request.
- If you serve different industries and want a generally recognized document, ISO/IEC 27001 is more widely recognized.
- If both requests exist, the common controls can be prepared in a single effort.
The type of outcome should also be considered when deciding. An ISO certificate is a document you can show to anyone; it can go into a tender file or on a website. A TISAX label, on the other hand, sits on the ENX portal and is seen only by participants you allow to see it. Showing a TISAX label to a customer outside automotive often means nothing. The reverse is also true.
Roadmap for joint preparation
- Define the scope for both frameworks.
- Use a single risk assessment method and risk register.
- Prepare a control matrix mapping VDA ISA questions to ISO/IEC 27001 Annex A controls.
- Define a single evidence source for each control; don’t produce two separate document sets.
- Handle TISAX-specific requirements such as prototype protection or data protection as a separate work package.
- Rehearse both frameworks at the same time with an internal assessment.
The control matrix is the backbone of this plan. For example, access management is defined with a single procedure; on the ISO side it ties to the access control and identity management controls in Annex A, and on the TISAX side to the relevant VDA ISA questions. The evidence is single too: access review records, account deactivation dates for departed staff, the list of administrator accounts. If two teams produce two separate document sets, a year later they contradict each other.
Common mistakes in preparation
- Filling in policy documents from a template without checking technical implementation. The assessor doesn’t want to see the sentence “MFA is mandatory” but the list of accounts left without MFA.
- Leaving prototype protection requirements to the information security team. Physical security, visitor management, photography bans and transport processes concern production and logistics too.
- Treating suppliers and external service providers as out of scope. Cloud services, the IT outsourcing firm and courier processes are questioned in both frameworks.
- Skipping the internal assessment and going straight to the formal assessment. The time to fix findings is the item that stretches the schedule the most.
In the TISAX process, registration is done on the ENX portal, and the assessment is carried out only with assessment providers authorized by ENX. Verify the current version of the VDA ISA catalog and the assessment rules in ENX’s own publications; the catalog is updated over time.
Eretek doesn’t issue ISO/IEC 27001 certificates or TISAX labels; it provides preparation and technical consulting.
For details, see our ISO 27001 Consulting and ISMS Setup and TISAX Consulting pages; for the document set, Information Security Policies and Procedures; and for ongoing follow-up, vCISO.