Implementation Project
/
Step 1

Implementation Project

var(--variable-QsTa4u5mL)

How to Define the ISO 27001 Scope

var(--variable-Cl6cRG5u3)

Written by

Aron Lange

Published

Nov 5, 2026

Implementation Project

var(--variable-QsTa4u5mL)

How to Define the ISO 27001 Scope

var(--variable-Cl6cRG5u3)

Written by

Aron Lange

Published

Nov 5, 2026

Every ISO 27001 project starts with the same question: what exactly are we protecting? Before you assess a single risk or write a single policy, you draw a line around what your ISMS covers and what it doesn’t. That line is the scope.

Getting it right matters more than most people expect. Draw it too wide, and the project becomes hard to manage. Draw it too narrow, and the certificate may not cover what your customers actually care about. And everything that follows, from the gap analysis to the certification audit, works inside the boundary you set here.

Step 1 ends with one approved document: the scope of the ISMS. This article shows you what ISO 27001 requires to get there, how a company carries it out in practice, and the tasks you can work through for your own organization.

What ISO 27001 requires in Step 1

Step 1 covers the four subclauses of clause 4, context of the organization. Three of them build on each other: you look at your issues (4.1) and your interested parties (4.2), and with both in hand you determine the scope (4.3). The fourth (4.4) is the mandate for the whole ISMS.

Context of the organization: external and internal issues and external and internal interested parties lead to the scope of the ISMS and then to the ISMS processes

4.1 External and internal issues

Clause 4.1 asks you to determine the external and internal issues that are relevant to your organization’s purpose and that affect what your ISMS is supposed to achieve. So the question is never “what’s going on in the world?”, but “what’s going on that matters for our information security?”

External issues are outside your control: laws, the economy, technology, the weather. A simple way not to overlook a whole area is a PESTEL review of political, economic, social, technological, environmental and legal factors. Think of new regulations like NIS2, ransomware hitting your suppliers, or a recession that cuts security budgets.

Internal issues are within your control: your culture, your strategy and objectives, your structure, your processes, your IT and your supply chain. A board that doesn’t see security as its topic, or legacy systems with undocumented data flows, are typical examples.

One detail makes the difference between a useful list and a useless one: a factor only becomes an issue when you can say how it affects your ISMS. “International data transfer restrictions” on its own is a headline. “They limit which cloud providers we can use” is an issue.

And since the 2024 amendment, there’s one issue you can’t skip. You have to determine whether climate change is relevant for your ISMS. For many organizations the answer is yes, because extreme weather can hit their own sites, the data centers they rely on or a critical supplier. If your answer is no, you should be able to explain why.

4.2 Interested parties and their requirements

Clause 4.2 asks for three things: the interested parties that are relevant to your ISMS, their requirements for information security, and which of those requirements your ISMS will address.

Interested parties are simply stakeholders: anyone who can affect your decisions or is affected by them. Outside the organization, that’s typically regulators, customers, suppliers and partners, investors and insurers. Inside, it’s management, process and system owners, departments like HR, the employees and, in many countries, a works council.

Their requirements can be stated, like a clause in a customer contract, generally implied, like a customer who simply expects you not to lose their data, or obligatory, like a law.

The part that’s easy to miss is the last one: deciding which requirements the ISMS addresses. Some clearly yes, like a customer who requires an ISO 27001 certificate. Some only partly, like a privacy law that asks for much more than security. And some not at all, like a request for a SOC 2 report, which is a separate attestation. “Not addressed” doesn’t mean “ignored”. It means it’s handled somewhere else, and you should be able to say where.

Examples of deciding which requirements the ISMS addresses: an ISO/IEC 27001 certificate for a key customer is addressed, security of personal data under privacy laws is partly addressed, no performance monitoring without a works council agreement is addressed, and a SOC 2 Type II report is not addressed

To decide where to spend your time, a power-interest grid helps: parties with high power and high interest you manage closely, the rest you keep satisfied, keep informed or monitor. ISO 27001 doesn’t require the grid. It’s just practical.

4.3 The scope itself

Clause 4.3 is the central task of Step 1. You determine the boundaries and applicability of your ISMS, and you consider three things when you do: your issues from 4.1, the requirements from 4.2, and the interfaces and dependencies between what you do and what other organizations do for you.

That third point is the one people forget. Let’s say your software runs on a public cloud, your payroll is outsourced and a provider runs your service desk. None of them is part of your organization, but your ISMS depends on all of them. You can’t leave them out of the picture. You describe the interfaces, and you control them, for example through your supplier contracts.

ISO/IEC 27003, the guidance standard, suggests describing the scope in three dimensions, each with its boundaries and interfaces: the organizational scope, the physical scope and the ICT scope.

The three dimensions of the ISMS scope: organizational scope (legal entities, processes, departments), physical scope (locations, specific sections) and ICT scope (information and communication technology)

Does the scope have to cover the whole organization? No. You can leave out a site, a subsidiary or a business line. But the boundary has to be clear, the interfaces to what you exclude have to be controlled, and the scope has to make sense to your interested parties. A certificate that leaves out exactly the service your customer cares about won’t help you much.

In practice, you get to the scope in four rounds: a small group of managers sets a preliminary scope, you refine it to reduce the number of interfaces at the boundary (don’t forget support functions like HR, IT and facility management), all managers inside the refined scope evaluate it, and top management formally approves the final version.

Four rounds to the ISMS scope: preliminary scope, refined scope, final scope and approval

The scope is the one document in Step 1 that ISO 27001 explicitly requires: it has to be available as documented information.

4.4 Why this is a process, not a one-off

Clause 4.4 requires you to establish, implement, maintain and continually improve your ISMS, including the processes it needs and how they interact. For Step 1, that has a practical consequence: your context changes, and your management review has to consider those changes. So the analysis of issues and interested parties becomes a process that runs at least once a year and whenever something significant changes, with an owner and a place for its results.

At Barvello: why “Connect only” didn’t hold up

Barvello Coffee Systems is the fictional company of our ISO 27001 Lead Implementer course: a family-owned maker of professional coffee machines in Munich, with about 500 employees. About 21,700 of its machines report to its own cloud platform, Barvello Connect.

The project starts with a letter. Ovena, Barvello’s largest customer with 14 percent of revenue, requires an ISO 27001 certificate to renew its framework agreement. The letter is specific: the certificate has to cover Barvello Connect and the processes that develop, operate and support it, including billing.

In the board meeting, two opinions collide. The CFO wants the scope “as small as possible”. The head of sales says Stopwell, the largest customer in the US, needs the American subsidiary in it. Nadia Berger, the new ISMS project lead, has to prepare the decision. Three options are on the table.

Barvello’s three scope options: Connect only, as Ovena’s letter puts it; the GmbH in Munich, the legal entity NIS2 applies to; the whole group with the plant in Treviso and Barvello Inc. in Charlotte

Option 1 sounds like the smallest, but it rests on a misunderstanding. ISO 27001 isn’t a product certification. A certification body doesn’t certify Connect. It certifies Barvello’s management system, and the scope says which parts of the organization that management system covers.

And even translated into activities, “Connect only” falls apart. Connect’s user accounts and network come from IT. The firmware team signs the updates Connect sends to the machines. Production registers every machine at the flashing stations. Finance creates invoices from Connect’s cup counters. Field service gets its tickets from Connect, and HR decides who gets access. Outside the company, Connect depends on Microsoft Azure, developers in Warsaw and an electronics manufacturer in Penang. A scope around Connect would have meant a boundary through almost every department, with an interface at each one.

What Barvello Connect depends on: IT, the firmware team, production, finance, field service and HR inside Barvello, and Microsoft Azure, developers in Warsaw and a manufacturer in Penang outside Barvello

So the GmbH became the preliminary scope. When Nadia refined it, Barvello Inc. came in: only 34 people, but on the same systems as Munich, and Stopwell buys through it. The plant in Treviso stayed out for now. It makes parts, doesn’t process customer data and runs its own IT, so it’s treated as an interface (the VPN connection, the exchange of drawings and the purchase orders) and is planned for later. On 14 December, the CEO approved the final scope.

Two details from Nadia’s scope document are worth copying. First, she wrote down why Treviso is excluded and what the interfaces are, not just that it’s excluded. Second, her proposed scope statement for the certificate doesn’t mention Barvello Connect at all. It speaks of “cloud services for connected coffee machines”. A product name on a certificate reads like a product certification, it’s outdated the day marketing renames the product, and the next service isn’t covered until the certificate is extended.

Watch the full case study above. It’s the complete lecture from the course, including Nadia’s issues, her interested parties and the scope document itself.

Your turn: Step 1 in the project plan

In the project plan of our ISO 27001 Toolkit, Step 1 is 14 tasks and one milestone. Every task points to the clause it implements:

ID

Task

Clause

2

Purchase ISO/IEC 27001:2022

3

Establish context analysis process
Deliverable: Context analysis process

4.4

4

Review external environment

4.1

5

Determine external issues
Deliverable: External issues

4.1

6

Review internal aspects

4.1

7

Determine internal issues
Deliverable: Internal issues

4.1

8

Identify external interested parties

4.2 a)

9

Identify internal interested parties

4.2 a)

10

Identify requirements of interested parties
Deliverable: Requirements of interested parties

4.2 b)

11

Determine which requirements are addressed through the ISMS

4.2 c)

12

Determine preliminary scope

4.3

13

Determine refined scope

4.3

14

Determine final scope

4.3

15

Obtain approval for final scope

4.3

16

Milestone: ISMS scope is approved
Deliverable: Scope of the ISMS

4.3

At the end of Step 1, you have four deliverables, and the toolkit has a template for each of them:

The four Step 1 deliverables: context analysis process (determined, clause 4.4), external and internal issues (determined, clause 4.1), requirements of interested parties (determined, clause 4.2) and scope of the ISMS (required, clause 4.3)

Only the scope is required by ISO 27001. The other three aren’t explicitly required, but most organizations decide they need them. Without them, it’s hard to explain to an auditor how you arrived at your scope.

Your scope is one of 19.

Here are the other 18.

ISO 27001 requires 19 documents and records, and auditors expect 124 more. The checklist lists all of them, each mapped to its clause or Annex A control.

From the auditor’s chair

When I review a scope in a stage 1 audit, I start with the exclusions. An exclusion without a reason is typically the first thing I ask about. Write down what you exclude, why, and how you control the interfaces to it, like Nadia did for Treviso.

The second thing I look at is whether the issues and interested parties actually belong to the organization in front of me. If a record still says “emergence of quantum computing” because it came with a template, I’ll ask what that has to do with your ISMS. Delete every example that doesn’t apply to you.

And when a requirement is marked as not addressed through the ISMS, I’ll ask where it’s handled instead. Have that answer in the record.

Frequently asked questions

Does the ISMS scope have to cover the whole organization?

No. ISO 27001 lets you exclude sites, subsidiaries or business lines. But the boundary has to be clear, the interfaces to the excluded parts have to be controlled, and the scope has to make sense to your interested parties, above all to the customers who asked for the certificate.

Is the scope on the certificate the same as the ISMS scope?

Not quite. The ISMS scope is what you determine under clause 4.3, and it can be a detailed document. The scope statement on the certificate is a short wording that the certification body decides, based on your scope. It pays to propose a generic statement that describes services rather than product names.

Which Step 1 documents are mandatory?

Only the scope of the ISMS. Clause 4.3 requires it as documented information. Your issues, your interested parties and the context analysis process are up to you, but most organizations document them because the scope is hard to justify without them.

Can we change the scope later?

Yes. Many organizations start with the part of the business their customers ask about and extend the scope later, like Barvello plans to do with Treviso. Once you’re certified, an extension goes through your certification body.

Step 1 in the course.

Watch Barvello do it.

7 lectures (42 min) walk you through clauses 4.1 to 4.4. Then you watch Nadia scope Barvello’s ISMS with the real templates. Your turn: 14 tasks in the project plan and the templates for your issues, interested parties and scope.

4.1 Context of the Organization

07:24

4.3 Scope of the ISMS

05:08

Case Study: Scoping Barvello

12:22

Template: ISMS Scope

4.3

With the scope approved, you’re ready for Step 2: the gap analysis, where you find out where your organization stands against the requirements of ISO 27001.


€690

/ year

incl. 19% VAT · billed yearly

12-hour Video Course

ISO 27001 Toolkit

Practice Exam

Weekly Live Q&A

Exam Voucher + Free Retake

Bundle

Study Guide

Bundle

€690

/ year

incl. 19% VAT · billed yearly

12-hour Video Course

ISO 27001 Toolkit

Practice Exam

Weekly Live Q&A

Exam Voucher + Free Retake

Bundle

Study Guide

Bundle