EvidenceSheet

7.5.3 Documented information: control

Documented information that the standard and the ISMS call for must be controlled so that people can get it, in a usable state, at the place and time they need it, and so that it is suitably protected, for example against loss of confidentiality, misuse or loss of integrity. As applicable, the organization addresses distribution, access, retrieval and use; storage and preservation including keeping it legible; control of changes such as version control; and retention and disposition. External documented information the organization needs for planning and operating the ISMS is identified as appropriate and controlled. A note explains that access can mean permission only to view, or also the right to edit.

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

4
artefacts
1
held by a system
0
at each review
moderate
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

  • Version histories and change records for ISMS documents · Document repository

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • A document control procedure covering distribution, access, storage, version control, retention and disposal · Policy repository / GRC workspace
  • Access permissions on the document repository showing view and edit rights · Policy repository / GRC workspace
  • A register of external documents such as standards and regulations used by the ISMS · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

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

7.5.2 Documented information: creating and updating · 8.1 Operational planning and control