Vendor Security Questionnaire Template: 20 Questions
By Nemanja Vukmirović, Lizzard Solutions. Last updated 17 November 2026.
Your accountant, your hosting company, the agency that built your website and the SaaS tool that stores your customer list all hold a key to your business. If one of them is careless, your data leaks and your name is on the apology email.
This vendor security questionnaire template gives you 20 plain-language questions to send before you sign, a simple way to score the answers, the red flags that should stop a deal, and a worked example. It is built for small businesses that have no security team, only a few suppliers that matter.
TL;DR
- A vendor security questionnaire is a short list of questions a supplier answers in writing, so you can judge how they protect your data and access before you trust them.
- Send the 20 questions below to every supplier that stores your data or can log in to your systems, and score each answer green, amber or red.
- Any red on access, breach notification or data location means: fix it in the contract, ask for evidence, or pick another vendor.
What is a vendor security questionnaire?
A vendor security questionnaire is a written set of questions you ask a supplier about how they protect your data, systems and access. The supplier answers before you sign or renew, and you use the answers to decide whether the risk is acceptable and what the contract must require. It turns a vague "we take security seriously" into specific, checkable commitments.
Large companies send questionnaires with hundreds of rows. You do not need that. The UK NCSC's supply chain security principles boil the job down to understanding the risks, setting clear security expectations for suppliers and checking that they are met. NIST's Cybersecurity Framework 2.0 also lists supply chain risk management as its own category under the Govern function. Twenty good questions cover the essentials for a small company.
Key takeaway
Ask in writing, keep the answers, and put the important promises into the contract. A friendly phone call is not evidence.
Action for today: list every supplier that stores your data or can log in to your systems.
Which vendors need a questionnaire?
Not every supplier. Sort them by what they can touch, then send the questionnaire to the top two tiers:
| Tier | Vendor examples | What to send |
|---|---|---|
| High | Hosting, IT support with admin access, accounting software, CRM, payroll, web agency with server access | All 20 questions, plus evidence |
| Medium | Email marketing tool, booking system, cloud storage, freelancers with shared-drive access | All 20 questions, evidence optional |
| Low | Office supplies, cleaning, vendors with no data and no logins | No questionnaire needed |
The test is simple: personal data or logins. If a vendor processes your customers' or employees' personal data, or can sign in to any of your systems, they belong in the high or medium tier. Your IT asset inventory template is a fast way to find them, because every subscription on it has a vendor behind it.
Action for today: give each supplier on your list a tier.
The 20-question vendor security questionnaire template
Copy these questions into an email or a form. Ask the vendor to answer each one in writing and attach evidence where you mark it.
Data and privacy (1-5)
- What data of ours will you store or process, and for what purpose?
- In which countries is our data stored and processed, including backups and subcontractors?
- Which subcontractors (sub-processors) can access our data? Will you tell us before adding new ones?
- Will you sign a data processing agreement? (Evidence: your standard DPA.)
- How do we get our data back, in what format, and how is it deleted when the contract ends?
Access control (6-10)
- Who on your team can access our data or systems, and how is that access approved?
- Do all your staff use multi-factor authentication for systems that hold our data?
- Will you use named accounts in our systems, never one shared login?
- How quickly do you remove access when one of your staff leaves?
- Do you log access to our data, and can we get those logs on request?
Security operations (11-15)
- Is our data encrypted in transit and at rest?
- How often do you back up our data, and when did you last test a restore?
- How quickly do you apply security updates to the systems that hold our data?
- Do you have a written incident response plan? (Evidence: a summary or table of contents.)
- Do you hold a security certification or recent independent test, such as ISO/IEC 27001 or a penetration test? (Evidence: certificate or summary letter.)
Incidents and continuity (16-20)
- Within how many hours will you notify us of a breach affecting our data, and who will contact us?
- Have you had a security incident in the last 24 months that affected customers? What changed afterwards?
- What happens to our service and data if your company is sold or closes?
- Who is our named security contact, with email and phone?
- Will you accept these answers as part of our contract?
If you are hiring a developer or agency, combine this with our software development contract checklist, so the answers end up in clauses, not only in an email.
Action for today: send the 20 questions to your highest-risk vendor.
How to score the answers
Use three colours. You are not grading the vendor's marketing. You are checking whether the answer is specific, written and backed by evidence.
| Score | Meaning | Example answer |
|---|---|---|
| Green | Specific, written, evidence provided | "MFA is enforced for all staff via our identity provider; screenshot attached." |
| Amber | Plausible but vague, or no evidence yet | "Yes, we use MFA for most systems." |
| Red | No, refuses to answer, or answer contradicts itself | "We share one admin login, it is easier for support." |
Weight the answers on access, breach notification and data location most heavily, because those are the ones that hurt most when they go wrong. One red there matters more than three ambers elsewhere.
Action for today: score the first set of answers you receive, and highlight every red.
Red flags that should stop the deal
- Shared logins into your systems. You cannot tell who did what, and you cannot remove one person.
- No written breach notification time. If they will not commit to a number of hours, assume you will hear late.
- Unknown data location or sub-processors. You cannot meet your own privacy duties without this.
- No way to get your data back. This is lock-in, and also a continuity risk if the vendor fails.
- Refusal to sign a data processing agreement. Under the GDPR Article 28, a controller may only use processors that provide sufficient guarantees, under a contract with set terms.
Serbia's data protection law (ZZPL) has the same idea for processors, so the same rule applies to Serbian businesses. Our ZZPL guide for websites explains the controller and processor roles.
Watch out
A red flag is not always the end. Often the fix is a contract clause, a configuration change or a second vendor for backups. Ask once, in writing, before you walk away.
Action for today: for each red, write the fix you will ask for: a clause, evidence or a change.
Worked example: choosing a booking system
This is a fictional example to show the process, not a real client. A physiotherapy practice with six staff compares two online booking tools that will store patient names, phone numbers and appointment notes.
- Both vendors get the 20 questions by email with a ten-day deadline.
- Vendor A answers all 20, attaches its DPA, lists EU hosting and two named sub-processors, and commits to breach notification within 48 hours. Three ambers, no reds.
- Vendor B answers 14 questions, does not name its sub-processors and says breach notification is "as soon as possible". Two reds.
- The practice picks Vendor A, adds the 48-hour notice and data export format to the contract, and files the answers.
- A calendar reminder is set to re-send the questionnaire at renewal.
Total effort: about an hour of the owner's time across two weeks, and a clear written record if anything goes wrong later.
Action for today: pick the vendor contract that renews next and put a questionnaire reminder one month before it.
Keep it alive: renewals, changes and records
A questionnaire is a snapshot. Re-send it at every renewal for high-tier vendors, and whenever a vendor is acquired, changes hosting or has an incident. Keep one folder per vendor with the answers, evidence, contract and renewal date.
Vendor access also belongs in your quarterly user access review: agency and IT support logins are exactly the ones that tend to stay open for years. And if a vendor has a breach, your incident response plan template should already name who calls them.
Want an outside view of how your own site looks to an attacker? A website security check shows what your web vendor's work exposes publicly.
Action for today: create a Vendors folder with one subfolder per high-tier supplier.
Frequently asked questions
What should a vendor security questionnaire include?
At minimum: what data the vendor handles and where it is stored, who can access it and whether they use multi-factor authentication, encryption and backups, breach notification time, sub-processors, how you get data back at the end, and a named security contact. The 20 questions above cover these in plain language.
How long should a vendor security questionnaire be for a small business?
Short enough that a small vendor will actually answer it. Twenty focused questions usually take a vendor under an hour and give you what you need to decide. Long enterprise questionnaires often come back half-finished or copy-pasted, which tells you less than a short one answered properly.
How often should you reassess vendors?
Reassess high-risk vendors at every contract renewal and at least once a year. Also reassess immediately when a vendor is bought, moves your data to a new provider or country, or reports a security incident. Medium-risk vendors can be checked every two years or at renewal.
Is a vendor questionnaire required by GDPR?
GDPR does not require a questionnaire by name, but Article 28 requires that you only use processors that give sufficient guarantees of appropriate security, under a written contract. A completed questionnaire plus a signed data processing agreement is a practical way to show you checked. This is general information, not legal advice.
Want a second opinion on your vendors?
We can review your vendor answers, flag the real risks in plain language and suggest the contract fixes. Book a free consultation.
Book a free consultation