Records List and Retention Periods: How to Manage ISMS Records

The difference between documents and records in an ISMS, records list fields, the legal, contractual and operational bases for retention periods, disposal records and transition steps.
Technical summary
Technology
ISO/IEC 27001:2022 Clause 7.5.3, Annex A 5.31, 5.33, 8.10, KVKK, NIST SP 800-88
Topic
Listing, protecting, retaining and disposing of ISMS records
Level
Intermediate
Prerequisites
  • A document control setup in place
  • Regulatory support from the legal or compliance unit
In this article8 sections

When the auditor asks “do you apply this control?”, they ask for the record, not the procedure. The procedure says what will be done; the record proves it was done. That’s what shows an ISMS works. If where records are kept, how long they’re retained and how they’re disposed of when they expire aren’t defined, two problems appear at once: evidence can’t be found in the audit, and personal data kept longer than necessary becomes a separate compliance risk. Below we explain the fields of the records list, how to set retention periods and how to keep a disposal record.

The difference between documents and records

ISO/IEC 27001:2022 groups both under “documented information”. But they’re managed differently.

Feature Document Record
Purpose Defines what will be done Shows what was done
Change Revised and versioned Not changed once created
Control focus Approval, version, distribution Integrity, access, retention, disposal
Example Backup procedure Restore test form, backup job report

A record isn’t changed. If a record entered wrongly is to be corrected, the correction is made as a separate entry and who made it and when stays visible. A mistake you may come across is past rows in a shared Excel table being silently overwritten; in that case the table loses its evidential value. Version and approval management of documents is explained in the document control guide; here we focus only on records.

Fields of the records list

The records list gathers in a single table which records the organization produces and the lifecycle decisions for each. The standard doesn’t ask for this list by name. But in ISO 27001 documentation, it’s the most orderly way to show the retention and disposal requirement of Clause 7.5.3 and the record protection expectation of Annex A 5.33. The fields we recommend:

  • Record name and source process: the procedure or control that produces the record.
  • Record owner: the role responsible for the record’s accuracy and retention.
  • Media and location: system name, folder, archive room; electronic or printed.
  • Format: system record, PDF, signed form, log file.
  • Classification and personal data content: whether it holds personal data, and whether that’s special category data.
  • Access permissions: who can read, who can add; who has delete rights.
  • Retention period and start point: the period and what starts it (creation of the record, end of the contract, year end).
  • Retention basis: the legal, contractual or operational justification and its reference.
  • Disposal method: deletion, overwriting, physical destruction, anonymization.

The field most often missing from lists is the start point. “5 years” on its own can’t be applied. Unless it’s written whether to count from the day the record was created, from the employee’s departure or from the end of the calendar year, nobody dares delete the record when disposal day comes, and the record stays forever.

Bases for retention periods

Every record’s retention period rests on one or more of three sources. If there’s more than one basis, the longest mandatory period applies. But for records containing personal data, keeping them longer than necessary also has legal consequences. A long period isn’t always the safe option.

Legislation sets minimum periods for certain records. For example, Article 82 of the Turkish Commercial Code imposes a ten-year retention obligation for commercial books and supporting documents, and Article 253 of the Tax Procedure Law a five-year obligation for tax records. Obligations on access and traffic records on the internet are in Law No. 5651 and its secondary regulations. Legislation can change and the start point of the period differs by article; so the legal unit should verify every legal period in the records list against the current text and write it with the article number.

On the personal data side, Article 4 of KVKK (Law No. 6698) sets as a principle that data be kept for as long as required by the relevant legislation or necessary for the purpose for which it is processed. The Regulation on the Deletion, Destruction or Anonymization of Personal Data requires data controllers obliged to register with VERBİS to prepare a personal data retention and disposal policy, to carry out periodic disposal at intervals not exceeding six months, and to keep records of disposal operations for at least three years, except for other legal obligations. For current texts, the official KVKK website and the Legislation Information System should be the reference.

Contractual basis

Customer contracts, information security annexes or sector requirements may require certain records to be kept: access logs, incident records, test reports and so on. These periods are written into the records list with the contract reference; when the contract ends, the period of the related record is reassessed. For requirements specific to production quality records, see the article archiving PPAP and quality records.

Operational basis

If neither legislation nor contract sets a period, the period is derived from the record’s purpose of use. The question is: which decision or verification is this record needed for, and when does that need go away? Access review records must cover at least the period covered by the next certification or surveillance audit. System logs needed for retrospective review in incident investigations are set according to threat detection and response needs. When an attack is noticed weeks later and there are no logs for those weeks, the investigation ends there. For the technical architecture of log retention, the article central log retention architecture is a complement.

Sample ISMS records list

The table below is an example prepared to show the structure. Each of the periods must be set according to the organization’s own legal, contractual and operational analysis; don’t copy them from the table.

Record Owner / Media Example period and basis Disposal
Access request and approval records IT / ITSM tool A set period from account closure; operational Deletion from the system
Permission review minutes Application owner / ISMS folder At least one certification cycle; operational Deletion
Information security incident records ISMS owner / incident register From incident closure; contractual and operational Deletion or anonymization
Restore test forms System administrator / ISMS folder At least one certification cycle; operational Deletion
Training attendance records HR / training platform Duration of employment + a set period; legal and operational Deletion
Visitor entry records Administration / visitor system The period in the retention and disposal policy; KVKK Periodic disposal
Internal audit reports, management review minutes ISMS owner More than one audit cycle; operational Deletion

For how to present backup and restore records in an audit, the backup audit evidence guide contains detailed examples.

Protecting and accessing records

Annex A 5.33 requires records to be protected from loss, destruction, falsification, unauthorized access and unauthorized release. The measures vary with the media the record is kept on:

  • Integrity: prefer systems where records can’t be changed after creation, or where changes leave a trace; send critical logs to a separate log server or immutable storage. A log that stays on the server that produced it is in the hands of an attacker who takes over that server.
  • Access: read permission is kept broad, delete permission narrow. The person who produces a record not being able to delete it is the simplest application of segregation of duties.
  • Readability: for electronic records kept a long time, plan for the file format to be openable in future; move the records of an application being retired into a readable format before the application is removed.
  • Backup and cloud copies: a record deleted from the primary media continues to sit in backups. Backup retention periods must be aligned with the periods in the records list, or re-disposal of expired data on restore from backup must be defined.

Disposal and disposal records

Disposing of an expired record must be as planned as keeping it. Annex A 8.10 covers deleting information that’s no longer needed, and 7.10 and 7.14 the secure disposal of storage media and equipment. When choosing a media sanitization method, the clear, purge and destroy distinction in NIST SP 800-88 is a common reference; the method is decided by the sensitivity of the data and whether the media will be reused. A disk going back into service and a disk going to the shredder don’t get the same treatment.

The disposal operation is itself a record. The minimum fields a disposal record should contain:

  1. The record type and scope disposed of (date range, number of records or media serial number).
  2. Reason for disposal: the retention period expired, and the reference in the records list.
  3. Method applied: logical deletion, overwriting, cryptographic erasure, physical destruction, anonymization.
  4. The roles that carried out and approved the operation, and the date.
  5. If an external service was used, the service provider’s destruction certificate or report.

For records containing personal data, this disposal record is the evidence of periodic disposal under KVKK. Rows marked “contains personal data” in the records list must be fully consistent with the period table in the retention and disposal policy. If the two documents state two different periods, that’s the first place the auditor will ask about.

Steps for putting it into practice

  1. Build the records inventory by scanning the “Records” section of all procedures.
  2. For each record, determine the owner, media and personal data content.
  3. Clarify legal and contractual bases with the legal unit, and operational needs with process owners.
  4. Get the records list approved and match its periods with the KVKK retention and disposal policy.
  5. Configure automatic retention rules in systems (log rotation, archive policies, backup retention) according to the list. In most organizations, the period on paper and the rotation setting in the system have never met.
  6. Carry out the first periodic disposal and create the disposal record.

Designing personal data retention and disposal together with the ISMS records setup can be handled as part of our KVKK technical and organizational measures work.

Frequently asked questions

Does ISO 27001 set a specific retention period for ISMS records?

No. ISO/IEC 27001 requires retention and disposal to be controlled but doesn’t give periods. Periods are set according to the organization’s legal, contractual and operational needs and written in the records list with their justification.

If more than one retention period applies to a record, which one applies?

Usually the longest mandatory period applies. For records containing personal data, however, keeping them longer than needed for the purpose is also a risk; verify that the long period is really tied to a mandatory basis.

How long should the disposal record be kept?

For records of the disposal of personal data, the relevant regulation requires retention for at least three years, except for other legal obligations. For other disposal records, the organization’s records list sets the period; verify current legislation with the legal unit.

What about old records remaining in backups?

Backup retention periods should be planned in line with the periods in the records list. If they aren’t aligned, a step is added to the procedure so that expired records are disposed of again when a restore from backup is done.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles