Walkthrough playbook: Ship operators and owners
A walkthrough of CMDash for ship operators and owners, 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/ship-operators
- Recommended plan: Command
- Length: about 18 minutes, 6 steps
- Read first: Before any walkthrough
Who this is for
A technical superintendent, a DPA, a company security officer or a fleet IT manager at a ship owner or operating company. They answer for each ship to class and flag, and for the company to the safety management system and, in Europe, NIS2.
What they are tired of
- "Class wants the ship's documents, flag wants the plan, and NIS2 wants the company."
- "Each requirement is answered by a different person from a different file."
What it costs them: No fleet view, and maker documents chased ship by ship.
The line to open with: "Answer class, flag and company cyber rules from one fleet record." 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. A unit per ship (3 min)
- Go to: Maritime → Fleet (
/maritime/fleet), in your demo organization - Show: The fleet matrix; open a ship.
- Say: "A unit per ship, with its own applicability check and control status, rolled up into one fleet view."
2. The inventory class asks for (4 min)
- Go to: Maritime → Ship systems (
/maritime/cbs) - Show: The system inventory, the CSV import and the UR E26 vessel asset inventory export.
- Say: "The computer-based-system inventory, with the fields UR E27 asks makers to supply. You can import it from a CSV, and it exports as the UR E26 vessel asset inventory." Do not export in the sandbox.
3. Maker documents (3 min)
- Go to: Open a system, then its maker documents
- Show: The ten UR E27 maker documents for the system and which are held.
- Say: "For each system, the ten documents UR E27 expects from its maker, and which you hold. This replaces the e-mail chase."
4. Zones and conduits (3 min)
- Go to: Maritime → Security zones (
/maritime/zones) - Show: Zones, conduits and the findings.
- Say: "Zones and conduits per vessel, checked against the UR E26 zone rules, and exported with the inventory and exceptions as one documentation pack."
5. Company-level rules (3 min)
- Go to: Compliance → Frameworks (
/compliance), open IMO Maritime Cyber Risk Management or NIS2 - Show: Company-level controls.
- Say: "The company side: the IMO guidance you fold into the safety management system, and NIS2 for the company, not the ship. Same record, different level."
6. Carry it across (2 min)
- Go to: Compliance → Control mappings (
/control-mappings) - Show: UR E26 mapped to ISO 27001 and NIST CSF 2.0.
- Say: "If the company also holds ISO 27001, the UR E26 work counts toward it where the controls overlap."
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 UR E26 apply to our existing ships?"
That depends on the build contract date and is for class to confirm. Run the applicability tool with them and read the citation it gives.
Recommended plan and next step
Command. The reasons, as they appear at the foot of the public page:
- Fleet units: a unit per ship with its own applicability check and control status, rolled up into one fleet view.
- The vessel asset inventory, security zones and the UR E27 maker document tracker, per ship.
- The framework crosswalk engine carries control status from UR E26 to the ISO 27001 and NIST CSF 2.0 controls that overlap.
Enterprise adds monitored third-party risk management for makers and service providers.
Next step: Offer the 30-day trial on Command. Suggest importing one ship's system list from the spreadsheet they already keep.