Greece’s Achilles Shield Deal Leaves C2 Source Code in Israeli Hands

Key facts

• Israel’s Missile Defense Organization director said Greece will not receive Israeli C2 source code because it was not included in the licence
• Achilles Shield is a €3B Greece–Israel agreement (31 Aug.) to integrate Israeli tech against missiles, aircraft and drones
• Israel’s Defence Ministry says know-how transfer will enable Greek firms to develop a “Greek source code” under exclusive Greek control

3 minute read

Greece will not receive Israel’s source code for the command-and-control system at the centre of its new €3 billion Achilles Shield air-defence network, a point made explicitly by Moshe Patel, director of Israel’s Missile Defense Organization, in remarks reported by Greek outlet Kathimerini and echoed by Politico. Patel’s rationale is contractual rather than technical: the source code was not included in the licence to use agreed between Athens and Israel on 31 August. For Greece, which has framed operational sovereignty as a non-negotiable requirement, the disclosure complicates the stated objective of independently maintaining, modifying and upgrading a system intended to sit at the heart of national air defence against missiles, aircraft and drones.

The immediate implication is a classic dependency risk at the software-defined layer. Without source code rights, Greece’s ability to correct vulnerabilities, add capabilities, adapt interfaces, or re-host components on national infrastructure is structurally limited and likely requires vendor involvement. That may be manageable in steady-state support, but it becomes more consequential when requirements change rapidly, when cyber and EW threats evolve, or when political constraints affect support timelines. It also increases the leverage of the supplier during mid-life upgrades and integration work, with predictable cost and schedule consequences.

Israel’s Defence Ministry has sought to soften the impact by stating that Israeli know-how will be transferred to Greek companies participating in Achilles Shield, enabling development of a “Greek source code” that would remain under exclusive Greek control. If realised, this would shift the issue from outright denial of autonomy to a more complex engineering and certification challenge: building a national software layer that can command and control Israeli-origin sensors/effectors while preserving performance, safety, and security, and without breaching intellectual property constraints embedded in licence terms. The practical ceiling on “Greek source code” will depend on what APIs, data models, and integration documents are made available and whether Greece can meaningfully decouple mission-critical C2 functions from proprietary black boxes.

For European defence officials and procurement officers, Achilles Shield is a live signal that Europe’s accelerating turn to Israeli air and missile defence technology can come with constrained software rights at the C2 level. The episode reinforces the need for procurement language that treats software escrow, update authority, cyber patching rights, and interface openness as strategic deliverables rather than optional commercial terms. It also strengthens the case for European frameworks that prize interoperability and sovereign upgrade paths, especially as counter-UAS and integrated air and missile defence become increasingly networked across national and NATO architectures.

Source: Politico.eu