Isidore Quantum®

All-in-One Cybersecurity and Drop in PQC Solution

Beyond the Horizon: Securing Maritime Operations from Cyber and Quantum Threats

Why Isidore Quantum:

Affordable: 70% faster to implement and 60% lower total cost of ownership
Autonomous Cyber Resilience: AI-driven system detects, adapts, and self-heals against evolving threats
Drop-In Integration: Protocol, hardware, interface-agnostic design modernizes legacy networks without infrastructure overhaul
Low-SWaP Advantage: Compact, efficient, and scalable for enterprise, defense, and critical infrastructure use

1) Establish formal mandate for quantum-safe migration (board → fleet → port ops)

L0 — Not started

No owner; PQC not on ISM/ISPS agenda.


L1 — Initial

Champion named (e.g., CISO/CTO), ad-hoc working group.


L2 — Defined

Cross-functional Quantum-Safe Committee with RACI spanning HQ, fleet IT, port OT, legal, procurement.


L3 — Operational & improving

Governance reviews tied to safety & cyber KPIs; minutes feed budget & roadmap updates.


Evidence / KPIs

Approved ToR; committee cadence; inclusion in Safety Management System (SMS).


“Next level” moves

Stand up a formal committee; publish RACI and meeting schedule.

2) Strategic roadmap & resourcing

L0 — Not started

No plan/budget.


L1 — Initial

Draft roadmap exists; pending approval.


L2 — Defined

Multi-year roadmap with milestones for bridge systems, SATCOM, port gates; capex/opex allocated.


L3 — Operational & improving

Execution tracked; roadmap updated quarterly with lessons from pilots and audits.


Evidence / KPIs

Approved roadmap; funding line items; milestone burndown.


“Next level” moves

Approve roadmap; tie to dry-dock/maintenance windows.

3) Integrate quantum risk into enterprise cyber-risk program

L0 — Not started

Quantum risk not considered.


L1 — Initial

Acknowledged, but tracked separately from cyber risk.


L2 — Defined

Incorporated into ERM/CRR alongside ransomware/OT risk; risk owners assigned.


L3 — Operational & improving

Periodic effectiveness reviews; risk appetite & timelines adjusted.


Evidence / KPIs

Risk register entries for HNDL, PQC migration, SATCOM exposure.


“Next level” moves

Merge quantum risks into existing ERM and KRIs.

4) Policies & frameworks (crypto, key mgmt, data)

L0 — Not started

No formal policies.


L1 — Initial

Basic informal practices (e.g., ad-hoc key storage).


L2 — Defined

Documented cryptographic & key-management policies; data classification incl. long-shelf-life data.


L3 — Operational & improving

Policies reviewed with PQC/crypto-agility clauses; change control in place.


Evidence / KPIs

Approved policies; policy review logs; exceptions tracking.


“Next level” moves

Formalize policies; set annual review cycle with PQC updates.

1) Quantum risk assessment & prioritization

L0 — Not started

No assessment.


L1 — Initial

Preliminary scoping on a subset (e.g., AIS/VSAT).


L2 — Defined

Org-wide risk assessment using data value/shelf-life, crypto dependencies, criticality.


L3 — Operational & improving

Continuous reassessment aligned to NIST/ETSI updates & business changes.


Evidence / KPIs

Completed study; heat-map of crown jewels (ECDIS, GMDSS, port SCADA).


“Next level” moves

Expand pilot assessment to all fleets/ports; formalize in risk register.

2) Cryptographic asset management (IT, OT, SATCOM)

L0 — Not started

No inventory.


L1 — Initial

Partial list of systems/keys/certs.


L2 — Defined

Comprehensive CBOM (algorithms, keys, protocols, libraries, HSM/PKI) for vessels, ports, cloud.


L3 — Operational & improving

Automated discovery; inventory kept current; drives migration plan.


Evidence / KPIs

% coverage; discovery tool output; CBOM freshness.


“Next level” moves

Deploy automated discovery; reconcile with CMDB & fleet configs.

1) Quantum risk awareness

L0 — Not started

No awareness.


L1 — Initial

Initial briefings to execs/crews.


L2 — Defined

Role-based program (bridge officers, OT engineers, SOC) aligned to strategy.


L3 — Operational & improving

Effectiveness measured; content updated with latest PQC/IMO guidance.


Evidence / KPIs

Completion & quiz scores; incident drill outcomes.


“Next level” moves

Launch targeted awareness tracks per audience.

2) Competency development (crypto, PQC, OT)

L0 — Not started

Needed skills unknown.


L1 — Initial

Key skills identified (PQC, crypto-agility, SATCOM security).


L2 — Defined

Competency matrix per role; training plan & certifications.


L3 — Operational & improving

Matrix maintained; hiring/upskilling aligned to roadmap & audits.


Evidence / KPIs

Role→skill mapping; % roles upskilled.


“Next level” moves

Publish matrix; fund training & labs.

1) Third-party/vendor quantum risk (shipyard, OEM, SATCOM, port IT)

L0 — Not started

Not assessed.


L1 — Initial

High-risk vendors identified; questionnaires started.


L2 — Defined

Risk-based evaluation incl. data access & crypto posture; CBOMs & PQC roadmaps requested.


L3 — Operational & improving

Integrated into vendor governance; PQC/crypto-agility clauses in RFPs & MSAs.


Evidence / KPIs

% strategic vendors with CBOM/PQC plans; contract clauses present.


“Next level” moves

Update procurement templates with PQC/CBOM requirements.

2) Ecosystem collaboration (MLIT/IMO, ISACs, academia)

L0 — Not started

No engagement.


L1 — Initial

Stakeholders mapped (e.g., ISACs, standards bodies).


L2 — Defined

Active participation & knowledge sharing; lessons from pilots.


L3 — Operational & improving

Thought leadership; contributions to industry guidance.


Evidence / KPIs

Event participation; publications; working-group roles.


“Next level” moves

Join sector ISACs/standards roundtables; present pilot findings.

3) Promote standards & guidelines

L0 — Not started

Not monitored.


L1 — Initial

Tracks NIST PQC, ETSI QSC, IMO cyber.


L2 — Defined

Promotes adoption internally/with partners.


L3 — Operational & improving

Recognized adopter; shares implementation lessons.


Evidence / KPIs

Standards watchlist; adoption roadmap.


“Next level” moves

Build/adopt standards watchlist tied to roadmap.

4) Talent pipeline (Japan)

L0 — Not started

No initiatives.


L1 — Initial

Exploring university/industry tie-ups.


L2 — Defined

Active collaborations (internships, labs on PQC/OT security).


L3 — Operational & improving

Co-sponsoring impactful programs; tracked outcomes.


Evidence / KPIs

# interns; conversion rates; co-authored work.


“Next level” moves

Launch an academia partnership focused on PQC for OT/SCADA.

1) Technology experimentation & PoCs (bridge/port/space links)

L0 — Not started

No PQC or crypto-agility pilots.


L1 — Initial

Early PoCs on PQC/hybrid for AIS/GPS/VSAT or port SCADA.


L2 — Defined

Use-case-driven pilots aligned to roadmap; performance/latency baselined.


L3 — Operational & improving

Operational adoption; monitoring & optimization in production.


Evidence / KPIs

Pilot reports; latency KPIs across VSAT and gateway hops.


“Next level” moves

Select 2–3 high-impact use cases (ECDIS auth, SATCOM tunnel, port gate PLC) and launch PoCs.

2) Cryptographic agility by design

L0 — Not started

Not considered.


L1 — Initial

Concept acknowledged; options explored.


L2 — Defined

Approach documented (modular crypto APIs, hybrid classical+PQC, re-keying).


L3 — Operational & improving

Agility implemented; updated with NIST/ETSI/CNSA changes.


Evidence / KPIs

Architecture docs; code scans; config drift metrics.


“Next level” moves

Define agility patterns and embed in build/patch pipelines.

A) Quantum-resilient comms for AIS/GPS/VSAT & port OT

L0 — Not started

Rely on RSA/ECC & aging PKI; manual keys; flat networks.


L1 — Initial

Pilots of CNSA-aligned PQC tunnels; initial network segmentation.


L2 — Defined

Drop-in cryptographic upgrade for ship/port links; AI-enabled anomaly detection; zero-trust controls.


L3 — Operational & improving

Fleet-wide/port-wide rollout with centralized orchestration & self-healing; continuous compliance to IMO/ISO.


Evidence / KPIs

% links protected; time-to-rekey; false-positive rate.


“Next level” moves

Start with bridge systems, port command centers, satellite gateways using drop-in PQC appliances proven in maritime.

B) Japan context & recent incidents

L0 — Not started

No recognition of AIS spoofing/HNDL exposure.


L1 — Initial

Incident briefs circulated; basic mitigations planned.


L2 — Defined

Controls tuned for AIS/GPS integrity; HNDL risk prioritized in risk register.


L3 — Operational & improving

Drills & monitoring confirm resilience against spoofing and decrypt-later threats.


Evidence / KPIs

Post-incident actions; drill results; audit findings.


“Next level” moves

Use Eclipse AIS incident as a driver for exec buy-in and schedule near-term mitigations.