How to implement ISO 27001 Clause 4.3 – Determining The Scope Of The Information Security Management System (ISMS)

Home / ISO 27001 Tutorials / How to implement ISO 27001 Clause 4.3 – Determining The Scope Of The Information Security Management System (ISMS)

Last updated Dec 5, 2025

Author: Stuart Barker | ISO 27001 Lead Auditor

The ISO 27001 Clause 4.3 implementation checklist is designed to help an ISO 27001 Lead Implementer to implement ISO 27001 Clause 4.3 Determining The Scope Of The Information Security Management System (ISMS).

The 10 point ISO 27001 implementation plan sets out how to implement, the challenges faced and the solutions to adopt.

ISO 27001 Clause 4.3 Implementation Checklist

Time needed: 1 hour and 30 minutes

How to implement ISO 27001 Clause 4.3

  1. Define Organisational Boundaries

    Challenge
    Clearly identifying where the organisation’s boundaries lie, especially in complex or multi-national organisations.
    Solution
    Utilise organisational charts, legal documents, and stakeholder interviews to define the organisational structure.
    Consider third-party relationships and their impact on information security.

  2. Identify Core Products and Services

    Challenge
    Accurately determining the core products and services offered, especially in diverse organisations with multiple business units.
    Solution
    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.

  3. Identify Supporting Functions

    Challenge
    Determining which departments and functions are critical to the delivery of core products and services.
    Solution
    Analyse organisational structure and identify departments that directly or indirectly support core business functions.
    Consider departments like IT, HR, finance, legal, and facilities.

  4. Identify Information Assets

    Challenge
    Identifying all critical information assets, including data, systems, and intellectual property.
    Solution
    Conduct a comprehensive information asset inventory, including data classification exercises.
    Utilise data flow diagrams and business process mapping to identify information flows.

  5. Identify Information Security Risks

    Challenge
    Accurately assessing the potential threats and vulnerabilities associated with in-scope products and services.
    Solution
    Conduct a thorough risk assessment, considering internal and external threats.
    Prioritise risks based on their likelihood and potential impact.

  6. Determine Scope Exclusions

    Challenge
    Identifying activities, departments, or systems that will be explicitly excluded from the scope of the ISMS.
    Solution
    Clearly document the rationale for any exclusions.
    Ensure that excluded areas do not pose significant risks to the organisation’s information security.

  7. Define Scope Statement

    Challenge
    Creating a concise and unambiguous ISO 27001 scope statement that is easily understood by all interested parties.
    Solution
    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.

  8. Communicate Scope to Stakeholders

    Challenge
    Ensuring that all relevant stakeholders understand the scope of the ISMS and their roles and responsibilities within it.
    Solution
    Conduct training sessions and awareness campaigns.
    Distribute the scope statement to all employees.
    Include the scope statement in relevant policies and procedures.

  9. Obtain Management Approval

    Challenge
    Securing management approval for the defined scope of the ISMS.
    Solution
    Present the proposed scope to management and address any concerns or questions.
    Obtain formal approval from top management.

  10. Document and Maintain

    Challenge
    Maintaining accurate and up-to-date documentation of the scope of the ISMS.
    Solution
    Store the scope statement in a central location.
    Regularly review and update the scope statement as needed.
    Ensure that all changes to the scope are properly documented.
    By following these steps and addressing the associated challenges, organisations can establish a well-defined scope for their ISMS, which is essential for successful ISO 27001 implementation and ongoing compliance.

Further Reading

ISO 27001 Clause 4.3 Determining The Scope Of The Information Security Management System (ISMS)

ISO 27001 Clause 4.3 Audit Checklist

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