Back to insights
Cybersecurity

SIEM Log Retention: How Long Should You Keep Security Logs in SA?

Security logs are only useful if they still exist when an incident is investigated. The retention periods South African organisations should plan for, and how to set them in Splunk.

Either an auditor asks how long security logs are kept, or an incident responder asks for the sign-in records from four months ago and is told they were deleted after thirty days. The second conversation is the expensive one.

A security information and event management (SIEM) platform such as Splunk Enterprise Security collects logs from endpoints, identity systems, firewalls and cloud workloads and correlates them. Retention decides how far back that correlation can reach. This guide sets out the periods we plan for and how the settings work in Splunk, so that the policy and the configuration say the same thing.

Why thirty days is not enough

A credential phished in January may be used in March and noticed in April. Investigating that incident means reading authentication, endpoint and firewall records from before the first alert. Three obligations also shape the minimum for most South African organisations:

  • Payment card data brings the Payment Card Industry Data Security Standard (PCI DSS). Requirement 10.5.1 states that audit log history is retained for at least 12 months, with at least the most recent three months immediately available for analysis.
  • Financial institutions supervised by the Financial Sector Conduct Authority (FSCA) and the Prudential Authority fall under Joint Standard 2 of 2024, which requires security monitoring and detection and the notification of material incidents. Since 1 September 2026 the regulators' template requires an initial notification within 24 hours of classifying an incident as material, and a follow-up within 14 calendar days covering root cause and data compromise. Our Joint Standard 2 checklist covers the recovery side.
  • Any organisation holding personal information must notify the Information Regulator and affected data subjects of a security compromise under section 22 of the Protection of Personal Information Act (POPIA), as soon as there are reasonable grounds to believe personal information was accessed by an unauthorised person. The Regulator's SCN1 form asks for the incident date and the number of affected data subjects; both answers come from logs. Our POPIA compliance article covers the duty.

None of these can be met from a month of data. We treat 12 months as the floor, with the most recent 90 days searchable at once.

Decide the periods by log source

Group the sources by what they prove:

  • Identity and authentication logs (Microsoft Entra sign-ins, Active Directory, VPN and Citrix Gateway): 12 months or longer. They answer "who was it" in every investigation.
  • Endpoint detection events from SentinelOne: 12 months, because they show what a compromised account did on a device.
  • Firewall, NetScaler and proxy logs: 12 months, with 90 days searchable. They drive most of the cost.
  • Patch and device health records from N-able N-central: 12 months, as evidence that controls were maintained.
  • Backup job history and recovery test results from Cove Data Protection: for the regulatory review cycle, as recovery evidence.

Write the periods down as a schedule with an owner. POPIA also requires that personal information is not kept longer than its purpose needs, and logs that identify users can be personal information; a documented schedule with a stated security purpose answers that too.

How Splunk Enterprise retires data

In Splunk Enterprise, data moves through hot, warm and cold buckets, all searchable, and then to frozen, which is not. Two settings in indexes.conf decide when data freezes:

  • frozenTimePeriodInSecs sets the age limit. The default is 188 697 600 seconds, roughly six years.
  • maxTotalDataSizeMB sets the size limit. The default is 500 000 MB.

Data freezes when either limit is reached first, and that is the trap. An index that fills its size limit in five months discards data at five months whatever the age setting says, and frozen data is deleted by default. If logs must survive, configure archiving so frozen buckets go to storage you control and can be thawed later, and size each index so that the age limit, not the size limit, fires.

How Splunk Cloud Platform handles retention

Splunk Cloud Platform uses two per-index values:

  • Searchable retention, in days, is how long data stays in searchable storage.
  • Archive retention, under Dynamic Data Active Archive, is the total time data is kept, including the searchable period. The maximum is 3 650 days, or ten years. A policy of 12 months total with 90 days searchable is entered as 90 and 365, not 365 and 275.

When data leaves the searchable period it moves to the archive if archiving is enabled; otherwise it goes to a self-storage location you provide or is deleted. Archive changes are recorded in audit.log, which is itself evidence that the policy was enforced. Archived data is not searchable until restored, so the searchable period should cover the window investigators reach for most often; 90 days is a sensible minimum.

Protect the logs you keep

Retention counts for little if an intruder can edit the record. PCI DSS requirement 10.3 asks that log files are promptly backed up to a central log server that is difficult to modify, and that file integrity monitoring or change detection alerts if existing log data is changed.

A SIEM meets these when sources forward in near real time and access is restricted. Limit who can change indexes and retention, and review the audit.log entries for those changes each month.

A retention checklist

  • A written schedule by log source, with a floor of 12 months and 90 days searchable.
  • The schedule mapped to PCI DSS, Joint Standard 2 and POPIA where they apply.
  • Each Splunk index sized so that the age limit, not the size limit, retires data.
  • Archiving configured and tested with a restore.
  • Retention changes restricted, logged and checked against the schedule each quarter.

For managed clients, OAS configures and reviews these settings as part of the security intelligence service, so the answer to "how long do you keep your logs" is the same whoever asks.

Sources

Decide your retention periods once and have them enforced in the platform with Splunk SIEM deployed and managed by OAS.

Keep exploring

All insights