Blog
How to Read a Security Questionnaire from a Big Customer
At some point, a large customer will send you a security questionnaire. It might arrive with a new contract, at renewal, or out of the blue from a procurement or vendor-risk team. It may be a spreadsheet with hundreds of rows, a web portal, or a standard form with a name like SIG or CAIQ. And it usually comes with a deadline.
For a company of 50 to 250 people, the first one is daunting. It doesn't need to be. Most of these questionnaires ask about the same handful of controls in different words, and with a little preparation you can answer them honestly, quickly and in a way that builds the customer's confidence.
Why customers send them
Large companies are increasingly responsible for the security of their suppliers. If a supplier with access to their data or systems is breached, they may be affected too. Their own insurers, auditors and regulators expect them to check. The questionnaire is how they do it.
That means the person sending it usually isn't trying to catch you out. They need a completed file showing they did their homework, and they need to flag any real risks. Clear, honest answers make their job easier.
What they're really asking
Strip away the format, and almost every questionnaire covers the same areas:
- Access control: who can get into your systems, and is multi-factor authentication (MFA, a second step beyond a password) required?
- Data protection: what of their data you hold, where it's stored, whether it's encrypted, and who can see it.
- Device and network security: endpoint protection, patching, firewalls and remote access.
- Backups and continuity: can you keep serving them if something goes wrong?
- Incident response: do you have a plan, and will you tell them promptly if their data is involved?
- Vendor management: who else touches their data through you, such as your cloud providers and IT company?
- People: background checks, training, and what happens when someone leaves.
- Policies: written security policies, and whether anyone reviews them.
Notice how much of that overlaps with what cyber-insurance carriers ask. In our review of 13 public carrier applications (November 2026), MFA, backups, training, incident plans and encryption each appeared on 11 or more forms. Work done for your insurance renewal is most of the work done for your customers.
Read it before answering it
Before anyone starts typing, spend half an hour on these questions:
What will they actually use it for? Ask your contact. Sometimes the questionnaire is a formality; sometimes specific answers decide whether you get the contract.
What scope applies? A questionnaire written for a cloud software provider may ask about data centers and code development you don't have. "Not applicable, because we don't host customer data in our own systems" is a perfectly good answer when it's true.
Which questions are must-haves? Some questionnaires mark critical controls, or your contact will tell you which ones matter most. Focus there first.
Is there a deadline, and is it firm? Asking for an extra week to answer accurately is normal and usually granted.
How to answer well
Be accurate, not aspirational. The same principle as on an insurance application applies: answer what's true today, and be ready to show evidence. Contracts often include your questionnaire answers, or a promise that they're accurate.
"Partially" and "in progress" are allowed. A clear answer like "MFA is required for email and remote access; rollout to our accounting system completes in March" is far more credible than an unqualified yes. Most customers would rather see a plan than a guess.
Explain compensating controls. If you don't do something exactly as asked but have a reasonable alternative, say so. For example: "We don't have a dedicated security team; monitoring is provided by our managed-service provider's 24/7 security operations service."
Keep answers short. One or two clear sentences per question. Long answers invite more questions.
Attach evidence when asked, carefully. Share policies and summaries, not sensitive details like network diagrams or passwords. If something sensitive is requested, offer to walk through it on a call.
Don't overcommit in the comments. Avoid promising things like "we will notify you within one hour of any incident" unless you've confirmed you can deliver it. Notification timelines often end up in contracts.
Build an answer library
When I ran IT at a company of about 200 people, the second questionnaire took half as long as the first, and the fifth took an afternoon, because we kept every answer. Once you've answered a questionnaire carefully, save the answers, the evidence and the date, and reuse them.
A simple answer library includes:
- Standard answers to the common questions above, reviewed every six months.
- A short security overview document, two or three pages, describing your controls in plain language. Many customers will accept it in place of some questions.
- Your current policies: security, acceptable use, incident response, backups.
- Evidence: MFA settings, backup and restore-test dates, training completion, your IT provider's written answers.
- Your cyber-insurance certificate, which customers increasingly ask for.
The same evidence folder you build for insurance does double duty here.
When the questionnaire finds a gap
Sometimes the honest answer is "no." That's useful information, not a failure. Note the gap, tell your contact how and when you plan to address it, and add it to your security budget. Customers routinely accept known gaps with a credible plan. What damages trust is a "yes" that turns out not to be true.
Who should own it
Questionnaires touch sales, IT, legal and leadership. Put one person in charge of coordinating answers, usually someone in operations or the leader closest to the customer, with IT supplying the technical answers and a senior leader reviewing before anything is sent. Contract commitments deserve a look from whoever reviews your contracts.
What to do Monday morning
- Ask your sales and operations leaders whether any customer questionnaires are pending or expected this year.
- Pick one owner for coordinating questionnaires, with IT and leadership review built in.
- Start an answer library with your standard answers, policies and evidence, and date every item.
- Draft a two-page security overview in plain language that you can send with any questionnaire.
- Reuse your insurance-renewal evidence, since most questions overlap, and log any gaps with a plan and a date.
The living, dated security record we're building at Shorehelm is meant to answer many of these questions in one place, for brokers and customers alike.