Walkthrough playbook: Cruise lines
A walkthrough of CMDash for cruise lines, 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/cruise-lines
- Recommended plan: Command
- Length: about 18 minutes, 6 steps
- Read first: Before any walkthrough
Who this is for
A fleet IT or cyber security lead, a marine operations manager or a compliance officer at a cruise line. One ship holds operational technology, a hotel, payment systems and guest networks, and several regimes each ask about a different part.
What they are tired of
- "The engine room, the hotel and the shore office each answer to a different rule, on the same ship."
- "The CVSSA records, the class documents and the Coast Guard plan are kept by three different people."
What it costs them: Evidence kept three times, and gaps where the networks meet.
The line to open with: "One set of evidence for the ship's systems, the hotel and the shore office." 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 sandbox company is a technology firm with no vessels or facilities. For the Maritime steps use a prepared Command demo organization with two or three units added at Maritime → Fleet, a few ship systems and a zone. Use the sandbox for everything else.
- Open the free applicability tool (www.cmdash.com/tools/maritime-cyber-applicability) in a second tab.
- Two things to say every time: which instruments apply is for their classification society, flag state and counsel to decide, and IACS and IMO wording in CMDash is a paraphrase while US federal text is verbatim.
The walkthrough
1. The fleet at a glance (3 min)
- Go to: Maritime → Fleet (
/maritime/fleet), in your demo organization - Show: The fleet matrix: one row per ship with control status per framework.
- Say: "One profile and one control status per ship, rolled up so the fleet reads at a glance."
2. One ship (3 min)
- Go to: Open a unit from the matrix
- Show: The ship's profile and applicability table.
- Say: "For this ship: what is likely to apply, with the citation, and where it stands on each."
3. UR E26 and the CVSSA duties (4 min)
- Go to: Compliance → Frameworks (
/compliance), open IACS UR E26, then the Cruise Vessel Security and Safety Act - Show: Controls with owner, status and evidence.
- Say: "UR E26 for the ship's computer-based systems, and the CVSSA records duties, such as video retention and the stateroom-access log, with the statute text on each row. Each has an owner and its evidence."
4. Systems and zones (3 min)
- Go to: Maritime → Ship systems (
/maritime/cbs), then Maritime → Security zones (/maritime/zones) - Show: The inventory and the zones, with the findings where guest or crew networks touch ship systems.
- Say: "This is where the hotel side meets the ship side. The zones and conduits are checked against the UR E26 zone rules, and the documents a class society asks to see are kept per ship."
5. When something happens (3 min)
- Go to: Security → Incidents (
/incidents), in the sandbox - Show: An incident with reporting clocks.
- Say: "The incident record carries the deadlines of the regimes you choose: the Coast Guard's report to the National Response Center, the CVSSA's FBI report, NIS2 and others. CMDash tracks the clock. It does not decide which apply and does not file."
6. The board (2 min)
- Go to: Reports → Exports (
/exports) - Show: The Board Pack.
- Say: "Posture, top open risks and loss exposure for the board, from the same data."
Questions you will get
"Does CMDash tell us which rules apply?"
It shows the instruments likely to apply to a unit from its type, size, voyages, flag and dates, with the citation for each. It is not legal advice. The classification society, flag state and counsel decide.
"Our ships have poor connectivity."
Controls, statuses, owners and documents are kept ashore in the company's organization, and evidence can be uploaded by hand. Do not describe any shipboard collector on the call.
"Does it monitor shipboard OT?"
No. It is the record: the inventory, the zones, the controls and the evidence. It does not scan or monitor shipboard networks.
"Does it cover guest data and payments?"
PCI DSS and GDPR are in the framework list and run on the same evidence. Track them beside the maritime frameworks.
Recommended plan and next step
Command. The reasons, as they appear at the foot of the public page:
- Fleet units: one profile and one control status per ship, rolled up so the fleet reads at a glance.
- The framework crosswalk engine: work once against UR E26 and the status carries to the ISO 27001 and NIST CSF 2.0 controls that overlap.
- Incident reporting clocks for the regimes they choose, on the incident record.
Enterprise adds monitored third-party risk management for makers and service providers with access to the ships.
Next step: Offer the 30-day trial on Command and suggest setting up one ship as a unit first. Ask which survey or audit is next.