Guide
ISMS software for automotive suppliers: Meet customer requirements on time
Meet customer requirements on time: select ISMS software using orders, locations, production dependencies and dependable evidence.


A customer requires security evidence before awarding the next contract. What matters now is whether you can meet the requirement on time and for the right location. Another spreadsheet offers little help if nobody knows which gaps threaten the deadline.
These criteria translate customer needs into software requirements. A test involving two locations reveals whether open gaps remain visible before customer approval.
Start with the order, not the standards catalogue
Ask the customer for the specific requirement, scope and deadline. “We need TISAX” is too vague as a project brief. TISAX assessment objectives and scope must fit partner requirements; the procedure and result exchange are described in the ENX participant handbook.
Suppliers do not all process the same information. An engineering service provider protects different assets from a manufacturer receiving production drawings and delivery schedules. Prototype protection should neither be assumed for everyone nor overlooked where relevant.
Before the demo, record:
- Which order or customer relationship creates the need?
- Which locations, activities and information are affected?
- Which requirement was actually agreed, and who confirms its interpretation?
- Which result is needed by when?
If a few customers account for much of your revenue, missing evidence has particular commercial relevance. Compare purchasing costs with internal effort and the possible consequences of delayed customer approval.
Three supplier profiles need different priorities
| Starting point | What the software must demonstrate | What a generic control list misses |
|---|---|---|
| Engineering partner with confidential development data | Information assets, access ownership, external collaboration and suitable evidence | Which project data goes to whom |
| Production site with connected equipment | Assets, dependencies, outage impact and measures respecting operating constraints | That a security update requires an approved maintenance window |
| Corporate group with several plants | Central requirements and traceable local implementation | That evidence from plant A does not automatically cover plant B |
Selection should reflect your actual profile. An assessment-only assistant may suit narrowly bounded preparation. Where customer requirements, production and multiple locations come together, you additionally need a dependable connection to operations.
Use this template in these measures
Implementation measure
Approve and follow through supplier services
Mapped requirements (5)
- A.5.19 · Informationssicherheit in Lieferantenbeziehungen (DE)
Supporting contribution
Sections 1 and 2 connect the specific service, responsibility, risk-based assessment and approval in the existing record. Actual assessment and decisions must be made for your own services.
- A.5.20 · Berücksichtigung der Informationssicherheit in Lieferantenvereinbarungen (DE)
Supporting contribution
Section 3 supports appropriate security agreements and traceable deviation decisions. Actual agreement, legal review and implementation remain necessary.
- A.5.21 · Management der Informationssicherheit in der IKT-Lieferkette (DE)
Supporting contribution
Section 3 includes relevant ICT subcontractors, critical components, integrity and support in selection and agreements. Real supply-chain information and suitable evidence still need to be obtained and evaluated.
- A.5.22 · Überwachung, Überprüfung und Änderungsmanagement von Lieferantendienstleistungen (DE)
Supporting contribution
Section 5 connects regular and change-triggered service reviews with change decisions and corrections in the existing record. Reviews, evaluation and follow-up work must actually be carried out.
- A.5.23 · Informationssicherheit bei Nutzung von Cloud-Diensten (DE)
Supporting contribution
Sections 4 and 5 support the cloud lifecycle through specific task allocation, your own use, reviews, changes and exit. They do not prove actual configuration or implementation.
Further framework mappings of this measure
TISAX · 6.1.1
VDA ISA 6.0.3 · Partial contribution
The joint workflow supports risk-based selection and assessment of security-relevant services, suitable agreements and review of contractors and partners. Actual assessments, completed agreements, review results and applicable additional requirements remain to be evidenced. This is not a separate cloud ISA crosswalk or a claim to full objective fulfilment.
Read the source ↗
From customer need to implemented measure with Kopexa
Kopexa connects information assets, other assets, risks and measures. You can trace which sensitive information resides in which systems and what implementation is needed. Evidence stays with the measure, which is assigned to suitable controls.
Processes matter for production: BPMN can describe approval of external maintenance access or changes to a production application. A guided business impact analysis helps assess process outages over different time windows. The business basis for a measure’s priority becomes understandable.
This does not replace technical protection of equipment. It gives the technical work an owner, a traceable decision and verifiable completion. Our TISAX roadmap adds assessment preparation to this workflow.
The test: One order, two locations, one open gap
Use this fictional selection case: a customer wants to release development data. Engineering works at location A; testing takes place at location B. A defined process for revoking an external partner’s access is still missing.
Ask the provider to record the affected information and locations, assign the open measure, set an owner and attach evidence to the implementation. Then switch to management’s perspective: can you see what threatens the customer deadline and who must decide?
Finally, change the scope by adding a location. If all existing evidence still appears sufficient without further review, the software has transferred a status without clarifying the new situation.
Acceptance question: Can sales, the information security officer and plant management use the same data to explain what remains missing for the customer requirement?
What to clarify before signing
Check the supported ISA version, rights to catalogue content, scope modelling, roles and import of existing evidence. Ask how a time-limited deviation and an overdue review are handled. The external TISAX assessment remains a separate service; software does not guarantee a positive outcome.
Use the ISMS checklist with PDF download for software requirements. Add the customer requirement, location scope and operational test case.
In Kopexa’s two-week guided trial, you can test this exact workflow: follow a customer requirement through implementation to dependable evidence.
Quick answers
Frequently Asked Questions
Still have a question? Find the answers here.
Does every automotive supplier need the same TISAX preparation?
No. Partner requirements, information processed, assessment objectives and affected locations determine the need. Clarify these before choosing catalogues and software scope.
What should an automotive supplier test in an ISMS demo?
Follow a specific customer requirement through affected information assets and locations to an open measure and its evidence. Sales, information security and plant management should then see the same dependable status.
Sources
- TISAX: Procedure and assessment — ENX [Accessed ]