What evidence do auditors commonly ask for on 4.3 Determining the scope of the information security management system?

The documented ISMS scope statement naming organizational units, locations, processes, services and technology covered; A description of interfaces and dependencies on activities performed by other organizations such as outsourced providers and cloud services; Rationale showing how the 4.1 issues and 4.2 requirements shaped the boundaries; Consistency between the scope, the Statement of Applicability and the certificate scope.

What is the most common gap auditors find on 4.3?

Scope excludes areas that clearly process in-scope information without justification

ISO/IEC 27001:2022 · Clause 4

`4.3` Determining the scope of the information security management system

To set the ISMS scope the organization decides its boundaries and where it applies. In doing so it takes into account the issues identified under 4.1, the requirements identified under 4.2, and the interfaces and dependencies between its own activities and those carried out by other organizations. The resulting scope has to exist as documented information.

Source: ISO/IEC 27001:2022, 4.3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.

Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.

artefacts

held by a system

at each review

hard

to go live

Policy repository / GRC workspace

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

The documented ISMS scope statement naming organizational units, locations, processes, services and technology covered · Policy repository / GRC workspace
A description of interfaces and dependencies on activities performed by other organizations such as outsourced providers and cloud services · Vendor register / contract repository
Rationale showing how the 4.1 issues and 4.2 requirements shaped the boundaries · Policy repository / GRC workspace
Consistency between the scope, the Statement of Applicability and the certificate scope · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Scope excludes areas that clearly process in-scope information without justification
Dependencies on outsourced or cloud providers are not described
The scope document differs from the certificate wording
Scope was never revisited after reorganizations or acquisitions

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

4.2 Understanding the needs and expectations of interested parties · 4.4 Information security management system