Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.