The short answer
- A security questionnaire is a set of questions a larger customer sends before buying, covering access control, encryption, backups, testing, incident response, suppliers and data protection.
- Cyber Essentials is the UK government-backed certification for basic cyber security controls, and Cyber Essentials Plus adds a hands-on technical audit; UK central government requires it for some contracts.
- ISO 27001 certifies an information security management system and is widely recognised in the UK and Europe, while SOC 2 is an auditor’s report on your controls that US buyers more often ask for.
Before a large organisation buys a SaaS product, its security team sends a questionnaire and asks for evidence. A security questionnaire is a structured list of questions about how you protect the customer’s data, from staff access and encryption to backups, testing and incident response. A small company can answer one honestly if a few basics are in place, along with Cyber Essentials, a recent penetration test and a data processing agreement.
What a security questionnaire asks
Some customers use their own spreadsheet. Others use a standard set, such as the Cloud Security Alliance’s CAIQ or the Shared Assessments SIG. The topics are much the same.
- Access control. Multi-factor authentication, single sign-on, least privilege, and how you handle joiners and leavers.
- Data protection. Encryption in transit and at rest, where data is stored and how tenants are kept apart.
- Operations. Backups, patching, logging and monitoring.
- Assurance. Certifications, penetration tests and written policies.
- Incidents. How you detect, respond to and report them.
- Suppliers. Your hosting provider and other sub-processors.
- Privacy. Your data processing agreement, retention, and deletion at the end of the contract.
Keep a security pack ready with your policies, a library of approved answers, certificates, a pen test summary and your sub-processor list. Each questionnaire after the first then takes a fraction of the time.
Cyber Essentials and Cyber Essentials Plus
Cyber Essentials is a UK government-backed scheme, overseen by the National Cyber Security Centre and delivered through IASME, that certifies five basic technical controls. They are firewalls, secure configuration, security update management, user access control and malware protection. You complete a self-assessment questionnaire, which a certification body checks, and the certificate lasts a year.
Cyber Essentials Plus covers the same controls and adds a hands-on audit, in which an assessor tests a sample of your devices and accounts. The scope includes the company’s laptops, phones, servers and cloud services, so it is within reach of a small team that keeps its devices and accounts in order. UK central government requires Cyber Essentials for some contracts, such as certain contracts that involve handling personal information, and some private-sector buyers ask for it too. The requirements are updated from time to time, so check the current version before you apply.
ISO 27001 and SOC 2 compared
ISO/IEC 27001 is an international standard for an information security management system, meaning the policies, risk assessments and processes you use to manage security over time. An accredited certification body audits you and issues a certificate, followed by surveillance audits each year and recertification every three years.
SOC 2 is a US framework from the AICPA. A licensed CPA firm examines your controls against the Trust Services Criteria and writes a report. A Type 1 report covers how your controls are designed at one point in time. A Type 2 report covers how they operated over a period, usually several months.
| Cyber Essentials | Cyber Essentials Plus | ISO 27001 | SOC 2 | |
|---|---|---|---|---|
| What it is | Self-assessed certification of five controls | The same controls, independently tested | Certified security management system | Auditor’s attestation report |
| Who checks | A certification body reviews your answers | An assessor tests your systems | An accredited certification body | A licensed CPA firm |
| Renewal | Every year | Every year | Three-year cycle with yearly audits | Buyers usually expect a new report each year |
| Most often asked for by | UK public sector and UK businesses | UK public sector and larger UK buyers | UK and European enterprises | US enterprises |
| Effort for a small SaaS | Low | Low to moderate | High | High |
For a UK SaaS company, Cyber Essentials is the sensible first step. ISO 27001 usually follows when large UK or European customers require it, and SOC 2 when US customers do. Many controls overlap, so the work for one makes the next easier.
Penetration testing
A penetration test is an authorised, simulated attack in which specialists look for weaknesses in your application and infrastructure. For a SaaS product the test should cover the web app, the API and any mobile apps, and above all tenant isolation. Testers should use two test tenants to check that one customer can never reach another’s data (multi-tenancy explained).
Look for testers with recognised accreditation, such as CREST. Fix the findings, ask for a retest, and share a summary or letter of attestation with customers, keeping the full report for those who sign a non-disclosure agreement. Test again each year and after major changes.
The basics to have in place first
- MFA for all staff on email, cloud hosting, code hosting, the billing provider and the domain registrar.
- MFA and SSO for customers, with SAML or OpenID Connect for larger ones.
- Least privilege. Production access only for the people who need it, with named accounts and no shared logins.
- Encryption in transit with TLS, and at rest for databases, files and backups.
- Backups that run automatically, sit in a separate account and are test-restored on a schedule. A backup that has never been restored is only a hope.
- Patching of servers, laptops and software dependencies, with automated alerts for known vulnerabilities.
- Audit logs of administrative and security actions (audit logs for SaaS).
- Joiners and leavers. A checklist that removes every account on someone’s last day.
Incident response
Write a short incident plan before you need one. It should say who leads, how to contain a problem, how to preserve evidence, who decides whether customers must be told and how they will be told. Practise it once with a realistic scenario.
For most customer data in a B2B SaaS, you are a processor acting for your customer, the controller. UK GDPR requires a processor to tell the controller about a personal data breach without undue delay. The controller must report a notifiable breach to the ICO within 72 hours of becoming aware of it where feasible. Your contract may set a fixed deadline for telling the customer, so know what you have signed.
Data processing agreements
Under Article 28 of UK GDPR, a controller that uses a processor must have a written contract with set terms. The processor must act only on the controller’s documented instructions, keep the data confidential, secure it, use sub-processors only with authorisation, help the controller meet its obligations, delete or return the data at the end and allow audits. The contract must also describe the processing, including the types of personal data and whose data it is.
Publish your own data processing agreement and sub-processor list, so customers can review them early. Large customers will often send their own instead. If personal data leaves the UK, for example to a hosting region abroad, the transfer also needs a lawful route, such as UK adequacy regulations for that country or the ICO’s International Data Transfer Agreement. Take legal advice on the agreement before your first enterprise contract.
Questions people ask
Do I need Cyber Essentials to sell SaaS in the UK?
It isn’t a legal requirement for selling software. UK central government requires it for some contracts, and some private-sector buyers ask for it in their questionnaires. It is also a practical checklist of basic controls, which makes it a sensible first certification for a small UK SaaS company.
Should a UK SaaS choose ISO 27001 or SOC 2?
Choose the one your customers ask for. UK and European enterprises more often recognise ISO 27001, and US enterprises more often ask for SOC 2. Many controls overlap, so a company that holds one can prepare for the other with less work than starting from scratch.
How often should a SaaS product be penetration tested?
Once a year is a common expectation in security questionnaires, plus a test after major changes such as a new API, a new mobile app or a change to how tenants are separated. Fix the findings and keep evidence of the retest to show customers.
Can a small company answer a security questionnaire honestly?
Yes. Answer what is true today, say which controls are planned, and give dates for them. Security teams review small suppliers regularly, and an honest gap with a plan is easier for them to accept than a claim that doesn’t hold up.