Guide
TISAX for IT Service Providers & SaaS Companies
Why IT service providers need TISAX: scope definition, cloud requirements, and the path into the automotive supply chain.

Why IT service providers need TISAX: scope definition, cloud requirements, and the path into the automotive supply chain.
Why IT Service Providers and SaaS Companies Need TISAX
A customer wants to process development data in your SaaS or outsource part of its IT operations. It needs to judge whether you provide the required security. A TISAX result may be a contractual requirement. Required labels depend on activities, protection needs and the customer agreement, not simply on being an IT provider.
Clarify evidence requirements before quoting: which service is involved, which data or production processes depend on it, and when is the result needed? This makes TISAX part of engagement planning rather than a late procurement surprise.
Scope Definition for IT Service Providers
Scope definition is particularly important for service providers — and often trickier than for traditional suppliers. The scope must clearly delineate what is assessed and what is not.
What Is Typically in Scope
- Systems and data: processing, storage and transfer, including backups and administration.
- People and processes: operations, development, support and supporting security processes.
- Locations: actual service delivery and relevant infrastructure; address mobile work in the security design.
- Dependencies: cloud providers, data centres and subcontractors, plus your own responsibilities.
What not to exclude prematurely
- HR can be security-relevant because it initiates joining, role changes and departures.
- Central administration may operate multiple customer systems and form part of the security dependency.
- Shared infrastructure remains relevant even where data is logically separated.
Describe the boundary so the customer and provider understand the service covered. A restricted scope must support the required statement. Clarify location registration specifically; not every home office automatically becomes a separate assessment location.
Cloud and SaaS-Specific Requirements
Multi-Tenant Architecture
SaaS providers with multi-tenant architecture face particular challenges: How do you ensure that OEM data is isolated from other tenants? The auditor checks: logical data separation, tenant isolation at the database and application level, access controls between tenants, and demonstrability of the isolation.
Demonstrated tenant isolation is an important safeguard, but does not automatically restrict the assessment scope to one customer. Shared administration, infrastructure, development and continuity processes may remain relevant.
Dedicated Environments
Dedicated systems can make technical boundaries clearer. Still review supporting processes: who administers them, where are backups created, and which shared services are used? A dedicated database does not make the rest of the organisation irrelevant.
Data Center Location
TISAX does not universally mandate EU hosting for all information. Consider customer contracts, protection needs and applicable law. International transfers of personal data require separate assessment under GDPR rules. The privacy guide explains roles and objectives.
TISAX as a Competitive Advantage
A suitable, shared assessment result can satisfy a specific customer security requirement. Its value depends on whether scope, objectives and validity fit the requested service. It does not guarantee a contract.
- Clarify customer requirements early and reflect them in the offer.
- Share results deliberately for the relevant scope.
- Check whether existing labels still fit when services change.
- Track dependencies on your own suppliers throughout operations.
Typical Timeline for IT Service Providers
Technical experience may help implementation. It does not itself demonstrate clear ownership, sustained processes or suitable evidence. Establish the actual starting point before promising a completion date.
| Phase | What determines effort |
|---|---|
| Scope and registration | Customer requirements, locations and services involved |
| Gap analysis | Existing processes and verifiable evidence |
| Implementation | Technical changes, contracts, training and approvals |
| Assessment | Provider, evidence and possible findings |
A maintained ISO 27001 ISMS may reduce preparation effort. A gap analysis identifies reusable work. Plan internal hours and external services separately; the cost guide supports budgeting.
Typical Labels for IT Service Providers
Assess labels against your specific service:
- Confidential or Strictly confidential: protection needs of the information processed.
- High availability or Very high availability: consequences of interruption for the customer.
- Data or Special data: processor relationship and categories of personal data.
AL3 may be required for very high availability, strictly confidential information or Special data. Providing SaaS, hosting or support does not determine the level by itself. The level guide explains the mapping.
The complete step-by-step guide for TISAX preparation is available in our TISAX checklist .
Enter the automotive supply chain as an IT service provider
Our TISAX page shows how to turn customer requirements into a work plan and maintain evidence during implementation. Individually agreed support is available where needed.
Sources and reference date
Reviewed on 13 November 2026 using the ENX participant handbook and ISA 6, including the transition to ISA 2027.