TISAX Labels: Information, Prototype and Data Protection Objectives

TISAX labels: confidentiality, availability, prototype and data protection objectives, the levels they require, and moving from a customer request to the right list of labels.
Technical summary
Technology
TISAX, VDA ISA, ENX, GDPR
Topic
TISAX assessment objectives and choosing labels
Level
Beginner–intermediate
Prerequisites
  • The customer’s request letter or the contract’s information security annex
  • A list of in-scope locations
In this article8 sections

What you apply for in TISAX isn’t a certificate but one or more assessment objectives; after a successful assessment, a label is issued for each objective. Which label you choose determines which VDA ISA sections the assessment will cover, at which level it will be done and how much preparation will be needed. A wrong choice means either an incomplete scope or months wasted. Below we explain the information security, availability, prototype protection and data protection label groups, and how to get from a customer request to the right list of labels.

The concept of an assessment objective (label)

An assessment objective defines the object to be protected and its protection need together: “information with very high confidentiality”, “prototype parts” or “special category personal data”, for example. Each objective fixes three things:

  • Catalog modules covered: In VDA ISA, the information security, prototype protection and data protection modules are separate sections. The objective determines which modules and which additional requirements are assessed.
  • Assessment level: AL2 or AL3 depending on the objective’s protection need.
  • What the label means: When a customer sees the label in the ENX portal, they know what was verified.

ENX has simplified label names over time; the “Info high” and “Info very high” objectives now go by “Confidential” and “Strictly confidential”. You’ll see the old names in older request letters and the new ones in newer letters. Before applying, verify the current naming in ENX’s TISAX documentation.

Information security labels

This is the basic group most suppliers deal with. It’s defined on two axes: confidentiality and availability.

Target Protection need Level
Confidential (Info high) High confidentiality AL2
Strictly confidential (Info very high) Very high confidentiality AL3
High availability High availability AL2
Very high availability Very high availability AL3

Confidentiality labels focus on protecting the technical drawings, specifications, software, pricing and project information the customer shares. The “Strictly confidential” objective brings in the catalog’s additional requirements for very high protection needs; expectations harden on encryption, access restriction and logging.

Availability objectives were added later and defined for situations where the continuity of the supplier’s service or production is decisive for the customer. A typical example: a supplier delivering parts just in time (JIT), where a system outage could stop the customer’s line. When these objectives are selected, business continuity, backup and recovery processes gain weight in the assessment. The restore test record is among the evidence to be presented for these objectives.

Prototype protection labels

Prototype protection objectives concern the physical protection of vehicles and parts not yet on the market. For prototype protection objectives, the assessment level varies with the objective chosen. According to the ENX participant handbook, the Test vehicles and Proto events objectives have been under AL2 since 1 January 2025. Verify the objective against the customer’s request, and the assessment level against ENX’s current table.

Target Typical activity Level
Proto parts Production and storage of prototype parts and components AL3
Proto vehicles Storing and working on prototype vehicles AL3
Test vehicles Use of camouflaged test vehicles, test drives AL2
Proto events Events, photo and film shoots with prototypes AL2

These objectives cover the catalog’s prototype protection module: physical and environmental security, organizational requirements, transport of vehicles and parts, test vehicles, events. Prototype labels aren’t independent of the information security module; confirm from current ENX rules which information security requirements are assessed together with prototype objectives. Details are in the article TISAX prototype protection requirements. If the assessment objective covers production or prototype areas, assess the retention, access and on-site evidence requirements for video surveillance controls for TISAX.

Make the choice by activity. A supplier producing a prototype door panel mold needs the “Proto parts” label; if it doesn’t use test vehicles, “Test vehicles” is unnecessary. An engineering firm that only processes CAD data and never touches a physical prototype may be able to make do with an information security label instead of a prototype label. Confirm this with the customer in writing.

Data protection labels

Data protection objectives are for situations where the supplier processes personal data on behalf of the customer. The ENX participant handbook defines the Data objective as data protection in the processor role under Article 28 of the GDPR, and the Special data objective as processing, in the same role, the special categories of personal data set out in Article 9 of the GDPR. Assess the objective together with the customer’s request.

  • Data (AL2): Processing personal data on behalf of the customer. Example: running an application for OEM employees, or a CRM service working with dealer network data.
  • Special data (AL3): Processing the special categories of personal data defined in Article 9 of the GDPR. Example: an occupational health service involving health data, or a system working with biometric data.

For a supplier in Türkiye, a data protection label doesn’t replace KVKK compliance. The label makes it easier for an EU customer to assess its processor supplier within the GDPR framework. KVKK is managed separately.

From the customer request to label selection

To base label selection on the customer request, use the decision table below. Each row is a question; a “yes” answer shows the objective to add.

Question If yes
Does the customer share confidential information? Confidential
Does the customer classify the information as “very high”? Strictly confidential
Does an outage on our side directly affect the customer’s operations? Availability objectives (if the customer requests them)
Do we physically hold prototype parts or vehicles? The relevant prototype objective
Do we process personal data on behalf of the customer? Data or Special data

The final word is still the customer’s. For objectives that need interpretation, such as availability, act on the customer’s written request, not your own guess. If there’s more than one customer, combine their requests and record which label came from which customer; with this record, weeding out an unnecessary label at renewal takes minutes.

Label selection also determines the level; for the difference in method between AL2 and AL3, see the article TISAX AL1, AL2 and AL3 differences.

The cost of an unnecessary label

  • Producing documents, processes and evidence for additional catalog requirements.
  • On-site review for AL3 objectives, and the audit days that come with it.
  • Higher risk of findings: controls are expected to be implemented even for an activity you don’t carry out.
  • Carrying the same burden again at renewal.

Mistakes you may come across in label selection

  • Copying a competitor’s labels: Another supplier’s published labels in the same sector don’t reflect your customer relationships. The choice rests on your own contracts.
  • Confusing level with label: The sentence “we want AL3” doesn’t specify an objective. Strictly confidential, Very high availability, Proto parts, Proto vehicles and Special data are assessed at AL3; their preparation burdens differ greatly.
  • Selecting prototype labels in bulk: Selecting all four prototype objectives creates controls that can’t be assessed, or that produce findings, in a firm with no test vehicle or event activity.
  • Skipping the data protection objective: In IT services that process the personal data of customer employees or the dealer network, this objective is often overlooked; the customer later asks for an additional assessment.
  • Corresponding with old label names: When replying to the customer, write the old and current name together. The misunderstanding ends.

Keep the reasoning for the labels chosen in a short decision record: which customer, which request letter, which date, which objective. The same record is useful in the TISAX pre-assessment preparation process, in the preliminary meeting with the audit provider and for internal management approval; when a scope question comes up, your basis is ready.

Extending label scope

When a new customer or project requires a new objective, an additional objective can be added to the existing scope. How this is done in the ENX registration (updating the existing scope or a new assessment registration) depends on current ENX rules; in every case the audit provider carries out an additional assessment. Order of checks:

  1. Look at the level of the additional objective; adding an AL3 objective to an AL2 scope means an on-site review.
  2. Take the validity period of existing labels into account; if the renewal date is close, planning the additional objective together with renewal is usually more efficient.
  3. Assess the new objective’s effect on locations; since a prototype objective is tied to the in-scope locations, discuss with the provider whether it’s appropriate to keep locations with no prototype work in a separate scope.
  4. Give the customer a realistic date for when the additional label can be shared.

If you want your label selection verified by an independent eye and your preparation plan built around it, start from the TISAX consulting page. The general roadmap is in the article TISAX preparation guide.

Frequently asked questions

Do we need to have vehicles on site to get a prototype label?

No, but the activity the label covers must actually be carried out. A supplier that only produces or stores prototype parts needs the parts label; the vehicle, test vehicle and event labels are meaningless if those activities don’t exist, and create unnecessary scope.

Does a data protection label prove KVKK compliance?

No. Data protection labels are for assessing a supplier that processes personal data on behalf of a customer against the processor obligations in the EU General Data Protection Regulation. KVKK is a separate legal framework and is handled separately.

Is it possible to add labels later?

Yes. The scope can be extended by selecting additional assessment objectives for the existing scope. However, new objectives require an additional assessment, and AL3 objectives mean an on-site review; plan known requests together in the first application.

If the customer only says “get TISAX”, which label should we choose?

That isn’t enough information to choose. Ask the customer in writing for the protection need of the information it will share, whether prototypes are involved and whether personal data will be processed. Choosing labels by guesswork for a vague request ends with either an incomplete scope or an unnecessarily costly one.

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