Numerique

Cybersecurity lawyer

Anticipate cyber risk from a legal standpoint: security obligations, data breach management, directors' liability and crisis management.

Schedule a call

Context

Cybersecurity: a legal as much as a technical challenge

Cybersecurity is not solely a matter for IT specialists. The law imposes data security obligations on companies, governs the handling of breaches, structures liability in the event of an incident and multiplies sector-specific regulations. A cyberattack is not merely a technical problem: it is an event that engages the liability of the company and of its directors.

Between the GDPR's security obligation, the notification of breaches to the CNIL, new directives such as NIS2, and the question of liability towards clients and partners, the legal dimension of cybersecurity has become unavoidable, particularly in the midst of a crisis.

Problem

The day the attack strikes

Many companies treat cybersecurity as a purely technical subject, delegated to IT, until the day an attack hits them. At that moment, legal questions flood in: must the CNIL be notified, should clients be informed, should a complaint be filed, how should evidence be preserved, who is liable, what do the contracts with suppliers say.

Without preparation, crisis management is improvised under pressure, with a high risk of errors: late or missing notification, clumsy communication, lost evidence, aggravated liability. Added to this is the growing weight of regulations such as NIS2, which extend obligations to many companies that are still poorly prepared.

Solutions

Turning cyber risk into managed risk

I support you on the legal side of cybersecurity, both in prevention and in crisis management.

Upstream, I audit your security obligations under the GDPR and sector-specific regulations, I structure your documentation (security policy, incident management procedures, charters), and I secure your contracts with suppliers on the security front. I help you prepare an operational crisis management plan.

In the event of an incident, I step in for crisis management: classifying the breach, notifying the CNIL, informing the data subjects, preserving evidence, filing a complaint and defending your interests. My objective is to limit your liability and the consequences of the incident, by acting swiftly and accurately.

Method

Our method

Audit of your obligations

I analyse the cybersecurity obligations applicable to your activity: GDPR, sector-specific regulations (NIS2, DORA), contractual commitments. This audit identifies your actual obligations and the gaps to be closed in order to secure your legal exposure.

Legal and documentary security

I structure your security documentation: security policy, incident and breach management procedures, charters, contractual governance of suppliers. This documentation demonstrates your diligence and limits your liability in the event of an incident.

Preparation for crisis management

I prepare your cyber crisis management plan: roles, reflexes, decision-making chain, notification templates. Your teams know how to react, who to mobilise and which obligations to comply with from the very first hours of an incident.

Intervention in the event of an incident

In the event of a cyberattack, I step in for crisis management: classifying the incident, notifying the CNIL, informing the data subjects, preserving evidence, filing a complaint and defending your interests against third parties. You are supported at every critical step.

FAQ

Questions?

What legal cybersecurity obligations apply to companies?

The GDPR imposes an obligation to secure personal data appropriate to the risk. To this are added sector-specific regulations (NIS2 for many sectors, DORA for finance), contractual obligations towards clients, and a general duty of care. Companies must implement technical and organisational measures, document their approach and know how to respond in the event of an incident.

What should you do in the event of a cyberattack or data breach?

The response must be swift and methodical: classify the incident, contain it, assess whether it constitutes a personal data breach, and where applicable notify the CNIL within 72 hours, and even inform the data subjects concerned. In parallel, evidence must be preserved, communication managed and the filing of a complaint considered. Legal support in crisis management prevents errors with serious consequences.

When must a data breach be notified to the CNIL?

A personal data breach must be notified to the CNIL within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to individuals. Where the risk is high, the data subjects concerned must also be informed. Classifying the breach and assessing the risk are delicate legal decisions that determine the extent of the obligations.

Can directors be held liable?

Yes. In the event of a failure to meet security obligations, the company's liability may be engaged, and that of its directors in certain circumstances. A cyberattack revealing negligence in securing systems may give rise to sanctions from the CNIL, to actions by aggrieved clients or partners, and even to prosecution. Anticipating these risks is part of sound corporate governance.

How should security be governed in contracts with suppliers?

Contracts with IT suppliers, hosting providers and subprocessors must include precise security clauses: required standards, obligations in the event of an incident, notification, audit, reversibility. On the GDPR side, Article 28 requires a contract governing subprocessing. A clear allocation of security responsibilities prevents you from being left alone to bear the consequences of a flaw attributable to a third party.

What is a legally robust security policy?

Beyond technical measures, a robust security approach is documented: security policy, incident and breach management procedures, IT charters, staff awareness, contractual governance of suppliers. This documentation demonstrates that the company has taken measures appropriate to the risk, a decisive factor in limiting its liability in the event of an inspection or dispute.

Should you file a complaint after a cyberattack?

Filing a complaint is often recommended: it establishes the company as a victim, may be required by insurers, and contributes to the fight against cybercrime. It must be accompanied by the proper preservation of technical evidence. The decision and the arrangements form part of an overall crisis management strategy, combining the technical, legal, insurance and communication aspects.

How can cyber risk be anticipated from a legal standpoint?

Anticipation involves auditing the obligations applicable to your activity, putting in place security documentation, governing your suppliers contractually, and preparing a crisis management plan defining roles and reflexes in the event of an incident. Preparing in calmer times makes it possible to react swiftly and accurately the day an attack strikes, and to considerably limit the consequences.

Anticipate cyber risk from a legal standpoint: security obligations, data breach management, directors' liability and crisis management.

We support tech and commerce companies with dual legal and technical expertise, from analysis to implementation.

Homme en costume bleu foncé avec cravate et pochette blanche, bras croisés, regardant vers l'avant.

Resources

Our content & guides

00
article(s) displayed out of
00

12 min

Applications mobiles : les principales obligations juridiques en 2026
CGU, RGPD version mobile, SDK tiers, accessibilité, Data Act, IA embarquée, règles des stores : la cartographie complète des obligations juridiques d'une application mobile en 2026, avec la checklist de lancement en 12 points.

13 min

DPO dans le secteur de la santé : missions, désignation et bonnes pratiques
Quand la désignation d'un DPO est-elle obligatoire dans la santé, quelles sont ses missions au quotidien et comment le positionner correctement ? Le guide pratique, avec les spécificités du secteur et les évolutions à venir avec l'IA et l'EHDS.

14 min

IA en santé : AI Act, RGPD et dispositif médical, le triple cadre
Un logiciel d'IA en santé cumule trois réglementations : le MDR pour la qualification de dispositif médical, l'AI Act pour le régime haut risque, le RGPD pour les données, plus la garantie humaine française. Le guide de qualification et les checklists fabricant et établissement.

Let's discuss your project

Need to secure a contract, manage compliance, or anticipate a dispute? Our first meeting is designed to understand your needs and clearly explain how we can help.

Book an appointment
Book an appointment
Book an appointment📆 15-Min Meeting