Walkthrough playbook: Maritime equipment suppliers
A walkthrough of CMDash for makers of shipboard systems, 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/maritime-equipment-suppliers
- Recommended plan: Command
- Length: about 18 minutes, 6 steps
- Read first: Before any walkthrough
Who this is for
A product security lead, an engineering manager or a quality manager at a maker of shipboard computer-based systems. Shipyards and owners ask for UR E27 documentation per system, and enterprise customers send their own security reviews.
What they are tired of
- "Every shipyard asks for the UR E27 documents per system, and we assemble them by hand each time."
- "Nobody can say which documents exist for which product version."
What it costs them: Engineering time spent on paperwork for every order.
The line to open with: "Have the UR E27 package ready when the shipyard asks." 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. UR E27 as a framework (3 min)
- Go to: Compliance → Frameworks (
/compliance), open IACS UR E27 - Show: The maker documents, the security capabilities and the secure development lifecycle as rows with owner, status and evidence.
- Say: "UR E27 as a list: what a maker documents, builds in and tests. Each row has an owner and the evidence behind it."
2. Per system (4 min)
- Go to: Maritime → Ship systems (
/maritime/cbs), in your demo organization - Show: The system inventory with the UR E27 fields.
- Say: "Each product is a system here, with the fields UR E27 asks a maker to supply."
3. The ten documents (4 min)
- Go to: Open a system, then its maker documents
- Show: The tracker: ten UR E27 documents and which are held.
- Say: "For each system, the ten documents and which you hold. When the shipyard asks, the package is a list you already keep, not a week of collecting."
4. Evidence for the lifecycle (3 min)
- Go to: Compliance → Evidence (
/evidence), in the sandbox - Show: Evidence items from code and build tools.
- Say: "The secure development lifecycle rows need evidence. It comes from the tools you connect, such as your code platform, on a schedule."
5. The next framework (2 min)
- Go to: Compliance → Control mappings (
/control-mappings) - Show: UR E27 mapped to ISO 27001 and NIST CSF 2.0.
- Say: "If a customer asks for ISO 27001, the UR E27 work counts toward it where the controls overlap."
6. Fixes before release (2 min)
- Go to: Security → Risk register (
/risks) - Show: Ranked risks.
- Say: "A register that ranks what to fix before the next release."
Questions you will get
"Does it generate the documents?"
No. It tracks which of the ten documents exist for each system and holds the evidence. The documents are theirs.
"Does it test our product?"
No. It does not scan firmware or test a product. It tracks requirements, documents and evidence.
"We are small. Why Command?"
The maker documentation tracker and the system inventory are part of the maritime unit features, which are on Command. UR E27 as a framework alone can be tracked on any paid plan.
"What about the Cyber Resilience Act?"
It is a pressure they face for products outside marine equipment; it is not in the framework list. Do not imply coverage.
Recommended plan and next step
Command. The reasons, as they appear at the foot of the public page:
- The maker documentation tracker: which UR E27 documents are held for each system.
- A computer-based-system inventory with the fields UR E27 asks makers to supply.
- The framework crosswalk engine: work once against UR E27 and the status carries to the ISO 27001 and NIST CSF 2.0 controls that overlap.
If they only need UR E27 tracked as a framework, a lower plan holds it; say so.
Next step: Offer the 30-day trial on Command and suggest entering one product as a system and marking the documents they already hold.