← Back to blog

ISO 27001 Scope Statement: How to Write One That Passes Audit

November 15, 2026
ISO 27001 Scope Statement: How to Write One That Passes Audit

An ISO 27001 scope statement is a short, documented description of what your information security management system (ISMS) covers: which services, locations, systems, people and suppliers are inside the boundary, and what sits outside it. Write it narrowly enough to manage and broadly enough that a customer reading your certificate recognizes the service they buy. At Nexus, we handle IT, cybersecurity and compliance under one contract, so the boundary is drawn once and held consistently across every system it touches.

AccountNext-Nexus
Unify Security and Compliance
Nexus brings cybersecurity, IT management and compliance together under one umbrella, helping keep your security boundaries consistent across systems.
Visit

TL;DR

  • The scope statement is a documented boundary for your ISMS. Clause 4.3 of ISO/IEC 27001:2022 requires you to determine it and keep it as documented information.
  • It must reflect your internal and external issues, what interested parties expect, and the interfaces and dependencies with other organizations, such as cloud hosts and vendors.
  • A good statement names the service, the locations, the technology and the exclusions, in two to five sentences.
  • Scope decides audit effort and cost, and it is what your customers will read on your certificate. Too broad wastes budget, too narrow loses deals.
  • Adapt the examples below by naming your own product, environments and suppliers.

Table of Contents

What the scope statement actually is

ISO/IEC 27001 is the international standard for running an ISMS, the set of policies, risk processes and controls that protect your information. Before any of that works, you have to say what it applies to. That is the scope.

The ISACA implementation guide describes the scope as the documented definition of the ISMS boundaries: the included and excluded assets such as processes, business areas, locations and applications, plus the interfaces with anything outside the boundary. The same guide notes that a certificate on its own may not show whether a particular process or service is covered, which is why customers and suppliers increasingly ask to see the detailed scope.

Two terms are worth separating:

  • Scope document: the fuller internal record, with the detail auditors review.
  • Scope statement: the short wording that appears on your certificate and in sales and security questionnaires.

Both must say the same thing. If the certificate says "the customer portal" and your scope document includes the billing system too, you have a mismatch that an auditor or a customer will find.

What clause 4.3 requires

Clause 4.3 is short. According to the published standard text, you must determine the boundaries and applicability of the ISMS, and in doing so consider:

  1. Internal and external issues from clause 4.1: your business model, regulation, technology, contracts, and since Amendment 1:2024, whether climate change is a relevant issue.
  2. Requirements of interested parties from clause 4.2: customers, regulators, partners, staff and insurers.
  3. Interfaces and dependencies between what you do and what other organizations do.

The scope must be available as documented information. A second reading of the 2022 text confirms the same three considerations.

As of November 2026, the baseline remains ISO/IEC 27001:2022 with Amendment 1:2024. The amendment adds the climate-change consideration to clause 4.1 and a note to clause 4.2, and adds no new Annex A controls. You cannot claim conformity while ignoring clauses 4 to 10, according to the INCITS summary of the standard, so scope is a way to bound the ISMS, not a way to skip requirements.

The five boundaries to decide

In practice, you settle five questions before you write a word.

Organizational boundary

Which legal entities, business units and teams are inside? A startup with one product may certify the whole company. A larger firm might certify one division. Shared services such as HR or finance can often sit outside if they have no access to in-scope systems or data, but only if you can show that separation.

Information boundary

What information do you create, store or process for the in-scope service? Customer records, source code, patient data, payment data. If you can't say what data is involved, you can't draw a defensible line.

Physical boundary

Offices, data centres, remote work. Name the locations or state plainly that staff work remotely. A fully remote company still has a boundary: the endpoints, identity systems and home-working rules.

Technology boundary

Production cloud accounts, regions, networks, applications, endpoints, and the tools your staff use to administer them. Naming the environments (production, staging) removes ambiguity.

Supplier boundary

This is where most teams get caught. Your cloud provider, payment processor and support outsourcer are outside your organization but inside your risk picture. Clause 4.3 asks you to consider those dependencies, so the scope document should say which suppliers are relied upon and how they are managed. Our guide to types of third-party cybersecurity risks helps you list them, and why cloud security shared responsibility matters explains which side of the line each cloud control sits on.

How to write the statement: a working formula

A statement that auditors and customers both accept usually answers six questions in plain sentences:

  1. What service or activity? Name the product or service, not a vague "IT operations".
  2. For whom? Customers, patients, internal users.
  3. Which activities? Design, development, hosting, support, administration.
  4. Where? Locations and cloud regions.
  5. On what technology? Named platforms and environments.
  6. What is out? Explicit exclusions with a reason.

A template to fill in:

The ISMS of [Company] covers the [design, development, operation and support] of [service] provided to [customer type], delivered from [locations or regions], including [environments and supporting systems]. The scope excludes [named exclusions]. The ISMS applies to [employees, contractors] with access to in-scope systems and to [supplier types] relied on for delivery.

Keep it to a few sentences. The detail belongs in the scope document, with network diagrams, asset lists and supplier lists attached.

ISO 27001 scope statement examples

The examples below are illustrative wording patterns, not real certificates. Replace every bracketed detail with your own facts.

A SaaS startup

"The ISMS covers the design, development, hosting and customer support of the [Product] platform operated by [Company], including production and staging environments in AWS [region], the employees and contractors with access to them, and the identity, source control and monitoring tools used to administer them. Corporate finance and recruitment systems are excluded."

Why it works: it names the product, the cloud region, the people and the tools, and the exclusion is limited to systems with no route to customer data. Founders weighing this path can read our guide to cloud compliance for startups.

A published U.S. example from H33's ISMS scope document follows the same logic. It covers production AWS infrastructure in us-east-1, the employees and contractors with access, and third-party providers with infrastructure access. It excludes customer-side integrations, certain third-party services beyond their API boundaries, and unrelated tools. Note how every exclusion is a boundary the company does not control or does not operate.

A SaaS startup

A healthcare provider

"The ISMS covers the storage, processing and transmission of patient records and scheduling data within the [Practice] electronic health record environment, the clinical and administrative staff who use it at [locations], the managed network and endpoints at those locations, and the hosting and backup providers supporting the system. Research collaborations and the public website are excluded."

Why it works: it centres on the data that regulators care about and names the clinical sites. Healthcare organizations often pair ISO 27001 with HIPAA work, and a clear data boundary serves both, though the two are separate regimes with different requirements.

A small business with a limited budget

"The ISMS covers the delivery of [accounting, design, logistics] services to clients from our [city] office and remote staff, including the laptops, cloud file storage, email and line-of-business applications that hold client information. Personal devices not enrolled in device management are excluded from use for client data."

Why it works: a small firm does not need to certify everything. Bounding to the client-facing service keeps the audit proportionate. Our certification cost breakdown shows how scope drives the budget.

An enterprise division

"The ISMS covers the [Division] managed services business unit, including service delivery, security operations and client onboarding from [sites], the shared network and data centre services supporting it, and group-level IT services provided under internal agreements. Other business units are excluded."

Why it works: internal service providers are listed as dependencies, which satisfies the interface and dependency consideration without dragging the whole group into scope.

Common scope mistakes

The errors that cost teams the most time fall into three groups.

Too broad. Putting the whole company in scope "to be safe" adds assets, teams and evidence to maintain. Every item in scope must be covered by the ISMS, so a bigger boundary means more controls to operate and more to audit. It also makes the boundary harder to adjust as your technology changes.

Too narrow. Carving out the system that actually holds customer data, or the admin tooling that can reach it, produces a certificate your customers will find hollow. Auditors check for boundaries drawn to avoid difficult areas, and enterprise buyers read the wording closely.

Unclear. Typical symptoms:

  • Vague wording such as "IT systems" with no product or location.
  • Exclusions with no reason.
  • Suppliers ignored, even though the service cannot run without them.
  • A certificate statement that differs from the internal scope document.
  • A scope that never updates after a new region, product or acquisition.

A quick test: could a stranger read your statement and list which systems the auditor will sample? If not, tighten it.

How scope drives controls, cost and audit effort

Scope is the first input to your risk assessment. The assets inside it are what you assess, and the risks you find decide which Annex A controls you apply. The Statement of Applicability then records each control, whether it is applied and why, as the ISACA guide explains. Our piece on why Annex A's 93 controls are not a checklist walks through that relationship.

The effect on effort is direct: more locations, systems and people in scope means more evidence, more interviews and more audit days. That is why scope is the first lever to pull when a budget is tight, and why the ten implementation steps start with context and boundary before controls.

Review the scope when things change

The scope is not a one-time document. Revisit it when you:

  • launch a new product or enter a new market;
  • move to a new cloud region or provider;
  • acquire a company or open an office;
  • change a critical supplier;
  • see new customer or regulatory requirements.

U.S. organizations sometimes also use NIST CSF 2.0 as a voluntary complementary framework. It does not replace ISO's certifiable requirements, but the asset and supplier inventories you build for scope feed both.

Perspective

Most scope problems we see in the planning stage come from fragmentation, not from the standard. The cloud environment belongs to one team, endpoints to another, monitoring to a third vendor, and compliance to a consultant who never sees the logs. Nobody can then say with confidence where the boundary sits.

Our view is that scope should be drawn by one accountable party who sees IT, security and compliance together. When managed IT, 24/7 monitoring, cloud management and compliance assessments sit under one provider with a unified SLA, the asset list, the supplier list and the control evidence all come from the same place, and the scope statement stays true after the audit rather than only on the day of it.

Draw the boundary around the service your customers buy, name your suppliers honestly, and write exclusions you can defend in one sentence.

Nick - Sr. Executive

Getting the boundary drawn and evidenced

Writing the statement is the short part. Keeping the asset inventory, supplier list, monitoring evidence and cloud configuration aligned with it is what takes ongoing effort. Nexus provides managed IT, cybersecurity, cloud management and compliance assessments for SOC 2, HIPAA, PCI-DSS and ISO 27001 under one contract, with flat-rate monthly pricing and a single point of accountability.

AccountNext-Nexus

If you are scoping an ISMS and want one provider handling the technology, the monitoring and the compliance work behind it, see our services or start from the Nexus home page.

FAQ

What is an example of an ISO 27001 scope statement?

A typical one reads: the ISMS covers the design, development, hosting and support of a named platform, delivered from named locations or cloud regions, including the people and tools that administer it, and excludes named out-of-boundary areas. The examples above show versions for a SaaS company, a healthcare provider, a small business and an enterprise division.

What should a scope statement include?

Name the service, the customers, the activities, the locations, the main technology and the exclusions. Clause 4.3 also expects you to have considered internal and external issues, interested-party requirements and dependencies on other organizations, and to keep the scope as documented information.

Can we exclude parts of the business from scope?

Yes, as long as the boundary is justified and honest. Exclude areas that do not touch the in-scope service or its data, and state them. You cannot exclude clauses 4 to 10 of the standard itself, and excluding the system that holds customer data will undermine the certificate's value.

Does the scope statement appear on the certificate?

Yes. The short statement is what your certificate shows, so customers and suppliers read it to see what is covered. Keep it identical in meaning to the detailed scope document and be ready to share that document on request.

How often should the scope be reviewed?

Review it at least when something material changes: a new product, region, supplier, acquisition or customer requirement. Many teams also check it before each annual surveillance audit so the wording still matches reality.

Sources