Walkthrough playbook: Retail and e-commerce
A walkthrough of CMDash for retailers and online merchants, 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/retail-and-ecommerce
- Recommended plan: Essentials
- Length: about 18 minutes, 6 steps
- Read first: Before any walkthrough
Who this is for
An IT or security lead at a retailer or online merchant. PCI DSS is the fixed point, privacy law surrounds it, and everything is harder in the weeks before peak season.
What they are tired of
- "The PCI assessment, the privacy requests and peak season all land at once."
- "I don't know which of forty open items matters before Black Friday."
What it costs them: Fixes chosen by whoever shouts loudest, right before the busiest trading days.
The line to open with: "Go into peak season knowing what is fixed and what is not." 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, what needs attention and what is due.
- Say: "This is the page for the weeks before peak: what is open and what is due."
2. PCI DSS and what surrounds it (4 min)
- Go to: Compliance → Frameworks (
/compliance), open PCI DSS - Show: Control status with evidence.
- Say: "PCI DSS control by control, with GDPR and SOC 2 beside it on the same evidence. Essentials tracks five frameworks."
3. What to fix before peak (3 min)
- Go to: Security → Risk register (
/risks) - Show: Risks ranked, one opened.
- Say: "The ranked list. Before a code freeze, this is how you choose the three things that get done."
4. Your brand in other people's inboxes (3 min)
- Go to: Security → Domain posture (
/exposure/domains), then Security → IP reputation (/exposure/ips) - Show: The e-mail and DNS checks, then blocklist monitoring.
- Say: "Daily checks on the settings that stop someone sending mail as your brand, and on whether your sending addresses have landed on a blocklist. The second is on Essentials."
5. When something happens (3 min)
- Go to: Security → Incidents (
/incidents) - Show: An incident record with reporting clocks.
- Say: "If there is an incident, the record carries the reporting deadlines of the regimes you add, counted from when you became aware. CMDash tracks the deadlines. It does not decide which apply and does not file the report."
6. Platforms and processors (3 min)
- Go to: Security → Vendors (TPRM) (
/vendors) - Show: The vendor register.
- Say: "The platforms, plugins and processors you depend on, each with an owner."
Questions you will get
"Does it scan our checkout page?"
No. CMDash does not scan the payment page or detect skimming. It tracks PCI DSS controls and evidence, and checks e-mail, DNS and IP reputation.
"Does this make us PCI compliant?"
No. It keeps the controls and evidence in order for the assessment or self-assessment questionnaire.
"Can one answer cover PCI and ISO 27001?"
They see the mapping on Essentials. Carrying the status across by itself is on Command.
"We are a small shop."
Starter covers three frameworks, the posture grade and the daily e-mail and DNS checks. Essentials is the recommendation once IP reputation, reporting clocks or five frameworks matter.
Recommended plan and next step
Essentials. The reasons, as they appear at the foot of the public page:
- Five frameworks at once: PCI DSS, GDPR and SOC 2 tracked from one set of evidence.
- IP reputation monitoring and the external reputation score, beside the daily e-mail and DNS checks.
- Incident reporting clocks that track each regulator deadline added to an incident.
Command carries a status from PCI DSS to the ISO 27001 controls that overlap.
Next step: Offer the 30-day trial on Essentials. Ask when their code freeze starts and work back from it.