Risk register and control status report
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 risk_register_export, 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 register, control status, risk report, control report, issue register, risk register report.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| CPS 234 | no clock | CPS 234 para 29 Escalate control deficiencies that cannot be fixed promptly |
| SP 800-53 | no clock | SP 800-53 CA-7 Continuous monitoringa defined frequency |
Questions this page answers
How often does APRA CPS 234 require risk register and control status report?
The text of CPS 234 para 29 (Escalate control deficiencies that cannot be fixed promptly) sets no fixed period: no period set by the text. When testing reveals deficiencies in security controls that the entity cannot fix in good time, the entity escalates and reports them to the Board or to senior management.
How often does NIST SP 800-53 Rev 5 require risk register and control status report?
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 risk register and control status report job?
Which open items in the register are past the date their owner set, and who sees that?
The clauses in full
When testing reveals deficiencies in security controls that the entity cannot fix in good time, the entity escalates and reports them to the Board or to senior management.
What an assessor asks to see: Deficiency register with ageing and remediation due dates; Escalation criteria defining when a deficiency is overdue or cannot be fixed in time; Board or executive committee papers reporting unremediated deficiencies; Risk acceptance records signed by the right authority. Where it usually falls short: Overdue findings stay in an IT tracker and never reach senior management
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