Inspection reports, crew records, vessel photos and audit findings all end up on a vendor’s servers once you buy fleet software. This checklist helps owners test a vendor on hosting, encryption, access control, incident response and exit before any data moves, and shows what evidence to ask for at each step. Book a free demo and bring the list.
Marine software security due diligence: check the vendor before your fleet data moves
Six areas, the evidence that proves each one, and the contract terms that keep the answers true after you sign.
The six areas
Why software security due diligence is now part of an owner’s job
Cyber risk stopped being only an IT topic when IMO required it in the safety management system. A cloud inspection or maintenance platform is part of that risk, and vendors are now a common way in. Our explainer on MSC.428(98) and IACS UR E26/E27 covers the rules in depth. Try the platform free.
Map the data before the maritime cyber risk vendor review
You cannot judge security without knowing where the data goes. Trace one inspection from the device on board to every place it ends up, and ask two questions at each step: where is it, and who can reach it. If you also plan to connect other systems, our API integration guide for shipowners covers that link. Walk the data flow with us.
Vendor security assessment checklist: six areas to tick off
Work through each area with the vendor, and tick an item only when you have seen the evidence, not just heard the answer. Keep the evidence with your assessment record.
01Hosting and data location
02Encryption
03Access control
04Monitoring and incident response
05Governance and assurance
06Resilience and exit
Data security in shipping software: evidence that proves each answer
A questionnaire tells you what the vendor says; documents tell you what is true. Use the right-hand column to spot answers that need a follow-up. For data rights in the contract, read our guide to data ownership and lock-in. Start a free trial.
| Claim | Evidence to request | Weak answer to follow up |
|---|---|---|
| “We are certified” | ISO/IEC 27001 certificate with scope, issuer and expiry date, or a SOC 2 Type II report under NDA | “Our cloud provider is certified”, or a scope that leaves out the product |
| “Your data is encrypted” | Written description of encryption in transit, at rest and on the device | Encryption mentioned for transit only |
| “We test our security” | Summary letter from an independent penetration test, with date and how findings were fixed | Internal scans only, or a test more than two years old |
| “Only you see your data” | Policy for vendor staff access, plus a sample access log | No log of who at the vendor viewed records |
| “We back up daily” | Backup policy with the date and duration of the last restore test | Backups taken but restores never tested |
| “You own your data” | Contract clause on export format, timing and destruction on exit | Export “on request” at extra cost, PDF only |
Bring this checklist to your vendor demo
Ask us every question on this page, and we will show how inspection data is handled from the device on board to the shore office.
Incident response: what a fleet software vendor should tell you, and when
Ask the vendor to walk through a real or practice incident. The times below are example contract targets to negotiate, not legal requirements; US-flag operators also have their own duty to report cyber incidents to the National Response Center under the Coast Guard rule.
Scale the review to fleet risk under IMO cyber guidelines
Not every tool needs the same depth. Match the review to what the software touches and what an outage would stop. Our fleet software RFP template shows where these questions fit in a tender.
Basic review
Small fleet, office-only tool, no crew personal data.
- Questionnaire answers
- Certificate or report check
- Export and exit terms
Standard review
Ship and shore use, crew records, audit and inspection findings.
- All six checklist areas
- Evidence documents seen
- Incident terms in contract
Enhanced review
Large fleet, integrations with other systems, vetting or regulator data.
- Pen test summary reviewed
- Integration security checked
- Yearly reassessment agreed
Red flags in a ship software evaluation
Any one of these deserves a direct question. Two or more usually mean the vendor is not ready for fleet data.
Contract terms that keep software security due diligence true
Answers given before signing only count if they are in the contract. These six terms turn the review into obligations.
How Marine Inspection supports your software security due diligence
We answer vendor security questions openly in the demo, and the platform itself can run the review: build this checklist as an inspection template, attach each evidence document to its item, raise findings for gaps and track them to close-out. The board below is an illustrative vendor review.
Software security due diligence FAQs
What is software security due diligence for a shipowner?
It is a structured check of how a software vendor protects your fleet data, covering hosting, encryption, access, incident response, governance and exit, backed by documents rather than verbal answers.
Do the IMO cyber guidelines apply to my software vendors?
The IMO rules apply to the company and its safety management system, not the vendor directly. But cyber risk in the SMS includes the systems you rely on, so vendor risk belongs in your assessment.
Is ISO 27001 or SOC 2 enough on its own?
Either is a strong start, but check the scope covers the product you are buying, check the dates, and still confirm encryption, access, incident notice and exit terms in the contract.
How often should a vendor be reassessed?
At least once a year, and again after a major change such as a new hosting region, a new integration, an acquisition or a security incident.
What should happen to our data when we leave?
You should receive a full export of records and photos in open formats, after which the vendor destroys its copies and confirms it in writing.
Can we review Marine Inspection’s security before buying?
Yes. Book a free demo and bring this checklist; we will walk through each area with you.
Sign off the vendor on evidence, not promises
Run the six-area review, file the proof, and put the answers in the contract before your fleet data moves.