How to Respond to Automotive Customer Information Security Questionnaires

Consistent answers to an automotive customer’s information security questionnaire: an answer library, choosing shareable evidence, over-commitment traps and referring to the TISAX result.
Technical summary
Technology
VDA ISA, TISAX, supplier self-assessment questionnaires, customer audit
Topic
The process for responding to OEM and Tier-1 customer security questionnaires and customer audits
Level
Intermediate
Prerequisites
  • An information security policy set in force
  • A current VDA ISA self-assessment or similar checklist
In this article7 sections

An automotive supplier deals not only with the TISAX assessment but also with customers’ own information security questionnaires and audits. In the same year, dozens of similar but not identical questions come from different customers. If each is answered by a different person in different words, inconsistency is inevitable, and it comes out at the first customer audit. Below we explain the types of questionnaire, building a reusable answer library, choosing evidence attachments, over-commitment traps and how to use the TISAX result in a questionnaire.

Types of questionnaire and customer audit

Although customer assurance requests vary in form, they fall into a few main groups. Which group you’re facing sets the depth of the answer and the need for evidence.

Type Typical content Evidence expected
General supplier self-assessment Policy, organization, basic technical controls Mostly declarations, selected documents
VDA ISA-based self-assessment ISA control questions and maturity level Level declaration, justification
Project-specific security questionnaire Data exchange channels, access, prototypes Explanation of the project setup
IT service or cloud questionnaire Hosting, encryption, logging, incident reporting Architecture summary, certificates
On-site or remote customer audit Verification of questionnaire answers Records, system screens, on-site observation

With some customers these types come in sequence: first a self-assessment, then scoring according to the customer’s risk model, then an audit for suppliers seen as weak. That’s why a questionnaire answer is a declaration that will be verified later. It must be written that way.

Building an answer library

An answer library is a structure that keeps the approved answers to frequent questions together with the documents they rest on and their owners. The goal isn’t to write every question from scratch but to adapt an approved answer to the question. Using the VDA ISA control structure as the backbone is practical; automotive customers’ questions largely match the topics of this catalog. If a mapping to ISO 27001 controls is added, the same library also works for questionnaires from non-automotive customers. The relationship between the two frameworks is explained in the article TISAX and ISO 27001 differences.

Every library entry should have these fields:

  • Topic and mapping: VDA ISA control, ISO/IEC 27001 Annex A control.
  • Short answer: Yes / Partly / No and a one-sentence summary.
  • Long answer: Two to four sentences, suitable to send to the customer, describing how the control is implemented.
  • Supporting document: Name and version of the policy or procedure.
  • Shareable evidence: Evidence that can be shown without a confidentiality agreement, with one, or only during an audit.
  • Owner and last review date.

If the library is fed from the same source as the evidence matrix, maintenance gets easier: when a control’s evidence changes, the related answer is updated in the same place. Building the control–evidence mapping is explained in the article how to build an evidence matrix. An undated answer is a stale answer. If an answer’s last review date is more than a year old, have the relevant unit re-approve it before sending.

Principles for writing answers

A good answer describes how a control works, not that it exists. “Our access rights are checked” carries no information. “Permissions on project folders on the engineering file server are reviewed every three months by the folder owner; the review record is kept by the information security officer” says who does what, how often and where the evidence is. When the auditor reads the second sentence, they know what to ask for, and you know what to show.

Internal system names, IP addresses, VLAN numbers and configuration details of security products aren’t given in answers unless necessary. For the question “Which firewall model do you use, with which software version?”, answering with the product class and management method is often enough; exact version information is useful to an attacker too.

Questionnaire intake and approval flow

Questionnaires arrive scattered across sales, purchasing or quality. A single point of entry (a shared email address or request record) prevents both missed deadlines and the same questionnaire being answered differently by two people. The flow can stay simple: the questionnaire is recorded, draft answers are filled in from the library, questions without a match go to the relevant unit, the information security officer checks consistency, and an authorized manager approves before sending. The final version of the questionnaire sent is archived with the sending date and recipient; it’s the first document asked for at a customer audit. Approved answers to new questions are also added to the library.

Choosing evidence attachments, and confidentiality

Customers often ask for evidence attachments. The choice balances two goals: convincing the customer and not opening up your internal information more than necessary. The classification below can be used to fill the “shareable evidence” field in the library:

Class Example Sharing condition
Open sharing Policy summary, certificate, label details Can be attached directly to the questionnaire
With a confidentiality agreement Full policy, procedure, training plan After a confidentiality agreement
Shown only during an audit Network diagram, system reports, incident records Screen sharing or on site; no copies given
Not shared Penetration test finding details, password policy exceptions Summary information is given

Don’t share evidence containing another customer’s information without masking it. If one customer’s project name or drawing is visible in the corner of a screenshot attached to another customer’s questionnaire, you’ve breached exactly the confidentiality control the questionnaire asks about. That’s a leak you may come across. Folder names in a file explorer window, subject lines in an email client and open file names on the taskbar are the usual suspects in screenshots.

Avoiding over-commitment

Questionnaire answers often become a contract annex or are used as a reference at a customer audit. An answer describes the current state, not the target state. The most common forms of over-commitment:

  • Marking a partly implemented control as “yes”.
  • Describing a practice that applies only at head office as if it applied to the whole company.
  • Accepting deadlines the customer proposes (for example the incident notification time) without checking internal processes.
  • Generalizations with unclear scope, such as “we encrypt all data”.
  • Presenting an external service provider’s control as your own control.

Test the sentence “we encrypt all data” in the field: BitLocker may be on for laptops, but file server backups may be written to an unencrypted NAS, and old backup disks kept on site may be unencrypted. The auditor asks exactly this question. Write the answer by data type and medium: on which device, in which transfer, in which backup.

Honestly reporting partial implementation is usually accepted, as long as the comment field states the current situation, the compensating measure and the planned date. If a commitment the customer wants can’t be met by internal processes, saying so at the answer stage is cheaper than a breach after the contract.

Using the TISAX result in a questionnaire

If there’s a valid TISAX label, you can refer to the result for questions within the VDA ISA scope of the questionnaire. Add a short information note at the start of the questionnaire: the labels, assessment level, in-scope locations, validity date and that the result can be shared via the ENX portal. Sharing is done in the ENX portal with the participant’s approval; the customer seeing the result there is more reliable than an attached screenshot.

The reference has its limits. The label is valid only for in-scope locations; if the customer’s work is done at an out-of-scope location, the label doesn’t answer that question. Project-specific questions (such as which data exchange channel will be used) and questions about personal data are also often answered separately. If you don’t have a label yet, how to manage the customer request is covered in the article when a customer asks for TISAX.

Preparing for a customer on-site audit

A customer audit after a questionnaire is a verification of the answers given. Your questionnaire answers sit at the center of preparation: the auditor will most likely open the answers one by one and ask for evidence.

  1. Reread the answers: Find the final version of the questionnaire sent; mark practices that have changed since that date.
  2. Prepare an evidence folder: Decide in advance which record you’ll show for each answer; for evidence shown only during the audit, plan screen sharing or on-site display.
  3. Choose the interviewees: Pick the process owner who will explain each topic and make sure what they say is consistent with the questionnaire answer.
  4. Plan the site walk: Set the route and escort arrangements for prototype areas, the server room and entry control points; areas and information belonging to other customers must not be visible.
  5. Agree the findings process: Decide who receives the audit report, and when and how the corrective action plan will be sent.

Preparing process owners for interviews is explained in the article preparing for auditor interviews; the same principles apply to customer audits. For questionnaire answers and customer audits, see our automotive supplier information security and customer audits service, and for structuring the evidence file, our TISAX pre-assessment preparation and evidence file service.

Frequently asked questions

Why does the customer send a separate questionnaire when we have a TISAX label?

The label gives assurance on the basis of VDA ISA for a specific scope and location. The customer’s own questionnaire often contains questions specific to a particular project, cloud service, personal data or contract. Refer to the result for questions the label covers, and answer the rest separately.

Should we attach all our policy documents to the questionnaire?

Usually not. Attaching the section that directly answers the question, or a summary document, is enough. Documents containing details such as internal structure, IP addresses and system names shouldn’t be shared without a confidentiality agreement, and should be masked where needed.

Is it right to answer “yes” for a control not yet implemented and give a date?

No. The correct answer is “partly” or “no”, with the planned date given in the comment field. A questionnaire answer can be considered part of the contract; presenting an unimplemented control as implemented turns into a serious trust problem at the customer audit.

Who should update the answer library?

The library should have an owner, usually the information security officer. The content owner of each answer is the relevant unit. After a policy revision, infrastructure change or audit finding, affected answers should be reviewed and their dates updated.

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