TISAX Assessment Consulting: law, standards and implementation method

This page answers which legal and standard requirements apply, what the timeline and obligations are, and the phases Winners Consulting uses to get you there.

Standards: VDA ISA2027, ISO/SAE 21434, UN R155 and the EU CRA

VDA ISA2027: what changed and when it applies

What changed in ISA2027

The information security module keeps 46 controls, 44 of them revised: a new crisis management requirement (1.6.3), the policy obligation becomes mandatory (1.1.1), remote work is rewritten as a specific mandatory requirement (2.1.4), and supplier verification is tightened (former 1.2.4 moved to 6.1.3). The 12 data protection controls are unchanged from ISA 6. The biggest change is prototype protection.

Prototype protection restructured: two labels only

Prototype protection goes from 22 to 20 controls, and the former five sections 8.1–8.5 become two: 8.1 organisational requirements and 8.2 physical and environmental security. Only two labels remain, Prototype Protection Basic (AL2) and Prototype Protection Facilities (AL3); Facilities covers all Basic requirements and adds physical protection of the site holding prototypes.

ISA 6.0.3 or ISA2027?

The deciding factor is the order date, not the assessment date: assessments ordered by 31 December 2026 may still be completed under ISA 6.0.3; assessments ordered from 1 January 2027 follow ISA2027. Existing labels keep their validity; no early re-assessment is required.

ISO/SAE 21434: structure and how it divides work with TISAX

TISAX governs an organisation's information security (supply-chain confidential data, prototypes, personal data); ISO/SAE 21434:2021 governs cybersecurity engineering of the vehicle product from concept to end of support, matching the CSMS that UN R155 requires of OEMs, which indirectly reaches suppliers. They complement each other and do not replace each other.

Clauses 5–8Organisational level: organisational cybersecurity management, project-dependent management, distributed activities (customer/supplier interface agreements), continual activities (monitoring, event evaluation, vulnerability analysis and management)Policies, roles, supplier management and incident processes can be shared with TISAX / ISO 27001
Clauses 9–11Concept, product development, cybersecurity validationProduct-specific: item definition, TARA, cybersecurity goals and concept, design and integration verification
Clauses 12–14Production, operations and maintenance, end of cybersecurity support and decommissioningProduct-specific: production control, vulnerability handling and updates, end-of-support plan
Clause 15TARA methods: asset identification, threat scenarios, impact rating, attack paths, attack feasibility, risk value, risk treatment decisionThe method can be shared; each item's TARA results cannot

The seven TARA steps (Clause 15)

Each step must leave a reviewable work product; OEMs ask for them item by item during CSMS supplier reviews.

  1. 1. Asset identification

    List the item's assets and their cybersecurity properties (confidentiality, integrity, availability and others) and derive damage scenarios.

  2. 2. Threat scenario identification

    Map damage scenarios to possible threat scenarios.

  3. 3. Impact rating

    Rate damage from the road user's perspective across safety, financial, operational and privacy categories.

  4. 4. Attack path analysis

    Work back from the threat scenario to the paths an attacker could take.

  5. 5. Attack feasibility rating

    Rate by elapsed time, expertise, knowledge of the item, window of opportunity and equipment.

  6. 6. Risk value determination

    Combine impact and feasibility into a risk value.

  7. 7. Risk treatment decision

    Avoid, reduce, share or retain, and derive cybersecurity goals.

Evidence OEMs typically request in CSMS supplier reviews

UN R155 requires OEMs to demonstrate that their CSMS covers the supply chain; these are the supplier-side items usually requested, mapped to ISO/SAE 21434 clauses.

  • Cybersecurity policy and organisation (roles, responsibilities, competence and training records) — Clause 5
  • Project cybersecurity plan, tailoring rationale and cybersecurity case — Clause 6
  • Customer/supplier cybersecurity interface agreement (CIA) — Clause 7
  • Vulnerability monitoring, event evaluation and vulnerability management records — Clause 8
  • Item definition and TARA work products, cybersecurity goals and concept — Clauses 9 and 15
  • Design specifications, integration and verification test reports including penetration testing — Clauses 10 and 11
  • Production control and end-of-support plan — Clauses 12 and 14

TISAX × ISO/SAE 21434 evidence-sharing matrix

Which documents are built once and used for both, and which must be produced separately. This is Winners Consulting's practical mapping, not standard text.

EvidenceTISAX (VDA ISA)ISO/SAE 21434Shareable?
Security policy, organisation and roles1.1, 1.2Clause 5Shareable: one policy set plus product cybersecurity roles
Risk management method1.4Clause 15 methodMethod shareable; TISAX assesses organisational information risk, 21434 assesses item TARA
Supplier management and interface agreements6.1Clause 7Shareable: supplier list and requirements, plus a CIA template
Incident management and vulnerability handling1.6Clauses 8, 13Partly: reporting process shared; product vulnerability monitoring and updates built separately
Personnel security and training2.xClause 5Shareable: training records plus product cybersecurity competence
Physical and environmental security (prototype protection)8.x (ISA2027: 8.1, 8.2)—Not shared: not required by 21434
Item definition, TARA, cybersecurity goals and concept—Clauses 9, 15Not shared: produced per product item
Design specifications, verification and penetration test reports—Clauses 10, 11Not shared: product-specific
Personal data processing (data protection module)9.x—Not shared: not required by 21434

Sharing only works when versions and scopes line up: the sites in the TISAX scope must match the development sites of the 21434 project, or the shared evidence will contradict itself across the two audits.

TISAX, ISO/SAE 21434, UN R155, ISO/IEC 27001: label, product engineering standard, type-approval regulation, organisational standard

OEM due-diligence packs often name all four; they work at different levels: TISAX is a supply-chain information security label, 21434 is vehicle product cybersecurity engineering, R155 is the statutory CSMS for whole-vehicle type approval, 27001 is a generic ISMS.

ItemNatureWho and whereMandatory?How it is proven
TISAX (ENX)Automotive information security assessment and exchange mechanism (a label, not a certificate)OEMs and their suppliers (including service, software and prototype suppliers); VDA ISA questionnaire; used worldwideContractual (OEM procurement condition); legally voluntaryAssessment by an ENX-approved audit provider → TISAX label, valid 3 years, results exchanged on the ENX platform
ISO/SAE 21434:2021Road vehicle cybersecurity engineering standardOrganisations developing and producing E/E systems, components and software; whole life cycle (concept, TARA, development, production, operation, decommissioning)Voluntary, but the R155 interpretation document cites it as the practice baseline and OEMs almost always require itNo single official certificate; certification bodies offer process conformity assessments; OEMs check via audits and work products (TARA, cybersecurity case)
UN Regulation No. 155 (CSMS)UNECE vehicle regulation (mandatory in the EU via Regulation (EU) 2019/2144)Vehicle manufacturers (whole-vehicle type approval); EU new types July 2022, all new vehicles July 2024; also adopted by Japan, Korea and othersMandatory for OEMs; suppliers inherit it through OEM contractsCSMS certificate of compliance from the type-approval authority (3 years) plus vehicle type approval; suppliers provide supporting evidence
ISO/IEC 27001:2022International information security management standardAny organisationVoluntaryThird-party certificate

Key differences

  • TISAX governs your site's ability to protect OEM information, 21434 the cybersecurity engineering of the component you deliver, R155 the whole-vehicle CSMS and type approval — a TISAX label does not mean the product meets 21434, and vice versa.
  • The R155 legal duty sits with the OEM; suppliers have no direct statutory duty, but OEMs pass down 21434 processes, TARA and vulnerability management by contract.
  • A 27001 certificate greatly accelerates TISAX (much of VDA ISA 1.x, 2.x, 6.1 maps), but 27001 does not cover TISAX prototype protection and data protection modules or AL3 on-site verification.
  • TISAX moves fully to ISA2027 from 1 Jan 2027; orders placed by end-2026 may still use ISA 6.0.3.

How to choose

  • OEM due diligence requires a TISAX label → confirm the contractual objectives and level first, then decide whether to implement 27001 alongside.
  • You develop ECUs, software or connected components → 21434 processes and TARA are hard requirements; OEMs audit before SOP.
  • You are an OEM or apply for vehicle (modification) type approval → R155 CSMS certificate first, 21434 as the practice baseline.
  • Mainly non-automotive with occasional OEM customers → build 27001 first, add TISAX as orders require.

What to share when implementing together

Share one base: organisational documents (21434 clauses 5–8 = TISAX information security module = 27001 clauses 4–7), risk methodology (TARA clause 15 can share the framework with the 27001 risk assessment), incident and vulnerability management (21434 clause 8 = R155 Annex 5 = 27001 A.5.24–28 = TISAX 1.6), supplier management (21434 clause 7 = TISAX 1.5). What differs is the product layer: TARA, cybersecurity case and verification testing are done per product.

How Winners works

Winners supports all four: TISAX gap analysis through assessment support, ISO/SAE 21434 process build-out and TARA, R155 CSMS evidence preparation, ISO 27001 implementation and audit support. The first step is to read the OEM contract and your product role, then recommend one, a sequence, or passing several with the same evidence set.

Either entry works: start from your industry's pain points or from the standard you plan to adopt — we first clarify the differences, then give you the information and support.

Method: four phases

  1. 01 Scoping and diagnosis

    Inventory the current state against the VDA ISA information security, prototype protection and data protection modules; define scope and target level (AL2/AL3); deliver a gap analysis. Acceptance: scope determination and gap analysis.

  2. 02 Remediation plan and system build

    Build information security, supplier management and prototype protection procedures in priority order. Acceptance: system documents and implementation evidence.

  3. 03 ISO/SAE 21434 integration (optional)

    Share the security policy framework and risk assessment baseline to avoid duplicate build. Acceptance: sharing matrix and TARA work products.

  4. 04 Mock audit and assessment support

    Help select an ENX-approved audit provider, complete the mock audit and corrections, and accompany you to the TISAX label. Acceptance: label and correction records.

The most cost-effective path to full compliance

The law requires an outcome, not the most expensive method. Below is the lightest lawful path from the official text and our practice, the evidence you can reuse, the steps you can merge, and what must never be cut — cutting it voids the whole compliance.

Lightest lawful path

  • Assess only the objectives your customer contract actually requires: the objective sets the level, and every extra AL3 objective means another on-site audit.[Basis:ENX handbook v2.8 tables 3/5, §4.3.3]
  • If your scope includes prototype protection and labels expire in 2027, ordering by 31 Dec 2026 lets you finish under the familiar ISA 6.0.3 and avoid changing version and re-assessing at once.[Basis:VDA ISA2027 transition rule]
  • AL2 objectives are interviewed by web conference; no on-site visit is needed, and AL 2.5 fully remote can be requested.[Basis:ENX handbook §4.3.3.5]
  • Over 99% of participants are fine with the standard scope; do not customise scope for a single customer.[Basis:ENX handbook §4.3.2.1]

Evidence you can reuse

  • With ISO 27001 in place, security policy, risk assessment, supplier management, incident management and personnel security map directly to most VDA ISA information security controls.[Basis:VDA ISA 1.x, 2.x, 6.1]
  • Share organisational documents (clauses 5–8) with ISO/SAE 21434; only item-level TARA and verification are produced separately.[Basis:Evidence-sharing matrix on this page]

Steps you can merge

  • Run the TISAX mock audit and the 27001 internal audit in the same week on the same evidence set.[Basis:ENX handbook §5]
  • Cover multiple sites in one assessment (all sites in scope) instead of ordering separately.[Basis:ENX handbook §4.3.2]

Never cut (cutting voids compliance)

  • Assessments must be performed by an ENX-approved audit provider; a self-assessment (AL1) produces no label and is not used in TISAX.[Basis:ENX handbook §4.3.3.5]
  • On-site verification for AL3 objectives cannot be made remote (a video substitute when the site is temporarily inaccessible is recorded as a minor non-conformity).[Basis:ENX handbook §4.3.3.5]
  • Assessments ordered from 1 Jan 2027 follow ISA2027; prototype protection documentation must be re-mapped to 8.1/8.2.[Basis:VDA ISA2027]

Sources

Checked against the official documents on 2026-10-24

Next steps

Book a consultant

Confirm scope, objectives and level, and whether ISA 6.0.3 or ISA2027 applies. The first assessment is free.

Book a consultant

Request a service scope

Tell us your sites, customer requirements and whether to integrate ISO/SAE 21434 to receive a scope and quote mapped to the deliverables on this page.

Request a service scope

ISO/SAE 21434 page

Engineering details and advisory content for TARA, CSMS and UN R155.

Go to ISO/SAE 21434

Defined terms and framework elements in this service (Risk Glossary)

Each term is taken from the original legal or framework text, with its article or clause; Winners Consulting addresses each one in this service.

Ask a consultant on LINE

No forms: the button opens LINE with the page you are reading filled in. Send it and a Winners Consulting consultant will reply. The first diagnosis is free.

Winners Consulting track record

Winners Consulting Services is a Taiwan RegTech platform provider and enterprise risk management consultancy.

Trusted long-term by 20+ companies, we work as an industry-focused, long-term partner to our clients.

Named client engagements, published with client permission:

See case studies