Other system log review
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 app_server_log_review, 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: other log, system log review, non cde log, server log review, app log review, application log review, non-CDE log review.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| PCI DSS | no clock | PCI DSS 10.4.2 Periodic review of all other system component logsperiodically |
| no clock | PCI DSS 10.4.2.1 Periodic log review frequency set by targeted risk analysisthe frequency the targeted risk analysis defines | |
| ISO 27001 | no clock | ISO 27001 8.15 Logging |
| SP 800-53 | no clock | SP 800-53 AU-6 Audit record review, analysis, and reportinga defined frequency |
Questions this page answers
How often does PCI DSS v4.0 require other system log review?
The text of PCI DSS 10.4.2 (Periodic review of all other system component logs) sets no fixed period: periodically. The text of PCI DSS 10.4.2.1 (Periodic log review frequency set by targeted risk analysis) sets no fixed period: the frequency the targeted risk analysis defines. Logs from every other in-scope system component, meaning those not covered by the daily review in 10.4.1, must be reviewed on a periodic basis. Applies to all entities. Applicability: covers every remaining in-scope component outside the scope of 10.4.1. The guidance notes these reviews can reveal signs of trouble or attempts to reach critical systems by way of less critical ones. Customized approach objective: suspicious or anomalous activity on these other components is reviewed in line with the risk the entity has identified. The frequency for periodically reviewing logs of every other system component (those outside 10.4.1) must be set by the entity's own targeted risk analysis, and that analysis must be carried out in line with every element specified in Requirement 12.3.1. Applies to all entities. The guidance suggests criteria such as how complex the environment is, how many types of systems need evaluating and what those systems do. Objective under the customized approach: reviews of lower-risk components' logs happen often enough to address the entity's risk. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
How often does ISO/IEC 27001:2022 require other system log review?
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.
How often does NIST SP 800-53 Rev 5 require other system log review?
The text of SP 800-53 AU-6 (Audit record review, analysis, and reporting) sets no fixed period: a defined frequency. Requires audit records to be reviewed and analysed on a defined frequency for indications of organization-defined inappropriate or unusual activity and its likely impact, findings to be reported to defined personnel, and the depth of review to be increased when credible information changes the risk.
What does the register ask the owner of a other system log review job?
The card rule leaves this period to your targeted risk analysis. Does the analysis name the period this job runs on?
The clauses in full
Logs from every other in-scope system component, meaning those not covered by the daily review in 10.4.1, must be reviewed on a periodic basis. Applies to all entities. Applicability: covers every remaining in-scope component outside the scope of 10.4.1. The guidance notes these reviews can reveal signs of trouble or attempts to reach critical systems by way of less critical ones. Customized approach objective: suspicious or anomalous activity on these other components is reviewed in line with the risk the entity has identified.
What an assessor asks to see: Procedure defining periodic review for lower-risk in-scope components; Inventory distinguishing 10.4.1 components from other in-scope components; Documented results of periodic reviews with dates and reviewer; Interview notes with personnel performing the reviews. Where it usually falls short: Other in-scope components are logged but never reviewed
The frequency for periodically reviewing logs of every other system component (those outside 10.4.1) must be set by the entity's own targeted risk analysis, and that analysis must be carried out in line with every element specified in Requirement 12.3.1. Applies to all entities. The guidance suggests criteria such as how complex the environment is, how many types of systems need evaluating and what those systems do. Objective under the customized approach: reviews of lower-risk components' logs happen often enough to address the entity's risk. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
What an assessor asks to see: Targeted risk analysis document for periodic log review frequency, meeting 12.3.1; Approval record of the risk analysis and its review date; Log review records demonstrating the chosen frequency is met; Criteria used in the analysis (environment complexity, system types and functions). Where it usually falls short: Review frequency chosen arbitrarily with no documented targeted risk analysis
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
Requires audit records to be reviewed and analysed on a defined frequency for indications of organization-defined inappropriate or unusual activity and its likely impact, findings to be reported to defined personnel, and the depth of review to be increased when credible information changes the risk.
What an assessor asks to see: Defined review frequency and the activity indicators being looked for; Completed review records with reviewer, date and findings; Reports issued to the defined recipients and evidence of follow-up; Record of a review level adjustment made in response to changed risk. Where it usually falls short: Review is automated alerting only, with no periodic analytical review for slow patterns
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