Skip to main content

Guide

TISAX Prototype Protection

Physical and digital prototype security: access controls, encryption, test vehicles, and NDA management.

Julian Köhn
|Updated|Read time: 4 minutes

Physical and digital prototype security: access controls, encryption, test vehicles, and NDA management.

Why Prototype Protection in TISAX Is So Important

An unprotected component on a workshop bench or a photo of an unreleased vehicle can expose confidential development. The ISA prototype protection catalogue concerns physical vehicles, components and parts classified as needing protection. Digital design data also needs to be considered in the information security context.

The objectives distinguish activities: Proto parts and Proto vehicles use AL3; Test vehicles and Proto events use AL2. “Prototype protection high” and “very high” are not current label names. Confirm the required objective and customer-specific rules.

Protect the prototype along its route · © 2026 Kopexa GmbH

Physical Security

Access Controls

Define who may enter protected areas and how permissions are assigned, changed and removed. ISA 6 allows alternative access-control implementations: documented key allocation, electronic systems or documented personal access control. Biometrics or a mantrap are not universal requirements for every prototype area.

Visitor Management

Arrange visitor registration, a documented confidentiality obligation before entry and communication of security rules. Determine escorting and permissions for the area. Personal-data collection must respect applicable data protection rules.

Camera Surveillance and Alarm Systems

Protection must extend beyond a locked gate. ISA 6 requires intrusion monitoring and alarm response, describing a suitable intrusion detection system or continuous guarding by a certified security service. Video surveillance is not universally required, nor does this establish a general 30–90 day retention period.

Digital Security

Encryption

Determine where digital development data needs encryption and which methods meet protection needs. Consider transfer, storage, mobile devices and key management. ISA requires suitable industry-standard cryptography; naming “AES-256 and TLS 1.2” is not complete evidence of implementation.

DRM and Watermarks

DRM and watermarks may support handling development records where risks or customer agreements call for them. They do not prevent every disclosure and are not universal requirements of a supposed “prototype protection very high” label. Define permitted use, sharing and image recording specifically.

Access Controls and Data Classification

Grant access to digital development data according to tasks and protection needs. Review roles, privileged access and permission changes. Classification and labelling must follow the agreed scheme; “prototype” is not automatically a universal confidentiality level.

Test Vehicles

The "Test Vehicles" label imposes specific requirements for handling test and pre-series vehicles:

  • Apply customer camouflage rules and document agreed changes.
  • Confirm approved test locations and conduct rules before use.
  • Arrange parking and storage according to customer requirements.
  • Report incidents, camouflage damage and unplanned situations through agreed channels.

Prototype Events

When prototypes are shown or transported at trade shows, tests, or presentations, special protective measures apply:

  • Communicate protection needs and event rules to everyone involved.
  • Define access, image recording and handling of smartphones or cameras.
  • Arrange transport and intermediate storage with customer-approved parties.
  • Include subcontractors and verify agreed safeguards.

NDA Management

Non-Disclosure Agreements (NDAs) are a central instrument in prototype protection. The auditor checks:

  • Document commitments with customers, staff and project participants.
  • For subcontracting, clarify required customer authorisation and confidentiality agreements.
  • Adapt templates to the specific contract and applicable law.
  • Assign responsibility for breaches, questions and changes to project conditions.

IT, facilities, purchasing and operational teams need to define handoffs together. Trace a component from receipt through the workshop to return transport. The audit preparation guide helps organise relevant evidence.

Implement prototype protection systematically

Keep outstanding safeguards, ownership and suitable records together. Our TISAX page shows how Kopexa supports this, making it clear whether an agreed safeguard has actually been implemented.

Sources and reference date

Reviewed on 13 November 2026 using the ENX participant handbook and ISA 6, including the transition to ISA 2027.