Skip to content

Latest news

Eleutheros Ltd
Night view over a dense, illuminated downtown and its waterfront

Digital business trends

FrenchWeb: five years of cyberattacks on French public digital services

FrenchWeb reports five years of cyberattacks against French public digital services, from La Courneuve to the DGFiP. The investigations point to protections that were known but only partly applied, while Matignon prioritises existing systems.

FrenchWeb published on 20 November 2026 a review of five years of cyberattacks on French public digital services, covering cases from La Courneuve to the DGFiP. The report's central finding is not a lack of known countermeasures, but their incomplete application. Matignon, according to the same report, has put priority on existing systems, which makes both the deployment of measures and the duration of rebuilds decisive.

The gap between knowing and applying

The pattern described by FrenchWeb is familiar to anyone who runs a digital operation: the defensive measures were largely identified, but they were not fully in place. The report does not specify which measures were missing, which systems were affected in each case, nor the cost of any single incident. What it does say is that the investigations point to protections known but incompletely applied, and that reconstruction time has become a factor in its own right.

For teams, the useful lesson is organisational rather than technical. A security backlog behaves like any other backlog: it grows when nobody owns it and when it is measured only after an incident. Treating known-but-unapplied controls as a tracked list, with an owner and a deadline, is the least glamorous and most effective response.

Why this reaches marketing and growth teams

Attacks on public services rarely stay inside the public sector. When a tax portal, a benefits service or a local administration goes down, the consequences spread to the businesses and individuals who depend on it: delayed payments, interrupted sign-ups, verification steps that stall. Any acquisition funnel with a step that relies on a public-facing service inherits that fragility.

The same holds for monetisation. A payment or identity check that depends on an external system is a single point of failure in the checkout path, and rebuild periods reported after incidents show how long such a failure can last. The report does not detail the length of any specific outage, but it makes the question of recovery time an explicit one.

What a team can check this week

  • List every step in your acquisition and checkout paths that depends on an external service, public or private, and name a fallback or a manual procedure for each.
  • Confirm that access to analytics, ad accounts and billing is protected by multi-factor authentication and reviewed for departed staff.
  • Check how long your backups would take to restore, not just whether they exist.

None of this requires new tooling. It requires the same discipline the French state is being asked for: knowing which protections are supposed to be in place, and verifying that they actually are. The report leaves open which specific measures are still missing across public systems; that is precisely why teams should not assume their own dependencies are safer than they look.

Also worth reading

All news

Aerial night view of Alexander Nevsky Cathedral in central Sofia

Contact

Tell us where the project stands.

A few lines are enough: what you are building, where it is today, and what is blocking it. We answer every message personally.

Contact us contact@eleutheros.eu