Utility SCADA entity control tests must alert owners when they become overdue. What should the implementer configure?
Select an answer to reveal the explanation.
Short Explanation
SCADA controls going quiet is how overdue becomes invisible. Turn on overdue notifications for those utility entities so owners get the ping. Hallway reminders, no due dates, or one giant yearly dump do not keep operational technology tests on track.
Full Explanation
Overdue control test notifications prompt owners and testers when scheduled compliance work slips. For utility SCADA entities that protect critical infrastructure serving the public, configuring notifications that fire when control tests become overdue supports timely testing of operational technology controls. Relying on weekly hallway reminders from the GRC team with no system notifications fails by concept because informal reminders do not scale, leave no system audit of escalation, and miss remote or shift-based OT staff. Disabling due dates on SCADA control tests so nothing can be overdue fails by concept because removing due dates hides lateness rather than managing it. Sending a single annual digest of every GRC record fails by concept because annual bulk digests are neither timely nor scoped to critical SCADA entities that need prompt escalation. Exam caveat: CIS-RC expects scoped, timely overdue notification for critical entity populations rather than informal or once-a-year substitutes. Operational check: enable overdue notifications for utility SCADA entity control tests, advance a test past due in a lower environment, and confirm the owner or tester receives the notification for that scoped entity.