Control Testing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
7 hours ago
I am new to Service Now's IRM Module for our GRC implementation. We just got access to the Control Testing module that shows up in the Compliance Workspace. Can someone provide me a link to training for the Control Testing?
I've done some research and I see control tests mentioned under the Audit Workspace training. So I'm confused on why Control Testing is in the Compliance Workspace. Is there an independent process for doing control testing for Compliance vs doing control testing for Audit?
thank you,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi Buddy,
This is a really common question when you’re first getting into IRM, so you’re definitely not alone 🙂
There isn’t a separate control testing process for Compliance versus Audit. Control Testing is shared across IRM, and ServiceNow just exposes it in different workspaces based on who’s using it.
You’re seeing Control Testing in the Compliance Workspace because that’s where day-to-day, ongoing compliance work happens. Compliance teams run control tests there to make sure controls are operating as expected against regulations and internal policies.
You’ll also see control tests mentioned in Audit Workspace training because auditors rely on those same control tests and results as evidence during an audit. In many cases, audits reuse existing control testing rather than starting from scratch.
So in simple terms:
Compliance Workspace is where control tests are usually created and executed
Audit Workspace is where auditors review and leverage those results
As for training, there isn’t a standalone “Control Testing” course. It’s covered within the broader IRM / GRC courses in Now Learning, especially around Policy & Compliance and IRM fundamentals.
Once you start using it, the overlap will make more sense — it’s one control testing framework, just used by different teams for different purposes.
@kryon - Please mark Accepted Solution and Thumbs Up if you found Helpful 🙂
