Most people think ITAR is a hardware problem. Missiles. Satellite components. Launch vehicle specifications. Physical items on the United States Munitions List that cannot be exported without State Department authorization. That understanding was accurate in 1976 when ITAR was codified. It is dangerously incomplete in 2026, when the most significant ITAR exposure for a company like SpaceX is not a physical component — it is an AI system making autonomous decisions about data that touches defense-related infrastructure.
I spent 19 years at Shell managing compliance across multiple jurisdictions, including export control environments where a single documentation failure could trigger regulatory consequences disproportionate to the underlying act. I have seen what happens when organizations moving fast treat compliance frameworks as post-growth problems. I have also seen what forensic rigor applied to data flows can do to identify and contain exposure before regulators find it first.
What I am about to describe is not hypothetical. Every element of this risk profile exists today, inside SpaceX's operational infrastructure, and will become dramatically more visible the moment the company files an S-1 and subjects itself to public market accountability.
The International Traffic in Arms Regulations control the export of defense articles, defense services, and related technical data. The United States Munitions List includes spacecraft systems, satellites, launch vehicles, guidance systems, and the technical data related to any of the above.
Technical data is the critical category. ITAR defines technical data as information required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance, or modification of defense articles. That definition, applied to 2026 AI systems, covers an enormous and largely unmapped territory.
The traditional ITAR compliance framework was not designed to govern autonomous AI systems making thousands of decisions per second about data that may or may not touch defense-related infrastructure. The gap between what ITAR requires and what most aerospace AI governance programs actually document is the time bomb this article is about.
Starlink is active communications infrastructure in active conflict zones. Every time a Starlink AI system makes a routing decision that affects communications in a region with active US military operations or sanctions exposure, that decision potentially touches ITAR-controlled technical data.
The question is not whether the decision was correct. The question is whether it was documented. Whether the AI system's decision logic was recorded. Whether a compliance officer reviewed the parameters governing routing decisions in conflict-adjacent regions. Whether there is an audit trail demonstrating the decision was made within a documented ITAR compliance framework rather than autonomously, without human oversight.
If the answer to any of those questions is no — that is a material ITAR compliance gap that becomes a public company disclosure obligation the moment SpaceX files its S-1.
Every AI model trained on data related to launch vehicle performance, reentry trajectories, guidance system telemetry, or satellite constellation management is potentially trained on ITAR-controlled technical data. The model itself — the weights, the architecture, the inference outputs — may constitute a defense article or technical data under ITAR, regardless of whether the underlying training data was properly licensed.
The State Department has issued guidance making clear that AI models and software incorporating ITAR-controlled technical data inherit ITAR controls. Sharing those models with non-US persons — employees, contractors, partners, researchers — without appropriate authorization may constitute an unauthorized export.
ITAR's deemed export rule treats the transfer of technical data to a foreign national inside the United States as an export to that person's home country. A non-US engineer at SpaceX's Hawthorne facility accessing an AI system that processes ITAR-controlled technical data may require an export license — regardless of the fact that the access occurred on US soil.
Managing deemed export compliance for a workforce of SpaceX's size and technical complexity is already a significant undertaking for physical technical data. Extending that compliance framework to AI systems requires a governance layer that most aerospace companies have not built.
Every third-party AI vendor integrated into SpaceX's operational infrastructure is a potential ITAR exposure vector. A cloud AI provider processing telemetry data. A machine learning platform used to optimize launch parameters. Any of these vendors may be routing data through infrastructure in jurisdictions that create ITAR exposure — and most vendor contracts do not contain adequate ITAR compliance representations.
At Shell, vendor due diligence for operations touching export control environments was forensic — not a checkbox. Every vendor touching sensitive data was evaluated for data residency, access controls, employee nationality screening, and export compliance certifications. That same standard applied to AI vendors in aerospace is what ITAR compliance at AI scale actually requires.
Boeing's governance failures are instructive not because of what they did — but because of how the institutional response scaled relative to the underlying violation. The 737 MAX software governance failure was, at its core, a documentation and oversight failure. When the failure became undeniable, the institutional response was not proportional. It was existential — simultaneous FAA, DOJ, and congressional scrutiny, criminal charges, $20B+ in losses, and permanent reputational damage.
"When governance gaps intersect with national security or safety exposure, regulators do not apply proportional responses. They apply existential ones. The time to understand that is before the first incident — not during the congressional testimony that follows it."
An ITAR violation at SpaceX would trigger a response that makes the Boeing 737 MAX investigation look contained. Simultaneous DOJ, State Department, and SEC scrutiny — all at the moment the company is trying to manage its first public earnings call and demonstrate governance maturity to institutional investors.
That scenario is preventable. It requires building ITAR-aware AI governance infrastructure before it is needed, not retrofitting it after the first violation is discovered.
Every AI system in operational use classified by its ITAR exposure profile — what data it processes, whether that data includes or derives from ITAR-controlled technical data, which jurisdictions it operates in, and which users have access. This inventory does not exist at most aerospace companies. It needs to exist before the S-1 is filed.
A governance layer classifying AI-generated outputs by ITAR sensitivity in real time — flagging outputs that contain or derive from controlled technical data before they are transmitted, shared, or accessed by users whose nationality creates deemed export exposure.
A documented framework governing which AI systems foreign national employees can access, under what authorization, with what monitoring, and documented in what compliance record. This needs to be built before the IPO workforce disclosure requirements create a public record of the gap.
Every third-party AI vendor evaluated for ITAR compliance before integration — data residency, access controls, employee nationality screening, export compliance certifications, and contractual ITAR representations. Not a checkbox. A forensic review with documented findings and ongoing monitoring.
Every significant AI decision in ITAR-adjacent systems documented with the data inputs, the model version, the output, the user who triggered the decision, and the compliance review record. The CFE evidentiary standard applied to export control compliance rather than financial fraud.
Free FAIG assessment — 15 questions, 5 minutes, scored against NIST AI RMF, COSO, and ISO 42001. Or message Monte directly to discuss ITAR AI compliance frameworks, aerospace governance advisory, or board-level GRC roles.
US Citizen · Independent forensic CPA · No vendor agenda · 19 years Shell GRC · Board-level experience · Consulting and senior roles considered