Skip to main content
DocsWalkthrough playbooksWalkthrough playbook: Ports and terminals

Walkthrough playbook: Ports and terminals

A walkthrough of CMDash for ports and terminals, run in the live sandbox in about 18 minutes. It is written for the CMDash sales team and for partners who present the product.

Who this is for

A facility security officer, an IT or OT manager, or a compliance lead at a port authority or terminal operator. Terminal operating systems, cranes and gate systems now fall under cyber rules alongside corporate IT.

What they are tired of

  • "Cranes, gates and the terminal system are under cyber rules now, and they were never in IT's inventory."
  • "We would find out the reporting deadline in the middle of the incident."

What it costs them: A facility plan with no evidence behind it, and deadlines discovered late.

The line to open with: "Bring cranes, gates and terminal systems under one cyber 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. Each facility as a unit (3 min)

  • Go to: Maritime → Fleet (/maritime/fleet), in your demo organization
  • Show: Facilities as units, rolled up across sites; open one.
  • Say: "Each port facility is a unit with its own profile and control status, rolled up across your sites."

2. The Coast Guard rule (4 min)

  • Go to: Compliance → Frameworks (/compliance), open USCG Cybersecurity in the Marine Transportation System
  • Show: The plan, the officer, training, assessment, drills and incident reporting as controls, with the regulation text.
  • Say: "The rule as a list of requirements, each with the regulation text, an owner, a status and evidence. For a facility in Europe, NIS2 sits beside it."

3. Work once (3 min)

  • Go to: Compliance → Control mappings (/control-mappings)
  • Show: The Coast Guard rule mapped to NIST CSF 2.0 and ISO 27001.
  • Say: "Work done against the Coast Guard rule carries to the NIST CSF and ISO 27001 controls that overlap."

4. Reporting deadlines (3 min)

  • Go to: Security → Incidents (/incidents), in the sandbox
  • Show: An incident record with reporting clocks.
  • Say: "The incident record carries the deadlines you add, the National Response Center report among them. You choose the regimes. CMDash tracks the clock and does not file the report."

5. Vendors with access (3 min)

  • Go to: Security → Vendors (TPRM) (/vendors)
  • Show: The vendor register.
  • Say: "The crane, gate and terminal system vendors and contractors with remote access, each with an owner."

6. Findings and risk (2 min)

  • Go to: Security → POA&M (/poam), then Security → Risk register (/risks)
  • Show: Tracked actions and a loss estimate.
  • Say: "Findings become actions with owners and dates, and outage scenarios carry a loss estimate in dollars."

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.

"Does it write our Cybersecurity Plan?"

No. It tracks each requirement of the rule with its owner, status and evidence. The plan is theirs to write and submit.

"We are in the EU, not the US."

Track NIS2 and ISO 27001 for the facility. The unit model is the same.

Command. The reasons, as they appear at the foot of the public page:

  • Facility units: each port facility has its own profile and control status, rolled up across sites.
  • The framework crosswalk engine: work once against the Coast Guard rule and the status carries to the NIST CSF 2.0 and ISO 27001 controls that overlap.
  • Incident reporting clocks for the regimes they choose, the National Response Center report among them.

Enterprise adds monitored third-party risk management for equipment vendors and contractors.

Next step: Offer the 30-day trial on Command and suggest setting up one facility as a unit. Ask when their next assessment or drill is due.

This page is the product manual, published from the repository at docs/user/playbooks/ports-and-terminals.md. Customers read the same text inside CMDash under Help. Last updated November 15, 2026.

Walkthrough playbook: Ports and terminals — CMDash Docs