A retention policy sets how long an organization keeps each type of data. The period should reflect legal requirements and business needs, rather than applying one deadline to everything. Where no rule specifies a period, the organization must set and enforce its own. section 14.3.5
Different records, different periods
A company might keep financial records for seven years to meet tax requirements but employee emails for two years to limit storage and protect privacy. Keeping every email for ten years instead could raise costs, make records harder to find, and increase the impact of a breach. section 14.3.5
A practical retention decision weighs:
- Requirements: Laws, regulations, industry standards, and business needs may call for different periods for different records. section 14.3.5
- Future use: Logs may be needed for audits, investigations, or to connect security events discovered weeks or months later. section 12.6.3
- Costs and exposure: Keeping data unnecessarily uses storage and increases security and compliance risks. Periodic record reviews help remove what is no longer needed. section 14.3.5
Access logs show why the details matter: PCI DSS requires relevant audit logs to be kept for at least one year, with the most recent three months immediately available for analysis. Logs also need protection against tampering and unauthorized access so they remain useful as evidence. section 9.4.4
Retention is one part of the data lifecycle, alongside archiving and destruction. Policies should identify the departments that handle the records and be reviewed as organizational needs and requirements change. section 14.5 section 4.2.3











