A vendor security questionnaire is often treated as a gate: send the form, receive the answers, file the PDF. The useful version is a decision instrument. It tells the buyer which suppliers need deeper evidence, which answers are unsupported and what conditions should attach to a contract. This template is designed to be reused across procurements, with scoring and sign-off rather than a pass mark invented in the meeting.
Tier the vendor before you send anything
The same questionnaire should not go to a stationery supplier and a payroll provider. Tier by the consequence of failure, not by the size of the contract.
- Tier 1: sensitive personal, financial or health data; administrative access to production; an action that is hard to reverse; high concentration or regulatory exposure. Full questionnaire, independent evidence, contract controls and an annual review.
- Tier 2: business data with limited access, reversible impact and moderate concentration. Core questionnaire, selected evidence and a review every two years.
- Tier 3: public or low-sensitivity data, no access to systems and easy replacement. Short form and basic assurance.
Record the tier and the reason. A vendor that disagrees with the tier should discuss the data flow, not the paperwork.
How to score the answers
Use three values. 0 means the control is absent or the question was not answered. 1 means it is asserted but not evidenced. 2 means evidence was supplied and reviewed. Mark not applicable only with a written reason, and do not let a not-applicable answer inflate the score.
Weight the sections by tier. For a Tier 1 vendor, data protection, access and incident response should carry more weight than company profile. Produce one of three decisions: approve with no material gaps, conditional approval with compensating controls and dated actions, or reject for an unacceptable gap or a refusal to provide evidence. The business owner, security reviewer and procurement or legal lead should sign the decision.
The questionnaire
1. Company and service profile
- Legal entity, ownership, registered address and the exact service being bought.
- Data categories, volume, format and the locations where data is stored and processed.
- Subprocessors, their role and their locations.
- Certifications and audit reports with the scope statement and period covered, not only the logo.
- Material dependencies, concentration and the security contact with an escalation path.
2. Data protection
- Encryption in transit and at rest, including key ownership and rotation.
- Tenant isolation and the controls that prevent cross-customer access.
- Retention schedule, deletion method and backup retention.
- Whether customer data is used for analytics, product improvement or model training.
- Support for data subject requests and the breach notification route.
- Cross-border transfer mechanism and the return or export format at exit.
3. Identity and access
- Single sign-on support, MFA enforcement and session controls.
- Role model, least privilege and the frequency of privileged access review.
- Joiner, mover and leaver process, including contractor accounts.
- Administrative activity logging, retention and customer access to logs.
- Secrets management, key rotation and the break-glass procedure.
4. Application security
- Secure development lifecycle, code review and dependency scanning.
- Static and dynamic testing, penetration test cadence and the status of critical findings.
- Vulnerability disclosure route and remediation targets by severity.
- Change management, release approval and secure configuration baseline.
- API authentication, rate limiting, input validation and error handling.
- For AI features: model provider, prompt and response logging, guardrails and human review.
5. Resilience
- Hosting model, regions, redundancy and single points of failure.
- Backup frequency, encryption and the last successful restore test.
- Recovery time and recovery point claims, with evidence from a test.
- DDoS protection, capacity limits and the status page.
- Maintenance notice, incident history summary and the exit or transition plan.
6. Incident response
- Notification window, channel and the named security contact.
- Forensic support, evidence preservation and cooperation with your investigation.
- Customer communication, regulator support and the post-incident report.
- Whether the vendor carries cyber liability cover, and what the policy actually covers.
7. Privacy and AI
- Purpose limitation, lawful basis and consent handling.
- Whether prompts, outputs or customer documents are used to train models.
- AI subprocessors, model hosting locations and retention of prompts and outputs.
- Human oversight, output review and the route for a harmful or incorrect result.
- Data subject request and deletion support across backups and model stores.
8. Supply chain and exit
- Current subprocessor list and the notice period for a change.
- Flow-down obligations and the right to object to a new subprocessor.
- Concentration risk and whether a credible alternative exists.
- Audit rights, evidence access and the response time for a request.
- Data export, deletion confirmation and transition assistance.
- Termination notice, wind-down period and the return of your data.
Evidence hierarchy
Not all answers are equal. Rank evidence in this order: an independent audit report with the scope and period; a certification with a scope statement and statement of applicability; an independent penetration test summary; a configuration export or log sample; a policy; a self-attestation; a marketing page. If the only evidence is lower down the list, record the compensating control that makes the risk acceptable.
Scoring sheet
| Section | Weight | Score | Evidence | Owner | Decision |
|---|---|---|---|---|---|
| Company and service profile | 10 | 0-2 | Scope, subprocessors | Procurement | Approve / conditional / reject |
| Data protection | 20 | 0-2 | Data map, encryption, deletion | Privacy lead | Approve / conditional / reject |
| Identity and access | 15 | 0-2 | SSO, MFA, access review | Security | Approve / conditional / reject |
| Application security | 15 | 0-2 | Test summary, remediation | Security | Approve / conditional / reject |
| Resilience | 10 | 0-2 | Restore test, RTO and RPO | Operations | Approve / conditional / reject |
| Incident response | 10 | 0-2 | Terms, contact, report | Security | Approve / conditional / reject |
| Privacy and AI | 10 | 0-2 | Data use, model terms | Privacy lead | Approve / conditional / reject |
| Supply chain and exit | 10 | 0-2 | Subprocessor list, export test | Procurement | Approve / conditional / reject |
Review rhythm and triggers
Review Tier 1 vendors annually and Tier 2 vendors every two years. Trigger an earlier review after a security incident, a change of ownership, a new subprocessor, a major release, a change in the data you share or a regulatory change. Keep a register with the tier, owner, last review, open actions and next date. A questionnaire with no register becomes a folder of stale PDFs.
Common mistakes
- Sending the same form to every vendor and drowning the important answers in noise.
- Accepting a certificate without reading its scope and period.
- Scoring a sales answer as evidence because it was written confidently.
- Ignoring subprocessors, especially hosting, support and AI providers.
- Never testing the export or deletion path.
- Leaving the questionnaire with procurement while security and the business owner never see the answers.
- Having no conditional approval route, so every gap becomes either a yes or a stalled deal.
- Not tracking the actions that were promised after signature.
If you need the questionnaire adapted to your data flows and turned into a repeatable review, start with Managed Technology & Cybersecurity. The pricing page explains how assessment and vendor review work are scoped. For the risks behind a completed form, read the vendor security questionnaire risk guide.
Sources
- NIST, SP 800-161r1: Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations, accessed 17 November 2026.
- NIST, Cybersecurity Framework 2.0, accessed 17 November 2026.
- CISA, Supply Chain Security, accessed 17 November 2026.
- DataGuidance, Bangladesh: Data Protection Overview, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.