ISO 27001 Scope Statement Beginner’s Guide

Home / ISO 27001 Templates / ISO 27001 Scope Statement Beginner’s Guide

Last updated Jul 5, 2025

Author: Stuart Barker | ISO 27001 Lead Auditor

Introduction

You want to lean how to write an ISO 27001 Scope Statement? You are unsure about how to go about it, where to start, what to include and how to write it?

In this guide, you will learn what an ISO 27001 Scope Statement is, how to write it yourself and I give you a template you can download and use right away.

What is an ISO 27001 Scope Statement?

The ISO 27001 Scope statement is the statement that will appear on your ISO 27001 certificate. It is the public document that you share with customers and potential customers. They will use this information to assess if the ISO 27001 certificate covers what they are buying from you and therefore if they can place reliance on it for their needs.

The scope statement shows which parts of your business are certified and it shows them that you are doing the right thing for information security.

If the ISO 27001 scope statement does not cover the products or services that they are buying from you then they cannot place reliance on it and it will not be valid for them.

Consider an extreme example where your ISO 27001 scope statement covers the company stationary cupboard (I know, I know, it is an example) and the customer is buying an online SAAS Platform from you. Does the fact that you have ISO 27001 certification for your stationary cupboard give them assurances that the online SAAS Platform is secure and managed to the standard of ISO 27001?

If you are struggling with this one, let me help you, the answer is no.

What is ISO 27001 Scope?

ISO 27001 scope is the scope of the information security management system. 

We are going to build an information security management system with the information security policies and apply it to something to get ISO 27001 certified. 

The ‘something’ that we are going to apply it to is the scope.

We document the scope in an ISO 27001 Scope Statement.

ISO 27001 Scope Examples

When considering the what of ISO 27001 scope we can look at examples where we might want to apply the standard and gain ISO 27001 certification.

Common examples include

  • A product
  • A service
  • A location
  • A geography
  • A team
  • A department
ISO 27001 Toolkit Business Edition

How to write an ISO 27001 Scope Statement

The scope for ISO 27001 is going to be based on two things:

  • the products and services you offer
  • which of those products and services your customers expect to be certified

Time needed: 1 hour

How to write and ISO 27001 Scope Statement

  1. List your products and services

    Create list of all of your products and services. Use the names that your customers use and know them by.

  2. Choose the products and services that need ISO 27001 certification

    Using the list of products and services that you have created look at what your customers are asking to be certified.

    Customer Feedback: We start by reviewing the products and services we offer, then see what questions our customers have. This helps us identify that scope that is most relevant to their needs.

    Contract Review: Existing customer contracts can reveal specific certification scope required to do business with them.

    Sales Team Insights: Talking to your sales team provides valuable feedback on what certification scope customers are asking about.

    Since resources (time, money, and personnel) are limited, it’s crucial to focus certification efforts. The chosen scope might involve extensive paperwork, so including only what’s truly necessary minimises workload and cost.

  3. Identify the people, technology and premises that make up the chosen products and services.

    List out the departments in the company, the technologies and the locations that make up the products and / or services that you want to have and ISO 27001 certification.

  4. Write the ISO 27001 scope statement

    Write a clear statement that states the products and / or services and then clearly sets out the people, technology and locations that are in scope for the ISO 27001 certification.

  5. Document what is in scope and what is out of scope

    Clearly define your ISO 27001 scope for better management. When outlining your scope, be specific . Include both what’s included (in scope) and excluded (out of scope) in a dedicated Scope Document. This document goes beyond the brief scope statement and serves as a valuable internal resource.

    To further clarify your scope boundaries, consider including details on:
    Systems in use
    People involved
    Locations covered
    Departments encompassed

    A comprehensive Scope Document with visuals like architecture diagrams, technical documents, and network maps will greatly enhance clarity.

ISO 27001 Scope Statement Examples

ISO 27001 Scope Statement Example 1: High Table Scope Statement

The following is taken directly from our very own ISO 27001 scope statement:

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

High Table ISO 27001 Scope Statement

ISO 27001 Scope Statement Example 2: General Scope Statement

The scope encompasses all employees, locations, technology, data assets and business processes that deliver [List the products and services in scope] in accordance with the statement of applicability version [version number].

General ISO 27001 Scope Statement

A great ISO 27001 scope example is provided in the ISO 27001 Scope Document template and can be readily reused and adapted for your needs.

ISO 27001 Scope Statement Template

Doing so many ISO 27001 certifications over the years led to the creation of the ISO 27001 Scope Document Template that people can use as part of their own ISO 27001 certification.

ISO 27001 Scope Document Template

Watch the Video

To watch a video of how to implement ISO 27001 scope and write an ISO 27001 scope statement watch the tutorial – Determining the Scope of the Information Security Management System.

ISO 27001:2022 requirements

ISO 27001 Clauses

ISO 27001 Clause 4.1 – Understanding The Organisation And Its Context

ISO 27001 Clause 4.2 – Understanding The Needs And Expectations of Interested Parties

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

ISO 27001 Clause 4.4 – Information Security Management System

ISO 27001 Clause 5.1 – Leadership and Commitment

ISO 27001 Clause 5.3 – Organisational Roles, Responsibilities and Authorities

ISO 27001 Clause 6.1.1 – Planning General

ISO 27001 Clause 6.1.2 – Information Security Risk Assessment

ISO 27001 Clause 6.1.3 – Information Security Risk Treatment

ISO 27001 Clause 6.2 – Information Security Objectives and Planning to Achieve Them

ISO 27001 Clause 6.3 – Planning Of Changes

ISO 27001 Clause 7.1 – Resources

ISO 27001 Clause 7.2 – Competence

ISO 27001 Clause 7.3 – Awareness

ISO 27001 Clause 7.4 – Communication

ISO 27001 Clause 7.5.1 – Documented Information

ISO 27001 Clause 7.5.2 – Creating and Updating Documented Information

ISO 27001 Clause 8.3 – Information Security Risk Treatment

ISO 27001 Clause 9.1 – Monitoring, Measurement, Analysis, Evaluation

ISO 27001 Clause 9.2 – Internal Audit

ISO 27001 Clause 9.3 – Management Review

ISO 27001 Clause 10.1 – Continual Improvement

ISO 27001 Clause 10.2 – Nonconformity and Corrective Action

ISO 27001 Organisation Controls

ISO 27001 Annex A 5.1: Policies for information security

ISO 27001 Annex A 5.2: Information Security Roles and Responsibilities

ISO 27001 Annex A 5.3: Segregation of duties

ISO 27001 Annex A 5.4: Management responsibilities

ISO 27001 Annex A 5.5: Contact with authorities

ISO 27001 Annex A 5.6: Contact with special interest groups

ISO 27001 Annex A 5.7: Threat intelligence

ISO 27001 Annex A 5.8: Information security in project management

ISO 27001 Annex A 5.9: Inventory of information and other associated assets

ISO 27001 Annex A 5.10: Acceptable use of information and other associated assets

ISO 27001 Annex A 5.11: Return of assets

ISO 27001 Annex A 5.12: Classification of information

ISO 27001 Annex A 5.13: Labelling of information

ISO 27001 Annex A 5.14: Information transfer

ISO 27001 Annex A 5.15: Access control

ISO 27001 Annex A 5.16: Identity management

ISO 27001 Annex A 5.17: Authentication information

ISO 27001 Annex A 5.18: Access rights

ISO 27001 Annex A 5.19: Information security in supplier relationships

ISO 27001 Annex A 5.20: Addressing information security within supplier agreements

ISO 27001 Annex A 5.21: Managing information security in the ICT supply chain

ISO 27001 Annex A 5.22: Monitoring, review and change management of supplier services

ISO 27001 Annex A 5.23: Information security for use of cloud services

ISO 27001 Annex A 5.24: Information security incident management planning and preparation

ISO 27001 Annex A 5.25: Assessment and decision on information security events

ISO 27001 Annex A 5.26: Response to information security incidents

ISO 27001 Annex A 5.27: Learning from information security incidents

ISO 27001 Annex A 5.28: Collection of evidence

ISO 27001 Annex A 5.29: Information security during disruption

ISO 27001 Annex A 5.30: ICT readiness for business continuity

ISO 27001 Annex A 5.31: Identification of legal, statutory, regulatory and contractual requirements

ISO 27001 Annex A 5.32: Intellectual property rights

ISO 27001 Annex A 5.33: Protection of records

ISO 27001 Annex A 5.34: Privacy and protection of PII

ISO 27001 Annex A 5.35: Independent review of information security

ISO 27001 Annex A 5.36: Compliance with policies and standards for information security

ISO 27001 Annex A 5.37: Documented operating procedures

ISO 27001 Technical Controls

ISO 27001 Annex A 8.1: User Endpoint Devices

ISO 27001 Annex A 8.2: Privileged Access Rights

ISO 27001 Annex A 8.3: Information Access Restriction

ISO 27001 Annex A 8.4: Access To Source Code

ISO 27001 Annex A 8.5: Secure Authentication

ISO 27001 Annex A 8.6: Capacity Management

ISO 27001 Annex A 8.7: Protection Against Malware

ISO 27001 Annex A 8.8: Management of Technical Vulnerabilities

ISO 27001 Annex A 8.9: Configuration Management 

ISO 27001 Annex A 8.10: Information Deletion

ISO 27001 Annex A 8.11: Data Masking

ISO 27001 Annex A 8.12: Data Leakage Prevention

ISO 27001 Annex A 8.13: Information Backup

ISO 27001 Annex A 8.14: Redundancy of Information Processing Facilities

ISO 27001 Annex A 8.15: Logging

ISO 27001 Annex A 8.16: Monitoring Activities

ISO 27001 Annex A 8.17: Clock Synchronisation

ISO 27001 Annex A 8.18: Use of Privileged Utility Programs

ISO 27001 Annex A 8.19: Installation of Software on Operational Systems

ISO 27001 Annex A 8.20: Network Security

ISO 27001 Annex A 8.21: Security of Network Services

ISO 27001 Annex A 8.22: Segregation of Networks

ISO 27001 Annex A 8.23: Web Filtering

ISO 27001 Annex A 8.24: Use of Cryptography

ISO 27001 Annex A 8.25: Secure Development Life Cycle

ISO 27001 Annex A 8.26: Application Security Requirements

ISO 27001 Annex A 8.27: Secure Systems Architecture and Engineering Principles

ISO 27001 Annex A 8.28: Secure Coding

ISO 27001 Annex A 8.29: Security Testing in Development and Acceptance

ISO 27001 Annex A 8.30: Outsourced Development

ISO 27001 Annex A 8.31: Separation of Development, Test and Production Environments

ISO 27001 Annex A 8.32: Change Management

ISO 27001 Annex A 8.33: Test Information

ISO 27001 Annex A 8.34: Protection of information systems during audit testing

ISO 27001 Toolkit Business Edition

Do It Yourself ISO 27001