In an IATF 16949 audit, IT is often called into the room on the last day, and the auditor asks one question: “Does your contingency plan cover a cyber attack, and have you tested it?” If the answer is the sentence “IT is notified”, a finding is written. The standard is a quality management system standard; but many requirements, from production planning to shipping and from traceability to record retention, depend on information technology. With the Sanctioned Interpretations (SIs) published by IATF, cyber attacks have also explicitly entered several of the standard’s clauses. Below, the evidence the IT department needs to have ready is gathered clause by clause.
Cybersecurity expectations introduced by the SIs
| SI / Clause | Publication and effective date | Expectation (summary) |
|---|---|---|
| SI 3 · 6.1.2.3 Contingency plans | Revised July 2021, effective from November 2021 | Contingency plans cover cyber attacks on IT systems; their effectiveness is tested periodically (e.g. by simulation). Customer notification, at least annual review, employee training and, after an emergency in which production stopped without the normal shutdown steps being followed, verifying on restart that the product meets the customer specification are part of the plan. The clause doesn’t give a fixed frequency for testing; what’s at least annual is the review of the plans. |
| SI 18 · 7.1.3.1 Plant, facility and equipment planning | October 2019, effective from January 2020 | In plant layout and planning, cyber protection of equipment and systems that support production is applied with a multidisciplinary, risk-based approach. |
| SI 21 · 6.1.2.1 Risk analysis | July 2021, effective from November 2021 | The risk analysis includes, at a minimum, cyber attack threats to IT systems. |
| SI 22 · 7.2.1 Competence | July 2021, effective from November 2021 | Training includes recognizing the signs of attempted cyber attacks. |
The most current SI document for IATF 16949:2016 is dated November 2025: SI 23 was revised and SIs 27–30 were added. SIs 27–30 relate to the foreword, scope (1.1), terms and definitions (3.1) and design and development outputs (8.3.5.1).
What these four SIs have in common: none of them asks for a specific technology. Nobody asks about the firewall brand, the EDR product or the backup software. What’s asked is whether the risk has been identified, whether a plan exists and whether there’s a record that the plan was tried. In other words, IT’s job in the audit isn’t to give a technical presentation; it’s to show evidence.
IT evidence list by clause
6.1.2.1 — Risk analysis
- An up-to-date risk analysis that includes cyber attack scenarios (ransomware, ERP/MES outage, intrusion via remote maintenance access).
- Existing controls and actions for each scenario.
A mistake you may come across is a risk analysis that amounts to a single “computer failure” row added to the quality department’s FMEA table. The auditor wants to see the scenario, the likelihood and impact assessment and the action linked to the scenario. Ransomware and a disk failure on a line PC aren’t the same risk; they belong on separate rows.
6.1.2.3 — Contingency plans
- An IT dependency map of critical production processes (ERP, MES, labeling system, PLC/SCADA, network).
- A contingency plan that includes cyber attack and system outage scenarios; instructions for alternative working (manual labeling, offline shipping lists).
- The customer notification decision and who is responsible for it.
- An exercise or simulation report; measured times, lessons learned and actions.
- A record of at least annual review by top management.
- Product verification steps when restarting production that stopped without the normal shutdown steps being followed; data verification is an additional step Eretek recommends.
The dependency map is the foundation of this list. Which server prints the shipping label, which database is that server connected to, which identity system authenticates the database? A team that has never mapped this chain doesn’t know which system to bring up first during an incident. Keep the map together with the network diagram and application list; make updating it when a new system goes live part of change management. For the structure of a plan with cyber scenarios and the exercise method, see the IATF 16949 cyber attack contingency plan guide.
7.1.3.1 — Plant, equipment and system planning
- A cyber requirements checklist used for new lines, machines or software investments (network connection, remote access, update and support period, backup).
- The production network diagram and evidence of segregation from the office network.
- Approvals and records of machine suppliers’ remote access.
New machines often arrive with the manufacturer’s own remote access modem or cloud connection and are plugged into the network on installation day without anyone asking. On a flat production network, that means a single entry point opens up the whole line. A requirement that isn’t in the purchasing specification won’t come to the table on commissioning day. As evidence of network segregation, an up-to-date export of the VLAN and firewall rule list should be kept together with the diagram. You can identify on site which machines, connections and access on the production network are in scope with a factory OT infrastructure survey.
7.2.1 — Competence and awareness
- Cyber awareness content for office and production staff (phishing, suspicious USB drives, unusual system behavior).
- Attendance records and new employee training.
Content for production staff shouldn’t be the same as for office staff. There are three things a line operator needs to know: what to do when they see an unexpected message on screen, whom to call and which devices not to plug a USB drive into. Short training given at the start of a shift and recorded with a signature is the easiest evidence to show in an audit.
Records and backup
- The backup policy, job reports and restore test records that support the retention of quality records (see backup audit evidence).
A “successful” report from the backup software doesn’t prove restorability. As an example practice, keep a report showing that at least once a year the ERP or quality records database was restored to an isolated environment, the time was measured and the data was checked.
Common IT findings in audits
- No cyber scenario at all in the contingency plan, or one dismissed with the single sentence “IT is notified”.
- No record that the plan has been tested.
- Inability to prove that backups can be restored.
- Cyber requirements not included in the purchasing specification for new machines.
- A risk analysis that doesn’t include IT threats.
None of these findings requires an expensive investment. They’re all about missing records and discipline. Opening these five items as a checklist two months before the audit and matching evidence to each prevents most IT-related findings.
Cooperation between the quality and IT teams
The owner of IATF documentation is usually the quality department; IT is the owner of the evidence. The most effective approach is for the quality management representative and the IT manager to work from a shared evidence list and to plan exercises together. In organizations with TISAX or ISO 27001 work, the same evidence serves all three frameworks.
The setup that works in practice: the evidence list is kept in a single shared folder, by clause number; each row shows the name of the evidence, its owner, last update date and next review date. Before the audit, the quality department opens the list and assigns missing rows to IT. On audit day, the IT representative walks into the room with this list.
Eretek doesn’t carry out IATF 16949 certification and doesn’t take on the whole quality management system; this guide covers the standard’s expectations related to IT and cybersecurity. The current SI text should be followed on the IATF Global Oversight website.
Frequently asked questions
Does the IATF auditor technically test the IT infrastructure?
The IATF audit is a quality management system audit; no technical penetration testing is done. The auditor reviews plans, records, test results and evidence of implementation.
Is a cyber scenario needed for a small site too?
The SIs don’t distinguish by scale; however, the method is scaled to the risk. At a small site, a tabletop exercise and a basic restore test can provide sufficient evidence.
Do customer-specific requirements (CSRs) affect IT?
Yes. Some OEMs’ customer-specific requirements include information security, TISAX or continuity expectations; these should be reflected in the risk analysis and plans.
To prepare your IT evidence before the audit, take a look at our IATF 16949 IT Requirements and Audit Preparation service, and for exercises, our cyber attack and contingency exercise service.