Markdown Editor

ISMS Documented Information Register Template (ISO/IEC 27001 7.5)

Master list of ISMS documents and records: mandatory items flagged, owner, version, classification, location, retention, external documents, disposal

ISMS और ISO/IEC 27001मानकISO/IEC 27001:2022 + Amd 1:2024 clause 7.5, A.5.33 (cited only); ISO/IEC 27002:2022documentedinformationregister
एडिटर में खोलें.md डाउनलोड करें

उपयोग कैसे करें: Use it from the first day of the ISMS project and keep it current for Stage 1. Fill the mandatory items section first, then add the documents your organisation decided it needs. The main pitfall is listing documents but not records, with no retention or location.

प्रीव्यू

Documented Information Register: [Organization name] ISMS

Master list of every document and record in the information security management system (ISMS): identifier, title, owner, version, classification, location, retention and review date. It supports ISO/IEC 27001:2022 + Amd 1:2024 clause 7.5 (documented information: creating, updating and controlling it, including documents of external origin) and Annex A control A.5.33 (protection of records). Items the standard explicitly requires are flagged. Replace every [bracketed] value and every row marked Example.

Document control

FieldValue
Document IDDOC-ISMS-028
Version[1.0]
Status[Draft / In review / Approved / Superseded]
Owner[@isms-manager]
Approvers/reviewers[@ciso], [@records-manager], [@internal-audit]
Last updatedYYYY-MM-DD
Classification[Internal]
Standard and editionISO/IEC 27001:2022 + Amd 1:2024 (clause 7.5; Annex A A.5.33)
Next scheduled reviewYYYY-MM-DD
Document system[Tool or repository name and path]
Numbering schemeDOC-ISMS-NNN for documents, REC-ISMS-NNN for record series

Approvals

RoleNameDecisionDate
ISMS manager[@isms-manager][Prepared]YYYY-MM-DD
Top management[@coo][Approved]YYYY-MM-DD

Revision history

VersionDateAuthorChange
1.0 (Example)YYYY-MM-DD[@isms-manager]First issue before Stage 1
[x.y]YYYY-MM-DD[@author][Change summary]

Contents

1. Purpose and rules

This register is the single list of ISMS documented information. The rules below apply to every entry:

  1. Identification: each item has a unique ID, title, owner and version (clause 7.5.2).
  2. Review and approval: documents are approved before issue and reviewed at the interval in the register.
  3. Availability and protection: the current version is available to the people who need it, and nobody can lose it, alter it without trace or read it without a reason (clause 7.5.3).
  4. Change control: superseded versions are withdrawn from use and kept as records for the retention period.
  5. Records: records are not edited after completion; corrections are new, dated entries (A.5.33).
  6. External origin: standards, laws, contracts and supplier documents used by the ISMS are listed in section 5 and controlled.

2. Register fields

FieldMeaning
IDDOC-ISMS-NNN (document) or REC-ISMS-NNN (record series)
TitleShort title
TypePolicy, procedure, plan, register, record
MandatoryM if explicitly required by ISO/IEC 27001:2022, otherwise blank
Clause or controlRequirement it supports
OwnerRole accountable for content
VersionCurrent approved version
ClassificationPublic, Internal, Confidential, Restricted (per DOC-ISMS-042)
LocationSystem and path
RetentionHow long superseded versions or records are kept
ReviewInterval and next review date

3. Mandatory documented information

IDItemClauseMOwnerVersionLocationReview
DOC-ISMS-002ISMS scope4.3MISMS manager[v][path]Annual
DOC-ISMS-001Information security policy5.2MCISO[v][path]Annual
DOC-ISMS-010Risk assessment process (methodology)6.1.2MISMS manager[v][path]Annual
DOC-ISMS-010Risk treatment process (same methodology)6.1.3MISMS manager[v][path]Annual
DOC-ISMS-011Statement of Applicability6.1.3 dMISMS manager[v][path]Annual and on change
DOC-ISMS-013Risk treatment plan (see note)6.1.3 e, 8.3ISMS manager[v][path]Quarterly
DOC-ISMS-024Information security objectives6.2MISMS manager[v][path]Quarterly
REC-ISMS-001Evidence of competence7.2MHRRecords[path]Continuous
DOC-ISMS-028Documents determined necessary (this register)7.5.1 bMISMS manager[v][path]Annual
REC-ISMS-002Operational planning and control information, to the extent necessary8.1MControl ownersRecords[path]Continuous
DOC-ISMS-016Risk assessment results8.2MISMS manager[v][path]Each cycle
REC-ISMS-003Risk treatment results8.3MRisk ownersRecords[path]Each cycle
REC-ISMS-004Monitoring and measurement results9.1MISMS managerRecords[path]Quarterly
DOC-ISMS-082Audit programme9.2.2MInternal audit lead[v][path]Annual
REC-ISMS-005Audit results (reports DOC-ISMS-084)9.2.2MInternal audit leadRecords[path]Each audit
REC-ISMS-006Management review results (minutes DOC-ISMS-085)9.3.3MISMS managerRecords[path]Each review
REC-ISMS-007Nonconformities, actions taken and results of corrective actions (DOC-ISMS-087)10.2MISMS managerRecords[path]Continuous

Note on the risk treatment plan: clause 6.1.3 expects you to have a plan that risk owners have signed off, and to keep records of how you treat risk (6.1.3) and what came of it (8.3). The plan is not itself named as documented information, so it carries no M flag, but nearly every auditor asks to see it; keep it controlled.

4. Master register

IDTitleTypeClause or controlOwnerVersionClassificationLocationRetention of superseded versionsNext review
DOC-ISMS-003 (Example)Context and interested partiesRegister4.1, 4.2ISMS manager1.2InternalDocument system / ISMS / 013 years2027-09-30
DOC-ISMS-006 (Example)Roles, responsibilities and RACIRegister5.3, A.5.2CISO1.0InternalDocument system / ISMS / 013 years2027-09-30
DOC-ISMS-020 (Example)Incident response planPlanA.5.24 to A.5.28Security lead3.0ConfidentialDocument system / Security3 years2027-03-31
DOC-ISMS-025 (Example)ISMS change planPlan and register6.3ISMS manager1.1InternalDocument system / ISMS / 023 years2027-12-31
DOC-ISMS-026 (Example)Competence and training matrixRegister7.2, 7.3, A.6.3ISMS manager and HR1.0ConfidentialHR system / ISMS3 years2027-12-31
DOC-ISMS-027 (Example)Communication planPlan7.4ISMS manager1.0InternalDocument system / ISMS / 023 years2027-12-31
DOC-ISMS-041 (Example)Access control policyPolicyA.5.15 to A.5.18Head of IT2.0InternalDocument system / Policies3 years2027-06-30
DOC-ISMS-061 (Example)Backup policyPolicyA.8.13Head of infrastructure1.1InternalDocument system / Policies3 years2027-06-30
[DOC-ISMS-NNN][title][type][clause or control][owner][v][class][location][period]YYYY-MM-DD

5. Documents of external origin

IDDocumentEdition or versionSourceOwnerAccessCheck for updates
EXT-001 (Example)ISO/IEC 27001:2022 + Amd 1:20242022, Amd 1 2024-02-23Purchased licenceISMS managerISMS team only, per licence termsAnnual
EXT-002 (Example)ISO/IEC 27002:20222022Purchased licenceISMS managerISMS team onlyAnnual
EXT-003 (Example)Cloud provider shared responsibility documentationVersion dated YYYY-MM-DDProvider websiteHead of infrastructureInternalQuarterly
EXT-004 (Example)Customer master agreement security scheduleSigned versionContract systemLegal counselRestrictedOn renewal
EXT-005 (Example)GDPR consolidated textOfficial journal versionEU official sitePrivacy leadPublicAnnual (via DOC-ISMS-014)

6. Retention and disposal

Record seriesRetention (Example)TriggerDisposal methodApprover
Superseded policies and procedures3 yearsDate supersededDelete from document system, keep register entryISMS manager
Audit reports, management review minutes, corrective actions6 years (two certification cycles)Date of closureSecure deletionISMS manager
Risk register snapshots3 yearsDate of next snapshotSecure deletionISMS manager
Competence and training evidenceEmployment plus period in HR policyEnd of employmentPer HR retention policyHR lead
Incident recordsPer legal register, at least [5] yearsIncident closureSecure deletion, legal hold check firstLegal counsel
Logs used as evidencePer security logging standardLog dateAutomated expirySecurity lead

Before disposal, check for a legal hold, an open audit finding or an ongoing incident. Record each disposal batch (series, date range, method, approver) so disposal is itself evidenced. For detailed schedules use compliance/iso-15489-records-schedule and data/data-retention-deletion-standard.

7. Size tiers

AspectSmall: Quillmere Analytics Ltd (46 staff)Medium: Quillmere Health Systems (320 staff)Large: Quillmere Group (2,400 staff, 6 sites)
Typical size (Example)30 to 45 entries70 to 120 entries150 or more, with site-level documents
ToolShared drive or wiki with version history, this table as the indexDocument management system with approval workflowIntegrated management system platform shared with ISO 9001 and ISO 22301
OwnerPart-time ISMS manager (0.5 FTE)ISMS manager with a document controllerGroup document control function, site coordinators
External documentsStandards, cloud provider terms, key customer contractsPlus health sector rules and hospital contract schedulesPlus local laws in 4 countries and OT supplier documents

8. Records and evidence

RecordProvesOwnerLocationRetention (Example)
This register with version historyDocumented information is identified and controlled (7.5)ISMS managerDocument systemCurrent plus [3] years of history
Approval records per documentReview and approval before issue (7.5.2)Document ownersDocument system workflowLife of document plus [3] years
Disposal logRetention and disposition applied (7.5.3)ISMS manager[path][6] years
Access permission reviews of the document systemProtection of documented information (7.5.3, A.5.33)Head of ITAccess review records[3] years

Map these records to clause 7.5 and control A.5.33 in the control evidence matrix (isms/control-evidence-matrix, DOC-ISMS-033).

9. References

ReferenceEditionUse
ISO/IEC 27001:2022 + Amd 1:2024Current; Amd 1 published 2024-02-23Clause 7.5 and the clauses listed in section 3; Annex A A.5.33 (cited only)
ISO/IEC 27002:2022CurrentGuidance for A.5.33 and A.5.37
ISO 15489-1:2016Cite without link; check the current editionRecords management concepts

Related templates: Controlled document (compliance/controlled-document), Records retention schedule (compliance/iso-15489-records-schedule), Data retention and deletion standard (data/data-retention-deletion-standard), ISMS manual (isms/isms-manual, DOC-ISMS-008), Policy framework (isms/isms-policy-framework, DOC-ISMS-005), Control evidence matrix (isms/control-evidence-matrix, DOC-ISMS-033), Legal register (compliance/legal-register, DOC-ISMS-014).

Standard and licence note

Structure aligned with ISO/IEC 27001:2022 + Amd 1:2024 (clause 7.5, the documented information requirements of clauses 4.3 to 10.2, and Annex A control A.5.33). The list of mandatory items is written in original words; no ISO/IEC text is reproduced, and you need the official standard to confirm each requirement. Retention periods are examples, not legal requirements. Check the current editions before use. Quillmere organisations and all figures are fictional examples. Template licence: MIT.

संबंधित टेम्पलेट