What evidence do auditors commonly ask for on 4.4 Privacy information management system?

PIMS description or manual showing the processes and their interactions; Evidence the system is operated against this document rather than as an ISMS annex; Records of maintenance and improvement of the system.

What is the most common gap auditors find on 4.4?

A PIMS that exists only as an addendum to the ISMS manual with no processes of its own

ISO/IEC 27701:2025 · Context of the organization

`4.4` Privacy information management system

The organization shall set up, operate, keep up and keep improving a privacy information management system, covering the processes it requires and how they interact, as this document requires. The first edition had the organization extend an ISMS built on clauses 4 to 10 of the 2013 edition of ISO/IEC 27001; the second edition asks the PIMS to satisfy this document on its own, leaving the organization free to align or combine it with an ISMS or another management system if it chooses.

Source: ISO/IEC 27701:2025, 4.4. 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 27701:2025 in the compliance library.

artefacts

held by a system

at each review

hard

to go live

Document repository

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

Evidence the system is operated against this document rather than as an ISMS annex · Document repository
Records of maintenance and improvement of the system · Document repository

governing documentDocuments that govern the control

PIMS description or manual showing the processes and their interactions · Document repository

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

A PIMS that exists only as an addendum to the ISMS manual with no processes of its own
Processes documented but their interactions with incident, supplier and change processes unstated

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.3 Determining the scope of the privacy information management system · 5.1 Leadership and commitment