Walkthrough playbook: CIOs and IT leaders
A walkthrough of CMDash for CIOs and IT leaders, 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/cios
- Recommended plan: Starter
- Length: about 18 minutes, 6 steps
- Read first: Before any walkthrough
Who this is for
A CIO, IT director or head of IT who has been handed security on top of everything else. There is usually no security lead, no written program, and several outside parties asking questions at once. They will bring in a CISO, vCISO or MSP to run it day to day, so they are judging whether this gives them a structure, not whether it has every feature.
What they are tired of
- "Security landed on my desk, and I don't know where to begin."
- "A CMMC deadline, a customer's questionnaire and our insurance renewal each ask a different question, and I answer each one from scratch."
What it costs them: Three separate scrambles a year and no program anyone can point to when the board asks who is responsible.
The line to open with: "Security is yours now. CMDash shows you where to begin." It is the headline of their page. Say it, then ask whether it is true for them before you show anything.
The walkthrough
1. Start on Home (2 min)
- Go to: Overview → Home (
/home) - Show: The Priorities view: the posture grade, what needs attention, the frameworks in scope and what is due this week.
- Say: "This is the page you would open each morning. One grade, the short list of what needs you, and what is due. Everything else in the next fifteen minutes is where these numbers come from."
2. The program builder (4 min)
- Go to: Security → Build your program (
/program/build) - Show: The layers of the builder (Start, Foundations, Your framework, Evidence and risk, Report and expand, Automate and scale) and the one step it recommends next.
- Say: "You said you don't know where to begin. This is the answer to that. It drafts starter policies for you to review, then walks you up one layer at a time. A step counts as done when the real record exists, so the progress is not a checklist someone ticked."
3. The program itself (3 min)
- Go to: Security → Security program (
/program) - Show: The charter, objectives, committees and management reviews, each with a named owner.
- Say: "When someone asks who is responsible for security, this is what you show them: the charter, the objectives and who owns each. It is the structure the next audit will ask for, whichever audit comes first."
4. One list of frameworks (3 min)
- Go to: Compliance → Frameworks (
/compliance), then Compliance → Control mappings (/control-mappings) - Show: The frameworks in scope with their progress, then the mapping between two of them.
- Say: "Your three asks are three frameworks. Here they sit side by side, and the mapping shows where a control in one answers a control in another, so you can see how much of the second request the first one already covers."
5. Posture from the tools you run (3 min)
- Go to: Overview → Posture (
/posture), then Integrations → Connections (/integrations) - Show: The A to F grade with its signals and the 30- and 90-day trend, then the list of connections it reads.
- Say: "The grade is computed from the tools you already run, not typed in. You connect identity, endpoint and cloud once and it recomputes as they change. The weights are on the page, so nobody has to take the number on trust."
6. What to fix first (3 min)
- Go to: Security → Risk register (
/risks) - Show: The risks ranked by score, one risk opened to show its owner, treatment plan and loss estimate.
- Say: "This is the short list for your next budget conversation: each risk has an owner, a plan and a figure in dollars. It is also what an insurer or a customer means when they ask whether you keep a risk register."
Questions you will get
"We don't have a security person to run this."
The builder is written for that case, and the program pages name owners who can be IT staff. If they want a person as well, CMDash lists independent vCISOs and MSPs in the partner directory at www.cmdash.com/partners, and Professional Services offers fractional security leadership.
"We only need CMMC for now."
Then one framework is enough to start, and a single CMMC Level 1 or Level 2 self-assessment is on the Free plan. Starter is the recommendation because the questionnaire and the insurance renewal usually arrive before the CMMC work is finished.
"Will this get us certified?"
No. CMDash is the system of record for the program and its evidence. Certification and assessment are done by an assessor or auditor, who can be given read-only access.
"How is this different from the spreadsheet we have?"
The spreadsheet records what someone typed. Here the grade is recomputed from connected tools, each control carries its dated evidence, and the frameworks are mapped to each other.
Recommended plan and next step
Starter. The reasons, as they appear at the foot of the public page:
- A posture grade and a risk register, so they can see where the program stands and what to fix first.
- Three frameworks at once, which fits CMMC, ISO 27001 and SOC 2 side by side with the overlap visible.
- The program builder, policies and POA&M tracking are included on every plan.
Essentials adds board snapshot reports and the report builder when they start reporting to a board. Command adds maturity models and carries a control status across frameworks.
Next step: Offer the 30-day trial on Starter and ask who will run it day to day. If that person is a vCISO or MSP, book a second walkthrough with them using the MSP playbook.