TISAX Reassessment: Preparing Before the Label Expires

Check the label’s expiry, customer expectations and the provider’s schedule together. Verify the ISA version that will apply and set aside time in the schedule for possible corrective actions.
Technical summary
Technology
TISAX, VDA ISA, ENX portal, ISMS
Topic
Planning reassessment before TISAX labels expire
Level
Intermediate
Prerequisites
  • Valid TISAX labels and the previous assessment report
  • A current VDA ISA self-assessment
In this article7 sections

Once the TISAX label is obtained, the project team disperses and the information security agenda goes back to daily operations. When the validity date approaches, the picture is clear: some of the evidence from the initial assessment is out of date, owners have changed, and the catalog version has been updated. Below we explain how to time the reassessment against label validity, how to run the system in the interim, the effect of catalog and scope changes, and a workable preparation timeline.

Label validity and renewal timing

TISAX labels are valid for a limited period; in ENX’s participant handbook this period is generally defined as three years. Verify from which date the period is calculated and how temporary labels affect this calculation from your own assessment report and the current documents of ENX; the validity date is visible for each label in the ENX portal.

The reassessment is registered in the ENX portal as a new assessment and proceeds through steps similar to the initial assessment: registration, scope confirmation, provider selection, assessment and, if needed, a corrective action plan. The real trap is here: if findings come up in the new assessment, time is also needed for the corrective action plan and follow-up assessment. The goal “let the assessment day be before the label expires” isn’t enough. Closing findings must also fit within the validity period. How the corrective action process works is explained in the article TISAX corrective action plan and temporary label.

Using the previous report, and choosing a provider

The previous assessment report is the most valuable input to the reassessment. Topics noted in the report as observations or areas for improvement are where the provider will look first; prepare records showing these were addressed in the interim. The provider can be changed for the reassessment. If you’re considering a change, start the quotation process early; decide under which confidentiality conditions the previous report and finding closure evidence will be presented to the new provider. Even if the provider stays the same, the assessment team may change. This time, support with written evidence the topics described verbally in earlier interviews.

Running the system in the interim

Unlike ISO 27001 certification, TISAX has no annual surveillance assessment during the label’s validity. Nobody pushes from outside; the system must stay standing through its own internal mechanisms. In the reassessment, the provider wants to see not only today’s state but also that controls were operated throughout the period; for target maturity level 3 (“established”), regular operating records are decisive.

Minimum activities to keep up in the interim:

  • Annual internal audit: A program covering all VDA ISA controls within the period; findings tied to the corrective action process.
  • Management review: With agenda items specific to the TISAX scope (customer requests, prototype projects, incidents).
  • Periodic controls: Putting record-producing activities such as access reviews, backup and restore tests, vulnerability scans and supplier assessments on a schedule.
  • Updating the risk assessment: For new systems, new locations and new customer projects.
  • Awareness and confidentiality undertakings: Keeping complete records for new employees and those joining prototype projects.

A link that can break is periodic technical controls. The backup job shows green every night, but the last restore test was done in the week of the initial assessment. A green job isn’t evidence of restore. Vulnerability scanning is the same: the scanning tool runs, reports pile up in a folder, but there’s no record that findings were closed. For every periodic control, keep not the “ran” record but the “result assessed and action taken” record.

Organizations that also hold ISO 27001 certification have an advantage in the interim; by adding TISAX-specific controls to the surveillance audit cycle, they can run both frameworks on the same schedule. For planning the surveillance cycle, the article surveillance audit preparation can also be used from this angle.

The effect of a catalog version change

The reassessment is done against the VDA ISA version valid at that date. Over a three-year period, the catalog is likely to be updated; control numbers, wording and requirement levels may have changed, or new controls may have been added. That’s why resubmitting the initial assessment’s self-assessment file as it is carries risk.

The way to manage the impact is a gap analysis: old and new version controls are mapped, for each changed or added requirement it’s assessed whether the current practice is enough, and gaps are turned into a work plan. Confirm early with the provider which catalog version you’ll be assessed against; during version transitions, ENX may accept more than one version for a certain period. Details of the version transition are covered in the article the VDA ISA 2027 transition.

Scope and organizational changes

Changes in the organization over three years directly affect the scope of the reassessment. Typical changes and their effects:

Change Effect on the reassessment What to do
New location May need to be added to scope Decided by customer request and data flow
Closed location Removed from scope Informing the customer
Request for a new label Additional controls and a level change Prototype or data protection preparation
Moving to a cloud service Supplier and technical controls change Provider assurance and contract evidence
Acquisition or merger New processes and systems Redefining the scope
Change of key personnel Loss of process knowledge Role definitions and a handover record

The scope decision must be made again with the same logic as in the initial assessment. Copying the existing scope automatically can leave out customer work running at a new site. A similar drift happens with a cloud migration: if the file server has moved to SharePoint or another cloud storage, evidence for access control, logging and backup controls now comes from a different console. The old evidence folder is no use. The criteria for the location decision are explained in the article TISAX scope and location selection.

Preparation timeline

The timeline below is an example for planning backwards, taking the label validity date as “T”. Adapt the durations to the organization’s size, the assessment level and the provider’s schedule.

Time Activity Output
T − 12 months Confirming scope and label needs with customers Approved draft scope
T − 10 months Self-assessment and gap analysis against the current catalog Gap list and work plan
T − 9 months Provider quotes and ENX registration Scheduled assessment date
T − 8 to T − 5 months Closing gaps, internal audit Closed gaps, internal audit report
T − 4 months Evidence file and interview preparation An evidence folder per control
T − 3 months Assessment Report and findings, if any
T − 3 months to T Corrective action plan and follow-up Renewed labels

This example leaves a buffer of about three months for a follow-up assessment if findings come up. The narrower the buffer, the greater the risk the label can’t be renewed within its validity. Also allow for providers finding it hard to fit you in during busy periods. The owner and date of each step in the timeline should be entered into the ISMS activity plan, and progress reported regularly in management review.

Change checklist

This list can be used at the start of preparation to ask systematically “what has changed since the initial assessment?”:

  • Has the VDA ISA catalog version changed, and if so, has a gap analysis been done?
  • Has there been an opening, closure or move at in-scope locations?
  • Have customers asked for new labels or a higher level?
  • Has the information security officer, IT manager or any process owner changed, and are role definitions current?
  • Have there been significant infrastructure changes (cloud migration, new ERP/PLM, new external service provider)?
  • Were the actions implemented for the previous assessment’s findings operated throughout the period, and are there records?
  • Have security incidents during the period, and lessons learned, been reflected in the ISMS?
  • Are any policy and procedure review dates overdue?
  • Are confidentiality undertakings and area access records for prototype projects current?

If an owner and date are assigned to each item, the list turns directly into the reassessment work plan. To measure the current state against the current catalog, see our VDA ISA gap analysis and maturity assessment service, and for the renewal process as a whole, our TISAX consulting and assessment preparation service.

Frequently asked questions

Does TISAX have annual surveillance audits like ISO 27001?

No. TISAX labels are valid throughout their validity period without interim assessments; a reassessment is done at the end of the period. Running the system in between depends entirely on the organization’s own internal audit, management review and control schedule.

Can we choose a different audit provider for the reassessment?

Yes. The reassessment is registered in the ENX portal as a new assessment and the provider is chosen again. If the provider changes, plan in advance how the previous report and finding closures will be presented to the new provider.

What happens if the label expires?

The label loses its validity in the ENX portal and customers can’t see the result as valid. If the contract requires a valid label, new projects or data sharing may stop. To prevent this, plan the reassessment early, also allowing for the time a possible corrective action plan would take.

Are findings closed in the previous assessment looked at again?

The assessment covers the whole scope again; the topics of previous findings are included. Records showing that the corrective actions implemented were operated throughout the three years are the strongest evidence that the maturity level has been maintained.

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