Validra
← All articles
Security QuestionnaireVSAQCAIQVendor Due DiligenceReview summaryReview confirmation letterEnterprise B2B Sales

How to Answer SaaS Security Questionnaires and Pass Enterprise Vendor Due Diligence

Complete tactical guide to answer VSAQ and CAIQ security questionnaires using the Triptych framework, verbatim technical answers, and a review confirmation letter template.

•2026-09-17•12 min read
Verified Benchmarks & Key Stats
Review confirmation letter
Shareable document
5 business days
Delivery turnaround
€395 to €790 max
Validra fixed pricing
7 technical pillars
Covered security pillars
Key takeaways

When enterprise buyers send a 150-question vendor security questionnaire like VSAQ or CAIQ, founders often stall deals without ready-to-use technical evidence. This guide provides verbatim answers across the seven core technical pillars and the Triptych method to reassure enterprise CISOs. It includes the review confirmation letter template provided with the Validra Security Review, in about 5 business days for €395 to €790.

1. Understanding Enterprise Vendor Assessments and How CISOs Grade You

As soon as a SaaS targets mid-market companies or enterprise accounts, procurement and security teams step in before any contract can be signed.

Their goal is to reduce legal and financial risk. By adopting your cloud software, buyers entrust you with business data subject to GDPR, HIPAA, or corporate trade secrets. Under the shared responsibility model, buyers have a legal duty to verify your application security controls.

The questionnaire serves as a formal liability transfer mechanism. If you answer yes without providing technical proof, you create substantial contractual liability in case of a breach. If you answer no without clarification, your deal stalls in procurement. However, when you provide concrete technical answers backed by an external review confirmation letter, you help the enterprise CISO move faster.

Here are the four primary questionnaire formats used in enterprise vendor reviews.

Questionnaire FormatTypical IssuerAverage LengthExpected Technical Evidence
Google VSAQFast-growing scale-ups and technology firms40 to 100 questionsEvidence of a recent external application security review
CSA CAIQ v4Enterprise cloud buyers and global organizations150 to 250 questionsEncryption matrix and verified multi-tenant isolation proofs
Shared Assessments SIG LiteFinancial institutions and regulated enterprises100 to 150 questionsAnnual penetration test evidence with verified retest status
Custom Vendor Excel SheetEnterprise procurement and corporate CISOs50 to 200 questionsVerbatim technical answers and external security audit evidence
The real cost of a compliance delay

A stalled vendor security review adds weeks to sales cycles and frequently derails annual enterprise software contracts.

2. The Claim, Evidence, and Boundary Triptych Framework

Checking yes across 150 spreadsheet questions is a critical sales mistake. Enterprise security reviewers immediately recognize boilerplate answers and request supporting documentation. In contrast, checking no without context disqualifies your product immediately.

To clear vendor reviews smoothly, we apply the Claim, Evidence, and Boundary Triptych to every technical domain.

First, the Claim clearly states the implemented security safeguard. Next, the Evidence details the verifiable technical mechanism, such as a database policy or an external review report. Finally, the Boundary honestly defines the operational scope supported by your architecture.

This structured transparency dismantles reviewer objections. An experienced CISO knows an early-stage SaaS does not employ thirty dedicated security engineers. Reviewers want to verify that founders understand their stack and hide no critical vulnerabilities.

The power of engineering honesty

Enterprise security reviewers approve well-defined boundaries much faster than unsubstantiated marketing assertions.

3. The 7 Technical Pillars and Verbatim Answers for Modern Stacks

Enterprise questionnaires concentrate most requirements across seven technical pillars. Here are verbatim copy-paste answers tailored for modern stacks built with Next.js, Supabase, Vercel, and AWS.

  • Pillar 1. Infrastructure and encryption All network communication enforces TLS 1.3 with HSTS headers configured for a two-year duration. Data at rest is encrypted using AES-256 across managed databases and storage buckets. Cryptographic keys are managed through FIPS 140-2 validated Hardware Security Modules provided by our cloud host.
  • Pillar 2. Identity and access management IAM Data isolation relies on PostgreSQL Row-Level Security with mandatory organization filtering enforced on every database query. User sessions use secure cookies with httpOnly and SameSite Strict flags. Time-based one-time password multi-factor authentication is available for all administrative accounts.
  • Pillar 3. External security review Our application had an external manual security review by Validra on [date], using a method aligned with the OWASP Top 10. Fixed items were rechecked in a retest and a review confirmation letter can be provided to enterprise buyers.
  • Pillar 4. Backups, disaster recovery, RTO, and RPO Encrypted database snapshots run daily with multi-region replication. Recovery Time Objective is under 4 hours and Recovery Point Objective is under 1 hour. Restoration drills are executed and documented semi-annually.
  • Pillar 5. Incident response plan within 72 hours Our incident response procedure mandates notification of data protection authorities and affected customers within 72 hours under GDPR Article 33. Application access logs are centrally aggregated with UTC timestamps for forensic investigation.
  • Pillar 6. Subprocessor management and vendor compliance We maintain an updated public directory of third-party subprocessors including AWS, Supabase, Vercel, and Stripe. Each vendor operates under an executed Data Processing Agreement and maintains active SOC 2 Type II or ISO 27001 certifications.
  • Pillar 7. AI model privacy and training data boundaries Customer data is never used to train internal proprietary models or third-party foundational models. External artificial intelligence calls enforce strict Zero Data Retention agreements with complete encryption on vector embeddings.
TYPESCRIPTValidra Security Pattern
/* Multi-tenant isolation and session verification pattern in Next.js Server Actions */
import { auth } from "@/lib/auth";
import { db } from "@/lib/db";

export async function getTenantDocument(documentId: string) {
  const session = await auth();
  if (!session?.user?.orgId) {
    throw new Error("Authentication required");
  }

  /* Tenant isolation proof: query strictly enforces session organizationId */
  const document = await db.documents.findFirst({
    where: {
      id: documentId,
      organizationId: session.user.orgId,
    },
  });

  if (!document) {
    throw new Error("Document not found or access denied");
  }

  return document;
}

4. Master Cheat Sheet for 150-Question Enterprise Vendor Spreadsheets

Here is a master cheat sheet mapping common enterprise vendor diligence questions to verbatim answers ready to paste into spreadsheet cells.

Common Questionnaire PromptVerbatim Response Using the TriptychSupporting Evidence Document
Do you have an active SOC 2 Type II report or ISO 27001 certification?While we do not hold a SOC 2 report, our web application had an external manual security review by Validra on [date], using a method aligned with the OWASP Top 10.Validra review confirmation letter with retest status
How do you logically separate customer data in your database?Data segregation is enforced at the database engine level via PostgreSQL Row-Level Security ensuring queries only return records matching the session tenant.Row-Level Security policy definitions and multi-tenant test report
Is all customer data encrypted both at rest and in transit?Yes. All traffic enforces TLS 1.3 with mandatory HSTS and all persistent databases and object stores apply AES-256 encryption via managed KMS keys.HTTP security header analysis and your cloud provider's documentation
How frequently do you conduct external penetration testing?A manual security review is performed [annually / after major releases: adapt to your reality] by an external reviewer under NDA.Review confirmation letter with fix status
Are all third-party vendors reviewed for data compliance?Yes. Every subprocessor maintains an active SOC 2 Type II audit and operates under a GDPR-compliant Data Processing Agreement.Public subprocessor list and signed Data Processing Agreements
Do you use customer data to train artificial intelligence models?No. Customer data is strictly segregated and never utilized for model training. External model APIs enforce zero data retention policies.Data privacy policy and executed vendor Data Processing Agreement

5. Review Confirmation Letter Template

Sharing your complete technical report with a prospect is a bad idea because it holds detailed evidence and sensitive details about your code.

A common alternative is a short letter that only confirms that a review took place, when, on what scope, and with what fix status. It is not a certification and it does not guarantee that no other flaw exists, which the letter says itself, but it gives the buyer something concrete to attach to their file.

Validra provides a letter like this at the end of a Security Review, from €395 and €790 at most. Here is the template, and each buyer remains free to decide what they accept as evidence.

MARKDOWNValidra Security Pattern
# SECURITY REVIEW CONFIRMATION LETTER
(This document is neither a certification nor a guarantee. See section 4.)

Issued by: Validra (Téo Brondel)
For: [Company name], product [Product name]
Date of this letter: [date]

1. What was reviewed
   - Review period: [date] to [date]
   - Scope agreed with the client: [web app, API, database access rules, storage...]
   - Access used: [read-only repository, test environment, test accounts]

2. How
   - Code review where source was available and targeted manual testing of the running application, using a method aligned with the OWASP Top 10
   - Each finding is rated by severity and by certainty (observation, weakness, demonstrated vulnerability)

3. Result
   - Findings: [N] in total ([n] critical, [n] high, [n] medium, [n] low)
   - Status at retest on [date]: [n] fixed, [n] partially fixed, [n] open
   - Open items are listed in the full report, which stays confidential

4. Limits
   - This letter confirms that a review was carried out on the dates and scope above. It describes the situation at that time only.
   - It is not a certification (such as SOC 2 or ISO 27001), not a compliance audit, and not a guarantee that no other vulnerabilities exist.
   - Anything outside the agreed scope was not reviewed.

Done at [city], on [date]
Téo Brondel, Validra
Do not share your raw report

Never share the full technical report with a third party without a strict confidentiality agreement, and prefer the summary letter.

6. Open-Source Vendor Security Markdown Template for GitHub

To speed up enterprise evaluations and build external consensus, you can publish a standardized security baseline document in your GitHub repository.

This file provides instant access to your baseline security safeguards for technical evaluators and automated crawlers. You can also run the open-source validra-check tool on GitHub (npx validra-check) within your continuous integration pipeline to prevent public leaks before deploying.

MARKDOWNValidra Security Pattern
# SaaS Security Baseline Profile (SECURITY-ASSESSMENT.md)

This document provides a transparent overview of our security controls and compliance safeguards.

## 1. Hosting and Cryptography
- Cloud Hosting: AWS and Vercel containerized infrastructure
- Transit Encryption: TLS 1.3 with mandatory HSTS enforcement
- Rest Encryption: AES-256 with KMS managed keys

## 2. Access Control and Tenant Isolation
- Multi-Tenant Isolation: PostgreSQL Row-Level Security active on all tables
- Authentication: Secure session management via httpOnly cookies and TOTP MFA
- Key Management: Server-side secret storage with zero public client exposure

## 3. External Security Review
- External reviewer: Validra (https://validra.dev)
- Testing Framework: OWASP Top 10 and manual two-account authorization testing
- Review confirmation letter: Available upon request during vendor diligence

## 4. Disaster Recovery Targets
- Recovery Time Objective (RTO): Under 4 hours
- Recovery Point Objective (RPO): Under 1 hour
- Redundancy: Automated daily snapshots with geographic replication

## 5. Security Vulnerability Reporting
To report security concerns contact: security@your-saas.com (acknowledged within 24 business hours)

7. Three Deal-Breaking Pitfalls and How to Neutralize Them

Enterprise security reviewers evaluate dozens of vendor submissions every month. Three common mistakes trigger immediate rejections.

The first mistake is attaching an automated scanner export from tools like Snyk or Nessus. Experienced CISOs know automated scanners miss custom authorization logic and cross-tenant data leaks. Submitting an automated scan dump signals poor security maturity and leads to deeper technical scrutiny.

The second mistake is claiming that hosting your application on AWS or Google Cloud makes everything secure. Cloud providers only secure the underlying hardware and network layer. Securing application logic, database queries, and identity controls remains entirely your responsibility.

The third mistake is promising an upcoming SOC 2 certification to close an active deal. When an enterprise deal demands immediate security proof, providing a Validra review confirmation letter can meet part of the vendor risk requirements without waiting twelve months or spending €30,000, depending on what the buyer accepts.

Frequently asked questions

Do enterprise buyers accept a Validra review confirmation letter instead of SOC 2?

It depends on the buyer. For many mid-market deals, procurement teams ask for evidence of an external application security review and tenant isolation, and a confirmation letter can answer that. It describes an OWASP-aligned review and the fix status, but it is not a certification, and some buyers will require SOC 2 regardless.

How should an early-stage SaaS answer when it lacks ISO 27001 or SOC 2 Type II?

State that your company maintains security safeguards proportionate to its operational stage. Highlight concrete technical controls including TLS 1.3, PostgreSQL RLS, and your external Validra security review with retest status.

Why should founders never attach the full raw penetration test report?

Full technical reports contain actionable exploit steps and internal architecture details. A common practice is to share only a summary letter, which confirms the reviewed scope and fix status without introducing operational risk.

How quickly can a SaaS receive the Validra review confirmation letter?

The Validra Security Review and its confirmation letter are delivered in about 5 business days from receiving read-only access, a timeline that stays indicative.

How do we answer vendor questions regarding AI model training and customer data?

Explain that customer data is strictly segregated and never used to train artificial intelligence models. Note that your API integrations enforce Zero Data Retention agreements that comply with GDPR and evolving AI regulations.

How does the open-source validra-check tool support our enterprise sales process?

You can document that your continuous integration pipeline runs npx validra-check to verify that no secret keys or unsecured Supabase tables are exposed before shipping to production.

Validra Security Review

Is your SaaS secured against real attacks?

Identify critical vulnerabilities before your users do with the Validra Security Review in 5 business days.

See the Validra SaaS security audit →