The TISAX request letter from a customer often has a single line: “We expect AL3.” The supplier takes it for a certificate class and starts preparing, and months later realizes it applied with the wrong objectives. The assessment level determines how deeply the auditor examines evidence and whether they come on site; preparation time, internal resources and cost all follow directly from it. Below, for information security owners and IT managers, we explain from a practical perspective the difference in method between AL1, AL2 and AL3, where the level comes from and the cost of a wrong choice.
What does the level measure?
The yardstick is the same at every level: the VDA ISA (Information Security Assessment) catalog. What changes is the level of assurance with which the controls in this catalog are verified. For the same control list, the level answers the questions “what does the auditor look at, how and where?”
Three levels are defined:
- AL1: A self-assessment carried out by the organization itself. There’s no independent verification; that’s why it doesn’t produce a TISAX label and isn’t used in the TISAX exchange mechanism.
- AL2: A plausibility check of the self-assessment by an audit provider authorized by ENX. Evidence review and interviews are the basis; the default method is remote.
- AL3: Comprehensive verification. In addition to evidence review, there’s on-site review, observation, interviews with employees and direct checking of physical controls.
The level isn’t a grade, it’s a level of assurance. An AL3 result doesn’t show you’re “more successful” than with AL2; it shows the same controls were verified with a stricter method. There’s one more difference: for objectives requiring AL3, the catalog’s additional “very high protection need” requirements also apply. The control scope widens.
AL1, AL2, AL3 comparison table
| Criterion | AL1 | AL2 | AL3 |
|---|---|---|---|
| Who assesses? | The organization itself | Audit provider | Audit provider |
| Basic method | Self-assessment | Plausibility check | Comprehensive verification |
| Evidence review | None | Selected evidence | Detailed, sampled |
| Interviews | None | Usually video conference | On site, with process owners |
| On-site review | None | Not by default | Main method |
| TISAX label | Doesn’t produce one | A label can be obtained for the related assessment objective | A label can be obtained for the related assessment objective |
Don’t underestimate the phrase “selected evidence” in the table. In AL2 the auditor doesn’t ask for every record for every control; they test with representative evidence and interviews whether the maturity level you declared in the self-assessment is credible. If they see an inconsistency between declaration and evidence, they ask for more evidence and write a finding. One inconsistency casts a shadow over the other declarations too.
What determines the level?
The participant doesn’t freely choose the level; it derives from the chosen assessment objective (label). Each label represents a protection need, and the level of assurance that need requires is defined. The general mapping is:
- Objectives for information with high protection needs (“Info high” / current name “Confidential”), high availability and personal data processing (“Data”), and the prototype objectives Test vehicles and Proto events are assessed at AL2.
- Information with very high protection needs (“Info very high” / “Strictly confidential”), very high availability, special category personal data (“Special data”) and the prototype objectives Proto parts and Proto vehicles are assessed at AL3.
The assessment level shows the method and depth of the assessment. The label is linked to the chosen assessment objective and the assessment result; the maturity score in the self-assessment is a separate measure.
Label names may be updated by ENX together with catalog versions. Before applying, verify the current names and level mappings in ENX’s official TISAX documentation. Which customer request corresponds to which label is explained in detail in the article TISAX labels and protection objectives.
In practice the decision chain works like this: the customer’s request letter or the information security annex of the contract says which information will be shared with which protection need; the need corresponds to a label and the label to a level. If the letter says only “TISAX AL3”, you don’t have enough information. Get written confirmation of which label is required.
The plausibility check and remote method in AL2
AL2 starts with the ISA self-assessment the organization fills in. The audit provider reviews the file and the attached evidence, then talks remotely with process owners. There’s one question: is the declared state realistic?
Where the auditor looks
- Is there a written process and record of practice consistent with the declared maturity level?
- Is the evidence current, and does it cover the in-scope locations and processes?
- Can the person interviewed describe the process in their own words, and does the description match the records?
- Is the justification for controls marked “not applicable” defensible?
In remote interviews, a live system demonstration via screen sharing is often requested: opening an access review record in the ticketing system, showing the latest restore test in the backup software, and so on. A mishap you may come across is an email or customer file left open becoming visible unintentionally during screen sharing. Prepare the screens to be shown in advance; details are in the article remote audit preparation.
Don’t think AL2 is easy. The plausibility check isn’t a superficial approval; if you declare maturity at a level the evidence doesn’t support, the auditor re-scores the control and approaches the whole self-assessment more skeptically. AL2 is an evidence-based assessment too. Being remote doesn’t change that.
On-site review in AL3
In AL3 the audit provider comes to the in-scope locations. Document and record review still happens; the real difference is that the auditor verifies controls with their own eyes:
- Physical security: The boundaries of security areas, badge access and its records, the visitor process, and the presence and operation of camera and alarm systems.
- Observation of practice: Behaviors such as clear desk, screen locking and compliance with the no-photography rule in the prototype area are seen on site.
- Random interviews: The auditor may talk not only with process owners but also with staff working on site. This is where it becomes clear whether awareness has stayed on paper.
- Technical verification: Configurations, logs and system reports are reviewed live with a sample the auditor selects.
In AL3 preparation, the most time goes not into technical controls but into organizing the evidence file by location and preparing process owners for interviews. For a structure that matches controls to evidence, start with the evidence matrix method. In multi-site scopes, which location is visited and how depends on the audit provider’s planning based on ENX rules; clarify this in the preliminary meeting.
The level’s effect on the preparation plan
For the same organization, AL2 and AL3 preparation produce different work packages. If you separate the plan by level, internal resources go to the right place.
| Work package | AL2 focus | AL3 focus |
|---|---|---|
| Self-assessment | Realistic scoring, justified explanations | The same, including additional requirements |
| Evidence file | Representative and current evidence | A full set per location |
| Physical security | Declarations and documents | A state that can be shown on site |
| Staff preparation | Process owners | Process owners and site staff |
| Logistics | Video conference setup | Visit schedule, escort, meeting room |
A mistake you may come across in organizations preparing for AL3 is completing the document set and leaving the site to the last week. Retaining badge access records, camera recording periods and keeping the visitor book regularly all require retrospective evidence. A practice started a few days before the audit doesn’t meet the expectation of “applied sustainably”. Past records can’t be produced afterwards.
Consequences of choosing the wrong level
Because the level derives from the label, a “wrong level” actually means a “wrong set of labels”. You pay in both directions.
Under-selection: AL2 objectives while the customer expects AL3
- The result doesn’t meet the customer’s acceptance criterion; the labels shared in the ENX portal don’t include the requested objective.
- An additional assessment is planned for the missing objectives: a new schedule, another on-site visit, extra cost.
- The contract or project start may be delayed; in work involving prototypes, the customer may not share information or parts without the label.
Over-selection: AL3 objectives you didn’t need
- The additional requirements for very high protection needs come into your scope; the preparation burden increases significantly.
- On-site review requires logistics and internal resources for every in-scope location.
- Prototype objectives are tied to all in-scope locations. If a location where no prototype work is done is in the same scope, clarify before registration how it will be handled (a separate scope, excluding it from scope).
Order of checks before applying
- Confirm in writing the label names in the customer’s request letter and the expected date.
- If there’s more than one customer, combine their requests; note the customer that sets the highest need.
- Match the level of each label against current ENX documentation.
- Check whether the in-scope locations are compatible with these labels.
- Review the selection once more with the audit provider in the preliminary meeting.
The TISAX preparation guide gives the framework for the whole process. If you want to settle the choice of labels and level with a preliminary assessment, you can see how we work on the TISAX consulting and assessment preparation page.
Frequently asked questions
Does the auditor never come on site in an AL2 assessment?
The default method for AL2 is a remote plausibility check; evidence is reviewed and interviews are held by video conference. An on-site review can be done if the participant requests it or if the audit provider can’t establish sufficient assurance with the remote method.
Can an AL1 self-assessment be shown to a customer as a TISAX result?
No. AL1 involves no independent verification; it doesn’t produce a TISAX label and isn’t an assessment result shared in the ENX portal. Some customers may separately ask for the completed ISA file, but it doesn’t replace a TISAX label.
Is it possible to get AL2 first and then upgrade to AL3?
It’s possible, but an upgrade means an additional assessment for new assessment objectives; it needs separate planning, cost and time. If it’s known that the customer wants a label requiring AL3, applying directly with the right objectives is usually more efficient.
Can the participant choose the assessment level themselves?
In practice, no. The level derives from the protection need of the chosen assessment objective, that is, the label. The participant chooses which labels to get; the level those labels require follows automatically.