Walkthrough playbook: Financial services
A walkthrough of CMDash for financial services firms, 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/industries/financial-services
- Recommended plan: Command
- Length: about 18 minutes, 6 steps
- Read first: Before any walkthrough
Who this is for
A CISO, head of IT risk or compliance officer at a bank, credit union, lender, insurer, payment firm or fintech. They answer to several regulators and to their own customers, on overlapping calendars.
What they are tired of
- "NYDFS, DORA, PCI and SOX all examine the same controls, and each examiner wants them their way."
- "The board and the examiner both want risk in dollars, and I have a heat map."
What it costs them: One control prepared several times a year, and exam findings that reappear.
The line to open with: "Stop preparing the same controls for each examiner." 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 grade, the frameworks in scope and what is due.
- Say: "One page for where you stand across every framework you answer to."
2. Every framework, one evidence set (4 min)
- Go to: Compliance → Frameworks (
/compliance) - Show: The frameworks in scope with their progress; open one.
- Say: "Each framework you answer to, control by control. Command has no limit on how many run at once, which matters when you carry NYDFS 500, PCI DSS, SOX ITGC and FFIEC together."
3. Where they overlap (3 min)
- Go to: Compliance → Control mappings (
/control-mappings) - Show: A mapping between two of their frameworks.
- Say: "One control status can serve PCI DSS and ISO 27001 where the crosswalk overlaps, and it carries across by itself on Command. The mapping is visible, so an examiner can see why."
4. Dates you answer to (3 min)
- Go to: Compliance → Regulatory horizon (
/horizon) - Show: The regimes and their dates with readiness mapping.
- Say: "DORA, NYDFS 500 and SEC cyber disclosure dates in one place, with what each asks of you."
5. Risk in dollars (3 min)
- Go to: Security → Risk register (
/risks), then Security → FAIR quantification (/risks/fair) - Show: The ranked risks and one loss estimate.
- Say: "A register with annualized loss estimates, for the board and the examiner. It replaces the heat map with a number someone can challenge."
6. Always ready (3 min)
- Go to: Compliance → Continuous audit (
/continuous-audit), then Compliance → Evidence packages (/evidence/packages) - Show: The rolling evidence window and the package list.
- Say: "Instead of preparing for each exam, you keep a rolling window of evidence that is current, and bundle it when someone asks." Do not download in the sandbox.
Questions you will get
"Is CMDash itself audited?"
Send them to the Trust Center at www.cmdash.com/trust, which states CMDash's own status on SOC 2 and penetration testing. Read it with them; do not summarize it more favorably than it reads.
"Where is our data held?"
CMDash Cloud runs in one commercial AWS region in the United States (us-east-1). If they need data kept elsewhere or in their own account, a self-hosted install is offered on the Enterprise plan in early access; route that to sales.
"We need monitored vendors."
The vendor register on Command holds five vendors without monitoring. Monitored third-party risk management, with 25 vendors included, is on Enterprise.
"Does it cover every rule we have?"
Check the framework list at www.cmdash.com/frameworks with them. A framework that is not listed can be imported as a custom framework on Enterprise.
Recommended plan and next step
Command. The reasons, as they appear at the foot of the public page:
- Unlimited frameworks: NYDFS 500, DORA, PCI DSS, SOX ITGC and FFIEC tracked together.
- The framework crosswalk engine carries one control status to the other frameworks where the controls overlap.
- Continuous audit mode keeps a rolling evidence window, and evidence packages bundle it for an examiner.
Enterprise adds monitored third-party risk management for the vendors they depend on.
Next step: Offer the 30-day trial on Command. If vendor monitoring or data location came up, book sales for an Enterprise conversation instead.