Most automotive suppliers first meet TISAX through a customer email or a contract clause. If that first request is misread, months of preparation head in the wrong direction: the wrong label or level is chosen, the assessment ends and the customer finds the result insufficient. Below, for purchasing, quality and information security owners, we explain how to break down a request from an OEM or Tier-1 customer, what to clarify with the customer in writing and how to pass the request on to sub-suppliers.
Reading the request letter correctly
A TISAX request comes in different guises: a general supplier announcement, a specification clause in a project, a sentence added to purchase order terms or a task opened in the customer’s supplier portal. Whatever the form, this information must be extracted from the request:
| Details | Where to look | What to do if missing |
|---|---|---|
| Label names | Request text, specification, supplier portal | Ask the customer for a written list |
| Assessment level | Stated together with the label | Confirm its link to the label |
| Location | Order or project address | Ask which site it’s required for |
| Deadline | Request text, contract | Ask about interim evidence conditions at the same time |
| Sharing details | The customer’s ENX participant details | Ask whom you should share the result with |
Label names may change between versions. A label name in a request sent with an old template may correspond to a different name in the current catalog. Which protection objective each label corresponds to is explained in the article TISAX labels, and the difference in method between levels in the article TISAX AL1, AL2 and AL3 differences.
A mistake you may come across is seeing the word “TISAX” in the request email and going straight to an application with the most common label. Labels aren’t chosen by guesswork. Don’t ask an audit provider for a quote until each of the five rows in the table has come from the customer in writing.
Topics to clarify with the customer
If the request text needs interpreting, don’t interpret it yourself; ask the customer and get the answer in writing. This correspondence also becomes evidence of why the scope was chosen as it was. The main topics to clarify:
- Which information, which projects? Does the request cover the whole business relationship or only a specific project? Prototype labels often come up in project-based requests.
- Which location? For a supplier with several sites, the customer expects only the site where its work is done. Details of the location decision are in the article TISAX scope and location selection.
- Is an existing result enough? If you have labels obtained for another customer, ask whether they meet this request; an additional label may be needed.
- What’s accepted in the interim? Can registration details, a scheduled assessment date or a self-assessment be presented?
- Who is the contact? Purchasing usually refers information security questions to the customer’s information security unit. If a technical question goes to the right person, the answer comes days earlier.
Assigning ownership of the request internally
The request usually comes to sales or purchasing, but most of the requirements are met in IT, information security, HR, facilities management and engineering. A request circulating in an email chain has no owner. Work without an owner doesn’t move. These decisions must be made in the week the request arrives:
- Owner: The person who will run customer correspondence and internal preparation from a single point (usually the information security officer or quality manager).
- Management sponsor: The senior executive who will decide on budget, choice of audit provider and prioritization between units.
- Unit representatives: One owner each for physical security, identity and access management, HR processes and engineering data management.
- Commercial impact: Which order or quote would be affected if the request isn’t met; management’s prioritization decision rests on this information.
These decisions also go into the first customer reply: the owner’s name and contact details make it possible to work directly with the customer’s information security unit. The same structure is reused for requests and questionnaires from later customers.
Timeline and transition period
The customer often gives a deadline, and this date may have been set independently of the supplier’s real preparation time. Preparation time depends on the firm’s current maturity, the labels chosen and the provider’s schedule. Presenting the plan to the customer split into three parts gives a realistic basis for discussion:
- Preparation: The VDA ISA self-assessment, closing gaps, the evidence file.
- Assessment: The initial assessment according to the provider’s schedule, and a possible corrective action plan.
- Result: Publication of the temporary or permanent label and sharing it with the customer.
When estimating preparation time, count technical gaps separately. Work such as rebuilding the permission model on the file server, separating the engineering VLAN or central log collection needs purchasing and maintenance windows; it takes much longer than writing policies.
The evidence that can be offered to the customer during the transition period is usually the registration in the ENX portal, the assessment plan and the current self-assessment. Some customers work with this evidence for a while; others won’t award new projects without a label. Don’t assume; ask. For the general steps of the process, the participant handbook published by ENX is the primary source.
Passing it on to sub-suppliers
If you share customer information or prototypes with a sub-supplier, the protection the customer expects from you doesn’t end there. In its supplier and service provider controls, VDA ISA expects information security requirements to be reflected in contracts and suppliers to be assessed appropriately. In the assessment, this control is tested with a single question: “Which external parties does customer data go to, and what assurance is obtained from them?”
The first step is an inventory: which sub-supplier does customer data or a prototype go to, for what purpose, and through which channel? Typical examples are external design offices, test and measurement labs, mold makers, logistics firms carrying prototypes and IT service providers. Write down the channel too. A drawing sent by personal email, a public file-sharing link or a USB stick is an uncontrolled flow, whatever the contract says. For each party on the list, check the transfer rule in the customer contract; some customers require prior permission to transfer data to sub-suppliers.
Whichever assurance method is chosen, the minimum terms expected in a sub-supplier contract are similar: a confidentiality obligation, use of the information only for the stated purpose, no transfer to other parties without your approval, reporting security incidents without delay, return or destruction at the end of the work, and a right to audit where needed. The obligations the customer places on you must be passed into this contract at least at the same level.
Options for sub-suppliers
Asking every sub-supplier for a TISAX label may not be proportionate. The choice is made based on the sensitivity of the information shared, the customer’s contract terms and the size of the sub-supplier.
| Option | When it fits | Limitation |
|---|---|---|
| TISAX label from the sub-supplier | The customer explicitly asks for it, or prototypes are shared | Time and cost burden for the sub-supplier |
| VDA ISA self-assessment and contract | Medium-sensitivity information, limited sharing | No independent verification |
| Your own audit | A critical but small supplier | Requires auditor competence and resources |
| ISO 27001 certificate and scope check | The customer accepts it | It must be verified that the scope includes the relevant service |
| Limiting data sharing | The sub-supplier doesn’t need all the data | May require changes in business processes |
The last option is often forgotten. Sending the mold maker only the relevant part geometry rather than the whole vehicle model, or giving the external design office restricted remote access to work in your own environment, reduces risk before the assessment burden. Data you don’t send doesn’t leak. For the general method of assessing sub-suppliers, see the article supplier information security risk assessment.
Request analysis checklist
- The request text and its source (email, specification, contract clause) have been recorded.
- Label names, assessment level and location have been confirmed in writing by the customer.
- The deadline and the evidence accepted during the transition period are clear.
- It has been checked whether existing TISAX results meet this request.
- The customer’s ENX participant details and the contact to share the result with have been identified.
- The flow of customer data and prototypes, including sub-suppliers and channels used, has been mapped.
- An assurance method has been chosen for each sub-supplier and contract terms reviewed.
- A plan covering preparation, assessment and result steps has been shared with the customer.
If the assessment objective covers production or prototype areas, assess the retention, access and on-site evidence requirements for video surveillance controls for TISAX.
For breaking down the request and corresponding with the customer, see our automotive supplier information security and customer audits service, and for preparation once the request is clear, our TISAX consulting and assessment preparation service.
Frequently asked questions
If the customer only says “TISAX is required”, which label should we get?
Don’t choose the label by guesswork. Ask the customer in writing for the label names, the assessment level and the location it’s required for. Most OEMs publish this information in their supplier portal or specifications; if the purchasing contact doesn’t know, ask to be referred to the information security unit.
What can we offer the customer until we have the label?
It depends on the customer. Commonly accepted interim evidence is the registration information in the ENX portal, an assessment date scheduled with the provider and a current VDA ISA self-assessment. Confirm in writing with the customer which ones are accepted and for how long they’ll be considered valid.
Do we have to ask our sub-supplier for TISAX too?
Not in every case. It depends on whether customer information or prototypes go to the sub-supplier and how the customer contract regulates this. Some customers ask for a label for sub-suppliers too; for others, a risk-based assessment and contract terms are considered enough.
Does an ISO 27001 certificate meet a TISAX request?
Usually not. A customer asking for TISAX wants to see the result via ENX and on the basis of VDA ISA. ISO 27001 preparation makes TISAX easier, but doesn’t replace the label; if the customer grants an exception, get it in writing.