The bill amends 10 U.S.C. 167b to require the Commander of U.S. Cyber Command (USCYBERCOM), under the Principal Cyber Advisor’s supervision, to directly control planning, programming, budgeting, and execution (PPBE) for training, equipping, operating, and sustaining the cyber mission force. It directs the Commander to prepare a program objective memorandum (POM) and budget estimate submission (BES) and to produce separate budget justification materials for inclusion in the President’s budget as distinct from any other military department or component.
The statute also limits that authority by excluding military pay and allowances and funding for facility support provided by the military departments, and it imposes a structured consultation process with the military department secretaries over reserve component cyber units. The change centralizes operational budget authority for cyber missions within USCYBERCOM while creating formal channels to surface and record disputes with the military departments before the Secretary of Defense receives budget proposals — a shift with practical consequences for resource flows, internal DoD roles, and congressional oversight of cyber spending.
At a Glance
What It Does
The bill adds a new subsection to 10 U.S.C. 167b requiring the Commander of USCYBERCOM to prepare the POM and BES and to submit separate budget justification materials for the cyber mission force as distinct from other services. It also requires consultation with military department secretaries on reserve component funding and mandates that nonconcurrences be included with budget proposals to the Secretary of Defense.
Who It Affects
Primary actors are USCYBERCOM, the Principal Cyber Advisor, the Secretaries of the military departments (and their budget offices), reserve component cyber units, OSD budget shops, and congressional defense appropriations/authorization staff who receive the separate justification materials.
Why It Matters
This changes who drives resource requests for cyber operations inside DoD, elevating operational control at USCYBERCOM and creating a formal reconciliation process for disputes. Practically, it can alter budget lines, oversight visibility to Congress, and how services plan and fund cyber‑related personnel and support functions.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill inserts a new subsection into 10 U.S.C. 167b that shifts primary PPBE responsibility for the cyber mission force to the Commander of USCYBERCOM, but explicitly places that authority under the supervision of the Department of Defense’s Principal Cyber Advisor. Practically, the Commander must prepare both a program objective memorandum and a budget estimate submission for the cyber mission force and prepare budget justification materials that are submitted with the President’s budget distinct from other military departments or components.
The statute draws two concrete boundaries around that authority. First, it excludes military pay and allowances from the Commander’s control, leaving those personnel cost decisions within the military department budgeting structures.
Second, it excludes funding for facility support that the military departments provide — a carve‑out that preserves some service responsibilities for infrastructure funding.The bill creates a two‑way consultation requirement between USCYBERCOM and the secretaries of the military departments focused on reserve component cyber units. Before USCYBERCOM’s budget goes to the Secretary of Defense, the Commander must consult the services about funding for reserve units; if a service secretary disagrees with the recommended level, that secretary’s views must accompany USCYBERCOM’s submission.
The reverse is also required: when a military department submits its budget, it must consult USCYBERCOM about cyber mission funding in its reserve component personnel budget and include the Commander’s views when the Commander does not concur.In short, the statute centralizes the preparation and presentation of cyber mission funding at USCYBERCOM while preserving specific service authorities and creating a formal record of disagreements. That combination aims to produce a consolidated operational request for cyber forces while ensuring service-level concerns—especially around reserve force resourcing—are transmitted to the Secretary of Defense for resolution.
The Five Things You Need to Know
The bill amends 10 U.S.C. 167b by adding a new subsection (f) that assigns PPBE responsibilities for the cyber mission force to the Commander of USCYBERCOM.
The Commander must prepare a Program Objective Memorandum (POM) and Budget Estimate Submission (BES) and prepare budget justification materials submitted with the President’s budget separate from other military departments or components.
The Commander’s PPBE authority explicitly excludes military pay and allowances and funding for facility support provided by the military departments.
Before USCYBERCOM’s budget goes to the Secretary of Defense, the Commander must consult the Secretaries of the military departments about funding for reserve component cyber units and include any non‑concurrences with the submission.
Reciprocally, each military department must consult USCYBERCOM before submitting its budget about reserve‑component cyber mission funding and include the Commander’s views if the Commander does not concur.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Assigns PPBE responsibility for cyber mission force to USCYBERCOM
This paragraph directs the Commander of USCYBERCOM, subject to the Principal Cyber Advisor’s authority, to control and manage PPBE activities to train, equip, operate, and sustain the cyber mission force. It specifies the deliverables: a program objective memorandum, a budget estimate submission, and budget justification materials for inclusion in the President’s budget that are presented separately from other services. Practically, this centralizes the drafting and presentation of operational cyber funding requests inside USCYBERCOM rather than dispersing them across service POMs.
Carves out pay and facility support from USCYBERCOM’s authority
This paragraph lists two explicit exclusions: military pay and allowances; and funding for facility support provided by the military departments. Those carve‑outs preserve existing service control over personnel compensation and service‑provided infrastructure, limiting how far the centralization extends and leaving the services responsible for those budget categories.
Consultation requirement for reserve units before Cyber Command submits its budget
Before USCYBERCOM transmits its budget proposal to the Secretary of Defense, the Commander must consult the Secretaries of the military departments about funding for reserve component units within the cyber mission force. If a service secretary does not concur in a recommended funding level, the service secretary’s views must accompany USCYBERCOM’s budget package. This creates a formal mechanism to surface service objections and ensures SecDef receives competing perspectives in writing.
Reciprocal consultation when services submit their budgets
This reciprocal paragraph requires each Secretary of a military department to consult USCYBERCOM before sending that department’s budget to the Secretary of Defense concerning reserve‑component cyber mission funding in the department’s military personnel budget. If the Commander disagrees with recommended funding for individual augmentees or units, the Commander’s non‑concurrence must be included with the department’s submission, guaranteeing the Commander’s operational concerns travel with service budget materials.
This bill is one of many.
Codify tracks hundreds of bills on Defense across all five countries.
Explore Defense in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- U.S. Cyber Command — Gains central authority to prepare and present operational cyber funding requests (POM/BES), improving coherence across cyber mission planning and giving the command clearer control over resources tied to missions.
- Principal Cyber Advisor (PCA) — The bill explicitly places USCYBERCOM’s PPBE role under the PCA’s authority, strengthening the PCA’s institutional leverage to align cyber budgeting with Departmental cyber policy and priorities.
- Congressional defense committees and appropriations staff — Receive a distinct, consolidated set of budget justification materials for cyber mission operations, which can increase transparency and make oversight more targeted and easier to trace.
- Operational cyber units (active and some reserve elements) — Can benefit from a unified resource request that aligns training, equipment, and sustainment priorities around operational needs rather than diffused service submissions.
Who Bears the Cost
- Military department budget offices and Secretaries — Lose some discretion over operational cyber funding presentation and must participate in additional consultations; they retain pay and facility budgets but may see operational accounts shifted out of their POMs.
- Office of the Secretary of Defense (budget and resource reconciliation staff) — Must reconcile potentially competing budget submissions and non‑concurrences from USCYBERCOM and the services, adding adjudication workload and complexity during SecDef review.
- Reserve component managers and service personnel planners — Face new procedural steps and possible uncertainty about where operational funding will flow, complicating long‑range manpower and training plans if authorities and execution pathways are not clarified.
- Treasury/appropriations execution practitioners (service comptrollers) — May need to manage cross‑account transfers or intra‑DoD reprogramming if operational funds are centralized at USCYBERCOM but execution still depends on service structures.
Key Issues
The Core Tension
The central dilemma is control versus execution: centralizing PPBE at USCYBERCOM promises a single voice for cyber operational needs and clearer congressional visibility, but it conflicts with military department authority over personnel, facilities, and execution. Resolving higher‑quality, consolidated resource requests against the services’ need to retain budget sovereignty and execution authority is the trade‑off the bill forces DoD to manage.
The bill centralizes preparation and presentation of cyber operational budgets but leaves execution and certain cost categories with the services; that split creates practical frictions. Where POM/BES authority sits does not automatically solve who obligates and disburses funds.
If USCYBERCOM’s POM requests end up routed through service appropriation accounts for execution (e.g., military personnel, O&M, MILCON), gaps can emerge between the line items Congress approves and who actually spends them. The statute’s carve‑outs for pay and facility funding help reduce that risk, but they do not address other cross‑cutting accounts (training ranges, IT sustainment, software licenses) that routinely straddle OSD and service purviews.
The formal non‑concurrence requirement improves documentation but can also institutionalize budgetary conflict. The Secretary of Defense will receive competing views in writing, which may slow decision cycles and provide Congress with multiple narratives about funding needs.
Implementation will require clear procedures for reconciliation, dispute resolution, and execution — none of which the bill prescribes. Finally, classifying a separate set of budget justification materials “separate from any other military department” raises questions about appropriation language, sub‑accounting, and whether Congress expects a distinct appropriation line for USCYBERCOM or accepts consolidated DoD accounts with explanatory materials.
Operationally, the bill leans toward unity of effort at the cost of complicating service budget sovereignty and execution pathways. Without follow‑on guidance about transfer authorities, execution channels, and funding lines, the PPBE changes could produce paperwork gains in visibility while creating operational friction during obligation and execution phases.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.