Walkthrough playbook: C3PAOs, auditors and assessing vCISOs
A walkthrough of CMDash for C3PAOs, auditors and assessing vCISOs, run in the live sandbox in about 18 minutes. It is written for the CMDash sales team and for partners who present the product.
- Public page: www.cmdash.com/for/assessors
- Recommended plan: Command
- Length: about 18 minutes, 6 steps
- Read first: Before any walkthrough
Who this is for
A C3PAO assessor, an ISO or SOC 2 auditor, or a vCISO who assesses clients. They do not buy CMDash; their client does. They decide whether to recommend it, and whether to list their practice in the directory. Their interest is fieldwork time.
What they are tired of
- "I ask once and get a folder of screenshots with no dates on them."
- "The fieldwork clock is running and the evidence is spread across whatever the client's tools exported."
What it costs them: Fieldwork hours spent sorting evidence instead of testing it.
The line to open with: "Stop sorting undated screenshots during fieldwork." It is the headline of their page. Say it, then ask whether it is true for them before you show anything.
Before this call
- The sandbox shows the client's side. Say so at the start: "I am showing you what your client sees and what they hand you."
- The assessor's own view (Overview → My access) appears only on an assessor login. Describe it; do not go looking for it in the sandbox.
The walkthrough
1. How you get in (3 min)
- Go to: Settings → External assessors (
/settings/assessors) - Show: The grant: named frameworks, an expiry date, read-only.
- Say: "Your client invites you for a fixed period, for the frameworks you are assessing and nothing else. No billing, no integrations console, no other client. You are not sharing a login, and every page you open is recorded on their side."
2. Evidence by control (4 min)
- Go to: Compliance → Frameworks (
/compliance), open a control - Show: A control, its status, and the evidence behind it with dates.
- Say: "This is what you read: every practice or control in scope, with the evidence already attached and dated. Not a shared drive."
3. Asking for what is missing (3 min)
- Go to: Compliance → Evidence requests (
/evidence-requests) - Show: The request thread on a control.
- Say: "When something is missing you ask here, against the control, and the answer arrives against the same control. The thread stays with the engagement."
4. The package (3 min)
- Go to: Compliance → Evidence packages (
/evidence/packages) - Show: A package for a framework and its manifest.
- Say: "When the client is on Command, they hand you one package per framework: every approved item, with a manifest. You are not assembling it."
5. The sample (3 min)
- Go to: Security → Auditor sample (
/sampling-export) - Show: The populations it draws from and the recorded seed.
- Say: "A sample drawn from users, access reviews, control assessments and more, with the random seed recorded, so you can reproduce it and defend it in your workpapers."
6. Being found (2 min)
- Go to: www.cmdash.com/partners
- Show: The partner and assessor directory, by region and framework.
- Say: "Organizations on CMDash look here for an assessor. Listing is opt-in. CMDash takes no part in the engagement."
Questions you will get
"Does CMDash tell me the control is met?"
No. It shows the status the organization set and the evidence behind it. The judgment is the assessor's.
"Can I export everything?"
The client exports the evidence package and the sample. An assessor session is read-only.
"Does being listed create an independence problem?"
Read www.cmdash.com/independence with them rather than answering from memory. Listing is opt-in and unpaid.
"What does it cost me?"
Nothing for the access a client grants. The plan is the client's. Evidence packages and the sample export need the client to be on Command.
Recommended plan and next step
Command, for the organizations they assess. The reasons, as they appear at the foot of the public page:
- Audit evidence packages: every approved item for a framework in one manifest.
- The auditor sample export, drawn with a recorded random seed so it can be reproduced.
- The assessor's own read-only, time-boxed access comes with whatever plan the client is on.
The recommendation is for the organizations they assess. The assessor pays nothing.
Next step: Invite them to list the practice at www.cmdash.com/partners/apply. Ask which of their clients struggles most with evidence and offer that client a walkthrough using the GRC playbook.