The scope question comes early in Stage 1. The auditor asks you to walk through what is in scope and what is not. Most teams have the inclusions listed somewhere. The exclusions are where things fall apart. "We excluded the data warehouse because it is not customer-facing." That answer will not hold. Here is how to build a scope that survives the conversation.
What ISO 27001 actually requires from your scope document
The standard requires you to define the boundaries and applicability of your ISMS, taking into account the organization's context, its interested parties, and the interfaces and dependencies between activities performed by the organization and those performed by other organizations [source: https://www.isms.online/iso-27001/].
That last phrase — interfaces and dependencies — is the one that trips teams up. It is not enough to list the systems you manage directly. You need to show you have thought through everything that touches those systems and made a deliberate decision about each one.
A scope document needs to answer four questions:
- Which organizational units are included?
- Which physical locations are covered?
- Which information assets and systems are in scope?
- Which external parties and their interfaces are accounted for?
Building your inclusions list
Start with your information assets. Not your systems — your information assets. Customer data, product source code, authentication credentials, financial records, employee PII. Once you have the asset list, work backward to the systems that store, process, or transmit each one.
This approach is more defensible than starting with a system inventory because it grounds each inclusion in a business reason. "This service is in scope because it stores customer payment records" is a complete sentence an auditor can verify.
For a Series B SaaS company, the inclusions list typically covers:
- The production application environment
- Identity and access management (your IDP, secrets manager, SSH access tooling)
- The code repository and CI/CD pipeline, because they can deploy to production
- The data store — including the analytics warehouse if it contains identifiable customer data
- Corporate systems that handle HR, finance, or legal information
- The security tooling itself (SIEM, vulnerability scanner, endpoint management)
Exclusions: the part that fails at audit
An exclusion is a deliberate decision, not a shortcut. You can exclude a system or process from the ISMS scope, but you have to show three things.
No in-scope interface. If the excluded system talks to an in-scope system — shares data, shares credentials, shares network segments — the exclusion is very hard to defend. A separate analytics environment that pulls from production via a shared service account is not isolated. It is in scope. No residual risk created by the exclusion. If you exclude your development environment because it does not hold production data, you need to confirm that dev credentials are not shared with prod, no production data is copied to dev for testing, and dev-to-prod deployments are gated. If any of those conditions are not met, you have created a risk pathway the standard requires you to address. Documented justification with sign-off. "We decided not to include it" is not a justification. "This system handles only synthetic test data, uses isolated credentials, has no network path to the production VPC, and was therefore assessed as outside the ISMS boundary. Approved by ISMS owner, version-controlled." That is a justification.The audit conversation you are preparing for
Auditors will pick two or three exclusions and probe them. The questions are predictable:
- What data does this system hold?
- Does it communicate with anything in scope?
- What controls exist on it even though it is excluded?
- When was this exclusion last reviewed?
Connecting scope to the Statement of Applicability
Your Statement of Applicability (SoA) lists every Annex A control and whether it applies. The scope determines what the SoA covers. They have to be consistent.
If you exclude your marketing tooling from scope, the SoA should not reference controls that only exist in that tooling. If you include the CI/CD pipeline, the SoA needs controls that address pipeline access and change management.
A common mistake: scoping tightly but writing the SoA broadly to avoid explaining non-applicability. Auditors notice. When the SoA says a control applies but no evidence exists for it in the scoped environment, the explanation unravels quickly.
The cleaner approach: write the scope first, finalize it with the ISMS owner, then draft the SoA against that scope. Decisions made in the scope document travel directly into applicability decisions in the SoA. The two documents should be able to cite each other — if they cannot, one of them is wrong.
When to review your scope
The standard does not mandate a fixed review cycle for the scope document [source: https://www.isms.online/iso-27001/]. It does require that management review the ISMS at planned intervals, which in practice means the scope should be a standing agenda item in your management review.
Beyond the calendar cadence, certain events should trigger an out-of-cycle review:
New product lines or features. If you launch a new product that stores customer data in a system not currently in scope, the scope is now stale. Acquisitions or significant vendor changes. A new subsidiary brings systems, people, and data flows that may fall inside or outside your existing boundary. Infrastructure migrations. Moving from one cloud provider to another, or from self-hosted to managed services, changes the interfaces and dependencies the scope must document. Personnel or organizational restructuring. If the ISMS owner role changes, or if a team that was included in the scope is spun off, the scope document needs to reflect it.In practice, Series B companies find that scope creep is the real problem. The company grows faster than the ISMS. Systems get added to the stack without a corresponding scope review. The first sign is usually a Stage 1 observation: the scope document does not reflect the current environment. Address it before the auditor finds it.
Audit prep should not produce surprises at Stage 1. The scope document is the auditor's map of your ISMS — if the map is wrong, everything downstream is suspect. CloudAnzen continuously tracks your infrastructure and data flows against your documented scope so the boundary stays current when your stack changes. Talk to us.