ISMS Document Set: Policies, Registers & Trackers You Actually Need

Template packs sell sixty documents. The standard asks for about fifteen, plus whatever your own controls need. Here is the line between documentation that passes an audit and paperwork nobody reads.

60+documents in a typical template pack
~15items clauses 4–10 require
93Annex A controls — each may add a record
1document that ties it together: the SoA

ISO/IEC 27001:2022 never says “write sixty documents”. It says documented information — and it says it in two ways. Some clauses require it outright (“shall be available as documented information”). Everything else is documented “to the extent necessary” for you to have confidence that processes run as planned. Auditors test the first list strictly and the second against your own risk assessment. A tidy ISMS is the mandatory set, plus the records your chosen controls produce, and nothing else.

1 · What Clauses 4–10 Require

ClauseDocumented informationWhat an auditor checks
4.3ISMS scopeBoundaries, interfaces and exclusions are explicit
5.2Information security policyApproved by top management, communicated, includes objectives framework
6.1.2Risk assessment processCriteria for acceptance and for performing assessments; repeatable results
6.1.3Risk treatment processHow controls are chosen and compared with Annex A
6.1.3 dStatement of Applicability (SoA)Every Annex A control: included or excluded, why, and implementation status
6.1.3 eRisk treatment planOwners, actions and approval of residual risk by risk owners
6.2Information security objectivesMeasurable, with plans, owners and dates
7.2Evidence of competenceTraining, qualifications or experience records for ISMS roles
8.1Operational planning and controlEnough evidence that processes ran as planned
8.2 / 8.3Risk assessment and treatment resultsCurrent risk register; dated reassessments after significant change
9.1Monitoring and measurement resultsWhat is measured, how, by whom, and the results
9.2Internal audit programme and resultsPlan covering the whole ISMS; independent auditors; findings
9.3Management review resultsAll required inputs considered; decisions and actions recorded
10.2Nonconformities and corrective actionsRoot cause, action taken, effectiveness checked

▸ The Statement of Applicability is the document everything else hangs from. It decides which Annex A controls apply — and therefore which of the documents in the next section you need at all.

2 · Documents Annex A Controls Call For

Once a control is in your SoA, these are the documents and records it is normally evidenced by. Several controls state that a procedure or list should be documented; for the rest, documentation is your choice, judged by whether it makes the control work.

ControlTypical documentForm
5.1Topic-specific security policiesPolicy
5.2–5.3Roles and responsibilities; segregation-of-duties matrixRegister
5.9Inventory of information and other associated assetsRegister
5.10Acceptable use of information and assetsPolicy
5.12–5.13Classification scheme and labelling rulesPolicy
5.14Information transfer rules and agreementsPolicy
5.15–5.18Access control policy; access rights matrix; review recordsPolicy Log
5.19–5.22Supplier security requirements; supplier register and assessmentsRegister
5.24–5.28Incident management plan and procedure; incident log; evidence handlingPlan Log
5.29–5.30Security during disruption; ICT continuity / disaster recovery plan and test recordsPlan
5.31–5.34Legal, regulatory and contractual requirements register; privacy / PII protectionRegister
5.37Documented operating proceduresProcedure
6.1–6.6Screening, terms of employment, awareness records, disciplinary process, NDAsLog
8.8Vulnerability management procedure; patch trackerLog
8.9Configuration baselines (including cloud)Standard
8.10–8.12Retention and deletion schedule; data masking and DLP rulesStandard
8.13Backup policy and restore-test recordsLog
8.15–8.16Logging standard; monitoring and log-source listStandard
8.24Cryptography and key management rulesStandard
8.25–8.29Secure development lifecycle; secure coding standard; security test recordsStandard Log
8.32Change management procedure and change logProcedure Log

Control numbers follow ISO/IEC 27001:2022 Annex A. For what changed from the 2013 edition, see ISO 27001:2013 → 2022, Quantified.

3 · What the Template Packs Add

Commercial cybersecurity template packs group 60-odd spreadsheets and documents by domain. Measured against the two lists above, they fall into three bins:

BinExamples from typical packsVerdict
Evidence you needAccess rights & permissions matrix; data classification register; asset inventory; patch & update tracker; data breach notification log; encryption key management sheet; backup & recovery testing tracker; DR plan and comms plan; audit findings remediation tracker; compliance requirements tracker; third-party risk assessmentKeep — each is a record a mandatory clause or an applicable control will be tested against
Useful operational toolsIncident triage checklist; incident response playbooks; log-source onboarding checklist; secure coding checklist; application threat model; cloud security configuration baseline; control framework mapping; KRI tracker; root-cause analysis templateAdopt where the team will actually use them; they make controls work, but are not audit requirements
Noise or out of scopeSeparate trackers for every log type; network traffic “dashboards” in a spreadsheet; workplace-violence and structural-damage reports; duplicate incident guide, policy and processSkip — belongs to other functions (HR, facilities) or duplicates a tool you already run

▸ The test for any document: which clause or SoA control does it evidence, and who updates it? If neither answer exists, it will be out of date by the next audit — and an outdated document is itself a finding.

4 · A 15-Document Starter Kit

For a small organisation starting an ISMS, these fifteen cover the mandatory clauses and the controls almost every SoA includes. Add the rest as your risk assessment demands.

  1. ISMS scope (4.3)
  2. Information security policy, with acceptable use and access control as sections (5.2, 5.10, 5.15)
  3. Risk methodology — assessment and treatment process in one document (6.1.2, 6.1.3)
  4. Risk register and treatment plan (6.1.3 e, 8.2, 8.3)
  5. Statement of Applicability (6.1.3 d)
  6. Security objectives and metrics (6.2, 9.1)
  7. Asset inventory and classification scheme (5.9, 5.12)
  8. Supplier register and assessments (5.19–5.22)
  9. Legal and contractual requirements register (5.31)
  10. Incident response plan and incident log (5.24–5.28)
  11. Business continuity / DR plan and test record (5.29, 5.30, 8.13)
  12. Operations standard — change, patching, backup, logging (5.37, 8.8, 8.13, 8.15, 8.32)
  13. Training and competence records (7.2, 6.3)
  14. Internal audit programme and reports (9.2)
  15. Management review minutes and corrective-action log (9.3, 10.2)

Bottom line

  • The standard asks for about fifteen items outright; the rest follows from your SoA.
  • The SoA decides the paperwork — an excluded control needs a justification, not a document.
  • Records beat documents — auditors sample logs, reviews and test results more than policies.
  • Every document needs a clause and an owner, or it will be stale by the next audit.
  • Merge where you can — one policy with sections is easier to keep current than twelve.

Sources & method. Clause references from ISO/IEC 27001:2022 (including Amendment 1:2024, which added climate-change considerations to clause 4); Annex A control numbers from the 2022 edition. The template-pack review is the author’s analysis of commonly marketed cybersecurity template collections; no pack is endorsed. The starter kit is a recommendation, not a certification guarantee. Original analysis; no third-party graphics or text reproduced.

← Back to Cyber security