India bought the Rafale. France kept the passwords.
Reporting on the India-France relationship describes a push for greater software freedom around Rafale systems. The dispute is about access to a fighter’s workings, not merely possession of its airframe.
India is reportedly seeking greater access to Rafale mission-system software so it can integrate its own missiles. France is keeping control so that India is locked into buying French munitions.
It’s not a security issue – it’s a business issue.
France is claiming that it considers the most sensitive code and interfaces at a higher level than the airframe. India is saying, “hello, I bought the planes, software included.”
Today, software governs how weapons, sensors and electronic-warfare systems are integrated.
A country may possess and fly the aircraft while still needing another’s permission to access the software. As of the time of going to press, the matter is still being negotiated.
But the negotiation exposes the real sovereignty clause: who controls the next modification after the aircraft has been sold?
There is a procurement fact hiding behind the public announcement: control of the hardware is treated as control of the capability.
But what actually matters is source code, encryption keys, mission data, cloud access, update servers, geofencing and proprietary integration rights. That is the control point hiding behind the headline saying: “India bought the Rafale” and the follow-up question- “Did it really?”
For India, this was not just an accounting issue. For India the issue was that France or even more specifically, Dassault, could disable, narrow or degrade the capability of these advanced jet fighters through software without moving a single physical asset.
In that case, the contract might remain alive, and the diplomatic relationship might remain cordial but the military effect would still be a white elephant – a multi-billion dollar purchase that’s as dead as a dodo.
What’s the lesson here for you?
Run the failure as a tabletop exercise for starters. Put yourself in India’s position. Assume the controlling party decides to disable, narrow or degrade the capability through software, which it can do, over the air, from France.
Who notices first? Who has authority to activate the alternative? How many days of usable stock remain? If the answers require a new budget and a new contract, you do not have a Plan B.
While your technical team will test the mission performance, your commercial team should test the sovereign independence just as aggressively.
Is any geography, target type or mode restricted in code? What happens when cloud access or a subscription ends? Do you possess usable source code, or only an escrow promise with conditions?
Finally, ask what happens under pressure: Can the system operate when disconnected from the supplier? Who controls mission data, encryption keys and software updates? Can your engineers integrate a new weapon or sensor?
Do you have a contingency? If it’s a contingency that has never been funded, integrated or exercised – it’s not a plan. It’s just optimism that’s probably misplaced.
You should aim for a better contract and test the system in a fully disconnected national environment, get control of the keys, mission data and negotiate integration rights before signing the platform contract. The objective is not to eliminate every dependency. It is to prevent any invisible dependency from becoming a national emergency.
Price that exposure honestly.
A cheaper bid with one uncontrolled access point may be more expensive than a higher bid that gives you all the control.
Sure, your acquisition teams may be good at comparing purchase prices. But they are probably less consistent at pricing the cost of a grounded fleet, an empty magazine or a capability that arrives after the defence need has passed. The headline fact, 'India bought the Rafale', should carry that exposure “Hardware, not the software” in its text.
No serious buyer needs every line of source code. But every serious buyer does need control over the functions, data, keys and integration rights that determine whether the system can actually perform its mission. That distinction matters here: France kept the passwords.
The final test for India is simple: what remains usable when the foreign network, update server, cloud account and integration team are unavailable? If the answer begins with 'provided that somebody else agrees', then that condition belongs on the first page of the procurement decision, not in an annexure that nobody reads.
The equipment can remain in your hands while its useful functions disappear behind a login, a server decision or a line of code.
The kill switch does not have to be a red button. It can be an expired credential. That is the practical question anyone should ask behind the headline 'India bought the Rafale'.
AI-generated representative image.