Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Log Retention Planning?

Retention planning decides how long each log source is kept, in which storage tier, and why. It balances investigation needs, compliance obligations, cost, and the data minimisation duty under UK GDPR.

Illustration for the cybersecurity term Log Retention Planning
Home / Blog / Cybersecurity Terms / What Is Log Retention Planning?
17 November 2026

What Is Log Retention Planning?

What Is Log Retention Planning?

Retention is where security, finance, and data protection pull in different directions. Investigators want everything kept indefinitely. Finance sees a line item that grows every quarter. Data protection points out that logs contain personal data and that keeping it longer than necessary is itself a compliance failure. A retention plan is the written resolution of those three positions, source by source.

Start With How Long Compromises Take to Find

The investigation argument rests on dwell time. IBM’s Cost of a Data Breach Report for 2024 put the average time to identify a breach at 194 days, with a further 64 days to contain it. If your authentication logs are kept for 30 days, an investigation that begins six months after initial access cannot establish how the attacker got in, which is the question clients, insurers, and the regulator all ask first.

That argument supports 12 months for the sources that answer the entry question: identity and authentication, VPN and remote access, email, DNS, and endpoint process telemetry. It does not support 12 months of full-fidelity firewall traffic, which is why retention is set per source rather than globally.

The Obligations That Set Floors

Litigation holds override everything. When legal counsel issues one, automated deletion must stop for the affected data, and a retention design with no mechanism to suspend expiry will destroy evidence on schedule.

Tiering Makes It Affordable

Treat retention as three decisions rather than one. A hot tier, fully indexed and instantly queryable, is what detection runs on; 30 to 90 days is typical and it is where the cost sits. A warm or searchable archive holds data that can be queried with a delay of minutes at a fraction of the price, and most platforms now offer something of the kind. A cold archive holds compressed objects in inexpensive storage for the remainder of the period, restorable in hours.

Deciding what goes where is the useful work. High-value, low-volume sources such as authentication and privileged access belong hot for longer. High-volume, low-density sources such as raw network flow can move out of the hot tier quickly, often with aggregates retained in their place.

The UK GDPR Constraint

Security logs contain personal data: usernames, addresses, device identifiers, and often a detailed record of individual activity. The storage limitation principle requires that personal data is kept no longer than necessary for the purpose, and the purpose here is security monitoring and investigation. That is a legitimate purpose, and it supports substantial retention, but it requires a documented justification per source rather than an open-ended default.

Three practical consequences follow. Record the period and the reason in your retention schedule and your record of processing activities. Tell staff about the monitoring through an employee monitoring policy, which the ICO expects. And make sure deletion actually happens at the end of the period, including in backups and in the archive tier, because a policy that is not enforced is worse than a longer policy that is.

Writing the Plan

Produce a table with one row per source: the retention period hot, warm, and cold; the driver, whether investigation, compliance, or contract; the approximate daily volume; the owner; and the review date. Review it annually and whenever a new source is onboarded. The table is also the document that answers an auditor in two minutes rather than two weeks.

Retention sits downstream of log source criticality, which tells you which sources deserve the expensive tier, and upstream of everything in log management. At Privia Security, we produce that table as a deliverable in our SOC maturation services, because almost every organisation we assess is keeping some sources far too long and others not nearly long enough.

FAQ – Frequently Asked Questions

How Long Should Security Logs Be Kept?

Twelve months is a reasonable default for the sources that answer how an attacker got in: identity, remote access, email, DNS, and endpoint process telemetry. Keep 30 to 90 days hot and searchable, with the remainder in a cheaper archive. High-volume, low-density sources such as raw network flow can be shortened or aggregated. Set the period per source and record the reason for each.

Does PCI DSS Require Twelve Months of Logs?

Yes. Requirement 10.5.1 of PCI DSS v4.0 requires audit log history to be retained for at least twelve months, with at least the most recent three months immediately available for analysis. The immediately available part is what drives tiering decisions, because it rules out an architecture where everything older than a month must be restored from cold storage before it can be queried.

Does UK GDPR Limit How Long Logs Can Be Kept?

It requires that personal data is kept no longer than necessary for the stated purpose. Security monitoring and investigation is a legitimate purpose that supports substantial retention, but the period needs a documented justification per source rather than an indefinite default. Record it in your retention schedule, cover the monitoring in an employee monitoring policy, and make sure deletion actually happens.

How Do You Reduce Retention Cost Without Losing Capability?

Tier the storage rather than shortening the period. Keep a short hot window for detection, use a searchable archive for the middle period, and compressed object storage for the remainder. Replace full retention of very high-volume sources with aggregates that still answer the common questions, and trim fields that no detection or investigation uses before the data reaches the priced tier.

Related Terms

You May Be Interested In These

What Is a MAC Address?

Cybersecurity Terms

30 March 2021

What Is a MAC Address?

Read More
What Is Critical Infrastructure Security?

Cybersecurity Terms

17 November 2026

What Is Critical Infrastructure Security?

Read More
What Is the Shared Responsibility Model?

Cybersecurity Terms

17 November 2026

What Is the Shared Responsibility Model?

Read More