The Senate Armed Services Committee voted 14-13 on Thursday against an amendment from Sen. Kirsten Gillibrand (D-N.Y.) that would have created a new U.S. Cyber Force as a separate service nested under the Army, structurally modeled on the Space Force's relationship to the Air Force and the Marine Corps' relationship to the Navy. The narrow margin did not kill the policy fight so much as put a precise number on how unsettled the underlying organizational question remains.
Nine Democrats and four Republicans backed the amendment. Ten Republicans and four Democrats opposed it, according to a Defense One report on the SASC markup by Thomas Novelly. The party-line math matters: this is a near-miss in committee, not a partisan verdict. The four Democrats who voted "no" are the more interesting data point for anyone trying to read the next move, because they signal genuine institutional hesitation inside the caucus most likely to support a new service.
Gillibrand's office framed the outcome as a waypoint. A spokesperson told Defense One the senator "will continue to push" for Cyber Force creation. That is forward motion, not a guarantee of any specific vehicle. A floor amendment, a conference fight, the FY27 NDAA, or a standalone bill are all open, and the SASC version of the FY NDAA is itself markup-stage and subject to change in the committee report, on the floor, and in conference.
What the SASC version of the FY NDAA does, in lieu of the new service, is commission two studies that go straight at the same structural problem. The bill directs an independent review of whether U.S. Cyber Command is "adequately organized and resourced to meet its expanding authorities and responsibilities," and an independent study on the roles, responsibilities, authorities, and resourcing of the Principal Cyber Advisors of the military departments, per the Defense One report. Read narrowly, those are bureaucratic placeholders. Read as a counter-proposal, they are the status-quo coalition's answer to the cyber-force-generation case: prove the existing architecture can do the job, and the case for a new service weakens on its own.
That case got its most visible external articulation earlier this month from the Commission on Cyber Force Generation, a joint project of the Center for Strategic and International Studies and the Foundation for Defense of Democracies, co-chaired by Joshua Stiefel, a former House Armed Services Committee staffer. The commission's June 2026 report argues a separate cyber service "would address longstanding structural challenges and build the Cyber Force the United States needs for this critical domain of warfare." Stiefel, in a media call hosted by FDD, framed the legislative environment as a "breaking point": any further authority granted to CYBERCOM, he argued, "doesn't start to begin to chip away or take away from the service chiefs" without the structural change the amendment proposed.
The commission and its report are advocacy-adjacent rather than neutral, and Stiefel's quotes should be read as the position of a body with a specific organizational outcome in mind. The four Democratic "no" votes likely reflect a different set of objections: stand-up cost, time to operational capability, the risk of duplicating functions the services say they can grow, and a civilian talent pipeline that a new military service would not, on its own, fix. None of those criticisms is foreclosed by Thursday's result, and they are the case the SASC studies are designed to test.
The honest read of the 14-13 vote is that it quantifies a standoff rather than resolving it. The amendment's supporters now have a commission-grade case for their preferred structure and a senator committed to the issue. The amendment's opponents have a committee majority and two independent reviews in their bill that, depending on what they find, can either ratify the status quo or quietly provide the evidence the next amendment will need. What neither side has is closure, and that is the story.