ISO 27001 mandatory documents: less paperwork than you fear

The standard explicitly requires a defined core: scope, policy, risk process and results, Statement of Applicability, objectives, audit and review records, and corrective action records. Beyond that core, each further document should earn its place through your risks.

By Alan Hutson, Certified ISO 27001 Lead Implementer, Certified ISO 27001 Lead Auditor, Certified Information Systems Security Professional (CISSP) · Reviewed November 2026

Which documents does the standard name?

DocumentWhy it exists
ISMS scope statementDefines what the system covers; the boundary every other decision references
Information security policyLeadership's direction, approved by top management and communicated
Risk methodology, assessment and treatment planHow risk is judged, what you found, what you decided to do about it
Statement of ApplicabilityYour justified position on all 93 Annex A controls; see my SoA guide
Information security objectivesWhat you are trying to achieve, measurably, and how it is going

Which records must you keep?

  • Evidence of competence: training, qualifications, experience for roles affecting security
  • Monitoring and measurement results against your objectives
  • Internal audit programme, plans and reports: see my internal audit guide
  • Management review minutes with inputs, decisions and actions: see my management review guide
  • Nonconformities and corrective actions, with evidence the actions worked
  • Operating records your controls generate: asset inventory, access reviews, supplier assessments, incident log, backup restore tests, change records

My ISO 27001 checklist places every item above in the order you will create it, alongside the clause requirements.

How large should your policy set be?

Beyond the main policy, write topic policies where a reader needs rules at the point of work: acceptable use, access control, suppliers, incidents, backup and recovery, remote working where it applies. Each should be short, owned, approved, versioned, and reviewed at planned intervals or after significant change.

The test an auditor applies is whether staff can find the current version and whether practice matches it. Matching practice sometimes means rewriting the policy to describe what you sensibly do.

How do you control documents without bureaucracy?

  • Every controlled document: title, owner, version, approval, review date.
  • One place of truth; uncontrolled copies removed or clearly marked.
  • Changes communicated to the people the document affects.
  • Review triggered by change and incident, not only by the calendar.

This is deliberately paraphrased guidance. For the authoritative wording, obtain the standard itself from BSI or ISO: any source reproducing its text verbatim should be treated with suspicion.

Frequently asked questions about ISO 27001 mandatory documents

Related ISO 27001 guides

What is ISO 27001?

What ISO/IEC 27001:2022 is, what an ISMS does, who needs certification and what the standard actually requires, in plain English.

Read the guide

A customer requires ISO 27001: what to do next

When a customer, tender or framework makes certification a condition, how to respond credibly now and build a realistic route to the certificate.

Read the guide

A practical guide to ISO 27001 implementation

How an ISO/IEC 27001:2022 implementation project actually runs, from scoping and gap analysis through to the independent certification audit.

Read the guide

ISO 27001 checklist: clauses, documents and controls

A working checklist covering clauses 4 to 10, the mandatory documents, the Statement of Applicability and Annex A, in the order you will tackle them.

Read the guide

Policy library grown faster than the business?

Arrange a readiness discussion. I can cut your documentation back to what the standard requires and your risks justify, and make the rest match practice.

Or email info@isosecurity.co.uk