When a UK business buys your SaaS, expect to be asked for four things before anyone signs: a data processing agreement that meets UK GDPR, an answer on where the data is stored and who can reach it from abroad, evidence of basic security (usually Cyber Essentials, sometimes Cyber Essentials Plus or ISO 27001), and a recent penetration test. Larger or regulated buyers add a long security questionnaire on top. None of this is exotic, and most of it is cheaper to build in from the start than to bolt on when a big deal is waiting.
- As a SaaS supplier you’re almost always a data processor, and UK GDPR requires a written contract with set terms.
- Know where your data and your sub-processors sit. Transfers outside the UK need a legal mechanism.
- Cyber Essentials is the usual first certificate for a UK supplier. IASME’s listed fees start at £320 plus VAT.
- ISO 27001 and SOC 2 come later, when bigger customers ask. The government’s Software Security Code of Practice is a free checklist to work from now.
Source: DSIT and Home Office, Cyber Security Breaches Survey 2025/2026
Why buyers are asking more questions
The government’s Cyber Security Breaches Survey 2025/2026, published by DSIT and the Home Office in April 2026, found that 43% of UK businesses and 28% of charities identified a cyber breach or attack in the previous 12 months. That’s roughly 612,000 businesses. Medium and large businesses, the kind most likely to send you a security questionnaire, reported far more.
Fieldwork August to December 2025. Covers breaches organisations identified and were willing to report.
Source: DSIT and Home Office, Cyber Security Breaches Survey 2025/2026
View data
| UK businesses identifying a cyber breach or attack in the last 12 months, by size | |
|---|---|
| Micro | 42% |
| Small | 46% |
| Medium | 65% |
| Large | 69% |
| All businesses | 43% |
Phishing was the most common type, reported by 38% of businesses. Yet the same survey found only 15% of businesses formally reviewed the cyber risks posed by their immediate suppliers, and 6% their wider supply chain. Buyers who do check are getting stricter, and as a supplier you’re part of their supply chain.
UK GDPR: controller, processor and the DPA
If your customer decides what personal data goes into your product and why, they’re the controller and you’re the processor. UK GDPR requires a written contract between the two. The ICO lists the minimum terms: processing only on the controller’s documented instructions, a duty of confidence, appropriate security measures, rules on using sub-processors, help with data subjects’ rights, assisting the controller with its own obligations, end-of-contract provisions, and audits and inspections.
In practice, publish a standard data processing agreement (DPA) alongside your terms, with a list of your sub-processors (hosting, email delivery, support desk, AI model provider) and a commitment to tell customers before you add new ones. You’ll also be a controller in your own right for some data, such as your customers’ billing contacts, so you need your own privacy notice too.
If your product uses AI models on customer data, buyers will ask whether that data trains anyone’s model and where it’s processed. We cover those questions in AI agents and UK GDPR.
International transfers
Many SaaS products use cloud hosting or tools run from the US or elsewhere. The ICO calls sending or giving access to personal data to a separate organisation outside the UK a “restricted transfer”. Every restricted transfer must be covered by UK adequacy regulations, an appropriate safeguard, or a narrow exception. The usual safeguards are the ICO’s International Data Transfer Agreement (IDTA) or its Addendum to the EU standard contractual clauses, and if you rely on one you must also complete a transfer risk assessment.
Buyers will want a simple table: what data, which supplier, which country, which mechanism. Hosting in a UK region removes some questions, but your support desk or AI provider may still sit abroad.
Cyber Essentials and Cyber Essentials Plus
Cyber Essentials is the government-backed certification scheme promoted by the NCSC, and IASME publishes the standard fees. Both levels assess the same five technical controls. The NCSC describes the basic level as “a combination of self-assessment and independent audit”. Cyber Essentials Plus adds “more rigorous, independent technical testing” of your systems.
IASME’s published fees for Cyber Essentials, as listed on its FAQ page when we checked in November 2026:
| Organisation size | Employees | Cyber Essentials fee |
|---|---|---|
| Micro | 0 to 9 | £320 + VAT |
| Small | 10 to 49 | £440 + VAT |
| Medium | 50 to 249 | £500 + VAT |
| Large | 250 or more | £600 + VAT |
Cyber Essentials Plus is quoted individually by the assessor, and both certificates expire after 12 months. Uptake is still low: the breaches survey found 5% of businesses adhered to Cyber Essentials and 2% to Cyber Essentials Plus. Holding it puts you ahead of most suppliers. For a small SaaS company, we’d treat basic Cyber Essentials as a launch requirement and Plus as the next step once you’re selling to larger firms or the public sector.
ISO 27001
ISO/IEC 27001 is, in ISO’s words, “the world’s best-known standard for information security management systems”. The current edition is from 2022. It certifies that you run a management system for security risks (policies, risk assessments, reviews, continual improvement), and certification, which is optional, is done through an accredited certification body. It’s a substantial project of documentation, internal review and external audit. It’s worth doing when enterprise or financial services customers make it a condition. It’s overkill for your first ten customers.
SOC 2: a US standard
SOC 2 is an American assurance report, not a certificate. It’s produced by CPAs (US-qualified accountants) under the AICPA’s framework, which covers controls relevant to “Security, Availability, Processing Integrity, Confidentiality, or Privacy”. It matters most when your buyer is US-owned or you’re selling into the US. If you’re UK-focused, we’d put Cyber Essentials and then ISO 27001 ahead of it.
Penetration testing
The NCSC defines a penetration test as “a method for gaining assurance in the security of an IT system by attempting to breach some or all of that system’s security, using the same tools and techniques as an adversary might.” It also says testing should be seen as a way of checking your vulnerability management, “not as a primary method for identifying vulnerabilities”. In other words, patch and scan routinely, then bring in testers to confirm it’s working.
A common request is a summary letter from an independent tester covering the application and its API, dated within the last year, with confirmation that high-risk findings were fixed. For government work the NCSC recommends testers in its CHECK scheme.
A sensible order of work
For a small SaaS team, the order matters more than the individual items. This is roughly how we would sequence it.
Step 1 of 5
Paperwork
Publish a standard DPA, a privacy notice and a sub-processor list.
Step 2 of 5
Map transfers
Record what data goes to which supplier, in which country, under which mechanism.
Step 3 of 5
Certify
Get basic Cyber Essentials before launch and renew it every 12 months.
Step 4 of 5
Test
Commission an independent pen test of the app and API and fix high-risk findings.
Step 5 of 5
Write it up
Keep a short security overview so questionnaires take an afternoon, not a week.
Internal rules matter too. If staff paste customer data into AI tools, buyers will ask how you control that, and a short AI policy gives you an answer. Security work also never really finishes, so budget for it alongside the other running costs after launch.
The Software Security Code of Practice
DSIT and the NCSC published the Software Security Code of Practice in May 2025. It’s voluntary and explicitly covers software delivered as SaaS. It sets out 14 principles under four themes: secure design and development, build environment security, secure deployment and maintenance, and communication with customers. The government provides a self-assessment form to go with it.
The code also says organisations buying software can use its principles “to inform agreements and contracts with their suppliers”. Expect procurement teams to start quoting it. Working through the self-assessment early is a cheap way to find gaps, and it fits naturally with scoping your first version so that the essentials are in from day one.
The Cyber Security and Resilience Bill
The Cyber Security and Resilience (Network and Information Systems) Bill would extend the UK’s NIS regulations, update incident reporting duties and give the government powers to direct organisations on national security grounds. The organisations it regulates include operators of essential services, digital service providers, managed service providers and critical suppliers. It finished its House of Lords stages in early November 2026, and a print of the bill with Lords amendments was published on 3 November for the Commons to consider. When we checked on 22 November 2026 it had not received Royal Assent, so it is not yet law, and much of the detail, including exactly which providers are in scope, will come in secondary legislation.
Most small SaaS products won’t be directly regulated. But if your customers are hospitals, utilities or managed IT providers, they may pass new duties down to you by contract, so keep an eye on it.
Common questions
What should a small SaaS have ready before its first enterprise sale?
A standard DPA, a sub-processor list, a short security overview document, Cyber Essentials, and a pen test summary. With those, most questionnaires become an afternoon’s work rather than a week’s.
Does hosting in the UK solve the transfer question?
Only partly. Your database may be in London while your email provider, support desk or AI model provider processes data elsewhere. Each of those needs checking against the ICO’s transfer rules.
This is general information, not legal advice. Take advice on your contracts and on whether new legislation applies to you.
Building it in
Security is far cheaper to design in than to retrofit, which is why it sits alongside billing and accounts in our guide on how to build a SaaS product. If you’d like help planning it, our SaaS product development team can work through it with you.
Sources
- DSIT and Home Office: Cyber Security Breaches Survey 2025/2026 (30 April 2026)
- ICO: What needs to be included in the contract? (accessed 21 November 2026)
- ICO: A brief guide to international transfers (accessed 21 November 2026)
- ICO: What are standard data protection clauses (the UK IDTA and the Addendum)? (accessed 21 November 2026)
- NCSC: Cyber Essentials (accessed 21 November 2026)
- IASME: Cyber Essentials frequently asked questions (page updated November 2025, accessed 21 November 2026)
- ISO: ISO/IEC 27001:2022 Information security management systems (2022)
- AICPA and CIMA: System and Organization Controls, SOC suite of services (accessed 21 November 2026)
- NCSC: Penetration testing (accessed 21 November 2026)
- DSIT and NCSC: Software Security Code of Practice (first published May 2025)
- UK Parliament: Cyber Security and Resilience (Network and Information Systems) Bill, bill stages (accessed 21 November 2026)