Walkthrough playbook: GRC leads and compliance managers
A walkthrough of CMDash for GRC leads and compliance managers, run in the live sandbox in about 17 minutes. It is written for the CMDash sales team and for partners who present the product.
- Public page: www.cmdash.com/for/grc-teams
- Recommended plan: Command
- Length: about 17 minutes, 6 steps
- Read first: Before any walkthrough
Who this is for
The person who runs the audits: a GRC lead, compliance manager or security analyst with two or more frameworks to keep current. They know the frameworks better than you do. They will test whether evidence can be traced and whether the crosswalk is real.
What they are tired of
- "The evidence request goes out again next week."
- "I am chasing screenshots for controls I collected screenshots for last quarter."
What it costs them: Weeks of collection before every audit, and evidence that cannot be traced back to where it came from.
The line to open with: "Stop chasing the same screenshots every quarter." It is the headline of their page. Say it, then ask whether it is true for them before you show anything.
The walkthrough
1. Control status that moves (3 min)
- Go to: Compliance → Frameworks (
/compliance) - Show: The frameworks in scope; open one and show its domains and the status of each control.
- Say: "Every framework you report on, control by control. The status moves when the evidence does. Pick the framework you are being audited on next and I'll stay in it."
2. Evidence with a source (4 min)
- Go to: Compliance → Evidence (
/evidence) - Show: The evidence library; open one item and show the control it supports, where it came from and its history.
- Say: "When the assessor asks how you know, this is the answer: the item, its date, the connection that produced it or the person who uploaded it, and every change since. Uploaded files keep an append-only history with a hash."
3. What is going stale (2 min)
- Go to: Compliance → Evidence freshness (
/evidence/freshness) - Show: The controls whose evidence is aging.
- Say: "This is the page that replaces the quarterly panic. You see what is about to go stale before the request goes out, not after."
4. The crosswalk, visible (3 min)
- Go to: Compliance → Control mappings (
/control-mappings) - Show: The mapping between two frameworks they run, with the mapped controls listed.
- Say: "The mapping is on the page, not hidden. On Command, a status you record on one control carries to the controls it maps to in your other frameworks. On Starter and Essentials you see the same mapping and apply it yourself."
5. What the auditor is handed (3 min)
- Go to: Compliance → Evidence packages (
/evidence/packages), then Security → Auditor sample (/sampling-export) - Show: The evidence package list and the sampling export with its recorded seed.
- Say: "A package bundles every approved item for a framework with a manifest. The sample is drawn with a recorded random seed, so the assessor can reproduce it. Both are Command. The sandbox will not let me download either; I'll send you an example afterwards if you want one."
6. Their own login (2 min)
- Go to: Settings → External assessors (
/settings/assessors) - Show: The grant form: frameworks in scope, expiry date, read-only.
- Say: "Your assessor gets a scoped, expiring, read-only login instead of a shared password or a folder. Every page they open is recorded."
Questions you will get
"Does evidence collect itself for every control?"
No, and say so. Integration data becomes evidence through rule packs and mappings the organization installs, writes or accepts. The framework pages on www.cmdash.com state, per framework, how many controls have a pre-built check. The rest are attested or uploaded by hand.
"We already have a GRC tool."
Ask what it costs them in collection time. CMDash can import from another tool (Admin → Import from another tool) so a trial can start from their existing controls rather than a blank screen.
"Why Command and not Essentials?"
Essentials stops at five frameworks and shows the crosswalk without writing across it. If they run two frameworks and are happy to apply the mapping by hand, Essentials is a fair start.
"Can we add our own framework?"
Custom frameworks are on Enterprise. They can add their own controls inside a framework they already track.
Recommended plan and next step
Command. The reasons, as they appear at the foot of the public page:
- The framework crosswalk engine: a status recorded on one control carries to the controls it maps to in other frameworks.
- Unlimited frameworks and integrations, so every audit draws on the same evidence.
- Audit evidence packages and the auditor sample export, ready to hand to an assessor.
Enterprise adds custom frameworks and monitored third-party risk management.
Next step: Offer the 30-day trial on Command and suggest they bring the control list from their next audit. Book a follow-up with whoever signs off the purchase.