TISAX & GDPR: Dual Compliance for Automotive Suppliers

Your OEM wants the TISAX label. Your counsel wants the records of processing. Your test vehicles keep recording people on public roads. Three requests land on one small team, and each arrives with its own deadline.
The good news is that they share more ground than the three email threads suggest.
Where TISAX and the GDPR overlap
TISAX is built on the VDA ISA catalog, which draws on ISO 27001, and it protects what the OEM shares with you: prototypes, drawings, confidential information. The GDPR protects the personal data of people: employees, customers, vehicle users. The purposes differ. The machinery looks alike.
Both ask for a risk process. Both ask for access control, encryption at rest and in transit, and an incident response plan. A personal data breach under the GDPR is very often a security incident under TISAX, and the other way round. Write the measures once and both frameworks can use them: the technical and organisational measures your record of processing has to describe are largely the controls an information security assessment looks at.
Connected vehicles raise the stakes
A modern car produces a great deal of data, and much of it is personal data under the GDPR: telematics, location, infotainment usage, even biometric information from in-car sensors. Several suppliers along the chain often handle the same stream.
That makes it a TISAX concern (sensitive vehicle information) and a GDPR concern (personal data) at the same time. UNECE R155 (cyber security management system) and R156 (software update management system) add the whole vehicle lifecycle on top. A supplier has to show it can protect the data from attack and respect the people it describes.
What the OEM asks, and what it passes down
For many German OEMs and other manufacturers, a TISAX label is a condition of doing business, and the requirement runs down the chain from Tier 1 to Tier 2 and beyond. The GDPR travels the same road: if you process personal data on behalf of an OEM or another supplier, you need a data processing agreement, and any transfer outside the EU needs a lawful mechanism. Missing paperwork costs fines, and it costs the trust of the customer who asked for it.
What the agent does on the GDPR side
Marsstein is live for GDPR. The agent reads your public website and the documents you upload, and lists every page it used. It finds the gaps and drafts the record of processing activities, the DPIAs for test fleets and connected vehicle data, the data processing agreements and the transfer documents. Your data protection officer or counsel then reads each one and decides what stands.
The information security side, the VDA ISA catalog behind TISAX, stays with your ISMS owner and your assessor. ISO 27001 support is in preparation, and Marsstein does not issue or guarantee a TISAX label.
Camera data: anonymize before it travels
If your test vehicles record street footage, the people in it are personal data. The anonymization service Marsstein AEON, which runs next to Marsstein Compliance, masks faces and license plates in vehicle camera data inside the EU, before any copy goes to a labeling team, an algorithm vendor or R&D abroad. More than 100 TB of camera data have been processed this way, in the EU.
Masking alone does not make a dataset anonymous. GPS traces, timestamps and vehicle IDs can still point to a person, so each dataset is assessed against singling out, linkability and inference. Marsstein does not certify that a dataset is anonymous: your counsel or data protection officer signs off the assessment, and Marsstein Compliance records it together with the transfer documentation. Planning to send footage to R&D in China? Our EU to China guide lays out the decision flow.
Talk to us
If the GDPR paperwork is the bottleneck, talk to us. If it is the camera data, talk to us about AEON.
