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.
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.
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 |
|---|---|
| Organisation | The company’s registered name and UEN |
| Activities and services in scope | Development, operation and customer support of the company’s web application |
| Locations | The Singapore office, and remote working by staff in scope under the remote working policy |
| People | Engineering, product, customer support and management; 22 of 25 staff |
| Systems and information | The production cloud account, source code repositories, the identity provider, the support ticketing system and customer data held in them |
| Interfaces and dependencies | The cloud hosting provider (infrastructure), the email and productivity suite, the outsourced payroll bureau (outside scope, managed as a supplier) |
| Exclusions and why | The three-person events team, which handles no customer data and uses no in-scope systems |
| Reference documents | Context and interested parties analysis, Statement of Applicability version, risk assessment |
The certificate carries a condensed version. These are illustrative examples of the shape, for a fictional company:
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.
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 QuoteYes. 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.
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.
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.
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.
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.
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.