VDA ISA Maturity Levels 0–5: How to Evidence the Target Level

VDA ISA maturity levels 0–5, what target level 3 requires in practice, level examples for the same control and evidence-based scoring in the self-assessment.
Technical summary
Technology
VDA ISA, TISAX, ISO/IEC 33001 process maturity approach
Topic
Defining maturity levels and scoring in the self-assessment
Level
Intermediate
Prerequisites
  • The current VDA ISA catalog (Excel)
  • Process owners of the controls identified
In this article8 sections

In the VDA ISA self-assessment, a maturity level between 0 and 5 is written next to each control, and a picture you may come across is the column being filled with “3” from top to bottom. That number is the auditor’s starting point in the TISAX assessment. A realistically scored self-assessment speeds up the audit; an inflated one produces findings and loss of trust. Below we explain the level definitions, what target level 3 requires in practice and how to evidence the level you declare.

The logic of the maturity model

The VDA ISA maturity model is derived from process assessment approaches (ISO/IEC 15504, today the ISO/IEC 33000 series). The model doesn’t measure whether a control exists, but how established the process delivering the control is. The distinction: a rule existing on the firewall is a technical state; managing rules through a cycle of request, approval, review and recording is a process. Maturity scores the second.

In the catalog, each control is defined with an objective and a list of requirements expected to achieve it. Requirements are divided into “must”, “should” and additional requirements for high and very high protection needs. The level is given according to how far and how systematically the relevant requirements are met. If the rule lives with one person, there’s no process.

Level definitions

Level Name Short definition
0 Incomplete No process, not applied, or not fit for purpose
1 Performed An undocumented or partly documented process is applied, with signs that it achieves its purpose
2 Managed A process that achieves its purpose is applied; process documentation and evidence of practice exist
3 Established A standard process integrated into the overall system; interfaces defined, evidence of continuous application
4 Predictable Process effectiveness is monitored with measures, and intervention thresholds are defined
5 Optimizing Continual improvement is the main objective, carried out with dedicated resources

The original wording of the definitions is on the relevant sheet of the catalog; the explanations here are for illustration. Check the catalog version and official text in the current file obtained from ENX or VDA; the version transition is covered in the article the VDA ISA 2027 transition.

What target level 3 means

From an information security compliance perspective, the general target maturity level in TISAX assessments is 3. Level 3 adds three things on top of level 2:

  1. Standardization: The process doesn’t vary by person or department; there’s a single defined method across the organization.
  2. Integration: The process is connected to other processes. Access management is triggered by HR’s joining and leaving processes; risk management feeds into change management.
  3. Sustainability: There’s evidence that the process has been actively applied for some time. A procedure that came into force a week ago, however well written, doesn’t meet this expectation.

The simple test we use in the field: when the process owner goes on leave, does the process keep working the same way, and can records of the last few cycles be shown? If both answers are “yes”, a level 3 claim is defensible. If either is “no”, it isn’t.

Level examples for the same control

Let’s take the periodic review of access rights. The same control may look like this in different organizations:

Level Situation on the ground Typical evidence
1 The IT manager glances over permissions once a year; there’s no written method Verbal description, irregular emails
2 The review procedure is written down, and there’s a record of the latest review Procedure, signed review list
3 All critical systems are reviewed periodically by system owners using the same method; findings are closed via tickets Records of several cycles, ticket closures, link to HR processes
4 The on-time completion rate of reviews and the number of permissions removed are tracked, and action is taken when thresholds are exceeded KPI report, threshold definition, record of action on a threshold breach

In most organizations, the difference between level 2 and 3 lies here: has a practice that works well on one system spread to all in-scope systems? If the review is done for the ERP but not for the file server, the VPN and privileged groups in Active Directory, a level 3 declaration isn’t supported by the records. Evidencing this control is explained in detail in the article access review evidence.

Scoring correctly in the self-assessment

Because the target level is 3, writing 3 against every control is the most common tendency. It comes out immediately in the plausibility check at AL2 and in the on-site review at AL3. The method that works proceeds in this order:

  1. Start from the evidence: For each control, first list the evidence you have, then set the level according to the evidence. No level is declared without evidence.
  2. Mark requirements one by one: If one of the control’s mandatory requirements isn’t met, a level 3 declaration isn’t consistent.
  3. Look at the whole scope: Does the same situation hold in all locations and all in-scope systems?
  4. Use the comment field: Write honestly about partial implementations and ongoing improvements; the auditor prefers an explained level 2 to an unexplained level 3.
  5. Have an independent check done: Having someone other than the process owner review the scoring against the evidence reduces exaggeration.

The catalog’s results sheet calculates a summary result from the scores per control, and in this calculation caps values above the target at the target. Declaring level 4 or 5 in one area doesn’t make up for a gap in another. Write levels 4–5 only if you really have measurement and improvement mechanisms and can evidence them.

Risks of inflated scoring

  • The auditor writes up the inconsistency between declaration and evidence as a finding.
  • The overall credibility of the self-assessment is questioned and evidence requests increase; the assessment takes longer.
  • The organization doesn’t see the areas that need improvement in its own internal plan, and resources go to the wrong place.

How does the auditor verify the declared level?

The audit provider tests the declared level by comparing three sources: the written process, records of practice and the description given by the person running the process. The provider assesses the declared level by the consistency of these three sources.

  • Records against the document: If the procedure says a review every three months, records for the last four quarters are looked for. A frequency inconsistent with the procedure weakens a level 3 claim.
  • Description against the records: The process owner is asked “what did you find in the latest review, and what did you do?” The action visible in the records is expected to match the description.
  • Sampling: The auditor picks a system, a location or a period and checks that the same practice is done there too. Level 3’s emphasis on “organization-wide” is tested at this step.
  • Interface check: The process’s links to the other processes it takes input from and gives output to are asked about; for example, how quickly a leaving record is reflected in access revocation.

This approach also shapes the structure of the evidence file. Instead of a single “best” piece of evidence for each control, prepare the procedure, records of at least a few cycles and interface evidence together; that’s the only way a level 3 declaration can be defended.

Roadmap for raising levels

A realistic self-assessment is the input to the improvement plan and to TISAX assessment preparation. Typical work packages for level transitions:

Migration Work to do
0 → 1 Starting to apply the control at a minimum level
1 → 2 Writing the process down, assigning owners, keeping records
2 → 3 Extending it to the whole scope, connecting it with other processes, running several cycles
3 → 4 Defining effectiveness measures and thresholds, regular reporting

Start prioritizing with controls whose mandatory requirements aren’t met, then move on to the additional requirements brought by the labels you’ve chosen. Moving from 2 to 3 takes time on the calendar; put these controls at the very start of the plan. Cycle records can’t be accelerated. For a realistic starting point, an independent VDA ISA gap analysis and maturity assessment reduces bias in internal scoring. For the general preparation process, see the TISAX preparation guide.

Frequently asked questions

Is target level 3 mandatory for every control?

The catalog defines the general target maturity level for TISAX assessments as 3. Individual controls falling below the target produce findings; the classification of findings and their effect on the label decision depend on the audit provider’s assessment of the findings.

Does declaring level 4 or 5 improve the result?

In practice, no. In the result calculation, values above the target are capped at the target level, and a surplus in one control doesn’t cover a gap in another. High declarations that can’t be evidenced reduce the auditor’s trust in the self-assessment.

What level is a process that works well but has no written procedure?

If it can be shown that it’s applied and achieves its purpose, it’s usually level 1. Level 2 requires the process to be documented and evidence of practice to exist; level 3 expects the process to be integrated into the organization’s overall system and to have been sustained for some time.

How do controls marked not applicable affect the result?

Not-applicable controls whose justification is accepted aren’t included in the scoring. However, the auditor questions the justification; treating a control related to an in-scope activity as not applicable increases the risk of a finding.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles