Clause 7 – Support

Clause 7.5 Documented information

Mandatory requirement Documented information required

What it means in plain language

Control your ISMS documents and records: each needs an ID, title, owner, version and approval; it must be available to the people who need it, protected from unauthorised change and loss, and retained or disposed of properly. External documents (e.g. contracts, laws) must also be controlled.

Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.

Documented information

  • The documented information required by the standard and that you decide is needed.

Why this requirement matters

An outdated procedure can direct staff to use an unsafe method even when a correct version exists elsewhere. Document control protects both the usefulness of instructions and the reliability of records used to demonstrate what happened. The challenge is to make current information easy to use while preserving approvals, preventing unauthorised changes and applying retention decisions consistently across collaborative tools and exported copies.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Different teams use conflicting versions of the same procedure because local downloads remain available after the approved source has changed.
  • Operational records can be edited without a meaningful history, so reviewers cannot distinguish the original result from a later correction.
  • External requirements such as contractual security schedules are referenced in procedures but have no assigned owner responsible for checking their currency.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define a controlled repository with permissions suited to documents and records. Establish identifiers, ownership, review and approval rules, then make the current version discoverable from the place where staff perform the associated task rather than a separate compliance archive.
  • Use version history and approval states to separate drafts from authorised instructions. Explain how emergency updates are approved and later reviewed. When a procedure changes, identify affected training, forms and linked documents so inconsistencies are addressed together.
  • Set retention and disposal rules by record type, considering applicable legal, contractual and business needs. Preserve records subject to a hold, document corrections without obscuring original evidence, and test recovery of important information from the chosen storage arrangement.
  • Assign ownership for externally sourced information needed by the ISMS. Record where authoritative versions are obtained and what triggers a review. Periodically sample links, access permissions and exported copies to check that availability and protection both remain effective.

What an auditor will ask to see

  • Repository permissions, approval history and document registers showing that current instructions have owners and obsolete versions are clearly distinguished or withdrawn.
  • A sample operational record with a traceable correction history, applicable retention rule and evidence that unauthorised editing or deletion is restricted.
  • Records of document reviews, external-source checks and recovery tests demonstrating that required information remains available and reliable throughout its intended life.

Baseline documents in the kit

These free kit documents help you document or evidence clause 7.5. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.33 — Protection of records and A.5.37 — Documented operating procedures. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.