Most third-party programmes either send the same long questionnaire to every supplier or skip assessment for suppliers that look small, and both fail because nobody scored the risk before choosing the depth of review. This template is the short intake questionnaire completed by the business owner before any security assessment starts. It scores inherent risk across data, access, criticality and integration, assigns a tier, and maps each tier to the diligence, contract terms and reassessment cycle that follow. It is written for third-party risk, procurement and security teams. The full security assessment that follows a high tier is in the Vendor Security Assessment Template; the programme around it is described in the Third-Party Risk Management Guide.
How to use this template
- Replace text in square brackets, such as [Organisation], [TPRM team] and [30 days], with your own terms and values. Scores, weights and thresholds are suggested defaults, not external requirements: calibrate them on your existing suppliers before use.
- The business owner of the engagement completes sections 3 to 6 with help from procurement. The [TPRM team] validates answers and confirms the tier in section 7. Answers take [15 to 20 minutes]; if a question cannot be answered, score it at the highest option until confirmed.
- Inherent risk is the risk before the supplier's controls are considered. Do not lower a score because the supplier "has ISO 27001" or "is a well-known brand": controls are assessed later and reduce residual risk, not inherent risk.
- Run the questionnaire at onboarding, at contract renewal, and whenever the scope of the service changes (new data, new access, new integration).
- Place it under your supplier policy. See the Supplier Security Policy Template.
1. Purpose and triggers
This questionnaire determines the inherent risk of a proposed or existing supplier relationship at [Organisation] and assigns a tier that sets the depth of security due diligence, the contract terms required and the frequency of reassessment. It supports NIST CSF 2.0 outcome GV.SC-04 (suppliers are known and prioritised by criticality) and GV.SC-06 (planning and due diligence before entering a relationship).
It must be completed when:
- A new supplier, product, SaaS application, integration or professional service is requested, before contract signature or purchase order.
- An existing engagement changes scope: new data types, new access, a new integration, a new hosting location, or a material increase in volume.
- A contract is renewed or extended.
- A free trial, pilot or proof of concept will use [Organisation] data other than Public data, or will connect to [Organisation] systems.
Engagements below [the de minimis threshold, for example one-off purchases of commodity goods with no data or system access] are recorded in the supplier inventory but need not complete sections 3 to 6.
2. Roles and contacts
| Role | Responsibility in tiering |
|---|---|
| Business owner | Completes sections 3 to 6; accountable for the accuracy of answers and for the relationship over its life. |
| [Procurement] | Triggers the questionnaire; does not issue a purchase order or contract until a tier is recorded. |
| [TPRM team] | Validates answers, calculates the score, confirms the tier, records it in the supplier inventory. |
| [Data protection officer] | Reviews any engagement involving personal data or international transfers. |
| [Identity or IAM team] | Confirms the access and integration answers in section 5, including OAuth grants and service accounts. |
| [Business continuity lead] | Confirms the criticality answers in section 6 against the business impact analysis. |
| [CISO or delegate] | Approves any tier override and any Tier 1 engagement before contract. |
Record the supplier name, legal entity, service description, contract owner, expected start date and contract value at the top of the form. Contract value is recorded for reporting but does not score: low-cost SaaS tools can carry the highest risk.
3. Detection and triage: service profile
These questions identify what the supplier is and route obvious cases quickly.
| Ref | Question | Answer options |
|---|---|---|
| 3.1 | What type of engagement is this? | SaaS or cloud service; hosted or managed service; on-premises software or hardware; professional services or contractors; data processor or outsourcer; other |
| 3.2 | Will the supplier, its staff or its software process, store or view [Organisation] data? | No; yes (go to section 4) |
| 3.3 | Will the supplier have any access to [Organisation] systems, networks, accounts or premises? | No; yes (go to section 5) |
| 3.4 | Will the supplier's product run inside [Organisation]'s environment (installed software, agents, browser extensions, AI assistants)? | No; yes (score 5.5) |
| 3.5 | Is this supplier already in the inventory under another contract? | No; yes (link the records) |
| 3.6 | Will the supplier use subcontractors or other service providers to deliver this service? | No; yes; unknown |
Fast-track rule: if 3.2, 3.3 and 3.4 are all "No", assign Tier 4 without further questions.
4. Containment of data exposure: data questions
Use the data classification levels from the Data Classification Policy Template; rename them to match your scheme.
| Ref | Question | Score 0 | Score 1 | Score 3 | Score 5 |
|---|---|---|---|---|---|
| 4.1 | Highest classification of data the supplier will handle | Public | Internal | Confidential | Restricted |
| 4.2 | Personal data involved | None | Business contact details only | Customer or employee personal data | Special category, financial, health, children's or authentication data |
| 4.3 | Volume of records | None | Fewer than [1,000] | [1,000 to 100,000] | More than [100,000] or the full data set |
| 4.4 | Where data will be stored or processed | Not stored | [Home jurisdiction] only | Jurisdictions with an adequacy decision or approved transfer mechanism | Other jurisdictions or unknown |
| 4.5 | Will data be used to train or improve the supplier's products or AI models? | No, contractually excluded | Aggregated or anonymised only | Unknown | Yes |
For AI suppliers, add the questions in the AI Vendor Security Questionnaire Template at the assessment stage.
5. Eradication of hidden access: access and integration questions
Access is where tiering most often goes wrong, because integrations and tokens are not visible to the business owner. The [Identity or IAM team] must confirm these answers.
| Ref | Question | Score 0 | Score 1 | Score 3 | Score 5 |
|---|---|---|---|---|---|
| 5.1 | User accounts for supplier staff in [Organisation] systems | None | Standard user accounts, via SSO | Accounts with elevated rights in one system | Administrator or privileged access, or access to the identity provider |
| 5.2 | Machine credentials issued to the supplier: API keys, service accounts, OAuth grants, certificates | None | Read-only, scoped to one system | Read and write, or tenant-wide read | Tenant-wide write, admin consent, or credentials that cannot be scoped or rotated |
| 5.3 | Network connectivity | None | Inbound from [Organisation] to the supplier only | Remote access to specific systems through [approved remote access] | Site-to-site VPN, direct connection or persistent remote access tool |
| 5.4 | Physical access to [Organisation] premises or data centres | None | Escorted visits | Unescorted access to offices | Unescorted access to data centres, OT sites or secure areas |
| 5.5 | Code or agents running in [Organisation]'s environment | None | Packaged software with no automatic updates | Software or browser extension with automatic updates | Endpoint or server agent with privileged rights, or an AI agent that acts with [Organisation] credentials |
Every credential recorded in 5.2 must be registered as a non-human identity with an internal owner and an expiry. See the OWASP NHI Top 10 NHI3 Vulnerable Third-Party NHI Guide and the Third-Party Access Policy Template.
6. Recovery dependence: criticality questions
| Ref | Question | Score 0 | Score 1 | Score 3 | Score 5 |
|---|---|---|---|---|---|
| 6.1 | Impact if the service is unavailable for [5 working days] | None | Minor inconvenience; workaround exists | Significant disruption to one business unit | Disruption to a critical or important business service, customers or regulatory obligations |
| 6.2 | Does the service support a process listed in the business impact analysis as critical, or a regulated "critical or important function"? | No | Indirectly | Yes, with a tested alternative | Yes, with no tested alternative |
| 6.3 | How easily could the supplier be replaced? | Days, many alternatives | Weeks | Months | More than [6 months], or no realistic alternative |
| 6.4 | Customer or public facing? | No | Internal users only | Some customers | All customers or the public, or the supplier acts in [Organisation]'s name |
Where several critical services depend on the same provider, flag the supplier for concentration review. See the Third-Party Concentration Risk Guide.
7. Communication of the result: scoring and tier assignment
Score: add the scores for sections 4, 5 and 6 (maximum 70). Then apply the override rules, which take precedence over the total.
| Tier | Total score | Override rules (any one assigns the tier) |
|---|---|---|
| Tier 1: Critical | [36 or more] | Any 5 in 5.1 or 5.2; a 5 in 6.2; Restricted data (4.1 = 5) at volume (4.3 = 5) |
| Tier 2: High | [21 to 35] | Any 5 in section 4; any 3 in 5.1, 5.2 or 5.3 |
| Tier 3: Moderate | [8 to 20] | Any personal data (4.2 of 3 or more) |
| Tier 4: Low | [0 to 7] | Fast-track rule in section 3 |
Record the tier, the score, the answers and the date in the supplier inventory, and tell the business owner and procurement what diligence follows. Any request to override the tier downwards must be justified in writing and approved by the [CISO or delegate].
What each tier triggers
| Tier | Due diligence before contract | Contract terms | Reassessment |
|---|---|---|---|
| 1 | Full security assessment, independent assurance report review with scope check, evidence sampling, penetration test summary, exit plan, concentration review | Full security schedule, audit rights, incident notification within [24 hours], subcontractor approval, exit and data deletion clauses | Annual full reassessment plus continuous monitoring and event-driven review |
| 2 | Standard security questionnaire with evidence for key controls; assurance report review | Security schedule, incident notification within [48 hours], data deletion at exit | Every [2 years], plus on scope change |
| 3 | Short questionnaire or assurance report only; privacy review if personal data | Standard data protection and confidentiality terms | At renewal |
| 4 | None beyond inventory record | Standard terms | On scope change only |
For contract wording, see the Third-Party Security Contract Clauses Template.
8. Post-assessment review of the tiering
- The [TPRM team] must review the tier at each reassessment and whenever an answer in sections 4 to 6 changes.
- After a supplier incident affecting [Organisation], the tier and the answers must be re-checked within [30 days]. See the Third-Party Incident Response Playbook.
- At least [annually], the [TPRM team] must sample [10]% of Tier 3 and Tier 4 suppliers and verify answers against SSO application lists, OAuth consent grants, firewall rules and accounts payable, to find under-tiered suppliers.
- At exit, the tier determines the offboarding checks. See the Vendor Offboarding and Termination Guide.
Implementation guidance
Rollout
- Calibrate first: score [20 to 30] existing suppliers whose risk you already understand, including your identity provider, payroll, a SaaS tool and a cleaning contractor. Adjust thresholds until the tiers match expert judgement, then freeze the version.
- Pilot with one procurement route: run the questionnaire for new SaaS purchases for [one quarter] before enforcing it for all categories.
- Back-fill the inventory: tier existing suppliers starting from those with privileged access or Restricted data.
- Enforce through procurement: no purchase order or contract without a recorded tier. Block expense claims for SaaS subscriptions without one.
- Roll back safely: if the questionnaire creates a backlog, keep the override rules and the fast-track rule, and temporarily raise the Tier 2 threshold, rather than suspending tiering.
Measuring it
- Percentage of active suppliers with a current tier.
- Median days from questionnaire submission to tier confirmed.
- Number of suppliers found under-tiered by the annual sample.
- Percentage of machine credentials issued to suppliers that are linked to a tiered supplier record.
- Tier 1 suppliers with an overdue reassessment.
Failure patterns this template is written to prevent
- Integrations missed at intake: in the Salesloft Drift breach, OAuth tokens held by a chat integration were used to reach customers' Salesforce data. Question 5.2 scores OAuth grants and API keys directly.
- Tiering by spend: low-cost tools escape review. Contract value is recorded but never scored.
- Controls counted as inherent risk: a certification lowers residual risk after assessment, not the tier.
- Tier never revisited: scope creep adds data and access after signature; section 1 triggers and the annual sample catch it.
Framework mapping
| Framework | Reference | Template sections |
|---|---|---|
| NIST CSF 2.0 | GV.SC-04 (suppliers prioritised by criticality), GV.SC-06 (due diligence before relationships), GV.SC-07 (supplier risks understood and assessed) | 3 to 7 |
| NIST SP 800-53 Rev. 5 | SR-2 Supply Chain Risk Management Plan, SR-6 Supplier Assessments and Reviews, SA-9 External System Services, RA-3 Risk Assessment | 7, 8 |
| NCSC supply chain security principles | Stage I, Understand the risks | 3 to 6 |
| ISO/IEC 27001:2022 | Annex A 5.19 Information security in supplier relationships, 5.21 Managing information security in the ICT supply chain | Whole template |
Sources
- NIST: Cybersecurity Framework 2.0
- NIST: SP 800-53 Rev. 5, Security and Privacy Controls
- NCSC: Supply chain security principles
Related NHI Mgmt Group resources: Third-Party Risk Management Guide · Vendor Security Assessment Template · Security Questionnaires Guide · Third-Party Risk Management Maturity Model · Supplier Security Policy Template