Sentinel Underwrite OpsEnterprise Underwriting Intelligence
Compliance

What TISAX Costs a Tier-2 Automotive Supplier: A Hypothetical First-Assessment Budget

A hypothetical 250-person supplier could spend roughly $65,000 to $600,000 on its first TISAX label. Where it lands depends on the assessment level, the scope, and whether ISO 27001 is already running.

By the Sentinel Underwrite Ops editorial team · November 2026 · 8 min read

Why the audit quote is the smallest number you'll see

The request usually arrives as a line in a supplier questionnaire or sourcing contract: provide a valid TISAX label at the required assessment level before you receive drawings, CAD data or prototype parts. Finance asks for a budget, and the first figure anyone finds is the audit provider's quote. It's misleading. For most suppliers, the audit invoice is only a minor share of the total TISAX assessment cost in the first year, often well under a quarter.

This piece builds a first-assessment budget for a hypothetical 250-person Tier-2 supplier. It covers audit provider fees, ENX fees, gap remediation, tooling and internal staff time, and shows how much an existing ISO 27001 program takes off the bill. All figures are indicative 2026 market ranges in USD. Day rates, travel and consulting fees vary widely by country and contract, so confirm every number with providers before you commit.

Advertisement

One terminology point first. Buyers often say "TISAX certification cost," but TISAX doesn't issue certificates. You receive an assessment result, shared as a label through the ENX Association's platform, and the label is typically valid for three years. Your customers see it only when you choose to share it with them on the platform.

TISAX assessment level 2 vs 3: let the customer's objective decide

Don't pick the assessment level yourself. The OEM or Tier-1 customer names the assessment objectives it needs, and those objectives set the level. Paying for AL3 when AL2 would do wastes money. Arriving with AL2 when the customer needs AL3 wastes more, because you'll be assessed again.

  • AL2 covers objectives such as information with high protection needs. The provider checks your self-assessment for plausibility, reviews evidence and interviews staff, usually by video. On-site visits are the exception.
  • AL3 covers information with very high protection needs and prototype protection. Expect a thorough on-site assessment, with auditors checking physical controls, sampling records and interviewing people at their workplaces.
  • AL1 is a self-assessment. OEMs rarely accept it for exchanging real engineering data.

Prototype protection pushes a budget highest. It brings in physical requirements such as secured zones, controlled photography, part handling and transport rules, and many suppliers have none of these in place.

The hypothetical supplier and our budget assumptions

Say a 250-person company makes electronic sub-assemblies. It runs a head office and engineering center with about 90 staff and one production plant with about 160. Its IT is a mix of Microsoft 365, an on-premises ERP, a PLM system holding customer CAD data, and roughly 40 engineering workstations. It has an IT manager, two administrators and no dedicated security staff.

We price three scenarios:

  • Scenario A: no ISO 27001, the customer asks for AL2 (information with high protection needs), both sites in scope.
  • Scenario B: no ISO 27001, the customer asks for AL3 with prototype protection at the plant.
  • Scenario C: ISO 27001 certified for at least a year with a matching scope, the customer asks for AL2.

We value internal staff time at a blended, fully loaded $60 to $80 per hour. In Western Europe or North America that may be too low for engineering managers. In India, Mexico or parts of Eastern Europe and Southeast Asia it may be too high. Swap in your own payroll figures.

Line-by-line first-assessment budget

Cost line (USD, year one)A: AL2, no ISOB: AL3 + prototype, no ISOC: AL2, ISO 27001 in place
ENX registration and platform fees$500 to $1,500$500 to $1,500$500 to $1,500
Audit provider, initial assessment$12,000 to $25,000$30,000 to $55,000$10,000 to $22,000
Follow-up assessment for findings$3,000 to $10,000$5,000 to $15,000$2,000 to $8,000
External gap analysis and consulting$25,000 to $60,000$40,000 to $90,000$8,000 to $20,000
Tooling and technical/physical controls$20,000 to $60,000$60,000 to $180,000$10,000 to $30,000
Internal staff time1,400 to 2,200 hrs ($85,000 to $175,000)2,000 to 3,200 hrs ($120,000 to $255,000)600 to 1,000 hrs ($35,000 to $80,000)
Indicative total$145,000 to $330,000$255,000 to $600,000$65,000 to $160,000

Two things stand out. First, internal time is the largest line in every scenario, and it's the one most often left out of the business case. Second, cash spend is much smaller than the totals suggest: in Scenario A, external spend is roughly $60,000 to $155,000. Show the CFO both figures, because the hours come out of engineering and IT capacity already committed elsewhere.

Audit fees depend on assessment days, the number of sites, travel and language. A provider with local auditors in your country can cut travel costs considerably. That matters most for plants in places like Mexico, India, Morocco or Southeast Asia, where flying in an auditor from Germany adds cost and scheduling delays.

Remediation and tooling: where budgets overrun

The VDA ISA catalog, the questionnaire TISAX is built on, rarely fails a company on policy writing. It finds the gaps in operations. For a supplier this size, remediation usually looks like this:

  • Identity and access: MFA on every remote and admin path, joiner-mover-leaver processes with evidence, and periodic access reviews for PLM and file shares. If you already run Microsoft Entra ID or a similar directory, this is mostly configuration and process work rather than new licenses.
  • Endpoint and mobile: full-disk encryption, managed devices and a mobile device policy. Expect a few dollars per user per month if you don't already have MDM and EDR.
  • Logging and vulnerability management: centralized logs with defined retention, plus patching you can prove. A managed SOC or MDR service often runs in the tens of thousands of dollars a year at this size. Most AL2 scopes don't strictly need one, but it closes several controls at once.
  • Supplier management: security clauses and evidence for your own subcontractors, especially any IT provider hosting customer data.
  • Prototype protection (Scenario B only): zoned access control, visitor management, camera coverage that respects local workplace-privacy law, sight protection for parts and secure transport procedures. Building work is where the upper bound in the tooling line comes from.

Workplace-monitoring rules differ by jurisdiction. EU works councils and data-protection laws in countries such as Mexico and India can each affect how you deploy cameras and logging. Have local counsel review those controls before you buy equipment.

TISAX vs ISO 27001: how much an existing program saves

Scenario C costs roughly half as much as Scenario A, for one reason. Many of the VDA ISA's information security controls map to ISO 27001 Annex A. A supplier with a working ISMS already has a risk methodology, asset inventory, internal audits, management review and an evidence culture. Those take the longest to build from nothing.

What ISO 27001 doesn't cover:

  • The VDA ISA maturity model. The assessor wants processes that are documented, implemented and effective, and you score yourself against that.
  • Automotive-specific requirements on handling and labelling customer information.
  • Prototype protection and data protection, which are separate assessment objectives in TISAX.
  • Scope alignment. If your ISO certificate covers only head office IT, the plant is still a greenfield project.

Some audit providers will schedule TISAX and ISO 27001 audits back to back and reuse evidence. That doesn't merge the two results, but it can save assessment days, so ask for it when you request quotes. If you have neither and serve customers outside automotive, build ISO 27001 first. The certificate counts in far more sales conversations, including cyber insurance underwriting, where documented ISMS controls can help with renewal questionnaires.

Red flags in quotes and scoping

  • A scope larger than the customer requires. If a sales or design office never handles customer data, ask whether it can be left out. Every extra site adds assessment days.
  • Fixed-price consulting that promises "guaranteed" labels. No consultant controls the assessment outcome. Pay for deliverables such as a gap report, policy set and evidence pack, not for promises.
  • No local auditor capacity. Get travel costs in writing and ask whether the assessment can run in your working language.
  • Quotes that omit follow-up assessments. Most first assessments produce findings. Budget for at least one follow-up.
  • A self-assessment completed by the consultant alone. Assessors interview your staff. If your team can't explain the answers, expect major findings.

A 12-month sequence and a decision rule

  1. Month 0: confirm in writing the customer's required objectives, assessment level and deadline.
  2. Month 1: complete ENX portal registration, define the scope and request quotes from two or three accredited audit providers. Book the assessment date early, because popular providers fill up months ahead.
  3. Months 1 to 3: run a gap analysis against the current VDA ISA, internally or with a consultant.
  4. Months 3 to 8: remediate, prioritizing controls that lack evidence over controls that don't exist at all.
  5. Month 9: run an internal pre-assessment, then the initial assessment.
  6. Months 10 to 12: submit corrective action plans, complete the follow-up assessment and share the label with the customer.

Decision rule: if the contracts that depend on the label are worth less than about three times your scenario estimate over three years, negotiate with the customer before you start. Ask for a later deadline, a narrower scope or an alternative data-exchange arrangement. If they're worth more, start ENX registration this month. The most expensive outcome is missing a sourcing deadline. Have a licensed advisor review any contractual commitments tied to the label.

Frequently asked questions

How long does a first TISAX assessment take from registration to label?

A supplier without an existing ISMS typically needs 9 to 12 months, most of it remediation. With ISO 27001 already in place, 4 to 6 months is realistic. Audit provider availability can add weeks, so book the assessment date early.

Can we skip AL2 and go straight to AL3 to future-proof?

You can, but you'll pay for on-site assessment days and controls no customer has asked for yet. Unless a customer has signaled that prototype or very-high-protection work is coming within the label's validity, match the level to current requirements. Upgrading later means a new assessment, but you won't rebuild from scratch.

Does ISO 27001 replace TISAX?

No. Automotive customers who ask for TISAX want the label exchanged through the ENX platform, and ISO 27001 doesn't substitute for it. A matching ISO 27001 scope can substantially cut the effort and cost of the first TISAX assessment, though.

What recurring costs follow after the first label?

Expect a reassessment roughly every three years, typically costing less than the first audit, plus ongoing ENX fees and the running cost of tools such as MDM, EDR or a managed SOC. The larger recurring cost is the internal time needed to keep evidence current. Confirm current fees with ENX and your provider.

Written by the Sentinel Underwrite Ops editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.