Audit log retention and archive
None of the published texts sets a fixed period on this consumer; every row below reads no period set by the text. Paste one job that feeds this consumer, for example audit_log_archive, weekly, and the register reads its period against the clocks below, names the gap in hours, and carries the question for its owner.
Matched on the job name or the consumer column by these words: log archive, log retention, log rotation, archive logs, log purge, log archive.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| PCI DSS | no clock | PCI DSS 10.5.1 Keep logs 12 months, latest three months onlinetwelve months retained, three immediately available; no run period |
| ISO 27001 | no clock | ISO 27001 8.15 Logging |
Questions this page answers
How often does PCI DSS v4.0 require audit log retention and archive?
The text of PCI DSS 10.5.1 (Keep logs 12 months, latest three months online) sets no fixed period: twelve months retained, three immediately available; no run period. Audit log history must be kept for at least 12 months, and at least the latest three months must be ready for immediate analysis. Applies to all entities. The guidance explains that compromises often stay undetected for a long time, and gives storing logs online, archiving them or restoring them quickly from backup as examples of keeping logs immediately available. Customized approach objective: historical activity records can be used straight away to support incident response and are held for at least 12 months.
How often does ISO/IEC 27001:2022 require audit log retention and archive?
The text of ISO 27001 8.15 (Logging) sets no fixed period: no period set by the text. Produce, store, protect and analyse logs of activities, exceptions and faults.
What does the register ask the owner of a audit log retention and archive job?
Does the archive keep twelve months, with the latest three months readable without a restore?
The clauses in full
Audit log history must be kept for at least 12 months, and at least the latest three months must be ready for immediate analysis. Applies to all entities. The guidance explains that compromises often stay undetected for a long time, and gives storing logs online, archiving them or restoring them quickly from backup as examples of keeping logs immediately available. Customized approach objective: historical activity records can be used straight away to support incident response and are held for at least 12 months.
What an assessor asks to see: Audit log retention policy and procedure stating 12 months and three months online; SIEM hot storage and archive retention settings; Oldest available log entries per sampled source showing 12 months of history; Demonstration of querying or restoring logs from the last three months. Where it usually falls short: SIEM hot tier only keeps 30 or 90 days with no archive beyond
Produce, store, protect and analyse logs of activities, exceptions and faults.
Guidance beside it, ISO 27002 8.15: Requires logs to be produced, stored, protected and analysed, covering activities, exceptions, faults and any other event of relevance. Older source material adds that records of user activity, exceptions and security events should be retained for an agreed period to support later investigation and access control monitoring, and that faults should be logged, analysed and acted on.
What an assessor asks to see: log_collection_policy; log_storage_and_protection; log_review_and_analysis; log_retention_and_disposal. Where it usually falls short: Inconsistent log collection across systems
Requirement text is our own statement of each clause, from the standards published at compliance.theartofservice.com, the same publisher as this register, read against the published text of each standard: our statement of each clause, not the instrument verbatim. Run this job through the register