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.

Vendor security assessment · owners and DPAs

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

HostingEncryptionAccessIncidentsGovernanceExit

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.

30%of breaches involved a third party, double the year beforeVerizon DBIR 2025
53%of maritime professionals are confident they see their supply chain’s cyber weak pointsDNV Maritime Cyber Priority 2024/25
241 daysaverage time to identify and contain a breachIBM Cost of a Data Breach 2025
2021IMO MSC.428(98)Cyber risk in the SMS by the first annual DOC verification after 1 Jan 2021
Jul 2024IACS UR E26 / E27Cyber resilience for ships contracted for construction from 1 July 2024
Nov 2024Industry guidelines v5The joint industry Guidelines on Cyber Security Onboard Ships, version 5
2025MSC-FAL.1/Circ.3/Rev.3IMO’s revised maritime cyber risk guidelines approved
2025–27US Coast Guard ruleUS-flag vessels: incident reporting from 16 Jul 2025, training by 12 Jan 2026, approved plan by 16 Jul 2027

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.

1Device on boardIs offline data encrypted on the device? What happens if it is lost?
2Ship-to-shore syncIs the link encrypted? Does sync work over VSAT and LEO without opening extra ports?
3Vendor cloudWhich provider and region? Who at the vendor can see your records?
4Users and partnersWho signs in, how, and what can a shared report link expose?

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.

ClaimEvidence to requestWeak 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 deviceEncryption mentioned for transit only
“We test our security”Summary letter from an independent penetration test, with date and how findings were fixedInternal scans only, or a test more than two years old
“Only you see your data”Policy for vendor staff access, plus a sample access logNo log of who at the vendor viewed records
“We back up daily”Backup policy with the date and duration of the last restore testBackups taken but restores never tested
“You own your data”Contract clause on export format, timing and destruction on exitExport “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.

Hour 0
Detect and containVendor monitoring flags the event; affected access is cut off
Within 24 h
First notice to youWhat happened, which systems, whether your data may be involved, a named contact
Within 72 h
Detailed reportRecords affected, actions taken, what you need to do on board and ashore
Recovery
Restore and confirmService and data restored from backup; integrity checked
Close-out
Root cause and fixesWritten root cause and corrective actions you can file with your own records

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.

No documents, only promisesSecurity answers given verbally, with nothing in writing.
Borrowed certificationThe cloud provider’s certificate offered in place of the vendor’s own.
Shared admin accountsVendor staff use common logins to reach customer data.
No notice commitmentThe contract says nothing about telling you of an incident.
Hostage dataExport only as PDF, or only at extra cost when you leave.
Offline means unprotectedData stored on devices with no encryption or remote wipe.

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.

A
Security scheduleThe measures the vendor described, attached as a contract schedule
B
Incident noticeA fixed time to notify you, and a duty to cooperate with your investigation
C
Sub-processorsA current list and advance notice of changes, with a right to object
D
Audit rightYearly evidence, such as a renewed certificate or report, on request
E
Data locationAgreed hosting region, with no move without your consent
F
Exit and returnFull export in open formats, then destruction with written confirmation

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.

Vendor security review · exampleStandard review · 4 open findings
Hosting
5/5Evidence filed
Encryption
3/41 finding
Access
5/5Evidence filed
Incidents
3/52 findings
Governance
4/51 finding
Exit
5/5Evidence filed
Checklist as a templateRun the same six-area review on every vendor.
Evidence on each itemCertificates, reports and policies kept with the answer.
Findings to close-outGaps get an owner and a due date, like any inspection finding.
Role-based accessShip and shore roles with an audit trail on signed records.

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.