TISAX Scope: Standard Scope and Choosing Locations

Which locations go into TISAX scope and which stay out: the difference between standard and custom scope, deciding locations by data flow, and a table for multi-site companies.
Technical summary
Technology
TISAX, VDA ISA, ENX portal, assessment scope
Topic
TISAX assessment scope and the location decision
Level
Beginner–intermediate
Prerequisites
  • The TISAX request from the customer (label and level)
  • The company’s list of locations and data flows
In this article8 sections

Most decisions in a TISAX application can be corrected later; the scope and location decision, however, directly sets the duration and cost of the assessment and whether the customer will accept the result. A narrow scope leaves out the building where customer data is processed. A broad scope stretches preparation by months. Below we explain what standard scope means in practice, by which criterion a location goes into scope, and how multi-site companies can make this decision by looking at data flows.

What does assessment scope mean?

In TISAX, scope defines which of the organization’s processes, resources and locations are examined with respect to the chosen assessment objectives (labels). Unlike the ISMS scope in ISO 27001, the scope here is largely standard; it leaves the organization little room to draw boundaries freely. The real question isn’t “which processes?”. The real question is “which locations?”

Scope is defined in the registration on the ENX portal and is visible to customers along with the result. When a customer opens the result, they see the labels, the assessment level, the scope type and the in-scope locations side by side. So scope isn’t a technical detail between you and the provider; it’s a statement made to the customer. The registration steps in the portal are explained in the article TISAX registration on the ENX portal.

Standard scope and custom scope

ENX publishes a definition of standard scope for TISAX. Under it, the assessment covers all processes, procedures and resources at the in-scope locations that are relevant to the protection goals of the chosen objectives and are the responsibility of the organization being assessed. In practice: once you bring a location into scope, you can’t set aside any process in that building that affects the security of customer information or prototypes by saying “let’s not look at that”.

Feature Standard scope Custom scope
Definition ENX’s fixed scope text A definition narrowed for the organization
Excluding processes Relevant processes can’t be excluded Specific processes or units can be limited
Customer acceptance This is the general expectation Customer approval is uncertain
Recommended use Almost every case Only with written agreement from the customer

A custom scope reduces the preparation burden, which is why it looks attractive. But if the customer doesn’t accept the result, the whole assessment may have to be repeated. Verify the current version of the scope text and the conditions for a custom scope in the participant handbook published by ENX.

Criteria that bring a location into scope

In TISAX, a location is the physical address where the assessed activity is actually carried out; labels apply only to in-scope locations. These questions decide whether a location needs to be in scope:

  • Is customer information processed here? If staff working at this address access drawings, specifications, project documents or test data, the location is a candidate.
  • Are prototypes kept here? If prototype parts, components or vehicles are stored, processed or tested here, even temporarily, the location must be in scope for prototype labels.
  • Are central security processes here? If IT management, identity management, the server room or the information security function is at another address, that location directly affects the security of the in-scope locations.
  • Which address does the customer contract show? If the quote or order was placed with a specific production or engineering location, the customer will look for that address’s label.

Remote working isn’t defined as a separate location; mobile devices and home offices are handled within the processes of the in-scope location. A data center or cloud service run by an external provider is also usually not your location; it’s assessed through supplier management controls.

Really separating an out-of-scope location

Leaving a location out of scope means being able to show that customer data can’t be accessed from that address. In firms using a shared domain, a shared file server and site-to-site VPN, this separation often exists only on paper. A picture you may come across: the sales office is marked “out of scope”, but the office VLAN talks to head office through a flat tunnel and the project share is open to the “Domain Users” group. When the assessment asks “can a user in the sales office open the project folder?”, the answer must come from permission groups, firewall rules and access logs.

If you can’t prove the separation technically, bringing the location into scope is usually cheaper than explaining it to the customer later. Separation on paper isn’t separation. The justification for an out-of-scope location should be kept in the ISMS documentation together with the scope decision.

Decision table for multi-site companies

In a company with several sites, bringing every location into scope increases time and cost; leaving them all out doesn’t meet the customer’s request. The table below gives a starting decision for typical location types. The final decision comes together with the labels the customer wants and the data flow diagram.

Location type Typical decision Reason
Engineering / R&D office Included Where customer data is mainly processed
Prototype production or test site Included Prototype labels are tied to the location
Head office (IT and HR here) Usually included Central control processes run here
Series production site Depends on data flow Included if drawings and project data reach the shop floor
Sales office Usually excluded If there’s no access to technical customer data
Logistics warehouse Included if prototypes are there A series parts warehouse is usually out of scope
External provider’s data center Excluded as a location Handled under supplier management

The series production site is the most debated row. If CAD drawings or customer specifications reach the operator panel at the head of the line, or a PLM client is installed in the production office, the site comes into scope. If only work orders and part numbers reach it, the situation is different. Check this at the terminal on the shop floor, not on paper.

For organizations with a central, mature ISMS and many locations, TISAX also defines methods such as the Simplified Group Assessment instead of fully assessing each location separately. The prerequisites (central management, shared processes, a certain maturity) are strict and may change between versions. Check eligibility with the provider and the current handbook.

How does the customer read the scope?

When the customer sees the result in the ENX portal, they look at three things: is the label they want there, is it at the required level, and does it cover the location where their work is done? If one is missing, the result doesn’t meet the request. The most common problem is the second site where the customer’s project runs being out of scope.

The solution is simple: send the draft scope to the customer before applying. A short email states the location addresses, planned labels and level; get the customer’s written approval. Which label represents which protection objective is explained in the article TISAX labels. For a supplier with several customers, the scope should be the union of the locations requested by all customers.

Scope changes

After the label is obtained, the organization changes: a new site opens, engineering moves to another address, a new customer asks for a prototype label. These changes don’t automatically extend the labels. A new location or new label requires an additional assessment; how this is done and whether validity dates can be aligned must be clarified with the provider.

Closing a location or moving an activity is also a change the customer must be told about; the label of the old address gives no assurance for the activity at the new address. A practical method: add the question “Does this affect TISAX scope?” to the ISMS change management form. When a server move or a new WAN connection comes up for approval, the question comes up in front of you too.

Relationship with ISO 27001 scope

ISO 27001 certified firms tend to copy the TISAX scope from their existing ISMS scope. The two scopes may overlap, but they aren’t built on the same logic: in ISO 27001 the organization sets the scope boundary with justification, while in TISAX it’s set by the standard scope text and the customer’s request. Setting up the ISMS scope is covered in the article defining ISO 27001 scope; for the general differences between the two frameworks, the TISAX preparation guide is the starting point.

Checklist for the scope decision

  • The labels, level and date the customer wants are in hand in writing.
  • The flow of customer data and prototypes has been drawn by location.
  • The addresses of the central IT, identity management and information security functions have been identified.
  • An include/exclude decision and its justification have been written for each location.
  • It has been verified with permission groups and network rules that customer data doesn’t flow to out-of-scope locations.
  • Standard scope has been chosen; if a custom scope is being considered, customer approval has been obtained.
  • The draft scope has been shared with the customer and approved.

To assess the scope and location decision together with customer requests, see our TISAX consulting and assessment preparation service, and for the evidence file of the chosen scope, our TISAX pre-assessment preparation service.

Frequently asked questions

Is it possible to choose a custom scope in TISAX?

Technically, yes. However, because results are shared on the assumption of a standard scope, whether customers will accept a custom scope is uncertain. If you’re considering a custom scope, get written confirmation in advance from the customer requesting the result.

Are home addresses of remote engineers added as locations?

No. Home offices aren’t registered as locations; remote and mobile working is handled within the processes of the in-scope location through policy, technical controls and awareness. The assessment asks how these rules are applied.

Does an outsourced data center become a scope location?

If a third party provides the service, the data center is usually not added as your location; it’s assessed under supplier management controls. Prepare as evidence the provider’s security assurances, contract terms and any certificates or labels of its own.

Can a new location be added after getting the label?

It can, but the new location doesn’t automatically benefit from the existing labels; an additional assessment is needed. Clarify with the audit provider whether this will be a separate assessment or a scope extension, and how validity dates will be aligned.

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