Which European companies support undersea cable and infrastructure protection?

Thales DMS France coordinates SEACURE development; Fincantieri has announced DEEP; Sonardyne commercialises Sentinel, designed by Wavefront Systems; Helsing introduced Lura and SG-1 Fathom in 2025. These companies cover different integration, sensing and autonomy roles. Their public evidence ranges from development programmes to product announcements; operational readiness, authorised response and repair require separate assessment.

Match protection requirements to industrial roles

The useful market boundary is the operator's need. Monitoring a cable landing area, inspecting a long offshore route and restoring a damaged connection require different resources. A sensor supplier may support detection without supplying inspection vessels or cable-repair services. An integrated defence system may address threats without managing the civilian operator's restoration arrangements. The procurement should describe the operational outcome and the responsibility at each stage before assembling a list of companies.

Thales' integration role has a clear programme reference. The European Commission’s SEACURE project factsheet identifies Thales DMS France as coordinator of a development project for integrated unmanned systems supporting anti-submarine and seabed operations and protection of critical maritime infrastructure. The consortium includes several European industrial actors. This is evidence of a funded development role and an integration objective. It is not proof that a complete operational cable-protection service is already available under that project.

Fincantieri's DEEP announcement describes a different public industrial proposition: underwater sensors, command and control, autonomous vehicles and data analysis within an integrated infrastructure-protection system. Its stated applications include critical underwater infrastructure and port areas. For a buyer, the next questions concern the offered configuration, deployment evidence, interfaces and support responsibility. A product launch establishes the supplier's proposition, while acceptance trials and contractual commitments establish what the customer can rely on at a particular site.

Sentinel, Lura and SG-1 Fathom

Sonardyne's Sentinel product page identifies a specialised threat-detection role around vessels, ports and infrastructure. The page states that the system is designed by Wavefront Systems and commercialised by Sonardyne. That distinction matters when mapping technology ownership, integration and support responsibilities. The product's published detection claims are supplier statements, not a substitute for site-specific acceptance. Water conditions, installation geometry and the operator's response process belong in the procurement evaluation rather than being inferred from a maximum-range figure.

Helsing's 2025 Lura and SG-1 Fathom announcement introduced software and autonomous underwater gliders for persistent surveillance. This places it in the autonomy and data-processing layer of the landscape. The announcement describes an intended operational approach and company demonstrations; it does not establish every later deployment or independently validate its comparative performance claims. The buyer should request evidence relevant to the proposed environment, including the human decision process and the support needed to keep the system operating.

Integration responsibility and operational readiness

These examples reveal why industrial roles should remain separate. Integration, acoustic sensing, autonomous operations and data interpretation can sit in different organisations. The customer needs to know who owns the interfaces, maintains the software and resolves an inconclusive alert. A monitoring system that produces data but has no agreed escalation route may add workload without improving response. The commercial specification should therefore connect technical outputs with named operational responsibilities and the records required to assess performance.

Readiness also includes sustainment and service continuity. Offshore assets need deployment, recovery, maintenance and access to suitable vessels and personnel. A demonstration under planned conditions does not establish availability during a simultaneous regional disruption. Contracts should identify which resources are dedicated, shared or obtained through subcontractors and how priority is determined. This is also relevant to an investor: product capability and a scalable service model are different sources of execution risk.

The resulting supplier landscape should record the role, evidence level and unresolved dependency for each candidate. A research consortium, a product announcement, a customer acceptance and a continuing service contract belong in different categories. Corporate location, ownership and export permissions need separate verification where they affect procurement eligibility. With these distinctions, the map becomes a practical basis for engagement: it shows which companies can address each requirement and which parts of protection, response and repair still need another counterparty. Its usefulness depends on keeping those evidence categories explicit and current.