On this page

A vendor security questionnaire response should turn each customer question into a scoped claim, connect the claim to current evidence, route exceptions to the right owner, and preserve the approved answer for reuse. The workflow below covers all four jobs without treating an old answer as permanent truth.

Security questionnaires are common in customer due diligence, but SOC 2 does not universally require a questionnaire. The AICPA Trust Services Criteria require organizations to assess and manage risks from vendors and business partners under CC9.2; they do not prescribe one assessment form. Your controls, contracts, customer requirements, and the vendor’s risk determine which records you need.

What is a vendor security questionnaire?

A vendor security questionnaire is a set of questions a customer sends to a supplier to evaluate security, privacy, resilience, and third-party controls. The supplier answers from its actual control environment and supports material claims with reports, policies, test results, or other current evidence.

A hand fills out a vendor security questionnaire on a clipboard with a pen and shield icon.

The same term is used from two viewpoints:

  • A buyer uses the questionnaire to assess a prospective or existing vendor.
  • A supplier answers the questionnaire during a customer’s security review.

This guide is for the supplier-side response team: security, governance, risk and compliance (GRC), sales engineering, privacy, legal, and the system owners who verify individual answers. For the buyer-side lifecycle (inventory, risk tiers, approval, contracts, monitoring, and offboarding), use the SOC 2 vendor management requirements guide.

How should you answer a vendor security questionnaire?

Answer a vendor security questionnaire in six steps: confirm scope, assign owners, draft from approved material, verify each claim against current evidence, escalate gaps or disclosure restrictions, and retain the approved submission. A named response owner should control the form from intake through archive.

NIST’s October 2024 Cybersecurity Framework 2.0 supply-chain quick-start guide covers how to define and communicate supplier requirements. The supplier side of that exchange benefits from the same discipline: named owners and recorded decisions make a response reviewable instead of improvised.

  1. Confirm the request and scope. Record the customer, deadline, product or service, deployment model, data involved, contractual context, required questionnaire edition, and confidentiality restrictions. Ask whether the customer accepts an existing security package before duplicating work.
  2. Triage questions by owner. One response owner manages the file. Route identity and access questions to security or IT, architecture and encryption questions to engineering, privacy questions to the privacy owner, contractual promises to legal, and recovery objectives to the business continuity owner.
  3. Draft from approved answers. Reuse an answer only when its applicability, evidence, review date, and approver still match the request. Copying a similar sentence from an old customer file is not enough.
  4. Verify the claim and evidence. Check the source record, not just the prose. Confirm dates, system scope, exceptions, report periods, and whether the evidence may be shared. Replace absolute words such as “all,” “always,” and “never” unless the evidence supports them across the stated scope.
  5. Resolve exceptions before submission. Route partial controls, missing evidence, stale reports, conflicting customer wording, and new contractual commitments to the appropriate owner. Record the decision instead of editing an inconvenient question into a “yes.”
  6. Approve, submit, and retain. Have security or GRC review the completed form; add legal or privacy approval where the answers create obligations. Save the final version, approval record, evidence references, submission date, and customer-specific deviations.

The retained record matters because the next questionnaire may ask the same control in different words. It also gives your team a dated account of what it represented to a specific customer.

What evidence should support each answer?

Evidence should match the exact claim, system scope, and time period in the answer. Use a policy for stated requirements, configuration or system output for implemented controls, and dated test records for operating effectiveness. Do not attach sensitive evidence merely because a question asks for it.

The rows below are response patterns, not claims to copy. Replace bracketed text only after the named owner verifies the value. The same eight rows, with the rest of the library fields, are in the downloadable answer library.

Question domainDefensible answer patternEvidence to verify internallyEscalate whenOwner role
Security governance“Yes. The information security policy applies to [scope], is owned by [role], and was last approved on [date].”Approved policy, version history, owner, acknowledgment or review recordThe policy is draft, overdue for review, or narrower than the answerSecurity lead
Identity and access“Production access uses [identity provider], requires [authentication control], and is reviewed every [approved cadence].”Identity-provider configuration, access-review record, joiner, mover, and leaver ticketsA system sits outside the stated control, or the last review missed its cadenceHead of IT
Encryption and key management“Customer data in [named service boundary] is encrypted in transit using [verified protocol] and at rest using [verified control].”Architecture or data-flow record, cloud or application configuration export, key-management procedureThe question says “all data,” but the evidence covers only selected stores or environmentsEngineering lead
Vulnerability and penetration testing“The last independent penetration test ended on [date]. [Summary status] and tracked remediation are available under [disclosure condition].”Test report, executive summary, findings register, remediation ticketsThe test is stale, material findings remain unresolved, or the customer asks for the full reportSecurity lead
Incident response“The incident response plan was last exercised on [date]. Customer notification follows [approved contractual or policy rule].”Current plan, tabletop record, incident communications procedure, contract termsThe notification deadline the customer asks for is not already approved in policy or contractSecurity lead
Availability and recovery“The approved recovery time objective is [value] and the recovery point objective is [value] for [service]. The last recovery test occurred on [date].”Business continuity plan, service-level objective, recovery test resultSales material, policy, and tested results state different valuesBusiness continuity owner
Privacy, subprocessors, and data location“The service processes [data categories] in [locations] and uses the subprocessors listed at [controlled source].”Data inventory, data-flow map, DPA, subprocessor register, retention scheduleThe request needs a new residency, deletion, or subprocessor commitmentPrivacy lead
Independent assurance“The current [SOC 2 report or ISO 27001 certificate] covers [entity and service] for [period or validity date]. Access is available under [condition].”Issued report or certificate, scope statement, report period, bridge material if applicableThe report period has ended, the scope does not cover the product, or an exception affects the answerGRC lead

Customer evidence and SOC 2 audit evidence overlap, but they are not interchangeable. A customer may accept a SOC 2 report, policy excerpt, test summary, or trust-center statement. A SOC 2 auditor evaluates whether evidence is sufficient for the control being tested. To stage the exports behind your answers, see the SOC 2 evidence request list, organized by source system. Teams handling recurring customer requests can compare security questionnaire automation software by source grounding, file and portal workflows, human review, and usage limits. For controlled document sharing, compare trust center software.

How should you answer yes, no, partial, and not-applicable questions?

Choose the status that matches the implemented control, then state scope and evidence. “Partial” is more accurate than “yes” when only part of the environment is covered. “Not applicable” needs a reason. A roadmap item does not turn a missing control into an implemented one.

StatusWhat the answer should containExample structure
YesImplemented control, scope, owner or mechanism, and current evidence“Yes. [Control] applies to [scope]. It is verified by [evidence] dated [date].”
PartialImplemented portion, excluded portion, compensating control, and approved remediation if one exists“Partially. [Covered scope] uses [control]. [Excluded scope] uses [verified alternative]. [Owner] is reviewing the remaining gap.”
NoDirect “no,” the actual risk treatment, and an approved target date only if one exists“No. [Control] is not implemented. Current risk treatment is [accepted/mitigated/transferred] through [approved measure].”
Not applicableThe product, data flow, or responsibility boundary that makes the question inapplicable“Not applicable. The service does not [activity], as shown in [architecture or data-flow source].”
Cannot discloseWhat can be shared, why access is restricted, and the approved disclosure path“The full report is restricted. We can provide [summary/report access] under [NDA, portal, or controlled-review condition].”

Avoid “yes, see policy” when the question asks whether a control operates. A policy describes what should happen. A configuration export, ticket population, review record, or test result shows what did happen.

Example: a “yes” that should have been “partial”

This is an illustrative example, not a real submission. A reviewer checks the draft answer to “Do you encrypt all customer data at rest?” against the evidence attached to it. The draft cites an encryption setting export for the production database. It says nothing about an analytics export bucket that also holds customer files, and nobody has checked that bucket. “All” claims more than the evidence shows.

DraftCorrected
Answer“Yes. All customer data is encrypted at rest.”“Partially. Customer data in the production database and application file storage is encrypted at rest. The analytics export bucket is outside the configuration reviewed for this answer, and engineering is checking it.”
Status in the libraryYesPartial
Scope qualifierNot statedProduction database and application file storage; analytics export bucket excluded until verified
Evidence referenceEncryption setting export for the production databaseThe same export, plus a storage inventory that lists every database and bucket holding customer data, with the encryption status of each and the analytics export bucket marked “not yet verified”

The library entry stays at Partial until the bucket’s settings are checked. If they show encryption, the owner records the inventory as evidence, resets the review date, and returns the status to Yes. If they do not, the answer stays Partial and the gap goes to the exception log below.

What do SOC 2 auditors expect from questionnaire records?

In a Type 2 examination, the auditor tests whether your defined vendor-risk control operated as designed over the period. A Type 1 covers design and implementation at one date and does not test operation. If your control uses questionnaires for certain vendors, an auditor may sample the completed forms, review conclusions, exceptions, approvals, and follow-up. CC9.2 does not make every questionnaire a mandatory artifact.

The direction of the questionnaire matters:

  • When your company sends a questionnaire to one of its vendors, the completed assessment can support your CC9.2 vendor-management control. A completed form without review notes or a decision only proves that answers were collected.
  • When your company answers a customer’s questionnaire, the submission usually supports customer assurance and sales due diligence. It becomes SOC 2 evidence only when it is relevant to a control, commitment, or sample in your own audit scope.
  • In both cases, unsupported or inconsistent claims reveal a governance problem. Keep the underlying control evidence authoritative and treat each customer submission as a dated representation.

This distinction prevents a common mistake: calling every outbound customer questionnaire “audit evidence” while ignoring the buyer-side assessment records an auditor may actually test.

When should you use a custom questionnaire, SIG, or CAIQ?

Use the format the requester accepts and the service context supports. Custom questionnaires capture customer-specific obligations. The Shared Assessments SIG covers broad third-party risk topics. The Cloud Security Alliance CAIQ focuses on cloud-service control transparency. None removes the need to verify answers and scope.

FormatBest fitStrengthLimitation
Custom customer questionnaireA buyer has product-specific, regulatory, privacy, architectural, or contractual questionsMatches the buyer’s exact decision and risk modelRepeats common questions and may introduce unfamiliar wording or new promises
Shared Assessments SIGThe buyer and supplier want a standardized, broad third-party assessmentCreates a common structure for reviewing multiple risk domainsIt is licensed and versioned; confirm the accepted edition and do not assume it satisfies customer-specific terms
Cloud Security Alliance CAIQ v4.1The subject is an IaaS, PaaS, or SaaS service and the buyer wants cloud-control transparencyUses yes/no questions aligned with the Cloud Controls Matrix and supports CSA STAR Level 1 submissionCloud-focused scope does not automatically answer every legal, privacy, financial, or resilience question in a custom review

A SOC 2 report is supporting assurance, not a substitute for every questionnaire. Its report period, system description, criteria, subservice-organization treatment, exceptions, and complementary user entity controls may answer many questions; customer-specific data flows and contract terms still need separate answers. SIG, CAIQ, and Cloud Controls Matrix artifacts are versioned, so confirm the edition the requester requires before you start.

How should you build a reusable answer library?

A reusable answer library stores more than approved prose. Each record carries a question pattern, a scope qualifier, an evidence reference, a disclosure level, an owner, an approver, a review date, and a status. Those fields let the response owner tell a reusable fact from a customer-specific commitment or a stale claim.

Download the answer library: Excel or CSV, free with no signup. It holds the eight domain rows above and the fields below, with blank rows and dropdowns in the Excel file for your own entries.

FieldWhat to recordWhy it prevents errors
Question patternThe concept customers ask about, such as privileged access review or encryption in transitMatches differently worded questions without relying on exact text
Approved answerPlain-language response with defined termsGives responders a controlled starting point
Scope qualifierProduct, legal entity, environment, region, data category, and what is excludedStops an answer for one service from being applied to another
Evidence referenceControlled link, document ID, report period, or the owner of the configurationLets the reviewer verify the claim at its source
Disclosure levelPublic, NDA, restricted portal, summary only, or internal onlyPrevents accidental sharing of sensitive reports or configurations
Owner and approver roleThe role accountable for the control and the role that approved the wordingCreates a clear escalation path that survives a departure
Last reviewed and review cadenceThe date the owner last checked the answer, how often to recheck, and the changes that force an early review: architecture change, policy revision, incident, new report, or contract updateStops a fixed annual review from missing a material change
StatusYes, Partial, No, or Not applicableShows at a glance which answers need a scope qualifier or an exception

Customer-specific wording, commitments, and exceptions belong in the exception log with legal approval, not in the library. Automation can search the library, suggest matches, flag expired records, and populate a draft. It should not approve scope, invent missing evidence, or turn a conditional answer into an unqualified “yes.” Keep a human control owner responsible for the final claim.

What should happen when evidence is stale, restricted, or missing?

An answer that no longer matches current evidence should not be reused. Mark the record stale, keep its last verified date, and send it to the control owner. Submit a bounded “partial” or “no” where that is the truth, and never change a date or control status to satisfy a form.

  1. Stale report or certificate: State the period or expiry accurately. Ask the assurance owner whether a current report, certificate, or SOC 2 bridge letter exists. A bridge letter does not extend the audit period.
  2. Restricted evidence: Offer the approved alternative: an executive summary, controlled trust-center access, NDA review, or an auditor-to-auditor discussion. Redact deliberately, and keep the dates, scope, and conclusions a reader needs to interpret the evidence.
  3. New commitment: Send notification windows, recovery objectives, residency promises, deletion periods, and audit rights to legal and the control owner before submission. For a missing control, answer “no” and record the risk treatment; our SOC 2 risk assessment template covers the four options. Give a target date only if the owner has approved and funded the work.
  4. Conflicting wording or records: Ask the customer to define terms such as “sensitive data,” “real time,” or “critical vulnerability” instead of substituting your own. If the library, policy, contract, and technical evidence disagree, pause the response, fix the control record first, then update the answer.

Keep an exception log with the question, risk, assigned owner, decision, approval date, and customer-facing wording. It shows which gaps recur without implying each one has been fixed.

What should the final reviewer check before submission?

The final reviewer confirms that every answer matches the requested product, current evidence, and approved disclosure level, and that no unsupported absolute, hidden commitment, or customer-specific wording has slipped into the file or the reusable library.

  • The legal entity, product, environment, regions, and data categories match the request.
  • Every “yes” has a current evidence reference and no known exception. Every “partial,” “no,” and “not applicable” has a stated reason and owner approval.
  • Report periods, certificate validity dates, test dates, and policy review dates are exact.
  • New contractual promises have legal approval and an operational owner, and restricted artifacts go out through the approved NDA, portal, or summary path.

If a customer review exposes weak vendor-management evidence on your side, fix the control record before audit fieldwork. The SOC 2 evidence request list shows how to organize the underlying artifacts, and SOC 2 compliance software can automate that collection. The vendor management requirements guide covers the buyer-side process that CC9.2 addresses.