Safeguard
Compliance•

TISAX for product managers: scope, timing and customer asks

A product manager should treat TISAX as a customer gate with a scope, a lead time and a three year label. Decide the scope and the roadmap trade-offs before you bid.

Safeguard Security Team
3 min read

TISAX is a gate in the automotive supply chain. A buyer may require a valid label before you receive their data or sign a contract. A product manager's job is to learn which label and scope the buyer needs, sequence the work, and avoid promising delivery dates the audit cannot support.

Why does it show up as a sales blocker?

ENX explains that before TISAX, companies used individual supplier audits or general requirement catalogues, which were hard to scale and gave inconsistent results. TISAX replaced that with one assessment that partners recognize. For a seller, the flip side is that a missing label can stop a deal at procurement.

Results are shared through the ENX Portal, and only registered participants exchange them. Ask the buyer how they want your result shared and which participant ID to address.

What do you decide, and what does security decide?

Product decides which offerings and customer data flows go in the scope. Security decides how to meet the catalogue. The overlap is the scope statement. ENX says a result only meets a partner's requirement if the scope covers every part of your company that handles their information.

If your product processes partner data in a multi tenant platform, a narrow scope may not be possible. Then the question is whether to build a dedicated environment for automotive customers, which can shrink the audit and reduce risk elsewhere.

How long does it take?

The pages we read give no fixed duration, and the answer depends on your starting point and audit provider capacity. What it does describe is the sequence: registration, selection of an audit provider, assessment, then exchange. Labels last three years. Plan the first assessment as a project with a self-assessment phase, remediation and an audit, and ask the providers for their own lead times.

A constructed example

A quoting tool vendor wins a pilot with a car maker. The pilot contract says a TISAX label is needed before production data is loaded. The team plans a launch in six weeks. The product manager asks the buyer for the label, objectives and ISA version in writing, and learns that the buyer accepts a registered assessment in progress for a limited pilot but needs the label for production. That single written answer changes the roadmap: demo data only until the audit, then production.

What to do

  1. Ask the buyer in writing which label, objectives and ISA edition they require.
  2. Decide whether the in-scope offering is a shared platform or a dedicated environment.
  3. Draft the scope with security and confirm it covers every site and system with partner data.
  4. Register the scope and ask several approved audit providers for quotes and lead times.
  5. Put remediation work on the roadmap with owners, not as a side task.
  6. Give sales a short, honest statement of status that avoids implying a label before it exists.
  7. Calendar the renewal at the end of the three year label.

Quick check

Can you share a TISAX result with anyone?

Only through TISAX participants. ENX says results are not publicly available and are exchanged in the ENX Portal between registered partners.

What if the partner uses a managed service provider?

ENX says some partners delegate supplier interaction to one. Your partner will tell you and you follow its requirements.

Sources

Last reviewed: 18 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.