Skip to content
Back to overview Illustration: a vehicle frame in production, connected to a cloud workspace and an assessment seal with three levels
TISAX Automotive Microsoft 365

TISAX and Microsoft 365: what automotive suppliers need to evidence

By , Founder & Managing Director 8 min read

Key takeaways

  • TISAX labels are valid for up to three years. For “Confidential”, the auditor checks the plausibility of your self-assessment against evidence at assessment level 2; for “Strictly confidential”, the auditor verifies comprehensively and on site at assessment level 3.
  • Assessments ordered from 1 January 2027 use the new VDA ISA2027 catalogue. Its main change is stricter supplier management requirements.
  • Microsoft 365 touches, among others, the ISA controls on authentication (4.1.2), access rights (4.2.1), mobile devices (3.1.4), cryptography (5.1.1) and event logs (5.2.4).
  • The target maturity level for each control is 3. That requires evidence that a process has been in use over an extended period. A freshly configured tenant is not enough.

For many automotive suppliers, TISAX starts with an email from a customer: the next order requires a label, often within a few months. At the same time, the company’s IT has long been running on Microsoft 365, managed by an external provider. Management then has to answer two questions: which label do we need, and how much of it can we evidence with our existing Microsoft environment? This article maps the ISA controls to Microsoft 365 features and shows which evidence holds up in the assessment.

What is TISAX, and which label do you need?

TISAX (Trusted Information Security Assessment Exchange) is the automotive industry’s assessment and exchange mechanism, operated by the ENX Association. It is based on the ISA (Information Security Assessment) requirements catalogue, which is maintained by the ENX Working Group ISA and published by the German Association of the Automotive Industry (VDA). After a self-assessment, an approved audit provider carries out the assessment. The result is a label that you share with selected partners through the ENX portal. Labels are valid for up to three years.

The required depth of assessment depends on the label. The TISAX participant handbook maps them as follows:

Label (assessment objective)Assessment level
ConfidentialAL 2
Strictly confidentialAL 3
High availabilityAL 2
Very high availabilityAL 3
Proto parts, Proto vehiclesAL 3
Test vehicles, Proto eventsAL 2
DataAL 2
Special dataAL 3

At AL 2, the auditor checks the self-assessment for plausibility, supported by evidence and an interview with the person responsible for information security. At AL 3, the auditor verifies all requirements comprehensively, including on-site activities. The labels “Info high” and “Info very high” from older assessments were replaced by “Confidential” and “Strictly confidential” with ISA 6. Your customer usually specifies which label you need.

What changes with ISA2027?

ISA 6 applies to assessments ordered since 1 April 2024. In summer 2026, the VDA published its successor, ISA2027; the German version followed in October 2026. ISA2027 applies to all TISAX assessments ordered from 1 January 2027. From now on, a new catalogue will be published every year, named after the year from which it applies. This does not affect the validity of existing labels.

According to ENX, the most important changes concern supplier management. For high protection needs, organisations must place more emphasis on documenting, reviewing and monitoring their suppliers’ compliance with security requirements. For very high protection needs, suppliers are expected to demonstrate their security level with a TISAX label, an equivalent third-party assessment or a supplier audit. ISA2027 also formally defines the phrase “The following aspects are considered”: each listed aspect must be consciously considered, and the implementation decision must be explainable in the assessment. Managers are named explicitly as a target group for awareness training.

For your IT provider this means it is itself a supplier in the ISA sense. Expect it to evidence its security measures.

Which ISA controls affect Microsoft 365?

The table lists the controls from the information security chapter that account for most of the technical evidence in a Microsoft 365 environment. Numbering follows the ISA2027 catalogue.

ISA control (paraphrased)Implementation in Microsoft 365Evidence
1.3.3 Only assessed and approved external IT servicesRestrict user consent to apps, admin consent workflow in Entra IDList of approved enterprise applications, log of consent requests
3.1.4 Mobile IT devices and storage: encryption, access protectionIntune compliance policies requiring BitLocker or FileVault and a device PIN, app protection policies for personal devicesCompliance report in Intune
4.1.2 Secure user accessConditional Access with MFA for everyone, phishing-resistant MFA for administrators, blocking legacy authenticationPolicy export, sign-in logs
4.1.3 User accounts and login informationPersonal accounts, no shared accounts, joiner and leaver processAccount list, inactive account report
4.2.1 Assignment and review of access rightsRoles and groups in Entra ID, access reviews, separate administrator accountsDated review results
5.1.1 Cryptographic proceduresBitLocker, sensitivity labels with encryption, cryptography policyCryptography policy, label policies
5.1.2 Protection during transferSensitivity labels and DLP for external sharingPolicies, DLP reports
5.2.3 Protection against malwareDefender for Business, Defender for Office 365Device protection status
5.2.4 Event logsUnified audit log, Entra sign-in logs, central storage in Log AnalyticsRetention setting, evidence of reviews
5.2.9 Backup and recoveryMicrosoft 365 Backup or a third-party productBackup policy, restore test

Three controls deserve a closer look because their requirements rise with the protection need.

4.1.2 User access. Even for normal protection needs, privileged accounts should be protected with superior methods such as two-factor authentication. For very high protection needs, strong authentication before accessing the data is required. In Entra ID you implement this with Conditional Access and authentication strengths. How to move to phishing-resistant methods is covered in our article on Conditional Access and passkeys.

4.2.1 Access rights. Rights of normal, privileged and technical accounts must be reviewed regularly. For very high protection needs, the ISA mentions shorter intervals, for example quarterly, and encryption at content level so that privileged users cannot access the information either. Access reviews in Entra ID require Entra ID P2 or Entra ID Governance. Without that licence, you document the review manually.

5.1.1 Cryptography. For high protection needs, key sovereignty requirements must be determined and met, particularly where processing is external. Microsoft 365 encrypts data at rest by default with Microsoft-managed keys. If your customer requires your own keys, Customer Key or Double Key Encryption are options. Neither is included in Business Premium.

What does maturity level 3 mean for evidence?

The ISA rates each control on a maturity scale from 0 to 5. The target is level 3, “established”. Level 3 requires a standard process integrated into the overall system and evidence that it has been applied consistently over an extended period.

For Microsoft 365 this leads to a clear recommendation: set up log forwarding, compliance reports and access reviews several months before the assessment. An auditor looking at Conditional Access policies created two weeks before the appointment will find it hard to confirm level 3. A history covering several months with documented deviations is more convincing than a complete but brand-new rule set.

What role does Microsoft itself play?

Microsoft has had its data centre regions, which provide the physical infrastructure for Azure, Dynamics 365 and Microsoft 365, assessed against TISAX by an ENX-accredited auditor, including assessment level 3 with the data protection module. Registered TISAX participants can find the result in the ENX portal. The label applies to Microsoft, not to your company. It helps with the controls on external IT services, such as 5.3.4 on protecting information in shared external IT services and 6.1.3 on dividing responsibilities. Configuring your tenant remains your task.

Next step

Our Conditional Access service implements the requirements of 4.1.2 in a way you can evidence. For mobile devices, encryption and malware protection under 3.1.4, 5.1.1 and 5.2.3, we build your endpoint security with Intune and Defender together with you.

Book an introductory call

Frequently asked questions

Is Microsoft 365 Business Premium enough for the “Confidential” label?

The licence contains most of the technical tools you need for AL 2: Conditional Access, Intune, Defender for Business and sensitivity labels. Gaps remain in access reviews and privileged access, which require Entra ID P2, and in log retention. TISAX assesses processes, not licences, though. Without policies, responsibilities and a track record you will not reach maturity level 3, even with the best licence.

Which catalogue will our assessment use?

The order date decides. Assessments ordered from 1 January 2027 use ISA2027; those ordered earlier use ISA 6. If you order around the turn of the year, check which catalogue applies to you.

Does Microsoft’s TISAX label also cover us?

No. The label refers to Microsoft’s data centre regions. Your own assessment covers your locations, processes and the configuration of your tenant.

Does our IT provider need TISAX as well?

The ISA requires you to subject providers to a security assessment and to define responsibilities. Under ISA2027, suppliers handling information with very high protection needs are expected to demonstrate their security level with a TISAX label, an equivalent third-party assessment or a supplier audit. A label of their own is therefore not mandatory in every case, but reliable evidence is.

Let's talk about your IT security

In the introductory call (30 minutes, no obligation) we clarify:

  • where your company stands today and what concerns you most
  • which next step makes sense for your organisation
  • what effort and price range to expect
Bastian Wenske

Bastian Wenske

Founder & Managing Director

Heidelberger Straße 15
12059 Berlin
Germany

Prefer to reach out directly? Send us an email at [email protected].