Skip to main content
DocsWalkthrough playbooksWalkthrough playbook: CISOs and security leaders

Walkthrough playbook: CISOs and security leaders

A walkthrough of CMDash for CISOs and security 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.

Who this is for

A CISO, head of security or security manager who owns the program and reports on it upward. They already run tools and usually already have a compliance obligation. They evaluate alone first and bring others in later.

What they are tired of

  • "I have to explain this to the board on Thursday."
  • "I open six consoles and a spreadsheet every morning, and the slide deck is out of date before I present it."

What it costs them: The night before each board meeting goes to rebuilding slides, and the number presented does not match any screen.

The line to open with: "Stop rebuilding the board report the night before." It is the headline of their page. Say it, then ask whether it is true for them before you show anything.

The walkthrough

1. The morning view (2 min)

  • Go to: Overview → Home (/home)
  • Show: The Priorities view, then switch to the Overview view with the signal breakdown, top risks and integration health.
  • Say: "This replaces the six tabs. Grade, what changed, what is due. I'll show you where each part comes from, and then the report that is built from the same data."

2. The grade and its trend (3 min)

  • Go to: Overview → Posture (/posture), then Overview → Trends (/trends)
  • Show: The grade, the signals behind it with their weights, and the 30- and 90-day trend.
  • Say: "The board's real question is whether it is getting better. This line answers that. It is computed from your tools, and the weights are visible, so when a director asks why it moved you can open the signal that moved."

3. Where the data comes from (3 min)

  • Go to: Integrations → Connections (/integrations)
  • Show: The connected tools, their sync health and when each last synced.
  • Say: "Each console you open in the morning is a connection here. Essentials takes ten of them. If one stops syncing you see it on this page and on Home, instead of finding out when a number looks odd."

4. Risk in dollars (3 min)

  • Go to: Security → Risk register (/risks), then Security → FAIR quantification (/risks/fair)
  • Show: The ranked register, then the loss estimate for one risk.
  • Say: "This is the slide directors remember: the top risks with an annualized loss figure beside each. It ties back to controls and to remediation, so the follow-up question has an answer."

5. The board pack (4 min)

  • Go to: Reports → Exports (/exports), then Reports → Report builder (/reports/builder)
  • Show: The Board Snapshot and the report builder's Board Pack template with its sections: posture headline, top open risks and loss exposure.
  • Say: "This is Thursday. One click produces the PDF from what you just saw. The sandbox is read-only, so I won't generate it here; in your trial it is a button." Do not press Generate or Download in the sandbox: it refuses, by design.

6. Maturity, for later (3 min)

  • Go to: Overview → Maturity (/maturity)
  • Show: The maturity models scored against a target (NIST CSF tiers, CIS Implementation Groups, C2M2).
  • Say: "When the board moves from 'are we secure' to 'how mature is the program', this is the page. It is on the Command plan. I am showing it so you know where the road goes, not because you need it on day one."

Questions you will get

"My tools already have dashboards."

Each tool grades itself. CMDash reads across them, weights the signals into one grade, maps the findings to the frameworks you report on and keeps the history, which no single tool does for the others.

"Does it connect to what we run?"

Check the integrations catalog at www.cmdash.com/integrations with them during the call. Say plainly which of their tools are in it and which are not. Tools not in the catalog can be covered by file import or, on Command, a custom connector.

"How is the grade calculated?"

Open Overview → Posture and read the signals and weights off the page. An owner or admin can change the weights. Do not paraphrase the method from memory.

"Is the board narrative written by AI?"

The Board Pack's numbers come from the organization's own records. AI drafting is a separate allowance on paid plans and nothing in the pack depends on it.

Essentials. The reasons, as they appear at the foot of the public page:

  • Board snapshot reports and the report builder: the board pack is a PDF built from live posture, top open risks and loss exposure.
  • Ten integrations, so the consoles they open every morning feed one posture grade.
  • A risk register with FAIR loss estimates in dollars.

Command adds maturity models scored against a target profile and the board deck generator.

Next step: Offer the 30-day trial on Essentials and suggest they connect the first tool the same day. Ask when the next board meeting is and book a follow-up a week before it.

This page is the product manual, published from the repository at docs/user/playbooks/cisos.md. Customers read the same text inside CMDash under Help. Last updated November 15, 2026.

Walkthrough playbook: CISOs and security leaders — CMDash Docs