Log Retention
Also called Retention Policy.
How long logs are kept available before deletion or archival.
What it is
Log retention is the policy and practice governing how long different log sources are stored and searchable before they are archived or purged, balancing investigative value, storage cost, and compliance obligations. Retention can differ by source and by tier of storage.
Why it matters
Because attackers often dwell for months before discovery, retention shorter than typical dwell time can erase the very evidence an investigation needs. Choosing what to keep, how long, and how quickly it is searchable is a core determinant of whether a past compromise can be reconstructed at all.
In practice
Discovering an intrusion began four months ago, only to find the relevant proxy logs were rotated out after thirty days.
What to look for
- Retention periods shorter than typical dwell time.
- Different retention for hot and archived data.
- Legal or regulatory minimums for your sector.
Common mistake
Keeping only 30 days. Many intrusions are found months after they start.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Event Log Reader
Read a binary .evtx file or pasted event XML, with logon types, NTSTATUS codes and the Keywords mask decoded.
- Linux Case
A server making outbound connections nobody can explain: read its audit log, journal and scheduled jobs, and say who did what.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Splunk Enterprise Security Commercial
A SIEM where these logs are searched with SPL and turned into correlation searches.
-
Microsoft Sentinel Commercial
Microsoft's cloud SIEM, queried with KQL and fed by connectors for these log sources.
-
Elastic Security Commercial
A SIEM built on Elasticsearch, with a detection rules library and timeline investigations.
-
Wazuh Open source
An open source platform that collects, decodes and alerts on host and log data.
Read next
- Log Aggregation: Collecting logs from many sources into a central, searchable store.
- Tamper-Evident Logging: Protecting logs so any alteration or deletion is detectable.
- Flow Logs: Metadata records summarizing network conversations, without packet payloads.