Skip to main content
DocsWalkthrough playbooksWalkthrough playbook: Cyber insurers and underwriters

Walkthrough playbook: Cyber insurers and underwriters

A walkthrough of CMDash for cyber insurers and underwriters, 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

An underwriter, a broker or a risk engineer who asks applicants about their controls. They will not run CMDash; the applicant does. They want to know what they would receive and how far they can rely on it.

What they are tired of

  • "The application says MFA is on everywhere. Nothing on it shows me that."
  • "I get a page of yes and no answers and cannot tell which were measured and which were typed."

What it costs them: Underwriting on answers nobody can tell apart.

The line to open with: "See which application answers were measured and which were typed." 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 walkthrough

1. What the applicant sees (3 min)

  • Go to: Overview → Posture (/posture), in the sandbox
  • Show: The grade and its signals, MFA coverage, time to patch and open critical and high vulnerabilities among them.
  • Say: "This is the applicant's own screen. The grade is computed from the tools it has connected and is recomputed as they change. It is not a form."

2. A receipt (4 min)

  • Go to: Compliance → Proof receipts (/proof)
  • Show: A receipt for a measured control: the statement, the numbers it signs, the dates and the basis label.
  • Say: "When you ask about a control, the applicant can issue a signed receipt. It states the claim, the numbers counted from its tools, when, and on what basis: measured, self-assessed or self-attested. That label is the part that answers your question."

3. Checking it yourself (3 min)

  • Go to: www.cmdash.com/verify
  • Show: The verifier page.
  • Say: "You check the receipt here, without a CMDash account and without calling us or them. A valid receipt proves who signed the statement and that it has not changed. It does not prove the control is effective, and the page says so."

4. The dated record (3 min)

  • Go to: Compliance → Evidence (/evidence)
  • Show: An uploaded evidence item with its history: uploader, time and hash.
  • Say: "Where an answer rests on a document, the document has an append-only history. A control the application says is in place has a record with a date on it."

5. A snapshot they can send (3 min)

  • Go to: Reports → Exports (/exports)
  • Show: Describe the share link: a frozen snapshot of the posture summary through a link that expires, with an optional passcode.
  • Say: "The applicant can send you a frozen snapshot through a link that expires. You are reading what they chose to share, at the moment they shared it."

6. Asking for it (2 min)

  • Go to: www.cmdash.com/for/relying-parties
  • Show: The request templates, the insurance one among them.
  • Say: "If you want to ask applicants in a standard shape, this page shows the templates and how a request works. Asking needs only a Free account."

Questions you will get

"Does a good grade mean a lower premium?"

CMDash has no part in pricing or underwriting and makes no such claim. It gives the underwriter evidence; what they do with it is theirs.

"Can the applicant fake it?"

A receipt marked measured was counted from a connected tool, and one marked self-attested was typed. The label is signed with the rest. It cannot show that the source system told the truth.

"Do I have to buy anything?"

No. Verifying needs no account, and requesting proof needs a Free account.

"Which carriers use this?"

Do not name any carrier, broker or customer. CMDash publishes no customer names.

Starter, for an applicant. The reasons, as they appear at the foot of the public page:

  • The applicant's posture grade is computed from signals such as MFA coverage, time to patch and open critical and high vulnerabilities.
  • Daily e-mail and DNS authentication checks on a domain the applicant has proven it owns.
  • Signed proof receipts and expiring share links are on every plan, Free included.

The recommendation is for an applicant. The insurer needs no paid plan.

Next step: Ask what they request from applicants today and send that through www.cmdash.com/contact?topic=insurer. Point them to the relying-parties playbook if they want to send requests themselves.

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

Walkthrough playbook: Cyber insurers and underwriters — CMDash Docs