Guide
How to prepare a vendor security questionnaire
Most security questionnaires are 70 to 300 questions long, and most of those questions have been asked before. The work is not writing. It is finding the answer your company already approved, and spotting the few questions that genuinely need a new decision.
1. Read the questionnaire before answering anything
Open the file and look for three things first: the deadline, the format the buyer expects back (their spreadsheet, a portal, or a PDF), and any instructions tab. Some questionnaires ask for a yes or no plus a comment; others want evidence attached. Knowing this up front avoids redoing work.
Then skim for questions that are not really security questions: indemnity, liability caps, insurance limits and contract terms. Mark them for whoever owns contracts. They should not be answered by the person filling in the technical sections.
2. Start from answers your company has already approved
Your best source is the last two or three questionnaires your team sent, plus any security policies and your SOC 2 or ISO report if you have one. Copy answers that were already reviewed rather than rewriting them. Rewording an approved answer creates a new statement that someone has to approve again.
If you do this regularly, keep those answers in one place: an answer library with one row per approved answer, the document that proves it, who approved it and when it expires.
3. Match, don't guess
Buyers phrase the same control in different ways. "Is MFA required for administrators?" and "Describe how privileged access is authenticated" often have the same answer. Match each question to an approved answer by its meaning, and keep the evidence reference next to it so a reviewer can check it in seconds.
When a question only partly matches, answer the part you can support and say plainly what is not covered. A precise partial answer is better than a confident full one you cannot evidence.
4. Make the gaps visible
Some questions will have no approved answer. Do not fill them in to make the spreadsheet look complete. List them separately with a suggested owner: security, engineering, legal or leadership. That list is the most useful output of the whole exercise, because once those answers are approved they are reusable next time.
5. Review in the right order
- Legal and contract questions, with the person who owns contracts.
- Questions with no evidence, so owners can decide whether to answer, decline or schedule the work.
- Answers you adapted or drafted, checking every factual claim against its evidence.
- Answers copied from your library, as a quick final read for fit.
6. Send, then improve your library
Before sending, check that you have not claimed a certification, audit result, encryption setting or incident history that your evidence does not support. After sending, add every newly approved answer to your library. Each questionnaire should make the next one faster.