How to answer a security questionnaire without a security team
A step-by-step process for small SaaS and fintech teams facing a buyer's security questionnaire, with answer templates, evidence and the rules that apply.
Answer every question with one of four honest positions (yes with evidence, partly with a plan, no with a plan, or not applicable with a reason), and never claim a control you do not have. Before you write a single answer, find out which framework the questionnaire is based on, build an inventory of what you run, and collect evidence once into a folder you can reuse. A first questionnaire done this way takes a few focused days. The second takes hours, because most of the answers already exist.
What lands in your inbox
Security questionnaires come in a few shapes. Knowing which one you have tells you where to look for help.
| Format | Who owns it | What to know | |---|---|---| | CAIQ | Cloud Security Alliance | A set of yes or no questions documenting the security controls in IaaS, PaaS and SaaS services. Version 4.1 maps to CSA's Cloud Controls Matrix and is what you submit to the STAR Registry for Level 1 | | SIG | Shared Assessments | A third-party risk questionnaire. Its site asked us to sign in, so we have not given version details here. Ask the buyer which version and scope they sent | | Request for a SOC 2 report | Your auditor, under AICPA standards | SOC reports are assurance reports provided by CPAs. SOC 2 covers controls relevant to security, availability, processing integrity, confidentiality or privacy | | Questions mapped to ISO/IEC 27001 | ISO and IEC | ISO's site blocked our request, so we give no detail here. Check the current edition and whether the buyer wants a certificate or just mapped answers | | The buyer's own spreadsheet | The buyer | Usually borrows from the formats above. Often a few hundred rows |
If the buyer accepts a filled-in CAIQ, or a published report, in place of their spreadsheet, ask. One reusable document beats a hundred custom ones.
Rules that may apply to you
This is general information, not legal advice. Rules depend on your sector, customers and country, so check your own market.
The principle is the same everywhere: buyers are asked to manage the risk their suppliers bring, so they pass questions down to you. In some markets, rules make that more formal.
- United States. No single law requires a SOC 2 report. Buyers ask for it because it is a CPA's report on your controls under AICPA standards.
- United Kingdom. Cyber Essentials is the government-backed minimum standard. It covers five technical controls: firewalls, secure configuration, security update management, user access control and malware protection. The NCSC says a growing number of organisations require suppliers to be certified to bid for work. Cyber Essentials Plus adds independent technical testing.
- European Union. The NIS2 Directive sets cybersecurity rules for 18 critical sectors, including finance and digital infrastructure. Member States had until 17 October 2024 to put it into national law, and national strategies include supply chain security. If your customer is in scope, expect detailed supplier questions.
- Australia. The Australian Signals Directorate publishes the Essential Eight, eight mitigation strategies with a maturity model for assessing them. If an Australian buyer refers to it, ask which maturity level they expect.
- India. CERT-In's directions of 28 April 2022 require service providers, intermediaries, data centres, body corporates and government organisations to report listed cyber incidents to CERT-In within 6 hours of noticing them, and to keep logs of ICT systems for a rolling 180 days within Indian jurisdiction. Indian buyers may ask how you meet both.
The process, step by step
Timings are a suggested starting point, not a benchmark.
Day 1: triage the questionnaire
- Find the deadline and the person on the buyer's side who reads the answers. Email them to introduce yourself.
- Identify the format. CAIQ, SIG, ISO-based, or custom.
- Split the rows into groups: policies, access, encryption, development, vulnerability management, incident response, vendors, business continuity, privacy.
- Give each group one owner. In a small company, this is often the CTO for half of it and the founder for the rest.
Day 1: know what you run
Most questionnaires start with some version of "describe your environment". You cannot answer well without an inventory:
- Code repositories.
- Public domains and URLs, including old ones.
- Cloud accounts and the services inside them.
- Third-party services that hold customer data.
- Where sensitive data lives: card data, identity documents, personal data.
Write it down once and keep it current. It is the base for every answer.
Days 2 to 3: collect evidence once
Make one folder. For each claim you expect to make, save the proof: a screenshot of MFA enforced on your identity provider, your branch protection settings, your encryption settings, a recent scan report, your incident response document. Date every file. Reviewers trust a dated screenshot more than a paragraph.
Days 2 to 3: scan what is in front of you
If the questionnaire asks about vulnerability management, you need a recent, honest answer for each surface:
- Code. Static analysis for risky patterns.
- Secrets. Scanning repos for keys and tokens, and checking whether found keys still work.
- Dependencies. Checking packages against known advisories.
- Infrastructure files and containers. Misconfiguration checks.
- Live URLs. Probing from outside, the way an attacker would.
Do not hand over the raw output. Rank what you find by how close it is to customer data, fix what sits on a short path, and re-scan to confirm. Our post on finding the path, not the pile shows how.
Day 4: write the answers
Use the four positions below. Keep answers short. Link evidence by file name.
Day 5: review and send
Have a second person read every "yes". For each one, ask: could we show this tomorrow if asked? If not, change it.
Who owns what
| Question area | Owner | Evidence | First step | Never | |---|---|---|---|---| | Access control and MFA | CTO | Identity provider settings | Screenshot MFA enforcement | Say MFA is enforced if some accounts are exempt | | Encryption | Lead engineer | Database and storage settings | Export the encryption config | Claim encryption you assume the provider turned on | | Vulnerability management | CTO | Scan reports, fix log | Run and save a scan | Send hundreds of raw findings | | Secure development | Lead engineer | Branch protection, code review rules | Screenshot the settings | Describe a review process nobody follows | | Incident response | Founder or CTO | Written plan, contact list | Write a one-page plan | Promise notification times you have never tested | | Vendors | Operations | List of processors and their reports | Build the vendor list | Leave out a tool that holds customer data | | Policies | Founder | Signed policy documents | Write the missing ones plainly | Download a template and claim it as practice |
Answers you can adapt
Names, products and dates are placeholders.
Yes, with evidence:
Yes. MFA is enforced for all staff accounts through our identity provider, with no exceptions. Evidence: mfa-policy-2026-11-03.png.
Partly, with a plan:
Partly. Production database access requires MFA. Two internal tools still allow password-only login. We will move both behind single sign-on by 31 January 2027 and can confirm when done.
No, with a plan:
No. We do not hold a SOC 2 report today. We have scheduled a readiness review for Q1 2027. In the meantime we can share our completed CAIQ, our latest vulnerability scan summary and our policies.
Not applicable, with a reason:
Not applicable. We do not store card numbers. Payments are handled by our payment processor, and we receive only a token.
When you are asked about something new:
We do not currently have a formal process for this. Can you tell us what you would expect to see? We would rather build the right thing than describe something we do not do.
Asking for more time:
We want to answer section 7 accurately rather than quickly. Could we return it by Friday 14 November? The other sections are attached.
Never claim a control you do not have
This is the rule that matters most. Questionnaire answers can be referred to in the contract, so read the contract with that in mind and ask your lawyer if unsure. If a breach happens and an answer was false, the problem is no longer just technical. Reviewers deal with startups every day. A specific "no, and here is our plan" is normal. A "yes" that falls apart when they ask for evidence damages trust in every other answer.
Watch for the quiet versions of overclaiming:
- Answering "yes" because the cloud provider offers a feature, without checking you turned it on.
- Describing a policy that exists as a document but is not followed.
- Saying "annual penetration test" when you had one test two years ago.
- Claiming a certification held by your cloud provider as if it were yours.
A worked example
This example is made up. Priya is CTO of a 9-person lending software company with staff in Pune and Toronto. A bank in Manchester sends a 240-row spreadsheet the week the contract is due.
On day 1 she finds that 180 rows map to CAIQ questions, so she asks whether a completed CAIQ will do for those. The bank agrees. That leaves 60 custom rows. She splits them between herself and her co-founder Tomás.
Her scan turns up a working API key in an old repository and a staging site nobody remembered. She rotates the key, takes the staging site down, re-scans, and saves both reports. The answer on vulnerability management now says what was found, what was done, and when.
Eleven answers are "partly" or "no", each with a date. The bank asks two follow-up questions and signs.
Mistakes to avoid
- Answering from memory. If you cannot point to evidence, the reviewer will ask for it later.
- Treating a scanner dump as the answer. Hundreds of unranked findings tell the buyer you have not triaged them.
- Forgetting old domains. A forgotten staging site is often the easiest way in.
- Scanning once, just before the review. Scans on a schedule keep the next questionnaire easy.
- Writing a new answer every time. Keep an answer library and reuse it.
- Leaving it to the last day. Contact the reviewer on day 1. Deadlines often move when you ask early.
What to measure
- Hours per questionnaire. It should fall sharply from the first to the third.
- Share of answers reused from your library.
- Follow-up questions from the reviewer. Fewer follow-ups usually means clearer evidence.
- Open "partly" and "no" answers past their promised date. This should be zero. Every date you give is a promise.
- Time from deal to questionnaire returned. Track it, because it affects when revenue lands.
A checklist for the next one
- An asset inventory you trust.
- An evidence folder with dated files.
- Scheduled scans across code, secrets, dependencies, infrastructure files and live URLs.
- Findings ranked by distance to sensitive data, with fixes confirmed by re-scan.
- A completed CAIQ, if your buyers accept it.
- An answer library with the four positions.
- A list of "partly" and "no" answers with owners and dates.
What runs in Sightline today
Sightline covers the scanning and evidence part of this process. It scans code, secrets, dependencies, infrastructure files and live URLs, ranks findings by their path to sensitive data, and keeps re-scan results after a fix. A person approves each finding before you see it. Its compliance view checks a small set of representative controls for SOC 2, ISO 27001, OWASP ASVS and PCI DSS, and exports a printable evidence pack.
Limits. Sightline does not fill in questionnaires, write policies or cover HR, physical or vendor controls. Its control checks help you prepare but are not a full framework, and your auditor still issues any audit opinion. It does not yet read AWS, Azure or Google Cloud accounts directly. Talk to us if you have a questionnaire on your desk, or read how Sightline works.
Common questions
Can I say yes if my cloud provider handles a control?
Only for what you have checked is switched on and covers your setup. A provider's certification covers the provider, not your configuration. Say what the provider does and what you do, separately.
What if the buyer asks for a SOC 2 report and we do not have one?
Say so plainly and offer what you do have: a completed CAIQ, policies, recent scan summaries and a date for your readiness work. SOC reports are issued by CPAs, so nothing you produce yourself is a substitute. Ask whether the buyer will accept a plan with dates in the meantime.
Is a CAIQ free to use?
CSA offers CAIQ v4.1 through its site, and the page lets you access it without an account. The page we opened did not state a price, so check the current terms there.
How long should a questionnaire take?
There is no standard. As a suggested starting point, plan about a week for the first one and expect later ones to take far less once your inventory, evidence folder and answer library exist.
Do we need Cyber Essentials to sell in the UK?
Not by law in general. The NCSC says a growing number of organisations require suppliers to be certified to bid for work, so check your buyer's tender requirements.
Sources
- Cloud Security Alliance, STAR Level 1: Security Questionnaire (CAIQ v4.1), 2026
- AICPA and CIMA, SOC 2 audit and assurance, 2026
- NCSC, Cyber Essentials overview, 2026
- European Commission, NIS2 Directive, 2026
- Australian Signals Directorate, Essential Eight, 2026
- CERT-In, Directions under section 70B(6) of the IT Act, 2022