Documented scope of the ISMS per ISO/IEC 27001:2022 Clause 4.3, including boundaries, interfaces and dependencies.
A compliant ISMS Scope Statement for ISO 27001 must include the following6 sections. Each section addresses a specific control requirement that auditors will review.
Why the scope is documented (Clause 4.3).
Internal and external issues (Clause 4.1) and interested parties with their requirements (Clause 4.2), as a table.
Products/services, organizational units, locations, processes, information systems and people in scope.
Anything out of scope and why; the exclusion must not affect the ability to provide secure services.
Cloud providers, SaaS suppliers, outsourced functions and customer interfaces, as a table.
Approving role, approval date, review cycle and signature line.
This template shows the required structure. PoliWriter generates a fully customized ISMS Scope Statement that references your actual cloud providers, identity systems, tools, and team practices — ready for auditor review.
Top-level information security management system policy.
Risk management methodology aligned with ISO 27005.
Mandatory ISMS document per ISO/IEC 27001:2022 Clause 6.1.3(d) — exhaustive table of all 93 Annex A controls with applicability, justification, implementation status, and exclusion rationale.
Defines access control requirements aligned with ISO 27001 Annex A controls A.5.15 and A.8.2.
Information asset inventory and classification aligned with ISO 27001 controls A.5.9 and A.5.10.
Information security incident management aligned with ISO 27001 controls A.5.24 and A.5.25.
Information security aspects of business continuity aligned with ISO 27001 controls A.5.29 and A.5.30.
Managing information security risks in supplier relationships per ISO 27001 controls A.5.19 and A.5.20.