The most useful thing a former Pentagon cyber chief said about Golden Dome this week was not about interceptors. It was about what happens to a satellite once it is up there.
A mandate that predates the architecture
Katie Arrington, now at IonQ and previously acting chief information officer at the Defense Department, told CyberSat attendees that she signed a memo as acting CIO requiring Golden Dome suppliers to meet NIST Special Publication 800-172. That standard is materially stricter than the 800-171 baseline the wider defense industrial base is held to.
Her reasoning is physical. Hardware cannot be swapped on orbit and software upgrades are difficult and slow. A component that ships with a flaw keeps it. Build security in from the design stage, she said, or the effort is wasted.
The funding question hanging over it
John Plumb, the first assistant secretary of defense for space policy and now at K2 Space, argued the program may not survive a change of administration. Its roughly $1T price tag, partisan branding and Democratic midterm gains, he said, combine badly. Missile defense will continue, he predicted, but the specific architecture may not.
Plumb was blunt that no amount of missile defense deters a peer adversary. It applies pressure, he said, and the adversary still gets a vote.
An unexpected policy unlock
Arrington credited the program with one concrete win unrelated to interceptors. A presidential exception let imagery funded under one title of law be used under another, loosening a longstanding barrier between military, civilian and intelligence collection.
That matters for defense because data locked in one legal silo cannot be fused with data in another. For the cybersecurity side of the program, the practical question is whether the stricter standard holds once production scales and cost pressure builds a thousand suppliers deep.
