Targeted risk analysis 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 annual_tra_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: risk analysis, tra review, risk assessment review, risk assessment, risk analysis review.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| PCI DSS | no clock | PCI DSS 10.4.2.1 Periodic log review frequency set by targeted risk analysisthe frequency the targeted risk analysis defines |
| SP 800-53 | no clock | SP 800-53 CA-7 Continuous monitoringa defined frequency |
Questions this page answers
How often does PCI DSS v4.0 require targeted risk analysis review?
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. 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 NIST SP 800-53 Rev 5 require targeted risk analysis review?
The text of SP 800-53 CA-7 (Continuous monitoring) sets no fixed period: a defined frequency. Requires a system-level continuous monitoring strategy aligned to the organizational one, defining the metrics monitored, the frequencies for monitoring and for assessing control effectiveness, ongoing control assessment, correlation and analysis of the results, response actions, and reporting of security and privacy posture to defined personnel.
What does the register ask the owner of a targeted risk analysis review job?
Which periodic-review frequencies in this register does the analysis justify, and where is that written?
The clauses in full
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
Requires a system-level continuous monitoring strategy aligned to the organizational one, defining the metrics monitored, the frequencies for monitoring and for assessing control effectiveness, ongoing control assessment, correlation and analysis of the results, response actions, and reporting of security and privacy posture to defined personnel.
What an assessor asks to see: Documented continuous monitoring strategy with metrics and frequencies; Evidence of ongoing control assessments performed at the stated cadence; Correlation and analysis output showing findings drawn from monitoring data; Posture reports issued to the defined personnel and the actions they triggered. Where it usually falls short: Monitoring reduced to vulnerability scanning, with most controls never reassessed
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