Third-Party Risk

When the Customer Sends a Security Questionnaire

Sooner or later a good customer sends a security questionnaire. A calm, honest process turns it from a threat into a sales asset.

A clipboard holding a blank sheet of paper with a pen resting on a wooden desk.

It usually arrives attached to good news. A bigger customer wants to expand, or a new one is ready to sign, and their procurement process includes a questionnaire: a hundred questions about encryption, access controls, incident plans, and certifications you may not have.

For a small company without a security team, the first reaction is often panic or its cousin, confident guessing. Both cost you. The questionnaire is really a trust conversation in spreadsheet form, and there is a calm way to have it.

Key takeaways

  • A security questionnaire is a trust conversation, and honesty scores better than bravado.

  • Read the whole thing before answering any of it; half the questions overlap.

  • "No, but here is what we do instead" is a legitimate answer when it is true.

  • Answers you write this time become the library that makes the next one cheap.

  • A questionnaire is also a free gap list: the questions you cannot answer are next year's plan.

Step 1: Read it end to end before typing a word

The first pass is reconnaissance. How many questions, what topics, what evidence do they want attached, and when is it due? Most questionnaires are templates written for companies ten times your size, and a third of the questions will ask about things you do not have in slightly different words.

Note the deadline and, if it is short, ask for the time you need now rather than apologizing later. Procurement teams grant extensions far more readily to vendors who ask on day one than day nine.

Step 2: Answer what is true, plainly

Go question by question and answer the business you actually have, not the one the template imagines. Where you do the thing, say so in a sentence. Where you do not, say that, and say what you do instead: no, there is no 24/7 SOC, and here is who gets woken up and how.

Resist the urge to stretch. A caught exaggeration poisons the whole deal, while an honest "no, not yet" with a sensible alternative is exactly how experienced buyers expect a small company to answer. The same plain-reading skill that helps you read a vendor's SOC 2 report is what your customer's reviewer is applying to you.

Step 3: Escalate the questions you cannot answer alone

Some questions need your IT provider, your landlord, or a decision you have not made. Collect them as you go and ask once, in a batch, rather than dribbling interruptions across the week. Your IT provider has answered these before and can save you hours.

Where the honest answer is a decision, such as whether to adopt a practice the questionnaire assumes, that is a real business choice. Make it on purpose: what it costs, what it unlocks, who owns it. The who-owns-the-fix question applies inside your own answers too.

Step 4: Save everything as next time's library

When it is done, save the completed questionnaire and every answer in a folder labeled for reuse. The next customer's questionnaire will be seventy percent the same questions, and the library turns next year's week of work into an afternoon of review.

Then take the questions you could not answer well and write them on a single page. That page is the cheapest security roadmap you will ever get: a real customer told you exactly what they need you to become.

Frequently asked questions

Can we just get certified instead?

Certifications like SOC 2 answer many questionnaire questions at once, but they are a significant, ongoing commitment. For most small companies, honest questionnaire answers come first, and certification becomes worth it when customers repeatedly demand it.

What if we fail the questionnaire?

A failed questionnaire is information, usually about the gap between what you are and what that customer needs. Sometimes the gap is closeable with a quarter of work; sometimes the customer was never going to fit. Both are worth knowing early.

Should the owner answer it personally?

The owner should own the judgment calls, especially anything that commits the business. The factual assembly can and should be delegated to whoever knows the systems best, with the owner reviewing before it goes out.

A practical next step

If a questionnaire is sitting in your inbox now, start with the end-to-end read and the deadline conversation. If the questions outrun your answers or a key customer's requirements are becoming a roadmap, book a Decision-Clarity Call and we will work through it together.

Next step

Get Board-Ready on AI and Cyber Risk

A 30-minute call. No charge. You'll leave with a clear read on where your oversight stands and what to do about it.

Stop Guessing. Start Scoring
Tyson Martin

Written by Tyson Martin, NACD.DC

Chief Trust, Security & AI Officer. CISO of record at MIO Partners; former CISO & CTO at Lumber Liquidators and Orvis; advisor to 200+ Fortune 500 boards and C-suites at AWS.

See the track record
Keep reading

More on Third-Party Risk

All CISO Insights
Third-Party Risk

When a Critical Vendor Gets Acquired

A vendor acquisition can change terms, roadmap and support overnight. Use a reassessment trigger list to review contract clauses, exit options and timeline.

Third-Party Risk

The Vendor Offboarding Checklist Nobody Runs

Contracts end but access and data often stay. Four steps to close out a vendor: revoke access, return or delete data, close the contract, record risk.

Third-Party Risk

When the AI Vendor Changes the Terms Mid-Contract

When AI vendor terms change, compare the notice with the signed agreement and deployed use. Check data, price, model behavior and available response options.