Start by defining what information must be protected, where it is stored, and who or what can access it. Then set clear in-scope and out-of-scope boundaries across products, locations, people, technology, and networks. A usable scope keeps the ISMS auditable, avoids overreach, and ensures controls map to real business and information risks.
How to define an ISO 27001 scope that auditors can actually test
The scope should describe the information security management system as it exists in the business, not as an abstract enterprise aspiration. That means naming the services, legal entities, sites, support functions and technology environments that are included, then stating any explicit exclusions and the rationale for them. A scope that is too vague creates audit friction; one that is too broad becomes hard to govern and evidence.
For that reason, scope definition is best treated as a boundary-setting exercise. Start with the information assets and services that matter, then trace the business processes, people and systems that protect or use them. If the organisation operates multiple product lines or regions, the scope should make it obvious which of those are covered by the ISMS and which are managed through a separate control boundary.
Where the business structure is complex, the useful question is not “what does the company do?” but “what part of the company needs the ISMS to protect the information risks we have accepted?” The answer often leads to a narrower and more defensible scope than a company-wide statement. If the scope cannot be explained in one or two sentences without ambiguity, it is probably not ready for certification evidence.
What to include, and what to keep outside the ISMS
An effective scope usually includes the products or services in scope, the locations where relevant information is processed or supported, the functions that operate or govern those services, and the technical boundaries that can materially affect confidentiality, integrity or availability. That may include head office, engineering, customer support, cloud platforms, outsourced operations or shared services when they influence the security outcome. For practical scoping discipline, many teams use a structured reference such as NHIMG’s ISO 27001 Certification Guide to keep scope, risk treatment and audit evidence aligned.
Out-of-scope areas need equal care. They should not be excluded simply because they are inconvenient to assess. If an excluded system can still store, process, transmit or influence in-scope information, the exclusion must be justified and its interface with the ISMS documented. That is especially important in shared-service environments, where a supposedly separate business unit may still provide infrastructure, identity administration, logging or support that affects the in-scope environment.
The strongest scopes separate ownership from dependency. A team may not own a platform, but if it relies on that platform to process protected information or maintain control evidence, the dependency still matters. In practice, scope conversations should surface shared infrastructure, outsourced services and common corporate functions early, because those are the places where boundary ambiguity most often creates weak controls or duplicated assurance work.
How to keep scope stable as the organization changes
Complex organisations rarely fail ISO 27001 because the first scope was impossible. They fail because the scope drifts faster than the change process. New products launch, support teams relocate, cloud tenancy patterns change, and acquisitions bring in systems that were never mapped to the original ISMS boundary. The scope therefore needs a change trigger, so that major organisational or technical changes automatically prompt a scope review.
Scope stability also depends on evidence. The organisation should be able to show why each included boundary exists, how exclusions were decided, and which business risks would be affected if the boundary moved. That evidence does not need to be elaborate, but it does need to be current. If the ISMS covers only part of a group structure, the rationale should also show how common services, governance and reporting avoid creating a hidden gap between the certified scope and the real operating model.
For multi-site and multi-entity environments, the practical test is whether the scope can survive organisational restructuring. If a team, site or platform could be transferred, spun off or absorbed without forcing a scope rewrite, the boundary is probably too loose. A usable scope keeps the certification target realistic while still reflecting the actual locations, technologies and people that shape the organisation’s information risk.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
ISO/IEC 27001:2022 provides the primary governance reference for this topic.
| Framework | Control / Reference | Relevance |
|---|---|---|
| ISO/IEC 27001:2022 | A.5.9 — Inventory of information and other associated assets | Scoping depends on knowing what information assets are in and out of boundary. |
| A.5.1 — Policies for information security | Scope is a policy-level decision that must define organisational boundaries and ownership. | |
| A.5.15 — Access control | Scope must cover the people, systems and services that can access in-scope information. | |
| Recommendation — Inventory the information assets and services that define the ISMS boundary before writing the scope statement. Document the ISMS scope as part of the top-level information security policy and keep it approved. Map access boundaries and shared services into the scope so the control set matches actual information access. | ||
Practitioner Guidance
What to prioritise: Start with the information flows and supporting services that create the highest audit and risk exposure, then define the smallest boundary that still captures them cleanly. The point is not to certify everything the organisation owns; it is to certify the environment where information security obligations are actually being met.
What to verify: Check that every exclusion has a written rationale, every dependency has an owner, and every included location or service has a clear relationship to the in-scope information assets. If a reviewer cannot tell why a boundary exists, the scope is not yet operationally defensible.
Common mistake: Teams often describe scope in terms of corporate structure instead of control reality. That produces a scope statement that sounds complete but does not match how information actually moves through products, platforms, support functions and outsourced services.
Practitioner takeaway: A strong ISO 27001 scope is a governance decision, not a marketing statement, and the best one is narrow enough to manage, broad enough to cover real dependency chains, and precise enough to survive audit challenge.
Related resources from NHI Mgmt Group
- How should organisations scope an ISO 27001 information security management system before certification?
- How should security teams govern non-human identities for ISO 27001?
- How can security teams align NHI controls to both NIST and ISO 27001?
- How should security teams budget for ISO 27001 certification work?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org