Supplier information security assessment breaks down in practice in two ways: either it isn’t done at all, or every supplier gets the same 200-question form. The second looks good in the file. Most answers go to the archive unread, the team gets tired, and the time that should go to the supplier that actually accesses your source code or production database is spent clearing paperwork. The solution is simple but takes discipline: put suppliers into tiers by data access and criticality, choose the right depth for each tier, and link the result to the contract and the monitoring cycle.
In the standard, the topic corresponds to controls 5.19 (information security in supplier relationships), 5.20 (addressing information security within supplier agreements), 5.21 (managing information security in the ICT supply chain) and 5.22 (monitoring, review and change management of supplier services) in ISO/IEC 27001:2022 Annex A; for cloud services, 5.23 also comes in. The topic here is the supplier’s information security risk. Service disruption and dependency risk is a separate topic; for that, see the article business continuity with critical suppliers.
1. Supplier inventory and classification
Assessment can’t start without knowing whom you’ll assess. The vendor list in the purchasing system isn’t enough for this. SaaS subscriptions bought by credit card, cloud tools departments set up themselves, machine manufacturers’ remote maintenance connections and freelance developers hardly ever appear on that list. Build the inventory by combining several sources: purchasing records, accounting payments, firewall and VPN access lists, enterprise application registrations in the identity provider (for example the enterprise application list in Microsoft Entra ID) and interviews with departments.
In the field, most surprises come out of the firewall rule table. A remote access rule described as “temporary”, with no record of who opened it, often belongs to a supplier that isn’t on the list.
Collect these fields for each supplier:
- Service description: What does it provide, and which process does it support?
- Data access: Which class of data does it see, process or store (personal data, special category personal data, customer engineering data, financial data)?
- System access: Does it connect directly to the network, servers or applications; does it use privileged accounts?
- Criticality: If the service stops, which process is affected and how quickly?
- Subcontractors: Does the supplier pass data to another party (hosting, a support center)?
- Business owner: Who in the company is responsible for the relationship?
Don’t leave the business owner field empty. The information security team carries out the assessment according to the corporate information security risk assessment method; but it’s the business unit that manages the contract, talks to the supplier and follows up remediation. A finding with no owner doesn’t get closed.
2. Assessment depth by tier
Two axes are enough for classification: the sensitivity of data and system access, and the business criticality of the service. Combining the two, a four-tier model works well in practice. The table below is an example setup; adapt it to your own risk acceptance criteria.
| Layer | Typical profile | Assessment method | Reassessment |
|---|---|---|---|
| T1 – Critical | Processes sensitive data or has privileged access to infrastructure; its disruption stops the core process | Comprehensive questionnaire + evidence request + on-site or remote audit if needed | Once a year and on significant change |
| T2 – High | Accesses personal or confidential data, or has limited system access | Comprehensive questionnaire + selected evidence | Once a year |
| T3 – Medium | Sees limited internal data, no system access | Short questionnaire | Every two years |
| T4 – Low | No data or system access | Security declaration and contract clauses | At contract renewal |
Don’t leave tier assignment to one person’s intuition. Use a pre-screening form of three or four questions: “Will the supplier process personal data?”, “Will access to our network or cloud tenant be needed?”, “If the service stops for more than a day, is customer delivery affected?”, “Will data the customer has classified as confidential be shared?”. The combination of yes answers sets the tier. That way the purchasing team can predict the tier correctly on its own, and onboarding a new supplier doesn’t get stuck for weeks waiting for information security approval.
3. Questionnaire design
Ready-made question sets are a good starting point. The Cloud Security Alliance’s CAIQ (Consensus Assessments Initiative Questionnaire) is widely used for cloud services, and Shared Assessments’ SIG (Standardized Information Gathering) for suppliers in general. In the automotive supply chain, the common language is the VDA ISA question catalog. Don’t send these sets as they are; shorten them by tier and adapt them to your own risk.
Rules for a form that works:
- Closed question + evidence field: Instead of “Do you have access management?”, write “Is multi-factor authentication mandatory for privileged accounts? (Yes/No/Partly) — Evidence: policy clause or configuration screen”.
- Service-specific questions: Asking a remote maintenance supplier about backups, or a SaaS provider about physical security, lowers answer quality. Split the form into modules: corporate governance, access, data protection, development, hosting, incident management, subcontractors.
- Weighting: “Incident notification time commitment” and “security awareness training” don’t carry the same score. Mark critical questions as “knock-out questions”; a no answer produces a finding regardless of the total score.
- A “partly” option with a mandatory explanation: A yes/no choice pushes the supplier to say “yes”. Make the explanation field mandatory when “partly” is selected.
- Responsible person and date: Record who filled in the form and on what date, so the answers can be referenced in the contract.
Around 60–120 questions for T1 and T2 suppliers and 15–25 for T3 is a manageable range in practice. This isn’t a rule, it’s a starting suggestion based on team capacity. The measure is simple: someone must be able to actually read every form you send and reach a decision. An unread form doesn’t reduce risk.
4. Evidence requests and assessing certificates
The questionnaire is a declaration; evidence verifies the declaration. For T1 and T2 suppliers, ask for evidence for every knock-out question. When a supplier presents a certificate or assurance report, carry out these checks:
| Document | What to check | Common problem |
|---|---|---|
| ISO/IEC 27001 certificate | Scope statement, locations, validity date, accredited certification body | The scope covers only the head office; the data center or team serving you is outside it |
| SOC 2 Type 2 report | Observation period, system in scope, exceptions, subservice organizations, CUEC list | Only the summary page of the report is read; the auditor’s exceptions are skipped |
| TISAX label | Assessment level, objectives, scope, validity (verification in the ENX portal) | The label belongs to another location |
| Penetration test summary | Test date, scope, closure status of critical findings | A report more than a year old, or only an executive summary |
The point most often missed is certificate scope. A supplier being ISO 27001 certified doesn’t mean the service it provides to you is within the certification scope. Read the scope sentence. In SOC 2 reports, the “complementary user entity controls” (CUEC) section lists controls expected to be implemented on your side; if you don’t implement them, the assurance the report gives is incomplete. For details of the report structure, see the SOC 2 readiness guide.
For small suppliers without certificates, the evidence request should be more concrete: a screenshot of the MFA policy, the latest access review record, a backup restore test record, a summary of the latest incident response exercise. A supplier avoiding sharing evidence is itself an assessment input. Record it.
5. Linking results to the contract and actions
An assessment that doesn’t turn into a decision is just file clutter. Every assessment should close with one of these four outcomes:
- Approval: No significant findings; standard contract clauses are enough.
- Conditional approval: There are findings; a dated remediation plan is obtained from the supplier and the plan is tied to the contract or an additional protocol.
- Approval with compensating controls: The supplier can’t fix the gap; you reduce the risk on your side (such as giving access through a jump server that records sessions, or limiting data sharing to masked data).
- Rejection or risk acceptance: If the risk is above the acceptance threshold, the supplier isn’t used, or the authorized risk owner accepts the residual risk in writing.
For the last option, who holds acceptance authority must be defined in advance; details are in the article risk acceptance criteria.
Minimum information security clauses to carry into the contract: the confidentiality obligation, the purpose and location of data processing, prior notice or approval for using subcontractors, incident notification time, the right to audit and request evidence, return or destruction of data at the end of the contract with proof of destruction, and closure of access accounts. For suppliers processing personal data, the data controller–data processor relationship and technical/organizational measures under KVKK (Law No. 6698) must be set out in the contract. For suppliers working through remote access, such as machine manufacturers or integrators, the technical design of the connection is a separate job; a permanently open VPN tunnel carries more risk than any clause in the contract. For this, see the guide secure supplier remote access.
6. Periodic reassessment and monitoring
A one-time assessment is a snapshot of the supplier on that day. Set up the monitoring cycle with three triggers:
- Calendar: Reassessment at the frequency in the tier table.
- Change: Expansion of service scope, sharing a new type of data, acquisition or merger of the supplier, a change of subcontractor, a change of hosting location.
- Incident: A security incident at the supplier, a publicly disclosed data breach or an announcement that the service is affected by a critical vulnerability.
For these triggers to be caught, the obligation of purchasing, legal and business owners to inform the information security team must be written into the procedure. If it isn’t written, the news doesn’t come. Remediation plans of conditionally approved suppliers are tracked on a separate follow-up list; an action past its target date is automatically escalated to the business owner and the risk owner. The annual management review receives as inputs the number of suppliers per tier, the number of open findings and overdue actions.
The end of a contract is also part of the process. The relationship isn’t considered closed until it’s recorded that the supplier’s accounts were closed, VPN and firewall rules removed and the data returned or destroyed. The most common gap found in audits is a still-active service account of a supplier that has left. Checking this takes ten minutes: search by the supplier’s name in the identity provider and the VPN user list, and look at the last sign-in date.
7. Checklist and common mistakes
Use the list below when setting up the process:
- Has the supplier inventory been completed with sources other than purchasing?
- Has every supplier been assigned a business owner and a tier?
- Has the pre-screening form been linked to the new supplier onboarding process?
- Has the questionnaire been split into modules by tier and service type, and have knock-out questions been defined?
- Are scope, period and exceptions checked in certificates and reports?
- Does every assessment close with an approval, conditional approval, compensating control or rejection/acceptance decision?
- Does the contract template include the minimum security clauses?
- Are the reassessment calendar and change/incident triggers defined?
- Is proof of access closure and data destruction obtained at the end of the contract?
Mistakes we see over and over in the field: sending the same form to all suppliers; archiving answers without reading them and reaching a decision; treating the existence of a certificate as enough without looking at its scope; treating assessment as the information security team’s job alone and leaving the business owner out; never asking about the supplier’s own subcontractors. Controlling IT service suppliers from a quality management system perspective needs a separate view; for the requirements on the manufacturing side, see the article controlling IT service providers under IATF 16949.
We support building the supplier inventory, setting up the tier model and assessing critical suppliers through our supplier and third-party security risk management service. The starting point for the standard’s general framework on supplier relationships is the official ISO/IEC 27001 page.
Frequently asked questions
Do we need to send an information security questionnaire to every supplier?
No. For low-tier suppliers with no access to data or systems, confidentiality clauses in the contract and a short security declaration are usually enough. The depth is determined by the sensitivity of the data the supplier accesses and the criticality of the service.
If the supplier has ISO 27001 certification, do we still need to assess it?
A certificate shortens the assessment; it doesn’t remove it. Check whether the service provided to you, the location and the team are within the certificate’s scope, whether the certificate is valid and the certification body’s accreditation. Ask targeted questions about topics outside the scope.
What should we do if the supplier refuses to fill in the questionnaire?
First check whether the request is appropriate to the tier and reasonable. If the supplier still won’t provide information, record this as a risk input; you can reduce the risk on your side with compensating controls, look for an alternative supplier, or continue with the written acceptance of the authorized risk owner.
How often should supplier assessment be repeated?
The tier sets the frequency; once a year for critical suppliers and at contract renewal for lower tiers is common practice. Regardless of the calendar, a change in service scope, a security incident at the supplier or a change of subcontractor triggers reassessment.