ASD ISM 0888 Annual review of cyber security documentation
What it says
Cyber security documentation is reviewed at least annually and includes a 'current as at \[date\]' or equivalent statement.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishReview all cyber security documentation at least annually, and show a 'current as at [date]' or equivalent statement in each document.
Cyber security documentation must meet two requirements:
- Review: it is reviewed at least annually, so no more than 12 months pass between reviews of a document.
- Currency statement: it includes a 'current as at [date]' statement or an equivalent, so a reader can see how recent it is.
This covers organisational-level documents such as the cyber security strategy (ISM-0039) and system-specific ones such as a system security plan (ISM-0041). A review that changes nothing still counts, provided it really happened and the date is updated.
Free. Save your status, tasks and notes.
Why it matters
Threats change, so a document left unreviewed can describe measures that no longer work and steer effort to the wrong places. A review at least annually brings it back into line, and the dated statement tells readers whether they can rely on it.
How to implement
List every cyber security document and its last review date.
Cover organisational-level and system-specific documents. Search the document repository and each system's records, not only the existing index, so unlisted ones show up. Include documents a provider writes for your systems, and ask the provider to review them.
Add the statement to each document and its template.
Put 'current as at [date]' or an equivalent such as 'last reviewed on [date]' where readers will see it, such as the cover or document control table. Set it by hand, because an automatic date field changes without any review.
Set each next review no more than 12 months after the last.
Track a due date against each document, with a named reviewer. Count from the last review rather than by calendar year, because a review in January one year and in December the next leaves a 23-month gap.
Review each document against what has changed.
Compare it with current threats, the latest ISM release, system changes and recent incidents, then update what has drifted. Record what was checked and the outcome, then update the date. Send changed versions for approval (ISM-0047) and tell stakeholders (ISM-1602).
Keep it running
Review sooner when threats, systems or the organisation change, and count the next due date from that review.
Evidence and audit
- Check 1 of 4What an auditor asks for
Ask for
The document list, compared with a search of the document repository and the documents required for a sample of systems, such as each system security plan (ISM-0041).
Look at
Whether any document found is missing from the list, and the date each was last reviewed.
Good evidence
No document found is missing from the list, and each has been reviewed within the last 12 months.
- Check 2 of 4What an auditor asks for
Ask for
Review records for the last two reviews of a sample of documents.
Look at
The gap between reviews, and what each review checked.
Good evidence
No gap between reviews of a document is longer than 12 months, and each record says what was checked and the outcome, even where nothing changed.
- Check 3 of 4What an auditor asks for
Ask for
The published version of sampled documents, with their file history.
Look at
Whether the statement is in the document itself, and whether its date agrees with the review record.
Good evidence
Each sampled document shows a 'current as at [date]' or equivalent statement, and its date matches the last recorded review, not an automatic field.
- Check 4 of 4What an auditor asks for
Ask for
The contents of a sampled document, compared with recent system changes, incidents and threat reporting.
Look at
Whether the document still describes the current system, contacts and threats.
Good evidence
The document reflects changes made before its 'current as at' date, so the date shows a real review. A new date on stale content fails.
Mappings
Closest match in ISO/IEC 27001: A.5.1, Policies for information security, which this control partially meets.
ISO/IEC 27001: 2 mappings
This control partially meets A.5.1.
ISM-0888 requires cyber security documentation to be reviewed at least annually and to include a clear 'current as at [date]' statement. ISO/IEC 27001:2022 Annex A 5.1 requires information security policies to be reviewed at planned intervals and when significant changes occur, which covers the review expectation for policy documents that would be part of cyber security documentation. Annex A 5.1 is broader (applies to the policy framework and change-driven reviews), while ISM-0888 is more prescriptive about annual cadence and explicit currency dating.
This control partially overlaps A.5.37.
Annex A 5.37 requires operating procedures for information processing facilities to be documented and made available to personnel who need them. ISM-0888 strengthens this by requiring cyber security documentation to be reviewed at least annually and dated, helping ensure the documented procedures referenced by Annex A 5.37 remain current and reliable for users. ISM-0888 does not itself require that operating procedures exist or are made available; it focuses on review cadence and currency markings.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




