A wrongly drawn scope breaks an ISO 27001 project from the first month. Which assets go into the risk assessment, which controls the Statement of Applicability (SoA) carries, how many days the audit lasts and what’s written on the certificate all depend on this one decision. Below, for ISMS and IT managers who will draw the boundary of the information security management system (ISMS), we explain the inputs to scope, the types of boundary, cloud and outsourcing interfaces and how to write a scope statement that stands up in an audit.
The inputs that determine scope
ISO/IEC 27001:2022 clause 4.3 requires three inputs for scope: the internal and external issues in clause 4.1, the requirements of interested parties in clause 4.2, and the interfaces and dependencies between activities performed by the organization and those performed by other organizations. The scope must also be available as documented information. So the work doesn’t start with the question “Which departments shall we include?” The right question is: who expects us to safeguard what?
In the field, these are the inputs that actually decide scope:
- The source of the certification request: If a customer contract, tender specification or OEM requires a specific service or location to be certified, the scope must include at least that service.
- Legal and regulatory obligations: Personal data processed under KVKK, sector regulations and confidentiality clauses in contracts tell you which processes can’t be left out.
- Information flows: In which systems, passing through which teams’ hands and at which suppliers is the information produced and consumed by the in-scope service processed?
- Resources and maturity: For the first certification, choose a boundary the organization can really operate and produce evidence for. A system that’s broad on paper and empty in practice falls apart in the first audit.
A scope decision made without context and interested parties work has no basis. For how to run this analysis, see the guide context of the organization and interested parties analysis.
Organizational, physical and technological boundaries
The auditor questions the scope along three axes and wants to see where the line runs on each. The axes aren’t independent of each other: the moment you bring a unit into scope, the building it sits in and the systems it uses come to the table too.
| Axis | What to define | Typical ambiguity |
|---|---|---|
| Organizational | Units, roles, services, processes | Are support units (HR, purchasing, legal) included? |
| Physical | Addresses, server rooms, warehouses, remote working | Home offices and coworking spaces |
| Technological | Network segments, applications, cloud tenants, endpoints | Shared Active Directory, a common firewall |
A mistake you may come across at the organizational boundary is taking in the unit that delivers the service while leaving out the support processes that feed it. If an organization that brings its software development service into scope leaves out HR, which runs hiring and leaving, it still has to bring evidence for Annex A controls 6.1 (screening) and 6.5 (responsibilities after termination or change of employment) from HR. HR is out of scope but is a control owner. This relationship must be written down as an interface.
At the physical boundary, an address list isn’t enough. Count every place the in-scope information touches: the second location where backup cartridges are taken, a colocation data center, an archive store, the homes of remote workers. If remote working is in scope, some physical controls (for example 6.7 remote working, 7.9 security of assets off-premises) are met through policy and technical measures; a locked door doesn’t help here.
At the technological boundary, the real headache is shared infrastructure. Even if the scope covers a single business unit, if that unit uses the same Active Directory forest, the same email tenant and the same core firewall, these components are effectively inside the scope. A domain admin is everyone’s domain admin. The realistic way to narrow the scope technically is network segmentation; but the auditor wants to see evidence that segmentation really works, meaning the ACLs, the firewall rule set and access tests.
Interfaces and dependencies
Clause 4.3(c) isn’t satisfied by splitting the scope into “inside” and “outside”; it requires the connection points between the two to be defined. An interface is a point where information, a service or a responsibility is exchanged between an in-scope process and an out-of-scope unit or external organization. Keep an interface register for each interface with the fields below; this is one of the first documents opened in an audit:
| Interface | Party | Information/service flowing | Assurance method |
|---|---|---|---|
| Cloud email and files | SaaS provider | All correspondence and documents | Contract, provider certificates, tenant configuration |
| Managed firewall | MSP | Network access policy | Service contract, change record, access review |
| Payroll | Out-of-scope HR | Staff personal data | Internal service agreement, access permissions |
| Data center | Colocation | Physical hosting | The provider’s certificate and its scope, entry records |
With outsourcing, the rule is simple: the process is outsourced, the responsibility isn’t. Annex A controls 5.19–5.22 (supplier relationships) and 5.23 (use of cloud services) expect requirements for every outsourced interface to be written into the contract and the service to be monitored. In the managed firewall example, a rule change the MSP makes must appear in your change record; if it doesn’t, the auditor will find it. If you rely on a cloud provider’s ISO 27001 certificate, always read the certificate’s scope statement: does it really cover the service and region you use?
Narrow vs broad scope
The breadth of scope is a strategic decision. There’s no single right answer; the choice depends on the organization’s goal, its resources and what the customer expects.
| Criterion | Narrow scope | Broad scope |
|---|---|---|
| Installation time | Short, focused | Long, with many stakeholders |
| Audit duration and cost | Lower | Increases with headcount and locations |
| Interface management | Many interfaces, complex evidence | Few interfaces, a simpler boundary |
| Customer perception | May look limited when the scope statement is read | Organization-wide assurance |
| Risk | Risks leaking from out-of-scope areas stay invisible | Immature units produce nonconformities |
In environments with a lot of shared infrastructure, a narrow scope doesn’t stay as narrow as people think. Every new interface means a new evidence file. In medium-sized organizations, a healthy start is to do the first certification with the main customer-facing service and the IT infrastructure that carries it, and to extend the scope in a planned way over surveillance cycles.
The audit consequences of leaving things out of scope
Two different kinds of “leaving out” are constantly confused. The first is the scope boundary: a unit or location being outside the ISMS. The second is excluding Annex A controls: this is done in the SoA with a justification and must be based on the risk assessment. The requirements of clauses 4–10 can’t be excluded in any way. The auditor tests both situations with these questions:
- Does the out-of-scope unit access in-scope information? If so, how is this access controlled?
- Is the justification for the excluded control real, or just a polite way of saying “we don’t do it”?
- Does the scope statement look broad enough to mislead the customer?
How to write exclusion justifications in the SoA is explained in detail in the ISO 27001 SoA guide.
Sample scope statements
Scope documentation has two layers: the short scope statement to go on the certificate, and the scope document explaining boundaries, interfaces and exclusions. The short statement must include the service, the location and a reference to the SoA version. The statements below are fictional examples:
Example 1 (service-focused): “The information security management system for the design, operation and support of managed IT infrastructure services provided from the [city] head office; in accordance with Statement of Applicability version 1.2 dated [date].”
Example 2 (organization-wide): “The information systems and processes supporting all activities carried out at [organization]’s [city] head office and [city] production site; Statement of Applicability version 2.0.”
What weak statements have in common is vagueness. “IT department” names a unit but doesn’t say which service is assured; “all information assets” draws no boundary at all. The scope document should also contain:
- Included units, roles and approximate headcount
- Addresses of locations and the activity carried out at each
- Main in-scope systems and applications, cloud tenants
- A reference to the interface register and the justification for what’s left out
- Approving manager, approval date and document version
Managing scope changes
The scope isn’t a document written once and shelved. A new location, a company acquisition, moving a service to the cloud or a change of main supplier affects the scope directly. A picture you may come across: email has been moved to the cloud and the file server shut down, but the scope document and asset inventory still show the old server. Clause 6.3 (planning of changes), added in ISO 27001:2022, requires changes to the ISMS to be planned. The order we suggest for a scope change:
- Assess the change’s effect on the context and interested parties.
- Update the interface register and asset inventory.
- Carry out a risk assessment for the new scope and revise the SoA.
- Present the change as an input to management review and get it approved.
- Inform the certification body; a scope extension is usually assessed in a surveillance audit or a separate special audit.
Using a certificate for an activity extended without notification removes the basis of the assurance given to the customer. When the scope is narrowed, the statement on the certificate must be updated too. The certificate must reflect reality.
To see the scope decision alongside the other steps of setting up an ISMS, the ISMS setup guide gives the overall framework. To measure your current state against scope options, see the ISO 27001 gap analysis page; to operate the scope in practice, the ISMS setup and implementation consulting page. The official introduction to the standard is on ISO’s ISO/IEC 27001 page.
Frequently asked questions
Can the scope be limited to a single department?
It can. However, the shared infrastructure that department uses (identity management, email, network) and support processes must be defined as interfaces, and the controls at these interfaces must be evidenced. A very narrow scope increases the number of interfaces and can increase the evidence burden.
Can we exclude Annex A controls from scope?
Annex A controls can be excluded on the basis of the risk assessment, with a written justification in the SoA. The management system requirements in clauses 4 to 10, however, can’t be excluded.
If we use cloud services, is the cloud provider within our scope?
The provider itself isn’t within your scope; it’s defined as an interface. Customer-side responsibilities such as tenant configuration, identity and access management and data classification are within your scope, and you’ll be asked for evidence of them.
Can we extend the scope after certification?
Yes. The change is planned: the risk assessment and SoA are updated, management approval is obtained and the certification body is informed. An extension is usually assessed together with a surveillance audit or in a separate special audit.