TISAX vs ISO 27001: Differences and Shared Controls

ISO 27001 is an ISMS requirements standard; TISAX is an assessment and result-sharing mechanism specific to the automotive supply chain. The differences, shared controls and how to run both as one program.
In this article6 sections

“We have ISO 27001, we don’t need TISAX” is something you might hear from automotive suppliers; when a customer asks for a TISAX assessment, this assumption doesn’t hold. The two frameworks cover the same topics but don’t do the same job: one is a management system requirements standard, the other an assessment and result-sharing mechanism specific to the automotive sector. Most of the controls are shared. An organization that doesn’t know the difference does the same work twice.

Key differences

Topic ISO/IEC 27001 TISAX
Nature International ISMS requirements standard VDA ISA-based assessment and result-sharing mechanism (ENX)
Result Certificate issued by an accredited body Label shared on the ENX portal
Who sets the scope? The organization (based on context and interested parties) Largely the customer request and ENX’s scope definition
Assessment logic Conformity with requirements and effectiveness Control-based maturity level (target usually 3)
Sector-specific topics None Prototype protection, data protection objectives, automotive supply chain
Validity Usually a three-year certification cycle with annual surveillance Label valid for up to three years
Sharing the result Certificate and scope statement Controlled sharing with the customer via ENX

The most important row in the table is scope. In ISO 27001, the organization defines and justifies the scope; that’s why narrowly scoped certificates such as “head office and IT department only” are common in the field. In TISAX, the scope is largely determined by the customer’s request and ENX’s standard scope definition; relevant processes at the selected location can’t be left out. A narrowly scoped ISO 27001 certificate therefore contributes less than expected to TISAX preparation.

Shared controls

The information security section of VDA ISA largely overlaps with ISO/IEC 27001 Annex A; ENX has announced that with ISA2027 the mappings were reviewed against ISO/IEC 27001:2022. Risk management, asset management, access control, cryptography, operations security, supplier relationships, incident management and business continuity are core topics in both frameworks. That’s why it’s possible to serve both frameworks with a single document set and a single evidence library.

The overlap is mostly at the level of “the same evidence”, not just “the same heading”. An access review record, a backup restore test report or a supplier assessment form is shown the same way in both assessments. The difference is that in TISAX this evidence must also show the process is established, meaning it’s repeated regularly. A single sample record may pass without questions in an ISO 27001 audit; in a maturity assessment, the question “Is this done every quarter?” will come.

Where TISAX goes beyond ISO 27001

  • Maturity assessment: It isn’t enough for a control to “exist”; it’s expected to be defined, communicated and applied across the organization.
  • Prototype protection: Physical and organizational requirements for prototype parts, vehicles and events (if the relevant objectives were selected).
  • Supply chain: Strengthened requirements for suppliers where protection needs are very high (clarified with ISA2027).
  • Customer-driven scope: The flexibility to narrow the scope is more limited than in ISO 27001.

The item that causes the most surprises in the field is prototype protection. ISO 27001 addresses physical security through general controls; TISAX prototype objectives bring detailed expectations for automotive-specific situations such as enclosed areas, visibility, transport, test drives and events. If this objective is requested, there’s nothing the IT team can solve alone; facility management, logistics and R&D have to work together.

The maturity logic also changes the internal audit method. In an ISO 27001 internal audit, the question is mostly “Is the requirement met?” In TISAX preparation, ask the same three questions for each control: Is the process written? Do the people concerned know it? Are there repeated records showing it’s applied? Keeping a maturity estimate per control in the internal audit report shows weak areas early, before the assessment.

Which should you start with?

If your customer explicitly wants TISAX, an ISO 27001 certificate doesn’t meet that request; TISAX is needed. However, in an organization with no information security management at all, a management backbone built with the ISO 27001 approach (risk, policy, internal audit, management review) also raises TISAX maturity quickly. For organizations serving both automotive and other sectors, the two are usually planned together, with shared controls.

Three questions are enough to decide: How many of your customers are automotive and how many are in other sectors? What result is the customer requesting in writing? Do you have a working risk management and internal audit process today? If the request comes only from automotive, TISAX takes priority; if you have a mixed customer portfolio, a shared program makes sense. If there’s no management backbone at all, that comes first whichever you choose.

Practical tips for a shared program

  1. Use a single risk methodology; keep TISAX and ISO 27001 risks in the same register.
  2. Prepare the document set in the ISO 27001 structure, with VDA ISA references.
  3. Tag evidence by control; one piece of evidence can serve several frameworks.
  4. Add VDA ISA controls to the internal audit program.
  5. Manage audit calendars (surveillance, TISAX renewal, customer audits) in a single calendar.

The most common mistake in a shared program is producing two separate document sets with two separate consultants. The result is two procedures for the same process, two risk lists and two conflicting definitions of responsibility. The auditor sees this in the first hour. Keep a mapping table: next to each ISO 27001 Annex A control, write the related VDA ISA control and the location of the shared evidence. This table becomes the working list both in the internal audit and on assessment day.

When building the evidence library, pay attention to evidence dates. If the ISO 27001 surveillance audit and the TISAX assessment fall in different months, evidence prepared for one framework may be out of date by the time the other comes round. Set the schedule for periodic controls (access reviews, backup tests, supplier assessments) by each control’s own period, not by audit dates.

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

Does our ISO 27001 certificate shorten the TISAX assessment?

It doesn’t provide a direct exemption; however, an existing management system, documents and records speed up TISAX preparation considerably.

Can a TISAX label be used instead of ISO 27001?

Customers outside automotive usually expect an ISO 27001 certificate. A TISAX label is a result recognized in the automotive supply chain.

Can the two assessments be done at the same time?

The assessment bodies are separate; however, the calendar, preparation and evidence foundation can be planned together.

For organizations managing all three frameworks together, we offer the Integrated TISAX, ISO 27001 and IATF program; for those who want to start separately, our TISAX consulting and ISO 27001 ISMS setup services.

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