TISAX Corrective Action Plan: Closing Findings and the Temporary Label

If you have a TISAX finding: an accepted corrective action plan row, temporary label conditions, a realistic target date and presenting evidence in the follow-up assessment.
Technical summary
Technology
TISAX, VDA ISA, ENX portal, corrective action plan
Topic
Closing TISAX findings through the corrective action plan and temporary label process
Level
Intermediate
Prerequisites
  • A completed initial TISAX assessment and list of findings
  • A good command of the VDA ISA self-assessment
In this article8 sections

If findings came up in the TISAX closing meeting, the problem isn’t the finding itself but the plan written afterwards. The audit provider sends back a weak corrective action plan; the temporary label is delayed and the date promised to the customer is missed. Below, for information security owners and TISAX project managers, we explain through mistakes we see in the field how finding classes affect the label, the structure of a plan row the provider accepts, the temporary label conditions and how to present evidence in the follow-up assessment.

Types of finding and their effect on the label

In the assessment report, the situation found for each VDA ISA control is recorded with the provider’s classification. This class determines the route by which the label is issued. The table shows the general logic; the binding definitions are in ENX’s participant handbook.

Type of finding Meaning Effect on the label process
Major nonconformity The requirement is systematically not met, or the protection objective is directly at risk Blocks the temporary label; a plan and follow-up assessment are mandatory
Minor nonconformity The requirement is partly met; there’s a single or limited deviation A temporary label is possible with an accepted plan; a follow-up assessment is needed
Observation Not yet a nonconformity; a trend that carries risk Doesn’t block the label; looked at in the next assessment
Area for improvement The requirement is met, but could be applied better No effect; advisory in nature

The logic is similar to the major–minor distinction in ISO 27001 certification; the difference is that in TISAX a finding is tied directly to a label and a deadline. For general classification principles, see the article major vs minor nonconformity. Look not at the count but at which label the finding relates to. A single major finding in prototype protection controls can hold up the prototype label even if it doesn’t prevent the information security label from being issued temporarily.

A mistake you may come across is leaving the closing meeting without fully understanding what a finding says. A misunderstood finding turns into a wrong plan. In the meeting, ask for each finding “which record or observation led to this conclusion?” and note the answer.

Flow from the initial assessment to the permanent label

  1. Initial assessment and closing meeting: The provider shares the findings and their classes. Clarify the reasoning behind each finding here.
  2. Submitting the corrective action plan: A plan with the root cause, action, owner and date for each finding goes to the provider.
  3. Plan assessment: The provider looks at whether the plan will really resolve the finding and whether the dates are reasonable. It asks for revisions if needed.
  4. Temporary label: If the conditions are met, a temporary label is published in the ENX portal and can be shared with customers.
  5. Implementation period: Actions are put into practice and evidence builds up.
  6. Follow-up assessment: The provider verifies that the actions were implemented and worked; if the findings close, the permanent label is published.

ENX defines a maximum period that may elapse from the initial assessment to the end of the follow-up assessment; in known versions of the handbook this period is nine months. Because the period and conditions can be updated, check ENX’s current documents and the information in the ENX portal before building your schedule. The schedule is built around this period. Not the customer’s date.

Content of the corrective action plan

The provider accepts the plan only when every row makes the finding understandable on its own and the link between the action and the finding is clearly visible. One-line rows ending with “the procedure will be updated” will very likely come back. Below is a sample plan row for a minor finding about access rights; verify the control number against the VDA ISA version you use.

Finding No    : F-07 (Minor)
ISA control   : 4.2.1 Management of access rights
Finding       : Project folder permissions on the engineering file server
                are not reviewed periodically; group membership of 2
                leavers is still active.
Root cause    : Review responsibility not defined; the HR leaving
                notification doesn't cover file server permissions.
Correction    : Group memberships of the leavers removed (date, record no).
Corrective action:
  1. Assign owners to project folders (project manager)
  2. Add file server groups to the leaving workflow
  3. Start a quarterly permission review record
Owner         : IT Infrastructure Manager / Engineering Manager
Target date   : Actions 1-2: 6 weeks, Action 3: first quarterly record
Evidence      : Owner list, current workflow screen and test record,
                signed first review report
Effectiveness : No active membership of leavers found
                in the second review

Three elements do the work in this row. First, separating correction from corrective action: closing the two accounts resolves the finding today, but tomorrow the same picture recurs with a third leaver. Second, the root cause: it must point to the process, not the person. “The system administrator forgot” isn’t a root cause. For root cause analysis, the 5 Whys application in the root cause analysis in corrective action guide works exactly the same for TISAX findings. Third, the evidence definition: writing at the planning stage what will be shown at follow-up cuts off the later debate about “is this enough?”.

For technical findings, the first place to look in the console to find the root cause is often not the configuration itself but the process that triggers the change. As in the example, leavers staying in a file server group recurs even when the Active Directory account is closed, if local groups or separate permission tables on the NAS aren’t tied to the HR workflow.

Temporary label conditions

A temporary label tells the customer: the findings are known and are being closed with an accepted plan. It’s a time-limited result. For it to be issued, these conditions are generally required:

  • No open major nonconformity within the scope of the relevant label,
  • A corrective action plan submitted for all minor nonconformities and accepted by the audit provider,
  • Plan dates staying within the maximum duration of the TISAX process.

For a major nonconformity, the ENX handbook defines a separate route: measures that temporarily reduce the risk (interim or compensating) are applied, and if the provider accepts, the finding can be downgraded to minor. If a badge access system is missing in the prototype area, a security guard keeping a log until the system is installed could be such a measure. An interim measure doesn’t replace the permanent action. The plan must contain both.

Planning implementation time

The most common planning mistake is writing the action’s duration by counting back from the desired label date, not according to the technical workload. A realistic duration covers purchasing, change approval, implementation and evidence of at least one operating cycle. The table below shows what sets the duration for typical action types and when the evidence matures; durations vary by organization.

Action type Factors that set the duration Evidence maturity
Document/role definition Preparation and management approval Approved version, announcement record
Starting a periodic control Completion of the first cycle At least one completed record
Technical configuration Change approval, testing, maintenance window Configuration report, test result
Physical arrangement Purchasing, installation, authorization On-site observation, access records
Supplier contract The other party’s legal approval Signed contract or additional protocol

Example calculation: purchasing six weeks, installation two weeks, access records building up four weeks. This physical security action needs a target date of about three months. Instead of tying the document actions in the same plan to this date, bring them forward; the number of findings closed at follow-up goes up. If you want the follow-up done in one go, gather the target dates of all actions before a single evidence delivery date.

For technical configuration actions, write the maintenance window into the plan from the start. If a firewall rule or permission model change is squeezed into the single weekend when the production line can stop, missing that date makes the whole plan slip. Dates need buffers.

Follow-up assessment and presenting evidence

At follow-up, the provider looks for answers to two questions: was the action implemented, and has the cause of the finding gone away? Document and configuration evidence answers the first; operating records answer the second. The method is affected by the assessment level: at AL2 most evidence can be reviewed remotely, while physical and prototype findings under AL3 usually need to be seen on site. The difference in method between levels is explained in the article TISAX AL1, AL2 and AL3 differences.

Arrange the evidence package by finding number: for each finding, the plan row, a summary of the root cause, the actions implemented, the evidence files and the effectiveness indicator. Use a dated system report instead of a screenshot, and an approved version instead of an unsigned draft. If you’re presenting PowerShell or other system output, the date the command was run and the server name should be visible in the output. Check the confidentiality class of documents to be sent; instead of sending the whole of a document containing prototype data, you can present the relevant section with the rest masked.

Before the follow-up, also review the topics noted as observations in the initial assessment. They don’t become findings at follow-up, but they’re the first places looked at in the reassessment. For how findings are reflected in maturity levels, the article VDA ISA maturity levels is a complement.

Common mistakes

  • Writing the inverse of the finding as an action: “Permissions will be reviewed” is the inverse of the finding, not an action.
  • Leaving the root cause field empty: The provider won’t be convinced that a problem with an unknown cause will be solved permanently.
  • The same name on every row: If the information security owner’s name appears on every row, the provider questions capacity.
  • Presenting an interim measure as a permanent solution: A compensating measure is a stopgap; the permanent action and its date must be written separately.
  • Leaving evidence to the last week: The record of a periodic control builds up over time. Evidence collected in the last week doesn’t show effectiveness.
  • Forgetting other locations: If the process fixed at one location works the same way at others, rolling the fix out should be in the plan.

For root cause analysis and evidence structure, see our post-audit nonconformity closure and corrective action consulting, and for the assessment process as a whole, our TISAX consulting and assessment preparation services.

Frequently asked questions

Can a temporary label be obtained while there’s a major nonconformity?

As a rule, no. A temporary label is issued only when only minor nonconformities remain and the corrective action plan has been accepted. The ENX participant handbook defines a route by which a major finding can be downgraded to minor with accepted interim measures; verify the conditions in the current handbook and with your audit provider.

Is a temporary label worth the same to the customer as a permanent label?

A temporary label can be shared in the ENX portal and many customers accept it as valid; however, it’s visible that it’s time-limited and tied to a follow-up assessment. Ask in advance whether your customer accepts the temporary label for contractual purposes.

Is the follow-up assessment always done on site?

No. The method is set by the assessment level and the nature of the finding. Findings that can be closed with documents and records can be verified remotely; findings relating to physical security or the prototype area, especially under AL3, usually need to be seen on site.

What happens if we miss the date we gave in the plan?

The plan date is your commitment; the provider plans the follow-up assessment around it. Tell the provider as soon as you notice a delay. If the follow-up can’t be completed within the maximum duration of the TISAX process, the validity of the temporary label and the assessment result is at risk; verify the consequences in the current handbook and with your provider. Give dates based on real capacity.

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