The IT team of an IATF 16949-certified supplier is usually ready for the standard’s own clauses. What causes problems in audits is customer-specific requirements (CSRs). A single sentence in an OEM’s quality manual can mean a new retention period, an information security label or an EDI connection expected to run without interruption for IT; and usually nobody from IT has read that sentence. Below we explain how to read CSR documents from an IT perspective, pick out the obligations and turn them into a trackable action list.
What a CSR is and how it relates to IATF
Customer-specific requirements are the full set of rules an OEM or higher-tier supplier expects from its suppliers in addition to IATF 16949. IATF 16949 doesn’t leave them optional: clause 4.3.2 requires CSRs to be evaluated and included in the scope of the quality management system. If the auditor sees you don’t meet a CSR that applies to your customer, they write it up as a breach of the standard. The defense “that’s this customer’s manual” doesn’t work.
From an IT perspective, CSRs have three characteristics:
- They’re scattered: They aren’t in a single document; they may be spread across the quality manual, supplier portal announcements, the logistics manual, general purchasing terms and contract annexes.
- They change: OEMs revise their CSR documents; the new version is often published only on the portal, and nobody gets an email.
- They flow down the chain: IATF 16949 clause 8.4.3.1 requires statutory and regulatory requirements and special product/process characteristics to be passed on to suppliers and cascaded down the supply chain; many OEM CSRs also require their own requirements to be passed on to sub-suppliers. If you’re Tier 2, requirements reach you both from your direct customer and from the OEM requirements it passes down.
The list of CSR documents of IATF-recognized OEMs, with links, is published on the IATF Global Oversight website. But not all customers are on this list, and contract-based additional requirements don’t appear there either. The list is a starting point, not an inventory.
Typical CSR topics that concern IT
CSR text is written for the quality team; the IT obligation is left between the lines. A paragraph that never mentions “information security” may be defining a notification deadline for EDI outages. Look for these topics as you read:
Information security and confidentiality
Some OEMs ask for evidence of a certain level of information security: a TISAX label, an ISO 27001 certificate or completion of their own security questionnaires. For suppliers working with prototypes or customer drawings, this requirement is stricter. If the requirement came as a questionnaire, the article automotive customer information security questionnaires explains how to answer; if a TISAX request came in, the article TISAX requests in the supply chain explains the process. You can identify on site which machines, connections and access on the production network are in scope with a factory OT infrastructure survey.
Electronic data interchange and portals
Specific EDI standards (for example EDIFACT DELFOR/DESADV, VDA messages, ANSI X12) and transmission protocols (for example OFTP2, AS2) may be required for delivery schedules, shipping notices, invoices and quality notifications. The CSR may also define how quickly EDI messages are processed, or how far ahead of shipment the shipping notice is sent. These times turn directly into a system availability requirement. If the EDI server stops overnight, the morning shipment goes out without notification.
Record retention
IATF’s general rule is the time the part is active plus one year; CSRs may define longer fixed periods for certain records. This information must be passed into the archive’s retention rules. How to apply it is in the article archiving PPAP and quality records.
Emergencies and continuity
IATF 16949 clause 6.1.2.3 requires contingency plans to cover cyber attacks on information technology systems as well. CSRs may add rules such as a customer notification deadline, an alternative communication channel or supply interruption notification. If ransomware has taken out the email server too, the channel you’ll use to reach the customer must be written down in advance. For the plan and exercise side, see the article IATF 16949 cyber attack contingency plan.
Engineering data and software
In what format customer CAD data is received, through which channel it’s shared and how it’s returned at the end of the project, along with software development process expectations for products containing embedded software, sit under this heading. A customer drawing shared from an engineer’s personal cloud account is the typical breach of this clause on the ground.
CSR–IT action mapping table
The output of reading the CSRs is a mapping table. Each row shows a CSR clause, how it reflects on IT, the owner and the evidence. The rows below represent typical findings; the clause numbers will come from your customer’s document.
| CSR requirement | IT action | Evidence | Owner |
|---|---|---|---|
| Information security label/certificate | Scoping, control gap analysis | Label/certificate, action plan | ISMS owner |
| Specific EDI messages and protocol | EDI infrastructure, certificate management, monitoring | Test records, error monitoring report | IT applications |
| Shipping notice deadline | Availability target, alarm, fallback procedure | Outage records, manual procedure | IT infrastructure |
| Extended record retention | Update to the archive retention rule | Retention matrix, archive configuration | Quality + IT |
| Outage/crisis notification | Customer communication step in the contingency plan | Plan revision, exercise record | IT manager |
| Portal use | User and permission management, closing on exit | Review of the portal user list | Quality + IT |
The table doesn’t close anything on its own. The closure status of each row must be tracked. In practice, each row of the table becomes a record in your action tracking system (corrective action tool, work tracking system or ISMS action list). A row without an owner and a target date comes back as the same finding in the next audit.
Customer portals and EDI access management
OEM portals (supplier portal, quality notification system, engineering data exchange platform) usually aren’t in the IT inventory. The quality, logistics or purchasing team opens users itself. The result is three familiar risks:
- Leavers: A user closed in the corporate identity system keeps an open account on the external portal.
- Shared accounts: A single “quality@” account used by several people makes it unclear who gave the approvals on the portal.
- Orphaned notifications: A CSR revision or quality notification from the portal lands in the email inbox of someone who’s no longer at the company.
The control is simple: keep an inventory of external portals. Portal name, customer, function, account owners, notification email address (a role-based distribution list, not a personal one) and last review date. This inventory is linked to the leaver checklist and the periodic access review. The article access review evidence explains how to document the access review as evidence.
On the EDI side, the most often overlooked point is certificate expiry. OFTP2 (RFC 5024) and AS2 connections use certificate-based authentication and encryption. When the certificate expires, the message flow stops and delivery schedules don’t arrive; the error is often first noticed in logistics as “no call-offs this week”. EDI certificate expiry dates must be added to the monitoring system, and the renewal schedule shared with the other party in advance. Sending the new certificate to the other party on the last day doesn’t work; they need time to put it into service too.
Tracking CSR changes
IATF 16949 clause 7.5.3.2.2 requires a documented process for reviewing changes to customer engineering standards and specifications, and requires this review to be completed within 10 working days at the latest. The clause is written for engineering specifications; but in practice, tracking CSR changes with the same discipline is also necessary.
The minimum structure is set up like this:
- CSR register: For each customer, the applicable CSR documents, revision numbers, publication dates and source (portal path or link).
- Change monitoring: An owner who checks portals periodically, and a role-based mailbox where portal notifications land.
- Difference analysis: Listing the clauses that changed in the new revision; most OEMs publish a revision history table, and if not, a text comparison with the previous version is done.
- Impact assessment: Answering “Is there an IT impact?” for each changed clause and, if necessary, adding a new row to the mapping table.
- Closure: Recording the assessment date and the decision.
Once this structure is in place, when the auditor asks, “When was the latest revision of this CSR published, and when did you assess it?”, the answer comes from a single record. If it isn’t, the answer is searched for in a pile of emails.
Showing CSR compliance in an audit
In IATF audits, auditors usually sample relevant CSRs from the organization’s customer list and ask how they’re met in processes. On the IT side, these should be on the table:
- An up-to-date CSR list per customer and its revision status
- The CSR–IT mapping table and closure evidence for each row
- A record showing CSRs are covered in the internal audit program (clause 9.2.2.2 requires customer-specific QMS requirements to be sampled along with quality management system audits)
- The external portal inventory and the last access review
- EDI connection and certificate monitoring records
- If there’s an information security requirement, the label or certificate and its validity date
Considered together with the standard’s general IT evidence set, the CSR mapping table becomes one of the central documents of IATF IT preparation. The general framework is in the article IT evidence in the IATF 16949 audit. To derive IT obligations from CSRs and prepare for customer information security audits, you can use our IATF 16949 IT requirements consulting and automotive supplier information security services.
Frequently asked questions
Where can CSRs be found?
CSR documents of IATF-recognized OEMs can be found from the list on the IATF Global Oversight website and from OEMs’ supplier portals. Contracts, purchasing terms and your direct customer’s quality manual may also contain CSRs; all of them should be gathered in a single register.
Is a Tier 2 supplier responsible for OEM CSRs?
Not directly, but through flow-down. IATF 16949 clause 8.4.3.1 requires statutory and regulatory requirements and special characteristics to be passed down the supply chain; many OEM CSRs also require their own requirements to be passed on. That’s why a Tier 2 supplier is subject to its direct customer’s requirements and the OEM requirements that customer passes down. Clarify in writing with your direct customer which CSRs apply.
How quickly should we assess CSR changes?
IATF 16949 clause 7.5.3.2.2 gives a maximum of 10 working days for customer engineering standards. If the customer specifies a period for the CSR document, follow it; if not, define a similar period as an internal rule and track it on record.
Does a CSR with no information security requirement still affect IT?
Yes. Topics such as EDI and portal use, record retention periods, emergency notification and sharing engineering data create direct obligations on IT systems and processes, even if the words “information security” never appear in the text.