On an operations floor, a cyber crew can watch an adversary move through a network in near real time and know exactly what would stop them. Then they hit the wall that never makes the briefing slide: the capability that would do it isn't funded this year, and the money that could buy it is the wrong color — parked in a program element (PE) someone wrote for an airplane.

I've shipped enough patches to know the shape of it. The fight runs at machine speed. The money runs at the speed of permission.

BLUF: Cyber is further along than almost anything else this series takes aim at. U.S. Cyber Command (CYBERCOM) is a unified combatant command with service-like authority over its own budget under a dedicated section of Title 10,[1] and since the fiscal 2024 request it programs that budget itself.[2] What it still does not have is a Major Force Program (MFP) of its own — one visible line of money the services cannot raid — or any way to move execution-year dollars at the speed the fight actually changes. Build it: MFP-CYBER. Consolidate the scattered cyber accounts and the weapons the services are already handing back into one program; structure it in three tranches — operations, tradecraft, and commercial capability; and wire every dollar to an outcome-tagged budget program activity code (BPAC) so a commander can maneuver inside a continuous authorization to operate (cATO) risk envelope instead of waiting on the next budget cycle. Enhanced budget authority told cyber it could own its money. This tells the money it can move. The template is not new — Special Operations Command (SOCOM) has run on it since 1987.

Cyber got the command. It still budgets at the speed of permission.

Give the system credit for how far it has already come. Cyber spent its early years exactly where special operations sat in 1986 — everyone's mission, nobody's command — and we fixed the first half of that problem. CYBERCOM stood up as a full unified combatant command (UCC) in 2018, and Congress wrote it a dedicated authority in Title 10 that reaches budget, acquisition, and personnel in a way most combatant commands never get — closer to a military department than to a theater headquarters.[1] Then it went further. Under what the command calls its enhanced budget authority, first exercised in the fiscal 2024 submission, CYBERCOM took direct control of planning, programming, and budgeting for the cyber mission force, and the major weapons the services used to buy on its behalf began transferring to the command.[2] Before that, it executed only about $600 million, most of it headquarters overhead.[2] That is real, and it is more than the innovation enterprise ever got.

And it still isn't enough, because authority over money is not the same as velocity with it. CYBERCOM's new power is a programming power: it decides what goes into the Future Years Defense Program (FYDP) two years before the dollars arrive. But cyber is a continuous fight. The adversary ships a new technique on a Tuesday; the budget that answers it was locked in a Program Objective Memorandum (POM) two cycles ago. The whole Planning, Programming, Budgeting, and Execution (PPBE) machine, as this series has said before, moves at the pace of litigation, not conflict. Handing CYBERCOM the pen on a two-year calendar does nothing for the commander who has to move money this week.

A program of its own

Here is the part the new authority did not fix. Cyber still has no MFP. Its money is scattered across the Department's defense-wide accounts — roughly $2.7 billion in fiscal 2025: about $1.6 billion in operations and maintenance (O&M), a billion in research, development, test, and evaluation (RDT&E), and barely $110 million in procurement[3] — while the larger cyber weapons still sit inside program elements (PEs) the services own. For scale: the Department of War (DoW) plans to spend something like $13.5 billion on cyberspace activities in a single year,[2] and almost none of it rolls up to one line anyone can point to and defend.

SOCOM's Major Force Program — MFP-11 — is the thing that made special operations un-raidable: a slice of the budget the services could not reach back into the moment a conventional bill came due. Cyber has the command SOCOM has, and the Title 10 authority SOCOM has, but not the one line of money that made the other two stick. And notice what that $110 million in procurement tells you: a combatant command expected to field capability at the tempo of commercial software has almost no money to buy any. The shape of the budget is the shape of the problem.

MFP-CYBER consolidates those scattered accounts and the transferring weapons into one program, and — like any command's money — it has to do three different jobs, so it carries three colors by design.

  • Operations (mostly O&M funding) — the persistent fight. This runs the cyber mission force, the sensors, and the data pipelines the whole enterprise fights on. Sustain the data the way you sustain fuel: a standing operations bill, not a project you have to re-justify every year.
  • Tradecraft (mostly RDT&E funding) — the tools and the labels. Capability development, the models, the data labeling and ontologies that make the pipelines mean something. This is where the weapons the services are handing back actually live.
  • Commercial capability (mostly procurement funding) — buying at tempo. The money to buy commercial threat intelligence, sensors, and dual-use tooling in weeks, through the Other Transaction (OT) and indefinite-delivery, indefinite-quantity (IDIQ) rails this series has already laid out — not a procurement line sized for a rounding error.

Keep the statutory walls between the three colors and the commander guardrails within each tranche; you don't need to knock them down. What you change is how fast money moves inside each color within each wall.

Budget as maneuver

The machinery that makes money move at tempo isn't new to this series; I've laid it out in painful detail before. It ports straight onto cyber. Tag every obligation in MFP-CYBER with an outcome BPAC that carries its own metadata: which mission thread it serves, which effect it buys, how much risk it carries, and its cATO lineage. Once a dollar is tagged, a commander can redirect execution-year money inside a validated risk envelope without reopening the POM — the move writes an automatic funds-change record instead of starting a reprogramming fight. That is the whole difference between owning your money and being able to maneuver it.

Pay for outcomes, not activity. Write the contracts as outcome contract line item numbers (CLINs): the bonus pays when the metric moves, not when a milestone slips. In cyber the metrics are the ones operators already live by — how long an intruder dwells before you see him, how fast you detect and respond, how quickly a known-exploited vulnerability (KEV) gets patched across the force, the cost per verified effect. When a vendor's pipeline misses its service level, the money migrates inside the same BPAC to one that doesn't — no new competition, because the vehicle was built to be ordered against.

The cATO envelope is what makes it safe. Move the authorization to the commander, express the controls as code, and "spend inside the risk envelope" stops being a slogan: the envelope is the pipeline's attested security state, and a buy that stays inside it doesn't need a staff in another building to bless it first. None of this is unique to cyber. The outcome-tagged BPAC does double duty: the same tag that lets a commander maneuver execution-year money is the one that makes every dollar auditable. That is the DoW-wide machine this series' money-and-authority rewire opened with — cyber is just the proving ground, because its tempo makes the need impossible to argue with. Win it here, and the same ledger that proved the money moved responsibly becomes the case for running it across the Department.

We gave cyber the authority to own its money. We never gave the money permission to move.

Man it like special operations, not like a line unit

The money is only half the SOCOM port. The same section of Title 10 that gives CYBERCOM its budget authority gives it personnel authority too,[1] and the command should use it the way special operations does: man the force on the skill the mission actually needs. There is nothing wrong with a coder who can't pass the Marine Corps combat fitness test but types at 200 words a minute and ships a patch in minutes instead of days. In the cyber fight that person is the operator, and a manning model that screens him out on a standard built for an infantry squad is optimizing for the wrong war.

So MFP-CYBER carries its own accession and retention authority — direct and lateral entry for technical talent, pay that competes with industry, relevant standards instead of universal ones — in the operations color, the same way it carries the fielding money in the others. The full workforce model is its own post later in this series; here it is enough to say the program has to buy people on the same outcome logic it buys capability. A command that can maneuver its money but not its talent has solved only half the problem.

The objections, answered

"Cyber already won enhanced budget authority — why does it need a new program on top of that?" Because programming authority and execution-year velocity are not the same thing. CYBERCOM's new power lets it decide what goes into the FYDP two years out; it does nothing for the commander who has to move a dollar this week, and it leaves the money scattered across defense-wide accounts the services can still raid. The Major Force Program is the un-raidable line and the velocity the authority never came with. Owning the money was step one; moving it is step two.

"Letting a commander move execution-year dollars without a reprogramming package guts Congress's power of the purse." It does the opposite, built right. The statutory color walls stay up — maneuver happens inside a single color of money, inside a validated cATO risk envelope, under an automatic funds-change record, and only below a threshold Congress sets; above it, the normal reprogramming rules still apply. Congress trades a slow, blind process for a fast, fully logged one, and the outcome BPAC tag is the receipt on every dollar. That is more oversight and visibility than the status quo, not less.

"Carve cyber its own money and every combatant command will want one." The bar isn't ambition, it's tempo and precedent. SOCOM got Program 11 because its mission ran on a clock the services' budget couldn't keep — and cyber's clock is faster still. Arguably the fastest of all the domains of warfare. The program is scoped to the cyber fight and stood up as a five-year pilot whose renewal rides on its evidence ledger; if it doesn't prove out, it folds. A sunset with a scoreboard is the opposite of empire-building.

The fix

Stand up MFP-CYBER as a dedicated major force program for the cyber fight. Pull the scattered defense-wide cyber accounts and the transferring PEs into one line that CYBERCOM programs under the Title 10 authority it already holds. Structure it for missions — operations, tradecraft, and commercial capability — and keep the statutory walls for existing colors of money. Tag every obligation with an outcome BPAC, write the contracts as outcome CLINs against service level agreements (SLAs), and let a commander maneuver execution-year dollars inside a cATO risk envelope with a funds-change record in place of a reprogramming action below a set threshold. Use the personnel authority the command already holds to man it on skill, not on standards built for another fight. Make it a five-year pilot whose renewal — and whose expansion into a department-wide maneuver authority — rides on that evidence ledger, not on the services' goodwill, because the services will want the money back. None of it needs a new color of money or a new idea. It needs the one thing cyber got for its command and never got for its budget: a home, and a clock.

What you can do Monday

  • Unit commanders (joint force headquarters and mission-force leads): Name the mission thread and the effect you need in writing, and report your readiness as dwell time and time-to-patch — the outcome the money is supposed to buy. A tagged requirement is what lets the dollar find you.
  • PEOs / PAEs (the cyber program offices): You still execute the weapons the command is taking ownership of. Treat the outcome BPACs and outcome CLINs as the standard you build to, and accept that funds migrate to the performer who moves the metric.
  • Contracting officers: Write outcome CLINs on the OT and IDIQ rails, so a capability proven this month has money on it next month instead of in two fiscal years.
  • CYBERCOM and the service cyber components: Ask for the Major Force Program by name, and publish who owns which dollar and which outcome inside it. The authority you won in Title 10 was the hard part; the line of money is the easy one to ask for.
  • OSD (the Comptroller and the Department's cost-analysis shop): Draw the wiring diagram — one program, outcome-tagged BPACs, a funds-change record that clears below a threshold without a reprogramming package — so the velocity arrives with the authority instead of a cycle behind it.
  • Congress: This one needs you. Authorize MFP-CYBER, fold the defense-wide cyber accounts and the transferring PEs into it, permit execution-year BPAC maneuver inside a cATO envelope under a funds-change record, and tie the whole thing to a five-year pilot judged on its evidence ledger. You already gave CYBERCOM its command and its budget authority. Give the money a home and a clock.

Works Cited

1 United States Code. 10 U.S.C. § 167b — Unified combatant command for cyber operations.

2 Pomerleau, Mark. 2023. US Cyber Command releases first full budget. DefenseScoop, March 13, 2023.

3 Congressional Research Service. 2025. Defense Primer: U.S. Cyber Command (USCYBERCOM) (IF13042).