Part of ISO 27001: Critical success factors, a series on building a management system that reflects how your organisation really runs.
What it is
Scope is the boundary of your management system: which parts of the organisation, which locations, which services and which supporting systems the ISMS covers. It's the first thing a customer reads on your certificate, and the frame for everything else you do.
In practice it's also where you settle the context: why you're doing this, who cares about the result, and what you're aiming to achieve. Those three things tend to be decided together, so they sit together here.
What the standard asks
Four short clauses set this up:
- Context (4.1). Understand the internal and external issues that affect your ability to achieve the ISMS's intended outcomes. Since the 2024 amendment, this includes deciding whether climate change is a relevant issue for you.
- Interested parties (4.2). Identify who has a stake in your information security (customers, regulators, staff, suppliers, owners), what they require, and which of those requirements the ISMS will address.
- Scope (4.3). Define the boundaries and applicability of the ISMS, taking account of the context, the interested parties, and the interfaces and dependencies with things outside the scope. The scope has to be documented.
- Objectives (6.2). Set information security objectives that are consistent with your policy, measurable where practicable, monitored, communicated and updated, with a plan for what will be done, by whom, by when and how you'll judge success.
What good looks like
A good scope statement fits on a page and reads naturally to a customer. It names the service or business unit, the locations and the main systems, and says plainly what sits outside.
- The scope matches what your customers actually need certified. That's usually a commercial question before it's a technical one.
- Interfaces and dependencies are named: the outsourced IT provider, the cloud platform, the group function that runs HR.
- The list of interested parties is short and specific, with the requirements that matter to each.
- Objectives describe outcomes you'd care about anyway, with a measure attached, and leadership has agreed them.
Evidence an auditor will ask for
- The documented scope statement
- A record of internal and external issues, including your decision on climate change
- A list of interested parties and their relevant requirements
- Information security objectives, with the plans and measures behind them
- Minutes showing leadership agreed the scope and objectives
Common failure modes
- Scoping around the hard bits. Leaving out the messy system or the difficult team makes the first audit easier, but customers and auditors notice when the scope doesn't match the service they're buying.
- Too wide for a first pass. Trying to certify the whole group first time round usually stalls. A tighter scope that you can genuinely run is a better starting point, and it can grow.
- Forgotten dependencies. The scope ends at your office door but your data lives with three suppliers. Naming the interfaces is what makes supplier controls make sense later.
- Objectives nobody can measure. "Achieve certification" or "improve security" won't survive a management review. Pick a few outcomes you can track.
How it connects
Feeds from
- Leadership's view of why you're doing this, agreed as part of management commitment.
Feeds into
- Risk analysis, which assesses risks within the scope.
- The Statement of Applicability, which is written for this scope.
- The management forum, which checks at each review whether the context, interested parties and therefore the scope are still right.
Where it sits in the plan
Stage: Commit. Scope is agreed before the loop starts, alongside leadership commitment. On later cycles it's revisited through management review, usually with small changes rather than redraws.
The plan in the main article shows how this fits with everything else, and the bootstrapping guide covers each stage in detail.
Resources
Tom Whipp is the founder of RiskQuilt. He spent around thirty years in cyber and technology risk in UK financial services, including CISO and Director of Technology Risk roles.