What evidence do auditors commonly ask for on 4.2 Understanding the needs and expectations of interested parties?

A register of relevant interested parties such as customers, regulators, staff, suppliers and shareholders, with their information security requirements; A record of which requirements the ISMS will address and which it will not, with reasons; Links from legal, regulatory and contractual obligations in the register to the controls or processes that meet them; Evidence the register is reviewed, for example as a management review input.

What is the most common gap auditors find on 4.2?

Parties are listed without stating what they actually require

ISO/IEC 27001:2022 · Clause 4

`4.2` Understanding the needs and expectations of interested parties

The organization has to work out which interested parties matter to the ISMS, what those parties require, and which of their requirements the ISMS will deal with. The note says such requirements may include legal, regulatory and contractual obligations. Amendment 1:2024 adds a note that relevant interested parties can have requirements related to climate change (the amendment's wording is not stated here; see the official text).

Source: ISO/IEC 27001:2022, 4.2. 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

A record of which requirements the ISMS will address and which it will not, with reasons · Document repository

governing documentDocuments that govern the control

A register of relevant interested parties such as customers, regulators, staff, suppliers and shareholders, with their information security requirements · Policy repository / GRC workspace
Links from legal, regulatory and contractual obligations in the register to the controls or processes that meet them · Policy repository / GRC workspace
Evidence the register is reviewed, for example as a management review input · 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

Parties are listed without stating what they actually require
No decision is recorded on which requirements the ISMS takes on
Contractual security obligations from customer contracts are missing
Climate-related requirements of interested parties are not considered after the 2024 amendment

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.1 Understanding the organization and its context · 4.3 Determining the scope of the information security management system