Security and risk · LessonBy Neelima, ServiceNow Architect · Published · ServiceNow · all levels
Continuous control monitoring
Automate control testing with indicators, templates and results that feed compliance and audit.
Quick answer
Automate control testing with indicators, templates and results that feed compliance and audit.
Key takeaways
- Indicators turn control testing into scheduled automation
- Templates scale one definition across many entities
- Failures must create owned issues to be worth running
- Keep versions so historical results remain explainable
What continuous monitoring does
Instead of asking a person whether a control operates, an indicator queries the platform or an integrated system on a schedule and records a pass or fail with the evidence. Compliance moves from point in time to ongoing.
Indicator templates
Templates let one definition apply to many controls. For example, a template that checks whether privileged accounts were reviewed in the last 90 days can apply to every in scope system, generating results per entity.
Designing good checks
A check is only useful when a failure is actionable.
- State the exact condition that constitutes a pass
- Sample rather than test everything when volume is huge
- Fail loudly, create an issue with an owner
- Version the check so an auditor can see what was tested last quarter
Practice challenge
+0 XPStreak ×0
Question 1 of 2
What lets one check apply to many entities?
Frequently asked questions
Can indicators use data outside ServiceNow?
Yes, through integrations that import results, or by querying an external system in a script include used by the indicator.
How often should checks run?
Match the control frequency. A quarterly control does not need a daily check, and daily noise makes people stop reading results.