Cyber Force: Build Capacity Without Militarizing the Internet

The strongest good-faith objection is that waiting for another study can become the classic Washington way of avoiding a decision. Cyber threats are already escalating, and proponents of a separate Cyber Force argue that the existing services have had years to fix readiness, career-path, training, and retention problems without solving them. If the services do not own cyber as a primary mission, a critic could argue, they will keep treating it as a support function while adversaries treat it as a decisive domain. That objection carries weight. It already had a live test: Gillibrand's amendment failed in Senate Armed Services Committee by a single vote in June 2026. A one-vote margin proves the idea wrong no more than it proves the idea right — what it proves is that the fight will keep recurring, markup after markup, on whatever coalition that year's amendment happens to find, unless something settles it with evidence instead of a floor count. That is the argument for this issue's approach, not against it. The answer is not indefinite delay; it is a deadline with criteria. This issue gives Cyber Command's enhanced authorities and Cyber Command 2.0 reforms a defined three-year test. If readiness and retention remain structurally broken under that test, the trigger flips toward creating the service. The position holds because it replaces both premature reorganization and endless study with a measurable decision point.

Critical-infrastructure operators bear reporting and compliance costs under CIRCIA, especially smaller entities with thin security teams. State and local governments bear coordination work to use a cyber reserve effectively. Cyber Force advocates bear the political cost of waiting for a readiness test before getting the branch they think is already necessary. Civilian agencies bear the burden of proving they can coordinate defense without becoming another slow federal help desk. Those costs are acceptable only with mitigation: harmonized reporting to reduce duplicative paperwork, grants and reserve support for smaller public entities, clear timelines for the military readiness test, and statutory privacy limits. The position accepts friction up front to avoid two worse outcomes: a domestic cyber system people do not trust, or a new military service created before Congress knows which capacity gap it solved.