General Dynamics Information Technology has taken the Defense Information Systems Agency to the Government Accountability Office, challenging DISA's move to hand roughly $11 billion in additional IT work to incumbent Leidos without competition. GDIT filed the bid protest on July 10, 2026, and GAO docketed the case the same day, with a decision due by October 19, 2026. At issue is DISA's decision to expand the Defense Enclave Services contract to cover migration of the combatant commands' common-use IT onto the Defense Department network, DoDNet, rather than open that scope to other vendors.

Background

Defense Enclave Services is the roughly $11 billion vehicle DISA awarded to prime contractor Leidos to consolidate the fourth estate's fragmented IT environments into a single managed enclave. The original requirement supported more than 370,000 users across DoD's defense agencies and field activities. Since 2022, Leidos has migrated more than 40,000 of those users onto the consolidated environment.

Background

The dispute traces to a May 2026 directive from DoD Chief Information Officer Kirsten Davies ordering DISA to transition all combatant commands onto DoDNet by the end of fiscal 2028. That deadline sits at the center of DISA's contracting rationale. Rather than compete a new task order or turn to an existing enterprise vehicle, DISA determined that folding the combatant-command migration into the standing DES contract was the fastest path to meeting the CIO's timeline. The combatant commands were not part of the original DES population, so DISA is treating the addition as an expansion of an existing award rather than a standalone procurement.

DISA published a noncompetitive justification to support the expansion. The agency concluded the DES contract was "the only viable contracting alternative" and argued that Leidos is "uniquely qualified" to carry out the work. The justification warns that bringing on a new vendor "would face an unacceptably steep learning curve" capable of delaying the migrations, and that recompeting the scope would produce "substantial duplication of administrative and technical cost."

Key Details

DISA's central argument rests on institutional continuity. In its justification, the agency states that "Leidos possesses the crucial requisite institutional knowledge of the 'as-built' environment which ensures the necessary technical continuity required for DISA and the combatant commands to meet the CIO's fiscal 2028 migration deadline." In DISA's telling, the schedule pressure created by the Davies directive leaves no room to absorb the ramp-up time a new contractor would need to learn the existing DoDNet architecture.

Advertisement

GDIT's protest attacks that logic on two fronts. First, the company argues DISA failed to consider other contracting pathways, including existing enterprise IT vehicles that could have delivered the migration through competition rather than a sole-source expansion. Second, GDIT contends that DISA overweighted DoDNet expertise while discounting a different body of knowledge that matters just as much: understanding the combatant commands' own IT environments. The migration is not only about the destination network but about the systems, users, and mission requirements being moved. On that dimension, GDIT argues, the incumbent holds no decisive edge that would justify skipping competition.

The numbers underscore how early the DES effort remains. Leidos has migrated more than 40,000 users since 2022 against an original base of more than 370,000. That leaves the bulk of the consolidation ahead, and the combatant-command scope now layered on top adds a fresh population that was not part of the initial award. GDIT's position is that a requirement this large and this incomplete is precisely the kind of work that should be tested against the market, not extended by justification.

GAO now has until October 19, 2026 to rule. The forum will weigh whether DISA's justification meets the legal standard for awarding work without full and open competition, which requires the agency to show that only one source can meet its needs and that it adequately considered alternatives. A sustain would force DISA to reconsider its approach or compete the scope; a denial would let the expansion proceed on the CIO's timeline without further delay from the protest process.

What It Means for Contractors

The GDIT protest is a direct test of how far agencies can stretch an existing large-vehicle award to absorb new, schedule-driven requirements. Incumbency plus a tight deadline is becoming a common template for sole-source expansions, and this case will show whether GAO treats "institutional knowledge of the as-built environment" as a genuine barrier to entry or as a rationale that any incumbent could recite to lock out competitors. Contractors bidding against entrenched primes on consolidation programs should watch the reasoning closely, because a sustain would signal that GAO expects agencies to test the market even when a deadline looms, while a denial would give incumbents a durable playbook for defending expanded scope.

For companies chasing DoD IT modernization work, the practical lesson is to document the distinction GDIT is pressing: the difference between knowing the target platform and knowing the environments being migrated. When an agency justifies a sole source on platform familiarity alone, a challenger's best opening may be to show that the harder, mission-specific knowledge is competable and that alternative vehicles already exist to carry it. Enterprise IDIQs and governmentwide vehicles are frequently available substitutes, and an agency's failure to consider them is a recurring vulnerability in noncompetitive justifications. GAO has sustained protests before where an agency named a single source without seriously testing whether the market could meet the schedule, and GDIT is framing its challenge to fit that pattern.

There is also a timeline signal here. The fiscal 2028 migration deadline is being used to justify skipping competition now, but a protest that runs to October 2026 itself eats into that schedule. Agencies weighing sole-source expansions to protect a deadline should factor in the delay risk a sustained protest creates. For contractors, a well-founded protest of a rushed sole-source award is not just a legal play; it can reset the acquisition onto a competitive track before the incumbent's position hardens further. With the bulk of the 370,000-user consolidation still ahead, the DES outcome will help set expectations for the wave of combatant-command and fourth-estate IT consolidation still to come.

Sources