Cybersecurity High Speed Internet US Navy: Inside the Fleet’s Real Push for Faster, Safer Connectivity
For most of the last thirty years, a warship’s internet connection was something sailors joked about rather than relied on. Slow. Rationed. Prone to dropping the moment it mattered. That’s no longer the story. Over the past two years, the Navy has quietly rewired how its ships talk to the world, swapping decades-old geostationary satellite links for low-Earth-orbit constellations, rebuilding its cybersecurity architecture around zero trust, and fielding new tools built specifically to watch for intrusions on ships at sea. None of this happened in a press conference. Most of it happened through a string of program rollouts, budget requests, and conference panels that only specialists tend to notice.
This is a look at what’s actually happening — not the generic version of the story, but the specific programs, the real numbers, and the tradeoffs the Navy is currently working through as it tries to make cybersecurity high speed internet US Navy infrastructure fast enough to matter and secure enough to trust.
Why the Navy Blew Up Its Old Satellite Model
For roughly three decades, Navy ships depended on a small constellation of Department of Defense satellites sitting in geostationary orbit, about 22,300 miles above the Earth. That distance was the whole problem. A signal traveling up to a satellite that far away and back down again introduces real latency, and the available bandwidth was thin by modern standards. Ships could send and receive essential traffic, but anything resembling consumer-grade internet — video calls, large file transfers, streaming — was out of reach for most of the fleet.
The cracks in that model became impossible to ignore during the COVID-19 pandemic, when port-call restrictions cut ships off from the world for extended stretches and crews had almost no way to stay in touch with home. Around the same period, sailors aboard at least one littoral combat ship reportedly installed a consumer Starlink terminal on their own initiative, well before it was authorized — a workaround that became something of a legend inside the fleet before NAVWAR built a sanctioned alternative. That sanctioned alternative became Sailor Edge Afloat and Ashore, or SEA2, and it’s now the backbone of the Navy’s push toward real high-speed connectivity at sea.
SEA2 began as an ad hoc experiment aboard the aircraft carrier USS Abraham Lincoln, championed by combat systems officer Cmdr. Keven White, who pushed to get Starlink and OneWeb terminals installed and working as fast as possible. Getting there wasn’t trivial. The Naval Information Warfare Systems Command needed satellites with laser crosslink capability so data could hop between satellites before reaching a fixed downlink, and it needed a mobility code so a ship’s terminal could hold its connection while underway. Once those technical pieces were in place, NAVWAR secured a cybersecurity approval that let SEA2 operate fleet-wide for unclassified purposes — something no earlier commercial internet workaround on Navy ships had ever formally received.
The performance difference is not subtle. According to reporting on the system, SEA2 delivers mid-range throughput of 30 to 50 megabits per second per terminal, scalable up to a full gigabit per second by linking multiple Starlink antennas together. Sailors aboard the Abraham Lincoln watched the Super Bowl live via the new network in February 2024, something that would have been unthinkable under the old geostationary architecture. NAVWAR has said SEA2 is now on the cusp of being available on every Navy ship and a growing number of shore sites.
What SEA2 Actually Changes Onboard a Ship
It’s tempting to file SEA2 under “quality of life upgrade” and move on, but that undersells what’s going on. Richard Haninger, a deployed resiliency educator aboard the carrier Gerald R. Ford, put it plainly after SEA2 was installed there in early 2023: having the ability to reach out to friends or family gives sailors “the opportunity to decompress for a few minutes,” which in turn helps them operate more efficiently. That’s morale framing, and it’s real, but it’s only half the picture.
The operational half matters just as much. Legacy shipboard networks have historically struggled to receive timely software patches and threat intelligence updates simply because there wasn’t enough bandwidth to push them out reliably. A ship that couldn’t get patched quickly was a ship carrying known vulnerabilities for longer than it should have. Higher-bandwidth links change that calculus, letting the Navy push security updates, refresh threat feeds, and maintain a stronger security posture across the fleet — assuming the rollout is done correctly, which is very much still a work in progress. There’s also a secondary effect worth noting: offloading morale and administrative traffic onto SEA2 reduces the load on a ship’s other, more sensitive networks, the ones actually carrying combat and navigational data.
It’s worth being honest about the tradeoff buried in all of this. For most of naval history, ships were partially shielded from the wider internet simply by distance and limited satellite bandwidth — a kind of accidental security by isolation. That isolation is now gone by design, and the Navy has been explicit that always-connected also means always-targeted. As of the most recent public reporting, the Navy had not authorized SEA2 for classified data, keeping a firm line between the connectivity that boosts morale and operational convenience and the networks that carry the fleet’s most sensitive information.
Flank Speed and the Navy’s Zero Trust Build-Out
If SEA2 is about getting data to and from ships faster, Flank Speed is about making sure that data — and everyone touching it — is verified at every step rather than trusted by default. Flank Speed is the Department of the Navy’s enterprise cloud service, built on Microsoft’s unclassified Azure and Microsoft 365 Impact Level 5 environment, originally stood up to securely support remote work during the pandemic. It’s since become the proving ground for the Navy’s broader zero trust strategy, and by most public accounts, it’s ahead of schedule.
The numbers here are unusually specific for a defense IT program. Flank Speed protects more than 560,000 identities across the Department of the Navy. It was built around the Department of Defense’s seven zero trust pillars — covering users, devices, applications and workloads, data, networks, automation and orchestration, and visibility and analytics — and as of a November 2024 zero trust newsletter from the DoD CIO’s office, Flank Speed had achieved 151 of 152 required zero trust security activities, including 60 of 61 “Advanced Level” activities that most components aren’t expected to reach for years. Department of the Navy CIO Jane Rathbun described the effort as born out of “a sense of urgency to deliver a secure collaboration and communications platform,” and DoD’s Chief Zero Trust Officer Randy Resnick has held Flank Speed up publicly as a benchmark for the rest of the department.
The Navy hasn’t stopped at IT systems. Acting CTO Justin Fanelli has said the service reduced its number of legacy accepted networks from more than 300 down to 179, and it’s now pushing zero trust principles into operational technology — the physical control systems running things like facility power and industrial equipment — through an effort called MOSAICS, short for More Situational Awareness for Industrial Control Systems. That matters because operational technology has traditionally been assumed safe due to air-gapping, an assumption that rarely holds up in practice. As former Interior Department CISO Lou Eichenbaum put it at a recent federal zero trust forum, a simple compromise on a laptop can allow lateral movement to a critical controller — the likelihood may be lower than a typical IT breach, but the impact can be catastrophic.
SABER: Watching the Ship Itself, Not Just the Network
A newer piece of the puzzle, and one that’s gotten far less press than Starlink or Flank Speed, is a system called SABER — Situational Awareness, Boundary Enforcement and Response. Developed with the Johns Hopkins Applied Physics Laboratory, SABER began fleetwide deployment in 2026 and is built to monitor and defend the systems that keep a ship physically running: hull, mechanical and electrical systems, navigation, and combat systems. This is a meaningfully different target than protecting email or file shares. It’s aimed squarely at the growing vulnerability of naval platforms to cyberattacks that could affect a ship’s actual ability to move, fight, or stay afloat, and it’s specifically pitched at surface ships operating in contested zones.
SABER continuously tracks activity across those critical functions and is designed to autonomously detect potential cyber incidents, then hand crew members a set of response options rather than requiring them to diagnose the problem cold in the middle of an emergency. That design choice reflects something the Navy has learned the hard way across other programs: a monitoring system that only alerts without offering a path to action just adds noise during the exact moment a crew can least afford it.
Where the Navy Is Still Behind
It would be misleading to present all of this as an unbroken success story. A July 2026 piece in the Naval Institute’s Proceedings magazine argues the Navy still lacks a dedicated program executive office with true program management authority over cyber capabilities, and that responsibility for cyber remains fragmented — PEO Digital handles host-based cybersecurity for enterprise IT, while a separate office, PMW-130 under PEO C4I, manages network-based sensors. No single office currently owns the full lifecycle of the tactical offensive and defensive cyber capabilities the fleet actually needs. The piece traces this gap back to a 2018 congressional budget review that found the Navy hadn’t invested in cyber capabilities to the level of the Army or Air Force, and argues the structural problem hasn’t been fully resolved since.
A separate Proceedings analysis has raised a related concern: that the Navy’s shift toward a single information environment — an effort called Project Flank Speed in its broadest sense — needs to be completed and extended to overseas environments, and that integrating Project Overmatch, the Navy’s initiative to connect ships, aircraft, and other platforms into a unified battle network, within the Consolidated Afloat Network Enterprise System is still unfinished work. That system, known as CANES, is effectively the information backbone running on naval platforms today, and the argument is that reliability and access are, in some respects, just as important as pure security — a fleet that locks its data down so tightly that legitimate users can’t get to it in time has traded one failure mode for another.
How the Layers Actually Fit Together
None of these programs work in isolation, and it helps to see how they stack. SEA2 handles the pipe — getting bandwidth to and from ships through commercial low-Earth-orbit satellites. Flank Speed handles identity and access at the enterprise level, verifying users and devices continuously rather than trusting anything by default once it’s inside the perimeter. SABER handles the ship itself, watching the physical and combat systems that SEA2 and Flank Speed were never designed to touch. CANES and Project Overmatch handle how ships, aircraft, and command centers share a common operating picture across the fleet.
| Program | What It Actually Does | Managed By |
|---|---|---|
| SEA2 (Sailor Edge Afloat and Ashore) | Delivers high-speed, low-latency internet via commercial LEO satellites (Starlink, OneWeb) for unclassified use | NAVWAR |
| Flank Speed | Enterprise cloud and zero trust identity platform covering 560,000+ users | PEO Digital, U.S. Fleet Cyber Command |
| SABER | Monitors and defends shipboard hull, navigation, and combat systems from cyber intrusion | Johns Hopkins APL, in partnership with the Navy |
| CANES | Information backbone connecting shipboard networks fleet-wide | Navy PEO C4I |
| Project Overmatch | Links ships, aircraft, and sensors into a shared combat network | Navy, under Joint All-Domain Command and Control |
| MOSAICS | Extends zero trust principles into operational technology and industrial control systems | Department of the Navy |
The gap the Proceedings authors keep flagging isn’t any single piece of that table. It’s that no one office is accountable for how well they all fit together, and in a domain where an adversary only needs one weak seam, that’s not a small concern.
What This Means for the Next Few Years
Two things are true at once. The Navy has made faster, more measurable progress on connectivity and zero trust in the last three years than in the previous fifteen combined — SEA2’s rollout speed, Flank Speed’s zero trust scores, and SABER’s fleetwide deployment all point in the same direction. And at the same time, the people closest to the problem, writing in the Navy’s own professional journal, are warning that the organizational structure behind cybersecurity high speed internet US Navy programs hasn’t caught up to the pace of the technology itself. Both of those facts are going to keep shaping fleet policy for years, particularly as CYBERCOM pushes for a significant increase in artificial intelligence funding for fiscal year 2027, aimed at speeding up threat detection and response across the joint force.
For sailors, the visible change is a ship that finally feels connected to the rest of the world instead of cut off from it. For the systems architects and program officers behind the scenes, the work is far less finished than it looks from the deck.
Frequently Asked Questions
What is SEA2 and how is it different from older Navy satellite systems?
SEA2, or Sailor Edge Afloat and Ashore, is the Navy’s program for delivering high-speed internet to ships using commercial low-Earth-orbit satellite constellations like Starlink and OneWeb, rather than the aging Department of Defense geostationary satellites the fleet relied on for roughly three decades. Because LEO satellites orbit much closer to Earth, the round-trip signal delay is far shorter, which translates into real gains in both speed and responsiveness. Where the old system offered slow, rationed connectivity, SEA2 can deliver tens of megabits per second per terminal, scaling toward a full gigabit per second when multiple antennas are linked, which is why it’s become the centerpiece of most current discussion of cybersecurity high speed internet US Navy infrastructure.
Is Flank Speed the same thing as SEA2?
No, and mixing the two up is a common mistake. SEA2 is about the physical satellite connection getting data to and from a ship. Flank Speed is the Navy’s cloud and identity platform, built on Microsoft 365 and Azure, that governs who and what is allowed to access Navy systems once that connectivity exists. Flank Speed is where the Navy’s zero trust work actually lives, covering more than half a million user identities and aligning with the Department of Defense’s zero trust framework. The two programs are complementary rather than competing: SEA2 provides the pipe, Flank Speed governs what travels through it securely.
Does more bandwidth actually make Navy ships less secure?
It can, if the connectivity outpaces the security controls wrapped around it, which is precisely the tension the Navy has been managing. For decades, limited bandwidth acted as an accidental security barrier simply because there wasn’t much of a target surface to attack. Removing that barrier through programs like SEA2 raises the stakes, which is why the Navy paired the connectivity rollout with a formal cybersecurity approval process before SEA2 went fleetwide, and why efforts like Flank Speed and SABER exist specifically to keep pace with the expanded attack surface. The honest answer is that cybersecurity high speed internet US Navy programs only stay net-positive for security if the defensive layers are built in step with the bandwidth increases, not after the fact.
What does SABER protect that other systems don’t?
SABER is focused on a ship’s physical and operational systems — hull, mechanical and electrical equipment, navigation, and combat systems — rather than office IT or enterprise cloud accounts. Most cybersecurity programs discussed in the context of the Navy, including Flank Speed, are aimed at protecting data, identities, and enterprise applications. SABER exists because a ship’s steering, propulsion, and weapons systems represent a different kind of target, one where a successful intrusion could affect the vessel’s ability to operate rather than just its ability to communicate. Developed with the Johns Hopkins Applied Physics Laboratory, it began fleetwide deployment in 2026 and is specifically aimed at surface ships operating in contested environments.
Why does the Navy still have gaps in its cybersecurity organization if these programs are working?
Program performance and organizational structure are two different things, and defense analysts writing in the Naval Institute’s Proceedings have pointed out that the Navy still lacks a single office with full authority over the lifecycle of its tactical cyber capabilities. Responsibility is currently split between offices like PEO Digital, which handles enterprise IT security, and PMW-130, which manages network-based sensors, with no organization owning the complete picture. That fragmentation doesn’t undo the real progress made through SEA2, Flank Speed, or SABER, but it does mean the next phase of cybersecurity high speed internet US Navy development will likely focus as much on fixing institutional structure as on rolling out new technology.
For readers who want to follow this directly from primary sources, the Department of the Navy’s Chief Information Officer publishes ongoing updates on Flank Speed and zero trust progress at doncio.navy.mil.
Trending Today: Best Software for Lawyers
