Skip to main content
Talk to a human
AI Assistant

ISMS Scope Statement: How to Define Your ISO 27001 Scope, with Examples

The ISMS scope defines which parts of your organisation the information security management system, and therefore the ISO 27001 certificate, covers: the activities, locations, people, systems and outside dependencies. It is required by clause 4.3 of ISO/IEC 27001:2022, and it is the decision that most affects how much certification costs and whether the certificate satisfies the customer who asked for it.

At a glance

  • Required by: clause 4.3, determining the scope of the ISMS, available as documented information
  • Two forms: a full scope document, and a one or two sentence statement printed on your certificate
  • Covers: activities and services, locations, people, systems and information, interfaces with outside parties, and exclusions
  • Drives cost: audit days depend mainly on the number of people in scope
  • Where it goes wrong: too narrow for the customer, too broad for the budget, or silent about cloud and outsourced dependencies

What clause 4.3 requires

To set the boundaries of the ISMS, the standard says you must consider:

The resulting scope must be documented. In practice that means two things: a scope document of a page or two that your ISMS works from, and the short scope statement the certification body prints on your certificate.

What a scope document contains

The table below shows the sections of a scope document, with illustrative content for a fictional 25-person Singapore company that runs a customer-facing web application.

Section Example content
OrganisationThe company’s registered name and UEN
Activities and services in scopeDevelopment, operation and customer support of the company’s web application
LocationsThe Singapore office, and remote working by staff in scope under the remote working policy
PeopleEngineering, product, customer support and management; 22 of 25 staff
Systems and informationThe production cloud account, source code repositories, the identity provider, the support ticketing system and customer data held in them
Interfaces and dependenciesThe cloud hosting provider (infrastructure), the email and productivity suite, the outsourced payroll bureau (outside scope, managed as a supplier)
Exclusions and whyThe three-person events team, which handles no customer data and uses no in-scope systems
Reference documentsContext and interested parties analysis, Statement of Applicability version, risk assessment

Example scope statements

The certificate carries a condensed version. These are illustrative examples of the shape, for a fictional company:

Service-based scope: “The information security management system supporting the development, operation and customer support of the [Product] web application, delivered from the Singapore office, in accordance with the Statement of Applicability version 1.0.”
Whole-organisation scope: “The information security management system covering all business activities, people, information and systems of [Company] Pte. Ltd. at its Singapore office, in accordance with the Statement of Applicability version 1.0.”

A statement that does not work: “All IT systems of the company.” It names no activity, no location and no boundary, so it tells a customer nothing about what is protected and gives the auditor nothing to test against.

How to decide your scope

  1. Start from who asked. If a customer or tender wants ISO 27001, find out which service they buy from you. The scope must cover that service, or the certificate will not satisfy them.
  2. Follow the customer data. Trace where it is collected, stored, processed and supported. Every team and system it touches belongs inside the boundary.
  3. Map the dependencies. List the cloud providers, outsourced IT and other suppliers the in-scope activities rely on. They stay outside your scope, but the interfaces with them are in it and are managed through supplier controls.
  4. Exclude only what is genuinely separate. A team or site can be left out if it neither handles in-scope information nor uses in-scope systems. If it shares the same email, laptops and identity provider, excluding it rarely holds up.
  5. Check the cost. Count the people in scope. That number drives the certification body’s audit days and much of the documentation effort.

Scoping mistakes that cost you at audit

How the scope connects to the other ISMS documents

Not sure where your boundary should sit?

We map how your business actually operates and who is asking for the certificate, then set a scope that satisfies the customer without paying to certify more than you need. Part of our ISO 27001 readiness work, from S$13,500.

Get an ISO 27001 Quote

Frequently asked questions

Is the ISMS scope a mandatory document for ISO 27001?

Yes. Clause 4.3 of ISO/IEC 27001:2022 requires you to determine the boundaries and applicability of the ISMS and to make the scope available as documented information. The certification body also prints a short scope statement on your certificate.

What should an ISO 27001 scope statement include?

The scope document should name the organisation and the business activities, products or services covered, the locations, the people and teams, the key systems and information, and the interfaces and dependencies with outside parties such as cloud providers and outsourced IT. It should also state anything excluded and why. The one or two sentences printed on the certificate summarise this fuller document.

Can we certify only part of our company to ISO 27001?

Yes. A scope can cover one product, service or site rather than the whole organisation, provided the boundaries and the interfaces with the parts outside scope are clearly defined. Before narrowing it, check that the scope covers what your customer or tender actually asked about, because a certificate that excludes the service they buy will not satisfy them.

Does the ISMS scope affect the cost of ISO 27001?

Yes, more than anything else. The certification body sets audit days mainly by the number of people in scope, and the documentation and controls grow with every site, system and team you include. Certifying one service line rather than the whole company is usually the single biggest lever on cost.

How does the scope relate to the Statement of Applicability?

The scope sets the boundary that the Statement of Applicability and the risk assessment work inside. An Annex A control can be excluded only where the activity it addresses does not happen within the scope, so a vague or inaccurate scope makes the exclusions in the Statement of Applicability hard to defend.

Useful resources

Disclaimer: This article is for general information only. The examples are illustrative and describe a fictional company; your scope must reflect your own organisation, customers and dependencies, and the final certificate wording is agreed with your certification body. Refer to ISO/IEC 27001:2022 for the authoritative requirements.