The Ultimate Guide to ISO 27001 Clause 4.3: Determining The Scope Of The Information Security Management System

ISO 27001 Determining The Scope Of The Information Security Management System

The biggest challenge for those new to ISO 27001 is getting the scope right.

ISO 27001 Determining The Scope Of The Information Security Management System is the requirement to define the scope of the information security management system (ISMS).

The scope clarifies:

• Which parts of the organisation are included in the ISMS
• The boundaries of the organisation’s ISO 27001 certification.

In ISO 27001 this is known as ISO27001:2022 Clause 4.3 Determining The Scope Of The Information Security Management System: It is one of the mandatory ISO 27001 clauses.

Key Takeaways

• The scope should reflect what you want to be shown on your ISO 27001 certificate
• Narrowing scope will remove undue cost and bureaucracy
• Getting the scope wrong can cost a lot of time and lot of money

What is ISO 27001 Clause 4.3?

ISO 27001 Clause 4.3 Determining The Scope Of The Information Security Management System is an ISO 27001 clause that requires you to define the scope of your information security management system.

Purpose and Definition

The purpose of ISO 27001 Clause 4.3 Determining The Scope Of The Information Security Management is to ensure a clear and well-defined scope for your Information Security Management System (ISMS) and your subsequent ISO 27001 certification. This clarity helps establish:

• Which parts of the organisation are included within the boundaries of the ISMS.
• The specific areas that will be assessed during the ISO 27001 certification audit.

By defining the scope, you can ensure that your ISMS is focused on the most critical areas and that your certification accurately reflects the extent of your information security efforts.

The ISO 27001 standard defines ISO 27001 Clause 4.3 Determining The Scope Of The Information Security Management as:

The organization shall determine the boundaries and applicability of the information security
management system to establish its scope.
When determining this scope, the organization shall consider:
a) the external and internal issues referred to in 4.1;
b) the requirements referred to in 4.2;
c) interfaces and dependencies between activities performed by the organization, and those that are
performed by other organizations.
The scope shall be available as documented information.

ISO27001:2022 Clause 4.3 Determining The Scope Of The Information Security Management System

1. Establish scope by determining the boundaries and applicability of the information security management system: There is a cost in time, resource and money to implement ISO 27001 so it makes sense to concentrate on protecting the things that your clients are expecting to you to protect and the things that represent the biggest risk to you. I will show you how to do this later in the article.
2. Consider your internal and external issues: When you set the scope you are making sure that you have addressed the internal and external issues that we covered in ISO 27001 Clause 4.1 Understanding the Organisation and It’s Context.
3. Consider the needs an expectations of interested parties: The interested parties and their requirements which we covered in ISO 27001 clause 4.2 Understanding the Needs and Expectations of Interested Parties will be reviewed on if, and how, they affect the scope you are setting.
4. Consider what you do verses what other people do for you: Third parties will be used a lot and those third parties will be responsible for the areas that they control so you will define the interfaces and dependencies between activities you do and activities that they do.

ISO 27001 Clause 4.3 Explained: A Complete Guide

In the video ISO 27001 Determining Scope Of The ISMS Explained – ISO27001:2022 Clause 4.3 I show you how to implement it and how to pass the audit.

How to Define Your ISMS Scope: A Step-by-Step Guide

Scope is vitally important for your ISO 27001 Certification. It clearly sets out what we are going to apply our information security management system to and more importantly it defines what will go on our ISO 27001 certificate.

Determining your scope effectively can be challenging. To assist you, we’ve created a comprehensive guide: How To Define ISO 27001 Scope.This guide provides clear, step-by-step instructions to help you establish a well-defined scope.

We’ve included an ISO 27001 Scope Statement Template within our ISO 27001 Toolkit. This template can be used as a valuable resource to assist in the development of your official scope statement.

Based on practical, real world implementations and experience this is how to implement ISO 27001 Clause 4.3 Determining The Scope Of The Information Security Management System (ISMS):

Step 1: Define Organisational Boundaries

Clearly identify where the organisation’s boundaries lie, especially in complex or multi-national organisations.

• Utilise organisational charts, legal documents, and stakeholder interviews to define the organisational structure.
• Consider third-party relationships and their impact on information security.

Step 2: List all your products and services

List out all of the products and services that you have and document them.

• Conduct workshops with key interested parties (e.g., management, product owners, sales) to identify and document core offerings.
• Utilise process mapping and data flow diagrams to visualise the flow of products and services.

Step 3: Ask your customers which products and services they expect to be in scope

From your list of products and services ask your customers which of them they expect to be in scope. Review current contracts for any scope requirements.

Step 4: Ask your leadership team which products and services they expect to be in scope

From your list of products and services ask your leadership team which of them they expect to be in scope.

Step 5: Ask the list of interested parties which products and services they expect to be in scope

From your list of products and services ask your interested parties which of them they expect to be in scope.

Step 6: Document the list of products and services that are in scope

Taking the input from customers, leadership and interested parties document the list of products and services that are in scope.

Step 7: Review your internal and external issues

Review the products and services that are in scope against the list of internal and external issues to determine if their are any direct issues or changes to issues.

Step 8: Confirm the list of of products and services that are in scope

Agree and sign off the scope with the senior leadership team and document the agreement.

Step 9: Identify Supporting Functions

Determine which departments and functions are critical to the delivery of core products and services.

• Analyse organisational structure and identify departments that directly or indirectly support core business functions.
• Consider departments like IT, HR, finance, legal, and facilities.

Step 10: Determine Scope Exclusions

Identify activities, departments, or systems that will be explicitly excluded from the scope of the ISMS.

• Clearly document the rationale for any exclusions.
• Ensure that excluded areas do not pose significant risks to the organisation’s information security.

Step 11: Document and understand the ISO 27001 Scope Boundaries

Identifying the people, premises, technology, and suppliers that directly support the in-scope products and services and understand the interfaces between in scope entities and out of scope entities as well as with third party organisations.

Step 13. Write your ISO 27001 Scope Statement

Summarise your scope in the required ISO 27001 scope statement.

• Use clear and concise language.
• Obtain input and approval from key interested parties.
• Regularly review and update the scope statement to reflect changes in the organisation or its environment.

Step 14: Communicate Scope to Stakeholders

Ensure that all relevant stakeholders understand the scope of the ISMS and their roles and responsibilities within it.

• Conduct training sessions and awareness campaigns.
• Distribute the scope statement to all employees.
• Include the scope statement in relevant policies and procedures.

Step 15: Obtain Management Approval

Secure management approval for the defined scope of the ISMS.

• Present the proposed scope to management and address any concerns or questions.
• Obtain formal approval from top management.

Step 16. Verify the scope statement with the certification body (optional)

Share your ISO 27001 scope statement with the external ISO 27001 certification for feedback and confirmation.

ISO 27001 Scope Statement Example

An example ISO 27001 Scope Statement:

The scope of this Information Security Management System (ISMS) encompasses all products and services offered by [Organisation Name], as outlined in [link to product/service catalogue or relevant document]. The implementation of controls is detailed within the Statement of Applicability, version [version number].

In practice:

A practical example, taken directly from our ISO 27001 certification, is:

Information security consultancy and virtual chief information security officer services in accordance with the statement of applicability version 2.1

High Table ISO 27001 Scope Statement

ISO 27001 Scope Template

The ISO 27001 Scope Template provides a structured framework for defining the scope of your Information Security Management System (ISMS), fully meeting the requirements of ISO 27001 Clause 4.3.

It was designed and built with these key features:

• Pre-filled with common scope examples: Provides a solid foundation and saves you time.
• Available as an individual download: Offers flexibility for specific needs.
• Included in the internationally acclaimed ISO 27001 Toolkit: Access a comprehensive suite of templates and resources to streamline your entire implementation process.

How to pass the ISO 27001 Clause 4.3 audit

To successfully pass an audit of ISO 27001 Clause 4.3, a crucial step in achieving ISO 27001 Certification, you must ensure you have implemented the mandatory ISO 27001 documents and ISO 27001 polices. You are going to need to put in place ISO 27001 controls to:

• Document an ISO 27001 Scope Statement
• Implement the ISO 27001 standard

What an auditor looks for

The auditor will assess several key areas related to Clause 4.3 during their audit:

1. That you have documented your ISO 27001 scope

You must have a documented scope for your Information Security Management System (ISMS). The auditor will check for the existence of a documented scope statement. Utilising the ISO 27001 Scope Template can simplify this process.

2. That you have implemented the scope

You must have implemented the ISO 27001 standard within the defined scope. The auditor will assess whether the requirements of the ISO 27001 standard have been applied effectively to the identified products, services, and areas included within the scope.

3. That the scope was approved

Your documented scope must be formally approved. The auditor will check for evidence of scope approval, such as documented approvals and signatures from relevant management personnel.

How to audit ISO 27001 Clause 4.3

This audit checklist is a guide on how to conduct an internal audit of ISO 27001 scope based on what the ISO 27001 certification auditor will audit. It gives practical audit tips including what to audit and how.

1. Check that scope boundaries are defined

• Review scope documentation, diagrams, and network maps.
• Interview personnel involved in defining the scope.
• Check for consistency with other documented information.

2. Check that the scope is aligned with the organisation’s goals

• Review business strategy documents, risk assessments, and management review minutes.
• Interview senior management about how the scope supports business objectives.

3. Review scope exclusions

• Review the documented justifications for exclusions.
• Interview personnel about the rationale behind exclusions.
• Assess the potential impact of excluded elements on information security.

4. Ensure the scope is documented

• Inspect the scope document for completeness, accuracy, and clarity.
• Check version control and document accessibility.

5. Check interdependencies between systems

• Review network diagrams, data flow diagrams, and agreements with third parties.
• Interview personnel about system interconnections and dependencies.

6. Check alignment with legal and regulatory requirements

• Review legal and regulatory requirements relevant to the organisation.
• Check that the scope document reflects these requirements.

7. Evidence the inclusion of supporting processes

• Review process documentation and interview personnel from supporting functions.
• Assess the impact of these processes on information security.

8. Ensure that the scope was communicated

• Review communication records and interview personnel about their understanding of the scope.
• Check for evidence of communication to relevant stakeholders.

9. Gain evidence of scope reviews

• Examine the process for reviewing and updating the scope.
• Check review frequency and evidence of updates.
• Look for triggers for review (e.g., changes in business strategy, new threats).

10. Review justifications for scope changes

• Review records of scope changes and their justifications.
• Interview personnel about the reasons for changes and their impact on the ISMS.

Top 3 ISO 27001 Clause 4.3 Mistakes and How to Fix Them

These are the top 3 mistakes people make for ISO 27001 Scope:

1. Defining an Overly Broad Scope

Including unnecessary areas within the scope of your ISMS can lead to wasted time, resources, and unnecessary costs. Carefully consider and document the specific products, services, and areas that require information security controls.

2. Neglecting Client Expectations

Failing to consider client expectations and requirements within the scope of your ISMS can diminish the value of your certification. Involve clients in the scope definition process to ensure your ISMS addresses their specific needs and concerns.

3. Poor Scope Management

Inadequate documentation, version control, and review of the scope statement can lead to confusion and non-compliance. Maintain accurate and up-to-date records of the scope statement, implement a robust version control system and regularly review and update the scope statement to reflect changes in the organisation or its environment.

How can an ISO 27001 toolkit help with ISO 27001 Clause 4.3?

An ISO 27001 toolkit gives you the tools you need to meet the rules in Clause 4.3 quickly and correctly.

1. It Offers a Clear Plan

Instead of beginning from nothing, a toolkit offers a ready-made plan for deciding your ISMS scope. It often includes a “Scope and Boundaries Document” that asks you to think about all the necessary parts of the clause. This helps you avoid missing key items like certain business groups, physical spots, or outside helpers.

2. It Saves Time and Effort

Using ready-to-use, flexible forms helps you save a lot of time and resources. Writing a scope document from scratch takes a lot of time. The forms provide the layout, so you just fill in your company’s details, like which departments, goods, or services are included.

3. It Ensures All Parts Are Included and Rules Are Followed

A good toolkit helps make sure your scope paperwork is full and can be checked. The forms are often made by experts and match the ISO 27001 rules. They have spots to write down why you left anything out, which is key for an auditor. Some kits even come with checklists to confirm all the rules of Clause 4.3 have been met.

4. It Connects to Other Rules

Clause 4.3 is directly linked to Clauses 4.1 and 4.2. Many toolkits offer combined documents or tips that show you how to connect what you found out about the “context of the organization” (Clause 4.1) and “interested parties”(Clause 4.2) right into your scope plan. This makes sure the first steps of your ISO 27001 rollout are logical and easy, making the whole process smoother.

ISO 27001 Clause 4.3: Determining The Scope Of The Information Security Management System FAQ