Centripetal v Palo Alto Networks (CFI, 11 July 2025)
| Date | 11 July 2025 |
|---|---|
| Court | CFI |
| Division | Mannheim (DE) Local Division |
| Type of action | Procedural Order |
| Case number(s) | UPC_CFI_636/2025 |
| Registry reference | ORD_32784/2025 · UPC_CFI_636/2025 |
| Parties | Centripetal Limited / v / Palo Alto Networks, Inc. |
Official decision (PDF) · UPC registry entry
Case timeline
- 25 July 2025 : Centripetal v Palo Alto Networks (CFI, 25 July 2025) App_32933/2025 · ORD_32958/2025 · UPC_CFI_636/2025
- 2 October 2025 : Centripetal v Palo Alto Networks (CFI, UPC_CFI_636/2025, 2 October 2025) UPC_CFI_636/2025
- 2 October 2025 : Centripetal v Palo Alto Networks (CFI, UPC_CFI_636/2025, 2 October 2025, doc. 2) UPC_CFI_636/2025
Dhenne Avocats represents claimants and defendants in European patent disputes before the Unified Patent Court, including the Paris divisions.
Dhenne Avocats · 10 October 2026
Our analysis
Summary
By order of 3 June 2025 (UPC_CFI_636/2025), made without hearing the defendant after referral back by the Court of Appeal, Judge Tochtermann (Mannheim Local Division) granted Centripetal a saisie targeting Palo Alto Networks’ network security solution at its Munich branch office. The judge rapporteur had rejected the application on 3 March 2025, on 28 May 2025 the Court of Appeal referred the case back, leaving the first instance to issue the orders.
The practical interest lies in the terms. Bound by the Court of Appeal on the points it decided, the judge used his discretion on the points it did not address: the defendant is given two hours to call in a lawyer before real-time monitoring of its system, and enforcement is conditional on security of EUR 100,000.
Facts and procedure
Centripetal, the registered proprietor of a European patent (EP 3 281 580 according to the order’s header, while the body also refers to EP 3 821 580), in force in Germany, France, Italy and the Netherlands among others following withdrawal of the opt-out, alleges that Palo Alto Networks’ next-generation firewall, with its Advanced Threat Prevention and App-ID Cloud Engine services, very probably infringes. It relies on an expert opinion filed as exhibit C2.
Its saisie application was rejected by the judge rapporteur on 3 March 2025. On appeal, the Court of Appeal referred the case back on 28 May 2025 (UPC_CoA_239/2025), entrusting the Local Division with issuing the orders, with Judge Tochtermann sitting as presiding judge and judge rapporteur.
The applicable law
The measure rests on Art. 60 UPCA and Rules 192 and 196 RoP. On referral back, the first instance is bound by the Court of Appeal’s decision on the points it decided (Rule 243.2), including the number of the applicant’s representatives allowed to attend. Under Rule 196.3 it retains the power to attach conditions, in particular as to whether immediate enforcement is proportionate and as to security where the measure is ordered without hearing the defendant (Rules 196.3(b) and 196.6).
Question
After referral back by the Court of Appeal, on what terms should a saisie concerning a live IT system be ordered without hearing the defendant?
Decision
The saisie is ordered for claims 1 and 16: inspection of the Munich branch, set-up and real-time monitoring by the expert of a firewall device connected to the defendant’s servers, copying of digital evidence and technical documentation, then an expert report within one month. The appointed expert may use two assistants. Four named representatives of the applicant (two lawyers, two patent attorneys) may attend, bound to secrecy towards their client. Its employees may not. The defendant must allow access and assist the monitoring, including by disclosing passwords, certificates and decryption keys.
Since the Court of Appeal said nothing on attendance on the defendant’s side, the judge considered that the defendant must be able to consult a lawyer to understand the scope of the order, read together with its reasons: set-up and monitoring may proceed only after it has been told of that right and given up to two hours, during which it may not alter the system, the other measures are immediately enforceable. The order takes effect only once security of EUR 100,000 is provided within three weeks of service, an amount held sufficient to cover costs and damage. Use of the results is limited to main proceedings against the defendant and its affiliates (Rule 196.2), and the measures are revoked if no action on the merits is brought within the Rule 198.1 time limits. The remainder of the application is rejected.
Key points for practice
- On referral back, the first instance is bound on the points the Court of Appeal decided but keeps its discretion on terms it did not address (Rules 243.2 and 196.3).
- A saisie of a live system may require active cooperation from the defendant, including handing over passwords and decryption keys.
- A short window to call in a lawyer may be granted before the most intrusive steps, while the others remain immediately enforceable.
- Practical point: the applicant must plan for the amount of security and the time allowed to provide it, on which the order’s effect depends.
Provisions applied
- Agreement on a Unified Patent Court
- Arts 60 and 73(2)(a)
- Rules of Procedure
- Rules 192, 196, 197.3, 198.1, 220.1(c), 224.2(b) and 243.2
- Case law cited
- CENTRIPETAL v PALO ALTO NETWORKS, 28 May 2025, Court of Appeal
Related decisions
Prepared by Dhenne Avocats from the official decision, consulted on 10 October 2026. The database is updated every week, on Friday. Only the official text is authoritative.
Decisions in the same proceedings
Going further
Lexicon: Written procedure (UPC), Court fees and costs (UPC).
Source and translations
- Official source
- Unified Patent Court registry link recorded in the record
- Original language
- not recorded
- Translation available
- no translation recorded the firm’s French record is a summary, not a translation
- Date checked
- not recorded
Follow this case
Proceedings, related decisions, appeals, parties and patents as recorded in the registry and in the Dhenne Avocats corpus. Each link states its source.
Parties
- claimantv14 decisions in the corpusFollow this party
- claimantCentripetal Limited11 decisions in the corpusFollow this party
- claimantPalo Alto Networks, Inc.6 decisions in the corpusFollow this party
Decisions in the same proceedings and documented appeals
- 11 July 2025 Centripetal v Palo Alto Networks (CFI, 11 July 2025) Procedural Order · UPC_CFI_636/2025
- 25 July 2025 Centripetal v Palo Alto Networks (CFI, 25 July 2025) Procedural Order · UPC_CFI_636/2025
Le saisi qui n'a pas élargi les droits d'accès d'un salarié pour rendre accessible un système hébergé ailleurs n'a pas méconnu l'ordonnance de saisie. La demande d'astreinte est rejetée, frais d'exécution à la charge du requérant.
- 2 October 2025 Centripetal v Palo Alto Networks (CFI, UPC_CFI_636/2025, 2 October 2025) Application Rop 333 · UPC_CFI_636/2025
La formation confirme le refus d'astreintes : le défendeur, tenu seulement de tolérer l'inspection des lieux et objets visés, n'avait ni à créer des accès ni à installer le système, et l'ordonnance de saisie rapportée ne peut plus fonder d'exécution.
- 2 October 2025 Centripetal v Palo Alto Networks (CFI, UPC_CFI_636/2025, 2 October 2025, doc. 2) Request to review an order ex-parte · UPC_CFI_636/2025
L'ordonnance de saisie du 3 juin 2025 est rapportée, sauf les mesures de confidentialité, et la demande de conservation des preuves est rejetée, les locaux visés n'abritant qu'une unité commerciale sans accès technique aux données.
What the record states
- Nature of the act
- Procedural Order
- Outcome (Dhenne Avocats summary)
- Après renvoi par la cour d'appel, la division locale de Mannheim ordonne une saisie de preuves sur la solution de sécurité réseau de Palo Alto Networks, avec surveillance en temps réel différée de deux heures pour permettre la venue d'un avocat, sous condition d'une garantie de 100 000 euros.
- Appeal
- No appeal documented in the corpus, this does not mean that no appeal was lodged.
- Instance
- First-instance decision, whether it has become final is not recorded.
Patents mentioned
EP 3 281 580mentioned in: Dhenne Avocats analysis Follow this patentEP 3 821 580mentioned in: Dhenne Avocats analysis Follow this patent
Related decisions cited in the analyses
- Centripetal v Palo Alto Networks (CFI, UPC_CFI_636/2025, 2 October 2025) cited in this record
- Centripetal v Palo Alto Networks (CFI, UPC_CFI_636/2025, 2 October 2025, doc. 2) cited in this record
- Centripetal v Palo Alto Networks (CFI, 25 July 2025) cited in this record
- CENTRIPETAL v PALO ALTO NETWORKS (CoA, 28 May 2025) cited in this record
Patents and standards
| Publication | Role in the dispute | Family | Standard and declaration | Pool | Sources |
|---|---|---|---|---|---|
EP 3 281 580 | Mentioned in the analysis (role not qualified) Also mentioned in 2 other decision(s): Centripetal v Palo Alto Networks (CFI, UPC_CFI_636/2025, 2 October 202 · Centripetal v Palo Alto Networks (CFI, 25 July 2025) | not recorded | not recorded | not recorded | Espacenet links not checked mentioned in: Dhenne Avocats analysis |
EP 3 821 580Methods and systems for efficient network protection recorded proprietor: Centripetal Ltd | Mentioned in the analysis (role not qualified) Also mentioned in 10 other decision(s): Centripetal v Palo Alto Networks (CoA, 4 February 2026) · Centripetal v Keysight (CFI, UPC_CFI_414/2025, 5 December 2025) · Centripetal v Keysight (CFI, UPC_CFI_414/2024, 5 December 2025) · Centripetal v Keysight Technologies (CFI, 5 September 2025) · Centripetal v Keysight Technologies (CoA, 1 September 2025) · Centripetal v Keysight Technologies (CFI, 20 August 2025) · Centripetal v Keysight Technologies (CFI, 1 August 2025) · CENTRIPETAL v PALO ALTO NETWORKS (CoA, 28 May 2025) | not recorded | not recorded | not recorded | Espacenet · European Patent Register existence and title of the publication checked on 30 October 2026 (Google Patents, Espacenet and Register links are not checked automatically) mentioned in: Dhenne Avocats analysis |
Receive an alert
Weekly summary of new records and substantive updates matching what you follow. Address confirmed by email, unsubscribe at any time, one email per week even where several of your follows match.