Why SaaS vendors get asked for ISO 27001
When a customer buys your SaaS product, they hand you their data and trust you to run the environment it lives in. Their security team has to decide whether that is acceptable, and an ISO 27001 certificate from an accredited certification body is the most widely recognised answer in Australia and Asia-Pacific.
The requests come from three directions:
- Enterprise and government buyers. Procurement teams and tenders list ISO 27001 as a condition or a scored criterion. See ISO 27001 for government tenders.
- Security questionnaires. Hundreds of questions per prospect, each one a delay. A certificate and Statement of Applicability answer most of them at once. See how to answer security questionnaires faster.
- Banks, insurers and super funds. Under APRA’s CPS 234, regulated entities must assess the information security capability of third parties that manage their information assets. A SaaS platform holding their data is exactly that, so the obligation flows down to you as questionnaires, contract clauses and a request for ISO 27001 or SOC 2. See CPS 234 vs ISO 27001.
None of this makes ISO 27001 a legal requirement. It becomes a commercial one. See is ISO 27001 mandatory in Australia?
ISO 27001 or SOC 2?
SaaS companies often face both. ISO 27001 ends in a certificate from an accredited certification body and is the usual ask from Australian, Asian, European and government buyers. SOC 2 ends in an attestation report from a CPA firm and is what most US customers expect. The underlying controls overlap heavily, so start with the one tied to your biggest near-term deals and reuse the work for the other. Our ISO 27001 vs SOC 2 comparison covers the differences in full.
Scoping a SaaS ISMS
Scope decides how much work you do and how many audit days the certification body quotes. For most SaaS companies, the scope is the product customers buy and everything needed to build, run and support it. Customers read the scope on your certificate, so it must clearly cover the service they’re buying.
| Area | Usually in scope | Usually outside or relied on |
|---|---|---|
| Product | The production application, APIs and customer data | Products or internal tools customers don’t use |
| Cloud platform | Your cloud accounts, configuration, networks, identities and keys | The provider’s data centres and underlying infrastructure, covered by its own certifications |
| Engineering | Source code, repositories, CI/CD pipelines and environments | Experimental work that never touches production or customer data |
| People | Engineers, support, operations and the leaders who run the ISMS | Roles with no access to the product or customer data, if they can be cleanly separated |
| Support | Ticketing, customer communications and support access to customer data | Marketing and sales systems, unless they hold customer data |
| Suppliers | Managed as dependencies: cloud, code hosting, monitoring, email and payment providers | Their own internal controls, which you assess rather than audit |
Clause 4.3 requires you to consider the interfaces and dependencies between what’s in scope and what isn’t. For a SaaS business that means being explicit about the cloud provider and the other services your product relies on. A scope that excludes the people who can deploy to production, or the support team who can see customer data, won’t survive Stage 1. For how scope and certification fit together in a startup, see ISO 27001 for small businesses and startups.
Shared responsibility: what your cloud provider covers
AWS, Microsoft Azure and Google Cloud all hold ISO 27001 certificates for their services and have been assessed against ISO 27017 and 27018. That helps you a great deal. It means physical security of data centres, hardware and the underlying platform are handled by a certified provider, and you can rely on that evidence rather than producing your own.
It doesn’t mean you are covered. Under the shared responsibility model, the provider secures the cloud itself; you secure what you build and run in it. That includes:
- how your accounts, storage, databases and networks are configured
- who has access to the console, production systems and customer data
- your application code and its dependencies
- encryption settings and key management choices
- logging, alerting and what you do when an alert fires
- backups of your data and whether you can restore them
The split shifts with the service type. On infrastructure services you own the operating system and everything above it; on managed databases or serverless platforms the provider takes more. Auditors expect you to know where the line sits for each service you use.
The 2022 edition added control 5.23 Information security for use of cloud services to deal with exactly this. It asks you to set out how you acquire, use, manage and exit cloud services, in line with your security requirements. In practice auditors look for a clear view of which cloud services you use, what the provider is responsible for versus you, how you checked the provider’s certifications and reports, and what your exit plan is. A downloaded certificate with no assessment behind it isn’t enough.
The Annex A controls that weigh most for SaaS
All 93 controls in Annex A have to be considered in your Statement of Applicability. For a SaaS company, these are the ones that carry the risk and draw the auditor’s attention. Titles follow ISO/IEC 27002:2022; see Annex A controls explained for the full set.
| Controls | What auditors look for in a SaaS business |
|---|---|
| 8.25 Secure development life cycle to 8.31 Separation of development, test and production environments | Security requirements captured for features, secure coding practice, code review, automated security testing in the pipeline, controls on outsourced development and real separation of production from everything else |
| 8.9 Configuration management | Defined secure baselines for cloud resources, ideally as infrastructure as code, with drift detected and fixed |
| 8.15 Logging and 8.16 Monitoring activities | Logs of admin, authentication and production activity, protected from tampering, and someone actually reviewing alerts and acting on them |
| 5.15 Access control to 5.18 Access rights; 8.2 to 8.5 | Single sign-on and MFA, least privilege, tightly controlled privileged and production access, restricted access to source code and regular access reviews with records |
| 5.19 to 5.22 Supplier controls | A list of the services your product depends on, security assessed before you adopt them, appropriate contract terms and periodic review |
| 8.13 Information backup | Backups that match your commitments to customers, kept separately, and restore tests that prove they work |
| 8.12 Data leakage prevention | Controls that stop customer data reaching places it shouldn’t, such as public storage buckets, logs, laptops or lower environments |
| 5.7 Threat intelligence | A deliberate way of learning about threats relevant to your stack, such as advisories for your cloud provider, frameworks and dependencies, and acting on what you learn |
Others matter too: 8.8 Management of technical vulnerabilities, 8.32 Change management, 5.24 to 5.28 on incident management and 5.30 ICT readiness for business continuity. The common mistake is to treat these as documents. Auditors sample records: pull requests with reviews, access review sign-offs, restore test results, incident tickets. If the control only exists in a policy, it will be raised as a nonconformity.
Compliance platforms and cloud integrations
SaaS companies are where compliance platforms earn their keep. Because your infrastructure, identity provider, code repositories and HR system all have APIs, a platform can continuously test configuration, track device compliance, flag access that hasn’t been reviewed and collect evidence without screenshots. Cyber Veda is an official Vanta partner, and we see the difference this makes to evidence collection in cloud-native businesses.
What a platform doesn’t do is decide your scope, assess your risks, judge which controls apply or make sure the ISMS actually runs. Those are the decisions auditors probe hardest. See consultant, platform or both? and choosing a compliance platform.
Penetration testing your product
ISO 27001 doesn’t name penetration testing, but a SaaS company has to show it manages technical vulnerabilities (8.8) and tests security during development and acceptance (8.29). An independent test of your application and its cloud environment is the clearest evidence of both, and enterprise customers ask for a summary of the results regardless of the standard. Our guide to whether ISO 27001 requires penetration testing covers what to test and how often, and penetration test vs vulnerability scan explains why scanning alone won’t do.
Startup realities
Most SaaS companies seeking certification are small. That’s fine: ISO 27001 asks for controls proportionate to your risk, not a security department. A few things are different, though.
- Engineers do double duty. The person who writes code is often the person who deploys it and administers the cloud account. Control 5.3 Segregation of duties expects conflicting duties to be separated. Where a small team can’t fully separate them, auditors look for compensating controls: peer review on every merge, protected branches, logged and reviewed production access.
- Time competes with product work. Remediation loses to the roadmap unless someone senior owns it. Plan the ISMS work into sprints rather than around them.
- Remote work replaces the office. There’s no requirement for premises. Physical controls shift to the cloud provider’s facilities and to 6.7 Remote working and 8.1 User endpoint devices: managed, encrypted laptops with screen locks and updates enforced.
- The ISMS has to keep running. Surveillance audits come every year. Keep policies short enough that people follow them. See the ISO 27001 audit cycle.
Effort depends mostly on scope, how mature your cloud practices already are and how much engineering time you can free up. A typical SME can be audit-ready in about eight weeks with focused support; see how long ISO 27001 takes and what drives the cost.
ISO 27017 and ISO 27018: optional extensions
Two related standards come up often in SaaS procurement:
- ISO/IEC 27017 gives cloud-specific guidance on the ISO/IEC 27002 controls, for both cloud service providers and cloud customers, with extra controls on topics such as shared responsibility.
- ISO/IEC 27018 gives guidance for protecting personal information in public clouds where the provider acts as a PII processor, which describes many SaaS companies handling customer data.
Both are guidance documents, not management system standards, so you can’t be certified to them on their own. Many certification bodies can include them as an extension to your ISO 27001 certification, assessing their controls alongside Annex A. They are worth it if customers or tenders specifically name them, or if privacy is central to what you sell. For most SaaS companies, ISO 27001 comes first and these are a later addition.
Next step
If you’re building the ISMS yourselves, plan the internal audit early. ISO 27001 requires internal audits to be objective and impartial; your own staff can do it if they aren’t auditing their own work, but in a small SaaS team almost everyone built some part of it. That’s why many bring in an independent internal auditor. Translating a fast-moving cloud environment into a scope, risk assessment and evidence an auditor will accept is the part we take on for clients. See how our ISO 27001 service works, or book a free 30-minute consultation and tell us what your customers are asking for.
