“Cyprus has not asked to activate Article 42.7.” The sentence, spoken by a spokesperson for the European Commission on the afternoon of March 2, 2026, hours after an Iranian drone struck the British base at Akrotiri, condensed the current state of European defense: a member state had been attacked on its soil, several countries were mobilizing naval and air assets bilaterally, and, nevertheless, the Union’s institutional framework remained formally inactive. Europe possessed a mutual defense clause. What it still lacks is the procedure to invoke it.
“What is being discussed in Nicosia is a conversation about the kind of security community the Union aspires to be”
That episode is the trigger for the debate that this week reaches the Cyprus informal Council, where European leaders will address the operationalization of Article 42.7 of the Treaty on European Union. What is discussed in Nicosia transcends the technical-legal dimension: it is a conversation about the type of security community the Union aspires to be.
A binding obligation whose architecture remains to be built
The article 42.7 has existed since the 2009 Treaty of Lisbon. It states that if a member state is the victim of armed aggression, the others will render “aid and assistance with all means at their disposal.” The formulation is unequivocal in its normative scope. Yet, in seventeen years of operation, the article has been invoked only once: in November 2015, when France activated it after the Paris attacks. At that time, there was no request for direct territorial defense; instead, France sought political and logistical support in its campaign against the Islamic State in Syria and Iraq. A precedent described by academic doctrine as a “creative use” and which leaves an unresolved question: can a clause of collective defense legitimize offensive actions abroad?
The comparison with NATO’s Article 5 is necessary in this context, albeit counterintuitive. NATO Article 5 binds each ally to take “the action it deems necessary.” It is, legally, a looser obligation than 42.7, which demands a response with all available means. Yet Article 5 rests on 75 years of institutional practice, an integrated chain of command, regular joint exercises, and a codified escalation doctrine. Article 42.7, by contrast, lacks a formal activation mechanism, defined timelines, and an execution structure.
In the strictly European framework, the existing instruments (the Permanent Structured Cooperation, PESCO, the EU “Battlegroups,” or the Initial Entry Capability) offer a degree of military coordination, but none constitute a fully activatable collective defense mechanism in the face of real aggression. The “Battlegroups,” in operation since 2007, have never been deployed. PESCO is a framework for developing capabilities, not for crisis response. The EU thus possesses tools for military cooperation, but not a genuine collective defense in the strict sense, which makes Article 42.7 the only formal tool available for that purpose and highlights the urgency of giving it a substantive operational content.
“This duality, between real defense and strategic positioning, is one of the pending debates of the European Council”
This raises a geometrical institutional question that few analyses address with precision: when a state that is a member of both the EU and NATO suffers an attack, should it activate Article 5, Article 42.7, or both? The theoretical answer is that they are compatible and additive, but political practice points toward an implicit choice. Article 5 provides the Alliance’s operational machinery; Article 42.7 mobilizes European political solidarity. France, in 2015, invoked Article 42.7 precisely because it wanted autonomous European support, without triggering NATO mechanisms. For a state seeking to underscore its strategic autonomy from Washington, Article 42.7 functions as a political signal, but it does not operate at the same level as a security instrument. This duality, between real defense and strategic positioning, remains one of the ongoing debates at the European Council.
There are technical differences between the two articles that rarely appear in public debate, but they condition their real strategic reach. The first is semantic: 42.7 refers to “armed aggression”; Article 5 to an “armed attack.” The prevailing legal doctrine regards “aggression” as a threshold that is broader and more flexible, applicable to hybrid threats or grey-zone actions that would not reach the threshold necessary to trigger the Atlantic machinery. If the Commission adopts this interpretation in the forthcoming “activation guide” it is preparing, 42.7 could be configured as the natural complementary instrument for the space between formal peace and conventional conflict, precisely where the bulk of contemporary conflict unfolds.
The second difference is geographic. NATO Article 5 covers attacks that occur in Europe or North America. By contrast, Article 42.7 encompasses all territory of EU member states under EU law, including Ceuta and Melilla, which would be outside the Atlantic umbrella but within Europe. If the article is endowed with a real operational mechanism, Spain would stand to gain as one of the main strategic beneficiaries. Madrid’s stance in this debate reflects not only solidarity with Cyprus but also a clear, concrete territorial interest.
< p>Moreover, within this map of commitments, the political tension at the summit is most acute. Cyprus has pushed for the operationalization of 42.7 more than any other member state and is simultaneously one of four countries (along with Austria, Ireland, and Malta) whose defense policies warrant the clause’s exemption provided in the treaty itself. The treaty text explicitly acknowledges the neutrality traditions of these States. Therefore, Cyprus claims guarantees of collective defense without having fully assumed the symmetrical obligations that this entails.
The reality that accelerates the debate
At this point, a discussion of Ukraine’s possible accession becomes unavoidable, because it conditions the entire debate. If Kyiv joins the Union before joining NATO (a scenario growing more plausible as some allies resist and as uncertainty about the long-term commitment to the Atlantic alliance persists), Article 42.7 would be automatically activated as a security guarantee for a country that could still be in active conflict. The Twenty-Seven would assume a defense obligation without an integrated chain of command, without a joint operational planning framework, and without an escalation doctrine. What the European leaders are building (or not) this week is the security infrastructure the Union will need when faced with decisions of a magnitude far greater than those of Cyprus.
Two additional, high-priority technical gaps accompany this reality. The first is legal: 42.7 covers “territory” in the traditional legal sense (land, internal waters, and airspace), but it excludes the exclusive economic zone, cyberspace, and outer space. In a landscape where the most sophisticated attacks strike submarine cables, satellites, or digital infrastructures in third countries, the article presents gaps that the activation guide will have to resolve or it will become obsolete in the most likely conflict scenarios.
“The resulting map is a constellation of armies that can march in the same parade, but hardly fight in a coordinated way under a unified command”
The second gap is industrial. Europe currently operates with more than 170 distinct military platforms (compared to fewer than 30 in the United States), many of them technically incompatible in communications, munitions, refueling, and command-and-control systems. This fragmentation stems from decades of national procurement, where each member state has maintained its own defense budget cycle, its own industrial preferences, and its own national champions. The resulting landscape is a constellation of armies that can march in step yet struggle to fight collectively under a single command.
When, in March 2026, several states mobilized assets in response to the Akrotiri incident, the coordination was bilateral and ad hoc precisely because there was no interoperability protocol allowing, for example, the Greek F-16 friend-or-foe systems to integrate with the Spanish Eurofighters or the French Rafales. The response worked, but it depended on goodwill and informal channels between national commands, not on an institutional architecture. In a scenario of greater intensity or pace of escalation, this reliance on informal coordination would be an unacceptable strategic risk.
To operationalize 42.7, therefore, the activation guide that the Commission is preparing must transcend the legal framework and include binding technical mandates: interoperable communication standards, joint command protocols, cross-platform certification criteria, and mechanisms for coordinated procurement that progressively reduce market fragmentation. Practically, this implies that the member states cede part of their sovereignty in defense procurement, historically one of the most guarded prerogatives of national sovereignty. The European Defence Fund and PESCO projects point in that direction, but current resources and mandates remain insufficient to create the critical mass required.
< p>Constructing interoperability standards tied to 42.7 is not only a political cost; it is a powerful accelerator of the consolidation of Europe’s defense industrial base. Companies capable of integrated command-and-control systems, secure communications, and AI applications for battlefield management have a direct incentive for the EU to adopt common standards, because that translates into joint contracts, shared research-and-development programs, and economies of scale that no single national market can generate. The operationalization of 42.7 and the building of a competitive European defense industry are, in the end, two sides of the same coin. An activation mechanism that does not take this dimension into account will have defined the invocation procedure without building the capacity to respond that gives it meaning. Without the material basis to back it, the clause will remain a promise without infrastructure.
A reflection on the European method
It is worth closing with an observation that transcends the immediate debate. European integration has historically advanced through a recognizable method: design the normative commitment first and then build the supporting institutions. The single market, the euro, or Schengen followed that logic. Article 42.7 is, in that sense, perfectly coherent with the European tradition. The commitment has existed since 2009; the architecture is being negotiated now, seventeen years later.
“A security guarantee only has strategic value if it is credible before it is needed; once it is, there is no room for gradualism”
The difference of this moment lies in the nature of the object at stake. Integrating markets or currencies allows for gradualism, error correction, and partial reversibility. Collective defense, by its definition, does not. A security guarantee only has strategic value if it is credible before it is needed; once it is, there is no room for gradual institutionalism. Europe is constructing, with increasing rigor, a capability that ideally should have existed from the outset. The Cyprus informal Council is not the end of that process. But if the leaders get it right, it could, for the first time, mark its true beginning.
