Batch Register

Audit evidence pack export

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_evidence_pack, 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: audit evidence, evidence pack, audit export, auditor pack, evidence export, audit pack, evidence pack.

The clock each rule sets

RegimeClockClause
ISO 27001no clockISO 27001 5.28 Collection of evidence
PCI DSSno clockPCI DSS 10.5.1 Keep logs 12 months, latest three months onlinetwelve months retained
SOX 404 / ICFR named referenceno clockSOX 404 ENT-8 Internal Audit Functionquoted below

Named reference beside this class, SOX 404 ENT-8 Internal Audit Function: Internal audit reports functionally to the audit committee and executes risk-based audit plan covering ICFR.

Questions this page answers

How often does ISO/IEC 27001:2022 require audit evidence pack export?

The text of ISO 27001 5.28 (Collection of evidence) sets no fixed period: no period set by the text. Have procedures to identify, collect, acquire and preserve evidence related to security events.

How often does PCI DSS v4.0 require audit evidence pack export?

The text of PCI DSS 10.5.1 (Keep logs 12 months, latest three months online) sets no fixed period: twelve months retained. 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 does the register ask the owner of a audit evidence pack export job?

Can this pack be produced for any month of the last twelve without a restore?

The clauses in full

ISO 27001 5.28 Collection of evidencethe standard's page

Have procedures to identify, collect, acquire and preserve evidence related to security events.

Guidance beside it, ISO 27002 5.28: Requires procedures to be established and used for identifying evidence relating to information security events, then collecting, acquiring and preserving it.

What an assessor asks to see: evidence_collection_policy; incident_response_log; forensic_preservation_report; chain_of_custody_form. Where it usually falls short: Procedures not aligned with legal requirements

PCI DSS 10.5.1 Keep logs 12 months, latest three months onlinethe standard's page

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

SOX 404 ENT-8 Internal Audit Functionnamed referencethe standard's page

Internal audit reports functionally to the audit committee and executes risk-based audit plan covering ICFR.

What an assessor asks to see: IA charter; annual audit plan; audit reports; issue tracker. Where it usually falls short: Internal Audit plan not refreshed for changes in risk or business operations

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