Security questionnaire template and 50 sample answers
Short answer: A security questionnaire is a list of questions a buyer sends a vendor to assess how it protects data. Most cover the same ten areas: governance, access control, data protection, infrastructure, application security, vulnerability management, incident response, business continuity, vendor management and privacy. A good answer starts with Yes, No or Partially, then says how in one or two sentences, and points to evidence such as a SOC 2 report or a policy. The template below gives 50 example questions with answer patterns you can adapt.
In Iris: Iris drafts security questionnaire answers only from your own policies, reports and approved answers, with citations, and says "There is not enough information to answer the question" when your documents don't support an answer.
Who this is for: security, compliance and sales engineering teams that answer vendor security questionnaires, and teams building their first standard answer set.
On this page
- How is a security questionnaire structured?
- How should you answer a security question?
- The template: 50 questions with sample answers
- Which evidence backs which answers?
- FAQ
How is a security questionnaire structured?
Buyers use a standard framework (such as SIG, CAIQ or HECVAT; see our comparison) or their own list. Either way the domains are similar:
| Domain | What the buyer wants to know | Typical evidence |
|---|---|---|
| Governance | Is security owned and managed? | Security policy, org chart, SOC 2 |
| Access control | Who can reach our data? | Access policy, SSO/MFA config |
| Data protection | Is data encrypted and handled correctly? | Encryption standard, data classification policy |
| Infrastructure | Is the hosting environment secure? | Architecture diagram, cloud provider reports |
| Application security | Is the software built securely? | SDLC policy, code review process |
| Vulnerability management | Are weaknesses found and fixed? | Pen test summary, patching policy |
| Incident response | Will they tell us, and fast? | IR plan, notification terms |
| Business continuity | Will the service survive an outage? | BC/DR plan, test results |
| Vendor management | Are their suppliers controlled? | Subprocessor list, vendor review process |
| Privacy | Do they handle personal data lawfully? | Privacy policy, DPA |
How should you answer a security question?
Use the same four-part pattern every time:
- Direct answer: Yes, No, Partially or Not applicable.
- How: one or two sentences on the control.
- Scope: what it covers (production, all employees, customer data).
- Evidence: the document that proves it, and how to get it ("available under NDA").
Never answer Yes to a control you don't have. A "Partially" with a remediation date is better than a "Yes" a buyer later finds is false, and it may end up in the contract. Track any commitment you make.
The template: 50 questions with sample answers
Download the template (XLSX). Each pattern is for Kestrel Data (fictional). Replace [brackets] with your facts; delete anything you can't truthfully say.
| # | Domain | Question | Answer pattern | Evidence |
|---|---|---|---|---|
| 1 | Governance | Do you have a documented information security policy? | Yes. Our information security policy is approved by [role], reviewed [annually] and available to all employees. | Security policy (TOC or excerpt) |
| 2 | Governance | Who is responsible for information security? | [Name/role, e.g. Head of Security] owns the program and reports to [role]. | Org chart excerpt |
| 3 | Governance | Do you have a current independent audit report? | [Yes. SOC 2 Type II for [period], available under NDA. / No; see evidence below.] | SOC 2 report or bridge letter |
| 4 | Governance | Do employees complete security awareness training? | Yes, at hire and [annually], with completion tracked. | Training policy; completion record |
| 5 | Governance | Do you perform background checks on employees? | [Yes, where permitted by law, for [roles/all] before start.] | HR policy excerpt |
| 6 | Access | Do you support single sign-on for customers? | [Yes, via SAML 2.0 / OIDC, including [IdPs].] | Product docs |
| 7 | Access | Is MFA required for employee access to production? | [Yes. MFA is enforced for all access to production systems and admin consoles.] | Access policy; IdP config screenshot |
| 8 | Access | How is access granted and revoked? | Access is role-based, approved by [role], and removed within [timeframe] of termination. | Access control policy |
| 9 | Access | How often are access rights reviewed? | [Quarterly] for production and sensitive systems. | Access review record |
| 10 | Access | Is privileged access restricted and logged? | [Yes. Admin access is limited to [roles] and logged to [system].] | Logging policy |
| 11 | Data | Is customer data encrypted in transit? | Yes, using TLS [version] or higher for all external connections. | Encryption standard |
| 12 | Data | Is customer data encrypted at rest? | Yes, using [method] with keys managed by [service]. | Encryption standard |
| 13 | Data | Do you classify data? | Yes. Data is classified as [levels], with handling rules for each. | Data classification policy |
| 14 | Data | Where is customer data stored? | In [provider], [region(s)]. [Residency options, if any.] | Subprocessor list |
| 15 | Data | How long do you retain customer data after termination? | [State the period in your contract/DPA], then deleted from production; backups expire within [period]. | DPA; retention policy |
| 16 | Data | Is customer data logically separated from other customers'? | [Yes. Each customer's data is scoped to its tenant at the application and storage layers.] | Architecture overview |
| 17 | Infrastructure | Where is your service hosted? | [Provider], [regions], using [managed services]. | Architecture diagram |
| 18 | Infrastructure | Are production environments separated from development? | Yes. Production is in a separate [account/network], with no production data in development. | Change management policy |
| 19 | Infrastructure | Do you use firewalls or network segmentation? | Yes. [Security groups / network policies] restrict traffic to required ports and services. | Network diagram |
| 20 | Infrastructure | How do you harden servers and containers? | Using [baseline/benchmark] and [image scanning]; changes go through [process]. | Hardening standard |
| 21 | Infrastructure | Do you monitor infrastructure for security events? | Yes. Logs from [sources] are centralized in [tool] with alerts to [team]. | Monitoring/logging policy |
| 22 | AppSec | Do you follow a secure development lifecycle? | Yes. Requirements, design review, code review and testing include security checks. | SDLC policy |
| 23 | AppSec | Is all code peer-reviewed before release? | [Yes. Every change to production code requires an approved review.] | Repository settings screenshot |
| 24 | AppSec | Do you use automated security testing? | [Yes: [SAST], [dependency scanning], [DAST] in CI.] | CI pipeline description |
| 25 | AppSec | How do you manage open-source dependencies? | Dependencies are scanned [continuously]; critical issues fixed within [timeframe]. | Vulnerability policy |
| 26 | AppSec | Do developers receive secure coding training? | [Yes, [annually / at onboarding].] | Training record |
| 27 | Vulnerability | Do you have an independent penetration test? | [Yes, [annually] by a third party. A summary is available under NDA.] | Pen test summary or letter |
| 28 | Vulnerability | What are your patching timelines? | Critical: [x days]; High: [y days]; others: [z days]. | Patch management policy |
| 29 | Vulnerability | Do you run vulnerability scans? | Yes, [frequency], covering [scope]. | Scan report summary |
| 30 | Vulnerability | Do you have a vulnerability disclosure program? | [Yes, at [URL / security.txt]. / Not yet; reports go to [email].] | Public disclosure page |
| 31 | Incident | Do you have an incident response plan? | Yes, reviewed [annually] and tested [frequency]. | IR plan (summary) |
| 32 | Incident | How quickly will you notify us of a breach? | Within [period stated in your contract/DPA] of confirming an incident affecting your data. | DPA / MSA clause |
| 33 | Incident | Have you had a security breach in the last [x] years? | [Answer truthfully, per counsel.] | — |
| 34 | Incident | Who do we contact about a security incident? | [Security contact email / page.] | — |
| 35 | Incident | Do you retain security logs, and for how long? | Yes, for [period], protected from alteration. | Logging policy |
| 36 | Continuity | Do you have a business continuity / disaster recovery plan? | Yes, reviewed [annually], last tested [date]. | BC/DR plan summary |
| 37 | Continuity | What are your RTO and RPO? | [State only targets you can support and are approved for external sharing.] | BC/DR plan |
| 38 | Continuity | How are backups performed and tested? | [Frequency], encrypted, stored in [location], restore-tested [frequency]. | Backup policy |
| 39 | Continuity | What uptime do you commit to? | [Only what your contract or SLA commits to, with the link.] | SLA |
| 40 | Continuity | Do you have redundancy across zones or regions? | [Describe accurately.] | Architecture diagram |
| 41 | Vendors | Do you maintain a list of subprocessors? | Yes, at [URL], with notice of changes per our DPA. | Subprocessor list |
| 42 | Vendors | How do you assess your own vendors' security? | Vendors handling customer data are reviewed before onboarding and [annually]. | Vendor management policy |
| 43 | Vendors | Do subprocessors sign data protection terms? | Yes, before they process customer data. | DPA template |
| 44 | Vendors | Do you use AI or machine learning providers to process our data? | [Name the category and providers exactly as in your subprocessor list; state whether data is used for training, per your DPA.] | Subprocessor list; AI policy |
| 45 | Vendors | Can we audit you? | [Our SOC 2 report is provided in place of on-site audits; additional audit rights per contract.] | MSA clause |
| 46 | Privacy | Do you sign a DPA? | Yes. Our DPA is available at [link / on request]. | DPA |
| 47 | Privacy | Do you comply with GDPR / applicable privacy laws? | [Describe your program honestly, e.g. "We act as a processor and support customers' obligations through our DPA and SCCs."] Avoid "certified". | Privacy policy; DPA |
| 48 | Privacy | How do you handle data subject requests? | We assist customers within [timeframe] per the DPA. | DPA |
| 49 | Privacy | Do you transfer personal data internationally? | [Describe, and the transfer mechanism.] | DPA; SCCs |
| 50 | Privacy | Do you use customer data to train AI models? | [Answer exactly per your DPA and AI policy.] | DPA; AI policy |
Which evidence backs which answers?
Many questions are answered by the same five or six documents. Have them ready and current; see our security evidence checklist.
| Evidence | Answers it supports (#) |
|---|---|
| SOC 2 Type II report (or ISO 27001 certificate) | 1–4, 7–12, 18–23, 27–29, 31, 36, 38, 42 |
| Security policy set | 1, 4, 8, 13, 20, 22, 28, 31 |
| Pen test summary | 27 |
| DPA and subprocessor list | 14, 15, 32, 41, 43, 44, 46–50 |
| Architecture diagram | 16, 17, 19, 40 |
| BC/DR plan and test record | 36–38 |
How Iris helps
Iris is AI software for RFPs, security questionnaires and proposals.
- Drafts from your own sources. Answers come from your policies, SOC 2 report and approved answers, uploaded or synced from SharePoint, Google Drive, Confluence, Notion or Vanta. Every answer links to its sources and carries a High, Medium, Low or Contradictory confidence label.
- Doesn't fill gaps with guesses. Where your documents don't cover a control, Iris says "There is not enough information to answer the question" and the answer can't be approved as-is.
- Excel in, Excel out. Iris reads Yes/No plus comment columns and dropdowns across tabs, and writes answers back into the original workbook.
- Evidence remembered. Evidence attached to an approved answer is suggested when that answer is reused.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.
FAQ
What is a security questionnaire?
A set of questions a buyer sends a vendor to assess its security controls before sharing data or signing a contract.
What questions are in a vendor security questionnaire?
Usually governance, access control, encryption, infrastructure, secure development, vulnerability management, incident response, continuity, vendor management and privacy. The 50 above are a representative set.
Can I send my SOC 2 report instead of answering?
Sometimes. Many buyers accept a SOC 2 report for most questions and send a shorter follow-up. Others require their own questionnaire regardless.
Should I answer "No"?
If it's true, yes, with context and any compensating control or plan. A false "Yes" can become a contractual misrepresentation.
How do I keep answers current?
Give each standard answer an owner and review date, and update it when the underlying policy changes. See our content library guide.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
