Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

Control 7.5.2Creating and updating

When creating and updating documented information, ensure appropriate identification and description — title, date, author, reference number — appropriate format and media, and appropriate review and approval for suitability and adequacy.

Housekeeping, and it earns its place. Without identification you cannot tell which version somebody followed; without review and approval you cannot tell whether anybody with authority agreed to it.

The requirement that is genuinely substantive is approval for suitability and adequacy — not merely that someone signed, but that someone competent judged the document fit for its purpose. A procedure approved by the person who wrote it, with no independent judgement of whether it is adequate, meets the form of the clause and not its substance.

In practice this clause is where an ISMS’s document set either becomes navigable or becomes an archive in which three versions of the same policy circulate and the current one cannot be identified.

How to put this in place

Documents need to be identifiable, approved and in a usable form from the start. Drafts in use and anonymous files undermine trust in the whole set.

  1. Set a standard for identification: title, ID, version, date, owner and classification.
  2. Use templates and a review and approval route.
  3. Define who approves each type of document.
  4. Record approvals and dates.
  5. Set review dates and chase them.

Evidence an auditor usually looks for: documents carrying identification, approval records and review dates, created from consistent templates.

What is in the packs for this

From ISO 27001 Implementation & Certification Readiness. Each one helps with this requirement.