Cyber insurance and client security reviews
How to answer a vendor security questionnaire
A vendor security questionnaire asks a small business how it will protect the data a bigger client hands it: who is in charge of security, written policies, multi-factor authentication, encryption, backups, updates, antivirus, incident response, staff and your own vendors. Answer every question for how your office works today, from a record you could show if asked, and mark questions about software you don't build or host "N/A" with a one-line reason. Explain each No with what you do instead, and attach only what the form asks for, because some clients make your answers part of the contract.
These forms come from clients, prime contractors and universities, not from a regulator, and there is no single form. Insurers ask many of the same questions on their applications, and the guide to cyber insurance requirements for small businesses covers those.
What are the common vendor security questionnaires?
Two published standards are the Shared Assessments SIG and the Cloud Security Alliance's CAIQ, and several universities publish their own. On October 18, 2026 we read three questionnaires that their owners publish openly, plus two documents that explain when a questionnaire is required:
- Rutgers University's 3rd Party Security Questionnaire (marked V5.0 on its question pages), 12 pages
- the University of Pittsburgh's Security Assessment Questionnaire (v1.7, March 2017), 12 pages
- the Cloud Security Alliance's Consensus Assessments Initiative Questionnaire, or CAIQ, version 4.1.0, an Excel workbook
- the University of Michigan's Third Party Vendor Security and Compliance standard (DS-20, version 2.2)
- Washington State University's Information Services Review Questionnaire, the intake form that decides which security review a purchase gets
We extracted the text of each PDF with a script, read every question, and counted. The Rutgers form has 100 questions for the vendor across 12 sections, plus 13 for the Rutgers staff member who requests the review. 68 of the vendor questions have a drop-down answer box, and the other 32 ask you to describe something. 20 of the 100, all of sections 12 and 13, ask about writing software or running virtual servers. An accounting firm, a law office or a staffing agency that doesn't build or host software answers those 20 with N/A.
The CAIQ has 283 questions in 17 domains, each answered Yes, No or N/A. It is written for cloud service providers. If a client sends it to an office that sells a service rather than software, ask whether a shorter form applies.
We left out the Shared Assessments SIG and SIG Lite, two common questionnaires, because we couldn't find a copy published by Shared Assessments to read. The Higher Education Community Vendor Assessment Toolkit (HECVAT), which the WSU form sends cloud vendors to, wouldn't download for us.
Why did a client send you a security questionnaire?
A client sends one because of the data you'll touch. The University of Michigan's standard spells this out. A vendor that will access, process or keep data the university classifies as Restricted or High must complete its Vendor Security Questionnaire before the contract is awarded. A vendor that handles Moderate data is generally expected to sign a data security agreement but doesn't have to complete the questionnaire. Low-risk data needs no security review.
The WSU intake form works the same way. Its key questions ask how the data is classified and whether it will be stored at an outside facility, and the answers decide which review follows.
So before you answer, find out what data the client will give you and which systems at your office will hold it. That tells you the scope of most answers.
What a vendor security questionnaire asks a small business
Rutgers and Pittsburgh word their questions differently, but they cover the same ground. This table pairs the topics both ask about with the record a small office can answer from.
| Topic | Rutgers | Pittsburgh | What to answer from |
|---|---|---|---|
| Who is in charge of security | 2.2 | Roles & Responsibilities | The person named in your written policy |
| A written security policy | 3.1, asks for a copy | Information Security Policy & Procedures | Your signed policy or WISP, with its date |
| Incident response | 3.2, 8.1 to 8.4 | Process & Procedures | Your incident response plan |
| Passwords and two-step sign-in | 4.3, 4.5 | Access Management | Your email system's sign-in report |
| Removing access when people leave | 4.2 | Termination or Change in Employment | Your offboarding record for each person |
| Encryption and laptops | 5.2, 5.6, 7.4, 7.5 | Encryption, Media Handling | Encryption status for each computer |
| Backups and recovery | 7.1 to 7.7 | Disaster Recovery Plan & Backups | Your backup log and the date of the last test restore |
| Disposing of old computers | 7.9 | Secure Disposal | A record of each drive wiped or destroyed |
| Staff agreements and checks | 6.1, 6.2 | Training, Background Checks, Prior to Employment | Signed confidentiality agreements, training records |
| Your own vendors | 2.9, 9.5, 9.6 | External Parties | Your vendor list and each agreement |
| Antivirus and patching | 11.1, 11.2 | Antivirus, Vulnerability Assessment | Update and antivirus status for each computer |
| Outside audits and testing | 10.1, 10.4, 11.3 | Supporting Documentation, Vulnerability Assessment | If you've had none, say so |
| Physical security | 9.1 | Secure Areas | Who has keys and where the computers sit |
Rutgers also asks whether you have security controls for email (5.3). If your domain has no DMARC record, the honest answer is weaker than it needs to be. On October 14, 2026 we checked the domains of 262 small tax and accounting firms in Alabama, Tennessee and Georgia that receive email on their own domain, and 122 (47%) had no DMARC record. The post on setting up DMARC for a small business covers the fix.
How to answer from evidence
Pittsburgh's instructions say the answers must describe what is in place now and that only people who know each area should answer. They also say the material becomes part of the related contracts. Read every answer as a promise you'll be held to.
- Get the whole package and the deadline. Ask whether there are attachments, a data security agreement or a business associate agreement to sign alongside the form.
- Pull the records first. Before writing anything, export the reports you'll answer from, dated today. For Microsoft 365, the MFA Capable column in the user registration details report (Entra admin center, Entra ID, Authentication methods, Activity) shows who can use multi-factor authentication; it needs an Entra ID P1 or P2 license. In Google Workspace, the Security user report shows each user's 2-Step Verification enrollment. On a Windows computer, manage-bde -status shows whether each drive is BitLocker-protected.
- Answer for the systems that will hold the client's data. Rutgers asks many questions about "the solution." For an office that provides a service, that's your email, file storage and practice or accounting software.
- Describe, don't stop at Yes. Pittsburgh asks for descriptive answers. "Yes. Every account in Microsoft 365 requires a code from the Authenticator app at sign-in. 9 of 9 users are MFA capable as of October 18, 2026" tells the reviewer what they need.
- Answer every question. Rutgers says it reviews a questionnaire only when every question has been addressed. Pittsburgh asks you to give the reason when a question doesn't apply.
- Answer each question in full. Pittsburgh asks you not to point to another answer, since a similar question may come from a different angle. Copy the text if you need to.
- Keep a copy. Save the form, the reports you used and the date you sent it. The next client will ask the same things, and your answers should match.
What to do with a no answer
Write No when the control isn't in place, then say what you do instead. The CAIQ defines a No as a control that is not implemented while in scope, and lets the vendor explain why and what has to be done. That's a good pattern for any form.
Some example answers, to rewrite so they match your office:
- Do you have a SOC 2 report? "No. We're a 6-person office and haven't had a SOC 2 audit. Our written security policy, signed October 2026, is attached." A SOC 2 is a report a CPA firm issues on a company's controls (AICPA).
- Do you conduct penetration testing? "No. We check every computer's updates, antivirus, firewall and encryption daily and keep a dated log of the results."
- Are passwords changed at least every 90 days? (Rutgers 4.5b) "No. We follow NIST SP 800-63B-4, which says verifiers shall not require periodic password changes, and require two-step sign-in on every account." The rule is in section 3.1.1.2 of NIST SP 800-63B-4.
Give a date only if you've committed to it. Pittsburgh asks for circumstances currently in place, and a contract that includes your answers turns "we plan to by March" into a promise.
Some Nos take an afternoon to fix. Turning on two-step sign-in for every account or adding a DMARC record is cheaper than explaining the gap, so do those before you send the form.
What to attach to a security questionnaire
Each form asks for supporting documents:
- Rutgers asks for a copy of your security policy (3.1), SOC 2 or SOC 3 reports (10.1), certifications (10.2), the results of any outside security review (10.4), proof of network segmentation (4.12), and architecture and data flow diagrams (1.13).
- Pittsburgh asks for a security or architecture diagram and a SOC 1 or SOC 2 report, sent as separate files and named in the answer that refers to them.
- WSU asks for security program documentation, outside audit reports such as a SOC 2 Type 2, and network diagrams.
If you have a written security policy or WISP, an incident response plan and the dated reports from step 2, send those, and say plainly which requested items don't exist.
If you'll handle patient information, the client may also ask for a business associate agreement, and Pittsburgh asks whether you have agreements with your own vendors that touch sensitive data. The post on which vendors need a business associate agreement covers who needs one.
Be careful with diagrams and test results. WSU's own form lists the security architecture of IT systems and security assessment, penetration test and audit results among the data it treats as confidential. Treat yours the same way. Send a simple diagram without internet addresses or passwords, ask for a confidentiality agreement first if you don't have one, and use the client's portal or a secure file link rather than an email attachment.
Crashcart, which runs IT for small offices, keeps an evidence log of every check and fix on each computer, with the date, and writes the security policies and incident plan for you to sign. For a client questionnaire, download the evidence pack from the Safeguards page and answer from it, or ask Crashcart's IT Manager about a question you're unsure of. You still answer the form and sign it.
Checklist before you send it
- Ask the client what data you'll handle and which form applies.
- Get every attachment and agreement that comes with the form.
- Export dated reports for two-step sign-in, encryption, updates, antivirus and backups.
- Answer every question, with N/A and a reason where it doesn't apply.
- Describe each Yes, and explain each No with what you do instead.
- Fix the quick gaps, such as two-step sign-in and DMARC, before you send.
- Attach your security policy or WISP, your incident plan and the reports, and say which requested documents don't exist.
- Send diagrams only under a confidentiality agreement and through a secure channel.
- Keep a copy of the form, the reports and the date.
This is general information, not legal advice. For your situation, ask your attorney.
More in this topic
Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.