Comparison Overview
Manta Marine Technologies
Manta Marine Technologies
Drammensveien 134, Oslo, undefined, undefined, NO
Last Update: 03/02/2026
Manta Marine Technologies has been at the forefront of maritime emissions reduction since 2010. We are working closely with ship-owners, yards, and naval architects as partners in our effort to drive the change toward sustainable shipping. We offer a comprehensive po...
Hapag-Lloyd AG
Ballindamm 25, Hamburg, DE, 20095
Last Update: 01/04/2026
About Hapag-Lloyd With a fleet of 313 modern container ships and a total transport capacity of 2.5 million TEU, Hapag-Lloyd is one of the world’s leading liner shipping companies. In the Liner Shipping segment, the Company has around 14,000 employees and 400 offices in ...
Compliance Ranges Comparison
Manta Marine Technologies
Hapag-Lloyd AG
Benchmark & Cyber Underwriting Signals
Incidents vs Maritime Transportation Industry Avg (This Year)
No incidents recorded for Manta Marine Technologies in 2026.
Incidents vs Maritime Transportation Industry Avg (This Year)
No incidents recorded for Hapag-Lloyd AG in 2026.
Incident History - Manta Marine Technologies (X = Date, Y = Severity)
Manta Marine Technologies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hapag-Lloyd AG (X = Date, Y = Severity)
Hapag-Lloyd AG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Manta Marine Technologies
Hapag-Lloyd AG
FAQ
Latest Global CVEs
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an inadequate encryption strength vulnerability which could allow an attacker to steal admin credentials via weak hash or a pass-the-hash attack.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could allow for asset discovery by unauthenticated users.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.
Pronetiqs IntraVUE Versions 3.2.1a14 and prior have a plaintext storage of a password vulnerability that could expose cleartext credentials through the API.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.