Walkthrough playbook: Maritime overview
A walkthrough of CMDash for a maritime organization you are meeting for the first time, 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/maritime
- Recommended plan: Command
- Length: about 18 minutes, 6 steps
- Read first: Before any walkthrough
Who this is for
A first conversation with a maritime organization when you do not know which kind it is: a ship operator, a cruise line, a port or a maker. Often a superintendent, a DPA, a fleet IT manager or a company security officer. Use this playbook to find out, then switch to the specific one.
What they are tired of
- "Class, flag, the Coast Guard and NIS2 each write rules for a different thing: the ship, the facility or the company."
- "We have one binder per ship and nobody sees the fleet."
What it costs them: Each rule answered from a separate file, and no view across ships or sites.
The line to open with: "One cyber record for every ship, facility and rule." 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. Which rules reach which unit (3 min)
- Go to: www.cmdash.com/tools/maritime-cyber-applicability
- Show: Enter a vessel like one of theirs: type, tonnage, voyages, build contract date, flag.
- Say: "Start with the question everyone asks first: which of these apply to this ship. This is free and public. It shows what is likely to apply with the citation for each, and it says plainly that it is not legal advice."
2. The fleet as units (4 min)
- Go to: Maritime → Fleet (
/maritime/fleet), in your demo organization - Show: The fleet matrix; open one unit to show its profile and applicability table.
- Say: "Each vessel or port facility is a unit with its own profile, its own applicability check and its own control status, rolled up here. This is the view you do not have today."
3. The maritime frameworks (3 min)
- Go to: Compliance → Frameworks (
/compliance) - Show: IACS UR E26 and E27, IMO guidance, the Coast Guard rule; open one.
- Say: "The frameworks are tracked control by control with an owner, a status and evidence, like any other framework. Ship-level ones are assessed per unit."
4. Systems and zones (3 min)
- Go to: Maritime → Ship systems (
/maritime/cbs), then Maritime → Security zones (/maritime/zones) - Show: The inventory, then zones and conduits with the findings the zone rules raise.
- Say: "The computer-based-system inventory with the fields UR E27 asks makers to supply, and the zones and conduits for each vessel, checked against the UR E26 zone rules."
5. The rest of the program (3 min)
- Go to: Overview → Home (
/home) and Compliance → Control mappings (/control-mappings), in the sandbox - Show: Home, then a mapping to NIST CSF 2.0 or ISO 27001.
- Say: "Maritime sits in the same place as the rest of your program. The maritime frameworks are crosswalked to NIST CSF 2.0 and ISO 27001, and to NIS2 for company-level obligations."
6. Which playbook next (2 min)
- Show: Ask: ships, a cruise line, a port, or a maker?
- Say: "Tell me which of these you are, and I'll show you the part built for you."
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.
"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.
"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.
"Is the IMO guidance mandatory?"
IMO's cyber guidance is non-mandatory. Say exactly that; the framework page says the same.
Recommended plan and next step
Command. The reasons, as they appear at the foot of the public page:
- Fleet and facility units: each vessel or port facility has its own profile, applicability check and control status.
- The OT inventory and security zones per vessel, with the UR E26 and UR E27 documents they export.
- The framework crosswalk engine carries a maritime control status to the NIST CSF 2.0 and ISO 27001 controls that overlap.
The maritime frameworks themselves can be tracked on any paid plan within its framework limit; the fleet units, inventory and zones need Command.
Next step: Book the specific walkthrough (ship operators, cruise lines, ports or equipment suppliers) and offer the 30-day trial on Command.