Clause 4 – Context of the organization

Clause 4.3 Determining the scope of the ISMS

Mandatory requirement Documented information required

What it means in plain language

Draw a clear boundary around what your ISMS covers: which locations, departments, products, systems and information. Take the issues (4.1), requirements (4.2) and dependencies on third parties into account. The scope must be documented, and anything excluded must be justifiable.

Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.

Documented information

  • The ISMS scope must be available as documented information.

Why this requirement matters

Clause 4.3 is frequently weakened by a scope statement that is too narrow, too broad or detached from actual operating dependencies. Teams should define what the ISMS covers, what it excludes and why those exclusions are reasonable, using evidence from context, interested parties and supplier relationships. A clear scope also prevents later mismatch between the documented ISMS and what users, customers and auditors actually observe.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • The scope omits a material system, site or function that processes in-scope information, creating a boundary gap between documented scope and operational reality.
  • An exclusion is listed, but the justification does not explain dependency, ownership or why the excluded activity cannot affect information security outcomes.
  • The scope document does not align with the Statement of Applicability, contract commitments or the services actually delivered to customers.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define the boundary in operational terms: legal entity, locations, products, services, platforms, support functions, outsourced activities and cloud regions. State where information is created, processed, stored and administered, and identify interfaces that cross the boundary so responsibility is not ambiguous.
  • For each exclusion, write the reason and the residual dependency. If payroll, a lab, or a support process sits outside the ISMS, explain whether it is controlled by another management system, a supplier agreement or an internal service arrangement, and why that does not undermine the ISMS boundary.
  • Validate scope with leadership, operations, IT and procurement before approval. Compare it to actual tooling, network diagrams, supplier lists and customer commitments, then update it when a new country, platform, office or acquired business changes the operating footprint.
  • Keep the scope document consistent with the Statement of Applicability, risk treatment decisions and public claims. If the organization shares scope externally, use the same wording in customer responses and on the website to avoid conflicting descriptions of what the ISMS covers.

What an auditor will ask to see

  • Signed scope document with clearly stated inclusions, exclusions and justifications.
  • Supporting network, system or service diagrams showing interfaces and third-party dependencies.
  • Cross-check to the Statement of Applicability and the current certificate scope wording.

Baseline documents in the kit

These free kit documents help you document or evidence clause 4.3. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with 4.1 — Understanding the organization and its context and 4.2 — Understanding the needs and expectations of interested parties. Keep the ownership and evidence consistent across these activities.

Plan your ISO/IEC 27001 implementation timeline for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.