Vendor security questionnaire template

A plain, original vendor security questionnaire you can use two ways: send it to your own suppliers, or — more often — fill it in once as your starter answer library, so the next customer questionnaire takes an afternoon instead of a week.

Download the CSV (60 questions) Import it into RFPKit

Columns: Section, Question, Answer. Each answer is a starter written in plain language; text in [brackets] is what you adapt. Written for RFPKit — not copied from SIG, CAIQ or any other licensed questionnaire.

What it covers

60 questions in 12 areas that most customer security reviews ask about, in roughly the order a reviewer reads them:

Tips for filling it in

All 60 questions

Company and governance

  1. Provide your company's legal name, headquarters location and year founded.
    Starter answer: [Company] is the trading name of [legal name], headquartered in [city, country] and founded in [year].
  2. Who is accountable for information security in your organization?
    Starter answer: Our [CTO] is accountable for information security and reports on it to the [leadership team] every [quarter]. Day-to-day security work is run by [our security lead].
  3. Do you maintain a written information security policy, and how often is it reviewed?
    Starter answer: Yes. [Company] maintains a written information security policy approved by [the CTO]. It is reviewed at least [annually] and after any significant change, and every employee acknowledges it on joining.
  4. Do you hold any independent security attestations or certifications?
    Starter answer: [Company] [has completed a SOC 2 Type II examination covering the Security criteria]. The most recent report covers [report period] and is available under NDA from our trust page.
  5. Describe how you identify and manage information security risks.
    Starter answer: We keep a risk register that lists each risk with an owner, likelihood, impact and treatment. It is reviewed [quarterly] by [the leadership team], and new risks are added when we launch features, change vendors or learn of new threats.

People security

  1. Do you perform background checks on employees and contractors?
    Starter answer: Yes, where local law allows. New employees and contractors with access to customer data complete [identity, employment and criminal record checks] before they are given access.
  2. Do employees receive security awareness training?
    Starter answer: Yes. Every employee completes security awareness training when they join and [every year] after that. Training covers phishing, password and MFA hygiene, data handling and how to report incidents.
  3. Do employees sign confidentiality agreements?
    Starter answer: Yes. All employees and contractors sign a confidentiality agreement before they start, and their obligations continue after they leave.
  4. How do you remove access when an employee leaves or changes roles?
    Starter answer: Offboarding follows a checklist: accounts are disabled [on the last working day], company devices are returned and wiped, and shared secrets the person could access are rotated. Role changes trigger an access review for the systems involved.

Access control

  1. Do you enforce multi-factor authentication for access to production systems?
    Starter answer: Yes. Multi-factor authentication is required for all access to production systems, cloud consoles, source code and our identity provider. [Hardware security keys] are required for administrators.
  2. How is access to customer data granted and reviewed?
    Starter answer: Access follows least privilege: engineers have no standing access to customer data. Access is granted per request with a ticket and approval, expires automatically after [24 hours], and all grants are reviewed [quarterly].
  3. Do you use single sign-on for internal systems?
    Starter answer: Yes. Employees sign in to internal systems through our identity provider ([Google Workspace]) with SSO and MFA, so disabling one account removes access everywhere.
  4. Describe your password policy.
    Starter answer: Passwords must be at least [12] characters and are checked against known breached passwords. We don't force periodic rotation; passwords are changed when there is any sign of compromise. All employees use a company password manager.
  5. How do you manage privileged and administrative accounts?
    Starter answer: Administrative privileges are limited to [a small number of named engineers], use separate admin roles, require MFA and are logged. Privileged access is reviewed [quarterly].

Data protection

  1. Is customer data encrypted at rest?
    Starter answer: Yes. Customer data is encrypted at rest using [AES-256] provided by our cloud platform, including databases, file storage and backups.
  2. Is customer data encrypted in transit?
    Starter answer: Yes. All connections to [Company] use TLS [1.2 or higher], HTTP is redirected to HTTPS, and HSTS is enabled. Traffic between our internal services is also encrypted.
  3. How are encryption keys managed?
    Starter answer: Encryption keys are managed by [our cloud provider's key management service]. Access to key management is restricted to [a small number of administrators] and logged, and keys are rotated [automatically].
  4. Where is customer data stored geographically?
    Starter answer: Customer data is stored in [the United States and Canada] on [Cloudflare's] infrastructure. We'll tell customers before moving their data to a new region.
  5. How long do you retain customer data, and how is it deleted?
    Starter answer: We keep customer data for as long as the customer's account is active. Customers can export and delete their data at any time; deleted data is removed from active systems immediately and from backups within [30 days].
  6. Do you segregate one customer's data from another's?
    Starter answer: Yes. Each customer's data is stored [in a separate logical database] and every request is checked against the customer it belongs to, so one customer can't read another's data.
  7. Do you use customer data to train AI or machine learning models?
    Starter answer: No. [Company] does not use customer data to train or fine-tune AI models, and our AI providers are contractually prevented from training on it.

Application security

  1. Describe your secure software development lifecycle.
    Starter answer: Every change is reviewed by a second engineer before it is merged, runs automated tests and dependency checks, and is deployed through CI/CD. Security requirements are considered at design time for new features.
  2. Do you perform penetration testing, and how often?
    Starter answer: Yes. An independent firm performs a penetration test of our application and infrastructure [annually]. Findings are tracked to resolution, and a summary letter is available under NDA.
  3. How do you manage vulnerabilities in third-party libraries?
    Starter answer: We scan dependencies automatically on every build and [daily]. Critical vulnerabilities are patched within [7 days] and high-severity ones within [30 days].
  4. Do you scan your code for security issues?
    Starter answer: Yes. We run static analysis and secret scanning on every pull request, and builds fail if a secret is committed.
  5. How do you protect against common web application attacks such as those in the OWASP Top 10?
    Starter answer: We use parameterized queries, output encoding, a strict Content Security Policy, CSRF protection and input validation on every endpoint, and we test for OWASP Top 10 issues during code review and penetration tests.

Infrastructure and network

  1. Which cloud or hosting providers do you use?
    Starter answer: [Company] runs on [Cloudflare (Workers and Durable Objects)]. We don't operate our own data centres.
  2. How do you protect your network perimeter?
    Starter answer: Our services sit behind [Cloudflare's] network, which provides DDoS protection, a web application firewall and rate limiting. No databases or admin interfaces are exposed to the internet.
  3. How do you keep servers and systems patched?
    Starter answer: We use managed platforms where the provider patches the underlying systems. Our own dependencies are updated [weekly], and critical security patches are applied within [7 days].
  4. Are production and development environments separated?
    Starter answer: Yes. Production is separate from development and testing, with different accounts and credentials. Production customer data is never copied into development or test environments.
  5. How do you secure employee laptops and devices?
    Starter answer: Company laptops use full-disk encryption, automatic screen lock, automatic OS updates and [endpoint protection]. Devices are managed centrally and can be wiped remotely if lost.

Logging and monitoring

  1. Do you log access to systems that hold customer data?
    Starter answer: Yes. Authentication events, administrative actions and access to customer data are logged with a timestamp and the user involved. Logs are kept for [12 months] and protected from tampering.
  2. How do you monitor for security events?
    Starter answer: We alert on suspicious activity such as repeated failed logins, privilege changes and unusual traffic. Alerts go to [the on-call engineer] [24/7].
  3. Can customers see an audit log of activity in their account?
    Starter answer: Yes. Account owners can see an audit log of security-relevant actions in their workspace, such as member changes, approvals and exports.
  4. Do you keep personal data out of application logs?
    Starter answer: Yes. Our logging rules forbid recording passwords, access tokens, customer content and other personal data; we log request identifiers and error codes instead.
  5. How do you monitor service availability?
    Starter answer: We monitor availability and response times from multiple locations every [minute] and are alerted when a check fails. Status updates are published at [status page URL].

Incident response

  1. Do you have a documented incident response plan?
    Starter answer: Yes. Our incident response plan defines roles, severity levels, communication steps and post-incident review. It is tested with a tabletop exercise at least [annually].
  2. How quickly will you notify customers of a security incident affecting their data?
    Starter answer: We will notify affected customers without undue delay and within [72 hours] of confirming an incident that affects their data, and we'll keep them updated as we learn more.
  3. Have you had a security breach in the last three years?
    Starter answer: [No.] [Company] has not had a security incident that resulted in unauthorized access to customer data in the last three years.
  4. How can customers or researchers report a security issue?
    Starter answer: Security reports can be sent to [security@yourcompany.com]. We acknowledge reports within [2 business days] and don't take legal action against good-faith research.
  5. Do you perform post-incident reviews?
    Starter answer: Yes. Every significant incident gets a written, blameless review covering timeline, root cause and follow-up actions, which are tracked to completion.

Business continuity

  1. Do you back up customer data, and how often?
    Starter answer: Yes. Customer data is backed up [continuously] with point-in-time recovery for [30 days]. Backups are encrypted and stored separately from the primary data.
  2. Do you test restoring from backups?
    Starter answer: Yes. We test restoring data from backups at least [twice a year] and record the results.
  3. What are your recovery time and recovery point objectives?
    Starter answer: Our recovery time objective (RTO) is [4 hours] and our recovery point objective (RPO) is [1 hour] for the core service.
  4. Do you have a business continuity and disaster recovery plan?
    Starter answer: Yes. Our business continuity plan covers loss of a cloud region, key vendors and key people. It is reviewed and exercised [annually].
  5. What uptime commitment do you offer?
    Starter answer: We target [99.9%] monthly availability for the core service. [Contractual SLAs with service credits are available on enterprise agreements.]

Vendors and subprocessors

  1. Do you use subprocessors that handle customer data?
    Starter answer: Yes. We use a small number of subprocessors, such as [Cloudflare (hosting)]. The current list is published on our trust page, and we notify customers before adding a new one.
  2. How do you assess the security of your vendors?
    Starter answer: Before onboarding a vendor that will handle customer data we review its security documentation (such as a SOC 2 report), sign a data processing agreement and record it in our vendor register. Critical vendors are re-reviewed [annually].
  3. Do your contracts with subprocessors include security and confidentiality obligations?
    Starter answer: Yes. Our agreements with subprocessors require them to protect customer data with appropriate security measures, keep it confidential and notify us of incidents.
  4. Do you rely on any single vendor whose failure would stop your service?
    Starter answer: Our main dependency is [Cloudflare]. We mitigate the risk with their multi-region architecture, regular backups we control and a documented recovery plan.
  5. Do you allow customers to audit your security?
    Starter answer: We share our [SOC 2 report], penetration test summary and policies under NDA, and we answer reasonable follow-up questions. On-site audits are available [under an enterprise agreement].

Privacy

  1. What personal data do you collect about your customers' users?
    Starter answer: We collect only what the service needs: [names, work email addresses and usage logs]. We don't sell personal data or use it for advertising.
  2. Do you have a privacy policy, and where is it published?
    Starter answer: Yes. Our privacy policy is published at [yourcompany.com/privacy] and explains what we collect, why, who we share it with and how to exercise privacy rights.
  3. Will you sign a data processing agreement?
    Starter answer: Yes. Our standard data processing agreement is available on request, and we review customer DPAs on [enterprise plans].
  4. How do you handle data subject requests such as access or deletion?
    Starter answer: Customers can export and delete their users' data themselves. For other requests we respond within [30 days] and help customers meet their own obligations.
  5. Do you transfer personal data across borders?
    Starter answer: Data is processed in [the United States and Canada]. Where data leaves its home region we rely on appropriate safeguards such as standard contractual clauses.

Product and support

  1. Do you support single sign-on (SAML or OIDC) for customer accounts?
    Starter answer: [Yes. Customers can connect their identity provider using SAML 2.0 or OpenID Connect.]
  2. Can customers export their data?
    Starter answer: Yes. Customers can export all of their data at any time in [CSV and JSON] formats without contacting support.
  3. What are your support hours and response times?
    Starter answer: Support is available [Monday to Friday, 9 am–5 pm Pacific time] by [email]. We respond to urgent issues within [4 business hours].
  4. Can customers control which of their staff can access the service?
    Starter answer: Yes. Account owners invite and remove users, assign roles that limit what each person can do, and can remove access immediately.

Turn this template into your answer library

Import the CSV, adapt the answers, approve them — and answer the next questionnaire from it. Free.

Create a free workspace