Selling SaaS to large companies: the security checklist
A SaaS security checklist for founders selling to large companies: what vendor questionnaires ask, what to build first and how to answer them honestly.


The demo went well, the business team wants your product, and then the deal stops moving. The buyer’s security team has sent a long spreadsheet of questions, and procurement will not sign until it is answered. This article is a SaaS security checklist for founders in that position: what a vendor security questionnaire usually asks, from single sign-on to certifications, what to build first when time is short, and how to answer honestly when the true answer is “not yet”. If you are still building your first version, start with launching a SaaS MVP.
This article gives practical pointers as of October 2026. It does not replace advice from your lawyer or a qualified auditor, and requirements vary by buyer, sector and country.
Why large companies send a vendor security questionnaire
When a large company buys your SaaS (software as a service), it hands you some of its data and opens your product to its staff. If your product is breached, its customers, regulators and board will ask the buyer, not you, what it checked. The vendor security questionnaire is that check, written down.
It may be the buyer’s own spreadsheet or a standard set, such as the SIG (Standardized Information Gathering) questionnaire from Shared Assessments or the CAIQ (Consensus Assessments Initiative Questionnaire) from the Cloud Security Alliance. Its depth follows the risk: a tool that stores staff names gets lighter questions than one holding health or payment data. The good news is that the questions are predictable, so you can prepare once.
The SaaS security checklist: what questionnaires ask
Requirements vary by buyer and sector, but seven areas come back in most questionnaires. Certifications, the eighth, have their own section below.
Single sign-on and multi-factor authentication
Large companies want their staff to sign in with their company account, through SSO (single sign-on) based on SAML 2.0 (Security Assertion Markup Language) or OpenID Connect, so that someone who leaves loses every access in one step. Expect questions on multi-factor authentication (MFA) for users outside SSO, and on SCIM (System for Cross-domain Identity Management), which creates and removes accounts automatically. For those users, passkeys, which resist phishing better than passwords and SMS codes, are worth considering.
Roles and permissions
Can the customer’s administrator decide who sees what? Buyers ask for role-based access, least privilege, and whether your own staff can open customer data, and on what conditions.
Audit logs
Who signed in, exported a file or changed a permission, and when. Buyers want logs that users cannot edit, kept for a stated period, that an administrator can export.
Encryption
Data encrypted in transit, with TLS (Transport Layer Security), and at rest, with keys managed properly.
Backups and recovery
How often you back up, where the copies are kept and, above all, when you last tested a restore. Expect RPO (recovery point objective: how much data you could lose) and RTO (recovery time objective: how long you could be down).
Data location and processing
Where the data is hosted, which subprocessors touch it and how you handle personal data. In the European Union, the GDPR (General Data Protection Regulation) requires a written data processing agreement between the customer and you as its processor; see AI and the GDPR for the AI side. Data location rules differ by country and sector, so have a lawyer confirm what applies to your buyers.
Incident process
Who decides, how fast you inform the customer and how you record it. Under the GDPR, a processor must inform its customer “without undue delay” after becoming aware of a personal data breach, and many contracts add a precise deadline.
The checklist: where do you stand?
| Area | Minimum before a first large deal | Evidence to have ready |
|---|---|---|
| Sign-in | MFA for every user; SSO planned | MFA settings, SSO set-up guide |
| Roles | Administrator and standard roles; least privilege for your staff | Table of roles and rights |
| Audit logs | Sign-ins, exports and permission changes recorded | Sample log export |
| Encryption | TLS everywhere; encryption at rest | Summary of your hosting set-up |
| Backups | Automatic backups in a second location | Date and result of the last restore test |
| Data | Hosting region known; subprocessors listed | Subprocessor list, data processing agreement |
| Incidents | Written process with a named owner | Incident response plan |
| Assurance | Independent penetration test; security policy | Test summary, policy |
Tick a row only when the evidence exists today, not when it is planned.
What to build first for an enterprise-ready SaaS
We order the work by three questions: what blocks deals, what is cheap, and what is hard to add later.
- MFA, roles and audit logs. They touch every screen and record, so they are hard to retrofit. Put them in the data model early.
- Tested backups and a written incident process. Mostly organisation rather than code, and they answer a whole section of the questionnaire.
- SSO when buyers ask for it. Identity providers and libraries support SAML and OpenID Connect well; building them from scratch is rarely worth it.
- SCIM and finer controls, such as IP restrictions, when a signed customer needs them.
- A certification or report when several deals depend on it.
Underneath sits the application itself, covered in web application security, and your company’s own basics, covered in cybersecurity for SMEs. And if your customers are SMEs (small and medium-sized enterprises), you may not need SSO or a certificate yet: MFA, clear roles and a short security page may be enough.
Roles are the clearest case for designing in early. Led by our founder, Anass Chabbab, in his previous role as IT director of DIGIIT Solutions (2019–2022), the CRM/ERP for a Sydney law firm was built for desktop, iOS and Android with role-based access and automatically produced documents, for 100+ users, with a first release in under 6 months. A law firm’s files are confidential, which is why access by role belongs in the design from the start. Building such controls into the product, and preparing the evidence buyers ask for, is part of our work on SaaS products.
ISO 27001 or SOC 2: what each one is
Most questionnaires end by asking for a certificate or report and, failing that, independent evidence: a recent penetration test of the application, a written security policy, staff training. The two names that come up are different things.
- ISO/IEC 27001 is an international standard for an information security management system: the policies, risk assessment and controls a company runs to protect information. A company is certified when an accredited certification body audits it against the standard; the certificate covers a defined scope and is maintained through regular surveillance audits.
- SOC 2 (System and Organization Controls 2) is not a certification but an attestation report, issued by an independent firm of certified public accountants under the Trust Services Criteria of the AICPA (American Institute of Certified Public Accountants). A Type 1 report describes your controls at a point in time; a Type 2 report tests whether they worked over a period. It is mostly requested by buyers in the United States.
Ask your buyers which one they accept before you choose. Neither replaces the controls themselves. AnazTech does not certify or audit: we help you build the controls and gather the evidence an auditor will look at.
How to answer a security questionnaire honestly
- Use three answers. Yes, with the evidence. Partially, saying what is missing. No, saying whether it is planned.
- Never answer “yes” to something planned. Answers are often attached to the contract, so an untrue one becomes a commercial and legal problem.
- Describe compensating controls. “No SSO yet; MFA is mandatory and administrators can remove a user immediately” is a strong answer.
- Keep an answer library. One owner, one place, each answer dated. Reuse it, but reread each question: similar wording can ask something different.
- Publish a security page with the essentials (hosting region, encryption, backups, incident contact), and offer a call with the buyer’s security team when a question needs discussion.
Frequently asked questions
Do we need ISO 27001 or SOC 2 before our first large customer?
Not always. For a first deal, many buyers accept a well-answered questionnaire, a recent penetration test and commitments in the contract, especially for less sensitive data. Others, often in finance or health, make a certificate or report a condition of purchase. Ask early what the buyer requires, and start a certification when several deals depend on it.
Should SSO for SaaS be included in every plan?
It is a pricing decision as much as a security one. Many vendors keep SSO for business or enterprise plans, because larger customers are the ones asking. Others include it everywhere, since it helps every customer remove access when someone leaves. Either way, state it clearly on your pricing page.
Who should fill in a vendor security questionnaire?
One named owner, usually your technical lead, collects and approves the answers, with input from whoever runs hosting, support and contracts. Sales should not answer alone: the replies are technical commitments. Keep approved answers in one place, dated, so the next questionnaire starts from reviewed material.
In short
Large companies send security questionnaires because they carry the risk of the software they buy, and the same areas come back every time. Build MFA, roles and audit logs early, test your backups, add SSO when buyers ask, and plan a certification when deals depend on it. Answer every question truthfully, with evidence and dates.
Is a large deal waiting on a security questionnaire? Book a free 30-minute discovery call: we go through the questions with you and decide what to build first.
Related servicesSaaS products
Let’s talk about it on a 30-minute discovery call, free and with no obligation.
Get our next articles in your feed: follow AnazTech on LinkedIn.Follow on LinkedIn






