They talk about us
Watch the videos and their transcriptsVideos
Kohen Avocats, NIS2 Directive lawyers in Paris
NIS2 Directive lawyer in Paris: scope, security, notification
Essential or important entity, governance and Article 21 measures, incident notification, supplier contracts, supervision and penalties: our NIS2 lawyers in Paris prepare companies and their management for Directive (EU) 2022/2555, and assist IT service providers whose clients are subject to it. As at 31 October 2026, the French transposition law has not yet been published in the Official Journal (Journal officiel).
The firm can be reached 24/7. The Directive requires essential and important entities to submit an early warning within 24 hours of becoming aware of a significant incident, followed by an incident notification within 72 hours (Article 23 of the NIS2 Directive); these time limits will apply in France once the transposition law is in force. A personal data breach must already be notified to the CNIL (the French data protection authority) without undue delay and, where feasible, within 72 hours (Article 33 of the GDPR).
4,9/5
Average Google review rating270 reviews
I received very high-quality support from this criminal lawyer. His professionalism, his complete command of the case and his constant involvement at every stage of the proceedings deserve to be highlighted. Communication was clear, structured and responsive, with precise advice suited to my situation. I recommend this lawyer to anyone looking for a rigorous and effective criminal defence.
Mr Kohen handled my criminal case. I am very satisfied with the work he did and I recommend him without any hesitation.
Excellent criminal defence lawyer, he got me out of trouble in a protection order case brought abusively by my ex
Very satisfied with the solution he found for my defence before the court. All the best
Hassan Kohen is a young, seasoned and highly competent lawyer. He is an excellent listener, shows great empathy and has a strong human sensitivity. Available and responsive, he has complete mastery of his profession.
I had a very good experience with Hassan Kohen. He took the time to listen to me carefully and to fully understand my situation. He is a lawyer who gives sound advice, caring and available, who knows how to steer his clients in the right direction. I recommend him without hesitation to anyone looking for an attentive and competent professional.
Mr Kohen advised and supported us well. I thank him for everything he did.
Paris Bar
Emergencies 24/7
Preliminary case review
Send your documents. Receive an analysis.
Hassan Kohen
Lawyer (avocat) at the Paris Bar, digital law, NIS2 Directive compliance, IT contracts and cybersecurity liability.
Official profile in the directory of French lawyers (CNB, National Bar Council) · 4.9/5 on Google (270 reviews)
Page updated on 1 November 2026.
Quick answer
Directive (EU) 2022/2555, known as NIS2, applies to public or private entities in the sectors listed in its Annexes I and II that are at least medium-sized enterprises, and to certain entities regardless of their size (Article 2). It classifies them as essential entities and important entities (Article 3), requires them to take cybersecurity risk-management measures (Article 21) and to notify significant incidents (Article 23). Management bodies approve these measures, oversee their implementation and must follow training (Article 20). Member States had to transpose it by 17 October 2024 at the latest (Article 41). In France, the bill on the resilience of critical infrastructure and the strengthening of cybersecurity (projet de loi relatif à la résilience des infrastructures critiques et au renforcement de la cybersécurité) was adopted by the Senate on 12 March 2025, then examined by a special committee of the National Assembly; as at 31 October 2026, no transposition law has been published. The following remain applicable: the Act of 26 February 2018 for operators of essential services, the Defence Code (code de la défense) for operators of vital importance, and the GDPR for personal data. Kohen Avocats, a NIS2 law firm in Paris 16th arrondissement, acts for the entities concerned, their executives and their suppliers. Contact us on +33 6 89 11 34 45.
An entity to classify, an incident to notify, a supplier contract to review?
Understanding your situation
The NIS2 Directive, explained
Directive (EU) 2022/2555 of 14 December 2022 lays down measures that aim to achieve a high common level of cybersecurity across the Union. Who is covered, where French transposition stands, what the Directive requires of management and staff, how to notify an incident, and what the entity, its executives and its suppliers risk.
Key points
Is your entity within the scope of NIS2? Four checks
Sector, size, exceptions, competent Member State: classification determines everything else.
A covered sector. Annex I, sectors of high criticality: energy, transport, banking, financial market infrastructures, health, drinking water, waste water, digital infrastructure, ICT service management (business-to-business), public administration, space. Annex II, other critical sectors: postal and courier services, waste management, chemicals, food, manufacturing, digital providers, research.
Sufficient size. The Directive covers entities that qualify at least as medium-sized enterprises within the meaning of Recommendation 2003/361/EC (Article 2(1)). Small enterprises remain in principle outside its scope: under that Recommendation, these employ fewer than 50 persons and have an annual turnover or annual balance sheet total not exceeding €10 million.
Size exceptions. The following are covered regardless of their size, in particular: providers of public electronic communications networks or publicly available electronic communications services, trust service providers, top-level domain name registries and DNS service providers, an entity that is the sole provider in a Member State of a service essential for the maintenance of critical societal or economic activities, where that State has identified it as such (Article 3), critical entities within the meaning of Directive (EU) 2022/2557, and entities providing domain name registration services (Article 2(2) to (4)).
The competent Member State. An entity in principle falls under the jurisdiction of the Member State in which it is established. Providers of electronic communications networks or services fall under the State in which they provide their services; DNS service providers, top-level domain name registries, domain name registrars, providers of cloud computing services, data centre services, content delivery networks, managed services and managed security services, online marketplaces, online search engines and social networking platforms fall under the State of their main establishment in the Union, where decisions related to cybersecurity risk management are predominantly taken; public administration entities fall under the State that established them (Article 26).
The category is then determined. Essential entities include in particular Annex I entities that exceed the ceilings for medium-sized enterprises, that is, under the Recommendation, at least 250 persons, or an annual turnover above €50 million and a balance sheet total above €43 million, as well as qualified trust service providers, top-level domain name registries and DNS service providers regardless of their size, and central government public administration entities. The other Annex I and II entities are important entities (Article 3 of Directive (EU) 2022/2555).
The difference lies mainly in supervision: ex ante supervision for essential entities, “ex post” supervision for important entities, and different maximum fines (Articles 32 to 34). ANSSI (the French national cybersecurity agency) offers on MonEspaceNIS2 a scope simulator and a pre-registration service, which provide guidance but do not amount to a legal classification: the firm checks the entity's actual activity, the group it belongs to and its chain of clients before reaching a conclusion. For an organisation that is not itself subject to the Directive but supplies an entity that is, the question shifts to the contract (see tab 5).
The timeline
Where NIS2 transposition in France stands, and what already applies
A directive in force at European level, a French law still under discussion, national texts still applicable.
December 2022
Adoption of the Directive on 14 December 2022, publication in the Official Journal of the European Union on 27 December 2022.
17 and 18 October 2024
Transposition deadline set by Article 41: “They shall apply those measures from 18 October 2024.” The first NIS Directive is repealed with effect from the same date (Article 44).
15 October 2024
Presentation to the Council of Ministers of the bill on the resilience of critical infrastructure and the strengthening of cybersecurity, which transposes three directives, including NIS2 (legislative file on Légifrance).
12 March 2025
Adoption of the bill by the Senate at first reading (adopted text No. 78), after the accelerated procedure was triggered.
10 September 2025
Vote on the text by a special committee of the National Assembly (report No. 1779). As at 31 October 2026, the file of the National Assembly mentions no adoption in plenary session.
17 March 2026
Publication by ANSSI of the Référentiel Cyber France (ReCyF), a working document listing the measures recommended to meet the objectives of NIS2, “non-mandatory by default” (our translation).
As at 31 October 2026, no transposition law has been published in the Official Journal, and no French text yet incorporates the obligations of the Directive for companies. ANSSI sums it up as follows: “NIS2 will therefore enter into force in France once all the transposition texts (law, decrees, orders) have been promulgated.” (our translation) (ANSSI, MonEspaceNIS2). It adds that this date does not correspond to the date on which all the requirements imposed on regulated entities will apply.
Three regimes continue to apply. Operators of essential services designated by the Prime Minister remain subject to the Act of 26 February 2018, which transposed the first Directive and remains in force according to Légifrance: security rules applied at their own expense (Article 6), reporting of incidents to ANSSI “without delay after becoming aware of them” (our translation) (Article 7), documentary and on-site inspections (Article 8) and fines targeting their executives (Article 9). Operators of vital importance apply the rules set by the Prime Minister and inform the Prime Minister of their incidents without delay (Articles L. 1332-6-1 and L. 1332-6-2 of the Defence Code (code de la défense)). Finally, any entity that processes personal data must ensure its security and notify breaches to the CNIL (Articles 32 and 33 of the GDPR).
Waiting for the law before starting would be a timing mistake: ANSSI encourages future essential and important entities to begin now a security approach consistent with NIS2 (ANSSI page on NIS2). The firm follows the parliamentary process and will adapt scope analyses to the text finally promulgated.
The obligations
Governance and Article 21 measures: what management must approve
Ten minimum measures, a risk-based approach, and management accountable for their implementation.
Policies on risk analysis and information system security, and incident handling (Article 21(2)(a) and (b)).
Business continuity: backup management, disaster recovery and crisis management (point (c)).
Supply chain security, including relationships with direct suppliers and service providers (point (d)).
Security in the acquisition, development and maintenance of systems, including vulnerability handling and disclosure (point (e)).
Policies and procedures to assess the effectiveness of the measures taken (point (f)).
Basic cyber hygiene practices and cybersecurity training (point (g)).
The use of cryptography and, where appropriate, encryption (point (h)).
Human resources security, access control and asset management (point (i)).
Multi-factor or continuous authentication, and secured communications, including emergency communications, where appropriate (point (j)).
These measures are proportionate. They ensure “a level of security of network and information systems appropriate to the risks posed”, taking into account the state of the art, applicable standards and the cost of implementation, and their proportionality is assessed in the light of the entity's exposure to risks, its size, the likelihood of incidents and their severity (Article 21(1)). An entity that finds a shortcoming takes the necessary corrective measures without undue delay (paragraph 4).
Management is in the front line. Member States ensure that the management bodies of essential and important entities “approve the cybersecurity risk-management measures taken by those entities in order to comply with Article 21, oversee its implementation and can be held liable for infringements by the entities of that Article”, and that their members “are required to follow training” (Article 20 of Directive (EU) 2022/2555).
A governance deficit cannot be shifted, without a specific complaint, onto an IT department employee. After an intrusion through remote access protected by a trivial password, the Paris Court of Appeal held that the dismissal of an IT department employee was without real and serious cause: “While the technical investigations carried out by parties external to the company revealed technical failures affecting the company's IT system and a governance deficit that contributed to the cyberattack of 10 April 2020, the dismissal letter does not attribute to the employee any specific complaint amounting to misconduct” (our translation) (CA Paris, pôle 6, ch. 8, 18 December 2025, No. 22/04541). The court noted that a quote for a security audit had been sent to management with no indication of any follow-up by the employer, and that management had not followed through on the recruitment of a system and network administrator initiated in 2019.
Evidence of compliance has to be prepared. Written policies, management decisions, training records, incident register, supplier assessments: these are the documents the authority will request during an inspection (Articles 32 and 33). The firm drafts the governance documentation and aligns it with the technical measures put in place by your teams or your service providers.
The incident
Significant incident: early warning, notification, final report
Short time limits, multiple recipients, and coordination with the GDPR to organise.
Classify
An incident is significant if it has caused or is capable of causing severe operational disruption of the services or financial loss for the entity, or considerable material or non-material damage to other persons (Article 23(3)).
24 hours
Early warning to the CSIRT or competent authority, without undue delay and at the latest 24 hours after becoming aware of the incident, indicating, where applicable, whether the incident is suspected of being caused by unlawful or malicious acts or could have a cross-border impact (paragraph 4, point (a)).
72 hours
Incident notification, with an initial assessment of its severity and impact and, where available, the indicators of compromise (point (b)).
On request
Intermediate report on relevant status updates, at the request of the CSIRT or the authority (point (c)).
One month
Final report no later than one month after the notification: detailed description, likely root cause, mitigation measures, cross-border impact; progress report if the incident is still ongoing (points (d) and (e)).
Recipients
Where appropriate, informing the recipients of services that are likely to be affected without undue delay, and communicating the measures they can take in response to a significant cyber threat (paragraphs 1 and 2).
Notifying does not worsen the entity's position: “The mere act of notification shall not subject the notifying entity to increased liability.” (Article 23(1) of Directive (EU) 2022/2555). Notification does not, however, protect against a penalty on the merits. Under a related regime, the Council of State (Conseil d'État) upheld the €250,000 fine imposed by the CNIL on a company that had itself notified the attack on its website and cooperated, but had already been penalised twice in five years, noting that the imposition of a penalty “is not conditional on a prior formal notice” (our translation) (CE, 10e ch., 26 April 2022, No. 449284).
The same event may require several reports. If personal data are affected, the controller notifies the breach to the CNIL without undue delay and, where feasible, “not later than 72 hours after having become aware of it” (Article 33 of the GDPR). An operator of essential services currently reports its incidents to ANSSI under the 2018 Act (Article 7). The firm prepares a single classification and reporting procedure that distinguishes these channels and keeps dated evidence of each step.
Crisis management, criminal complaints, insurance and the provider's liability after an attack are covered on our cybersecurity lawyer page; data breach notification and dealings with the CNIL, on our GDPR lawyer page. See also our article on zero-day vulnerabilities, logs and notification to the CNIL.
Both sides
Supervision, penalties, liability: regulated entity or supplier
The same Directive reads differently depending on whether you are regulated, or whether you serve an entity that is.
You are an essential or important entity
- Classify the entity and the group, appoint those responsible, and have the measures approved by management.
- Document the Article 21 measures and the Article 23 notification procedure.
- Assess direct suppliers and provide in their contracts for security, audit, notification and reversibility.
You supply an entity subject to NIS2
- Check whether your own activity falls within NIS2, in particular as a managed service provider or cloud computing service provider.
- Respond to your clients' security questionnaires and clauses without accepting commitments you cannot meet.
- Keep a record of your duty to advise and of your security recommendations, whether refused or accepted.
Essential entities are subject to ex ante supervision: on-site inspections and off-site supervision, regular and targeted security audits, requests for evidence, binding instructions and orders (Article 32). If these measures remain ineffective within the deadline set, the authority may request the suspension of an authorisation or a temporary prohibition on any person discharging managerial responsibilities at chief executive officer or legal representative level from exercising those responsibilities in the entity, until compliance is achieved and subject to procedural safeguards (Article 32(5)), except for public administration entities. Important entities are subject to “ex post” supervision, triggered by evidence, indications or information (Article 33).
The Directive sets a minimum for maximum fines: for an infringement of Article 21 or 23, national law must allow at least €10 million or 2% of total worldwide annual turnover for an essential entity, and at least €7 million or 1.4% for an important entity, whichever is higher (Article 34). These figures set what French law will have to provide as a minimum; they do not apply until that law is published. Executives remain liable under company law, towards the company or third parties, in particular for “misconduct in their management” (our translation) (Article L. 225-251 and Article L. 223-22 of the Commercial Code (code de commerce)); towards a third party, only misconduct separable from their duties engages their personal liability (Cass. com., 26 November 2025, No. 24-21.022).
The points the firm examines in every case:
FAQ
NIS2 compliance in France: frequently asked questions
Thirteen detailed answers, based on the Directive, the texts in force and verified decisions.
Does the NIS2 Directive already apply in France?
Not yet, as at 31 October 2026. Directive (EU) 2022/2555 is in force at European level and had to be transposed by 17 October 2024 at the latest, to apply from 18 October 2024 (Article 41 of the Directive). In France, the bill on the resilience of critical infrastructure and the strengthening of cybersecurity, presented to the Council of Ministers on 15 October 2024, was adopted by the Senate on 12 March 2025, then voted by a special committee of the National Assembly on 10 September 2025. No adoption in plenary session is mentioned in the National Assembly file, and no law has been published in the Official Journal as at that date (legislative file on Légifrance).
ANSSI states that NIS2 will enter into force in France once the transposition law, decrees and orders have been promulgated, and that this date will not correspond to the date on which all the requirements apply. The final text may still change during the parliamentary debates.
There is no complete vacuum, however. The Act of 26 February 2018, which transposed the first Directive, remains in force for operators of essential services designated by the Prime Minister (Article 5), the Defence Code governs the security of operators of vital importance, and the GDPR already requires the security of personal data. For each entity, the firm sets out what is required today and what will be required tomorrow.
Is my company covered by NIS2?
Three criteria combine. First, the sector: the activity must fall within a type of entity listed in Annex I (energy, transport, banking, financial market infrastructures, health, drinking water, waste water, digital infrastructure, ICT service management (business-to-business), public administration, space) or Annex II (postal services, waste, chemicals, food, manufacturing, digital providers, research). Next, size: the Directive covers entities that qualify at least as medium-sized enterprises within the meaning of Recommendation 2003/361/EC, or that exceed its ceilings. Finally, the place of activity: the entity must provide its services or carry out its activities within the Union (Article 2(1) of the Directive).
A small enterprise, within the meaning of that Recommendation, is one which “employs fewer than 50 persons and whose annual turnover and/or annual balance sheet total does not exceed EUR 10 million” (Recommendation 2003/361/EC, Annex, Article 2). It remains in principle outside the scope, subject to exceptions: electronic communications providers, trust service providers, domain name registries and DNS service providers, the sole provider in a Member State of a service essential for the maintenance of critical societal or economic activities, an entity whose disruption could have a significant impact on public safety, public security or public health, critical entities and central government public administration entities (Article 2(2) to (4)). For the sole provider and for an entity whose disruption could have such an impact, coverage depends on identification by the Member State (Article 3).
Classification is based on the actual activity, not on the corporate purpose. An industrial company that also operates a data centre, a group subsidiary, a software publisher that provides managed services to its clients: in each of these situations the analysis changes. The firm prepares a reasoned scope memo that management can produce in the event of an inspection.
Essential entity or important entity: what is the difference?
The substantive obligations are the same: the risk-management measures of Article 21 and the notification of significant incidents under Article 23. The difference lies in the category, supervision and penalties. Essential entities include in particular Annex I entities that exceed the ceilings for medium-sized enterprises, qualified trust service providers, top-level domain name registries and DNS service providers regardless of their size, certain electronic communications providers, central government public administration entities and critical entities. The other Annex I and II entities are important entities (Article 3 of the Directive).
An essential entity is subject to ex ante supervision: inspections, regular and targeted audits, security scans, requests for evidence and, if orders remain ineffective, measures that may go as far as a temporary prohibition on the chief executive officer or legal representative from exercising managerial responsibilities (Article 32). An important entity is subject to action taken, where necessary, “through ex post supervisory measures”, when there is evidence suggesting that it does not comply with the Directive (Article 33).
The maximum fines also differ: at least €10 million or 2% of total worldwide annual turnover for an essential entity, and at least €7 million or 1.4% for an important entity (Article 34). Two calculations must be distinguished. Size, which determines the classification, is assessed under Recommendation 2003/361/EC by aggregating the entity's data with those of its partner and linked enterprises (Annex, Article 6). The fine, by contrast, is calculated on the total worldwide annual turnover of the undertaking to which the entity belongs (Article 34(4) and (5)).
What should we do before the transposition law is published?
Prepare on the basis of the Directive, which sets the baseline that French law will have to respect, and apply the texts in force now. ANSSI encourages future essential and important entities to begin now an approach consistent with NIS2 and, since 17 March 2026, has been circulating the Référentiel Cyber France (ReCyF), which corresponds to the framework referred to in Article 14 of the bill. This framework is “non-mandatory by default” (our translation), but regulated entities that apply it will be able to rely on it in the event of an inspection (ANSSI page on NIS2).
Some obligations already exist. An operator of essential services applies the security rules set by the Prime Minister at its own expense (Article 6 of the Act of 26 February 2018), reports its incidents to ANSSI “without delay after becoming aware of them” (our translation) (Article 7), and its executives face a fine of €100,000 if they fail to comply with the security rules following a formal notice, €75,000 for failing to report and €125,000 for obstructing an inspection (Article 9). Every controller of personal data must ensure a level of security appropriate to the risk (Article 32 of the GDPR).
In practice, the firm proposes a sequence: scope memo, mapping of direct suppliers, draft security policy submitted to management, incident notification procedure, then contract review. This work is immediately useful under the GDPR and for current contracts, and it will be adjusted to the final text.
What security measures does the NIS2 Directive require?
Appropriate and proportionate technical, operational and organisational measures to manage the risks posed to network and information systems, and to minimise the impact of incidents (Article 21 of the Directive). They must ensure “a level of security of network and information systems appropriate to the risks posed”, taking into account the state of the art, applicable standards and the cost of implementation.
The Directive sets a minimum list: risk analysis and security policies, incident handling, business continuity with backups and crisis management, supply chain security, security in acquisition, development and maintenance, assessment of the effectiveness of measures, cyber hygiene and training, cryptography and encryption, human resources security and access control, multi-factor authentication and secured communications (Article 21(2)). An entity that finds a failure to comply takes the necessary corrective measures without undue delay (paragraph 4).
Courts already refer to public security recommendations when assessing an IT installation. Relying on an expert report noting that the ANSSI recommendations had not been applied, the Reims Court of Appeal held that the IT service provider of a company hit by ransomware “did not do everything possible to secure its client's IT system and committed a fault in performing its services” (our translation), while leaving half of the loss to be borne by the client for lack of a specification document (CA Reims, 1re ch. civ. et com., 28 April 2026, No. 24/01502). The firm translates the ten measures into written policies, management decisions and contractual requirements, while technical implementation remains in the hands of your teams or your service providers.
Can executives be held personally liable under NIS2?
The Directive provides for it, and French law already allows it under certain conditions. The management bodies of essential and important entities approve the Article 21 measures, oversee their implementation and must be capable of being held liable for infringements (Article 20 of the Directive). Natural persons who manage or represent an essential entity must be capable of being held liable for breaching their duty to ensure compliance with the Directive (Article 32(6)), a rule that Article 33(5) extends to important entities. The temporary prohibition on exercising managerial functions, requested where orders remain ineffective, is however reserved for essential entities (Article 32(5)). The French arrangements will depend on the transposition law.
Under company law, the directors and chief executive officer of a société anonyme, like the managers of a SARL, are liable towards the company or third parties in particular for “misconduct in their management” (our translation) (Article L. 225-251 and Article L. 223-22 of the Commercial Code). Towards a third party, the Court of Cassation (Cour de cassation) requires more: “the personal liability of a de jure executive towards third parties can only be established if he has committed misconduct separable from his duties. This is the case where the executive intentionally commits misconduct of particular seriousness, incompatible with the normal exercise of corporate functions.” (our translation) (Cass. com., 26 November 2025, No. 24-21.022). For operators of essential services, Article 9 of the 2018 Act already directly targets their executives.
An executive's best protection remains a record of his or her decisions: approved measures, budget decisions, training completed, alerts dealt with. The firm organises this traceability and defends executives who are implicated. See also our article on derivative actions for liability against company executives.
What are the deadlines for notifying a significant incident under NIS2?
The Directive sets out three stages (Article 23(4)). An early warning, without undue delay and at the latest within 24 hours of becoming aware of the significant incident, indicating where applicable a suspected malicious origin or a possible cross-border impact. An incident notification within 72 hours, with an initial assessment of the severity, the impact and, where available, the indicators of compromise. A final report no later than one month after the notification, describing the incident, its likely root cause and the mitigation measures; an intermediate report may be requested in the meantime.
The incident must also be significant: severe operational disruption of the services or financial loss for the entity, or considerable material or non-material damage to other persons (Article 23(3)). The Directive adds that “The mere act of notification shall not subject the notifying entity to increased liability.” (paragraph 1).
These time limits will apply once the French law is in force. Today, an operator of essential services reports its significant incidents to ANSSI without delay (Article 7 of the Act of 26 February 2018), and a personal data breach must be notified to the CNIL without undue delay and, where feasible, within 72 hours (Article 33 of the GDPR). Notification does not shield an entity from a penalty: the Council of State upheld a €250,000 fine against a company that had notified the attack on its website and cooperated, but had already been penalised twice in five years (CE, 10e ch., 26 April 2022, No. 449284). The firm drafts the procedure, the early-warning templates and the decision tree, and assists the entity on the day of the incident.
What penalties does the NIS2 Directive provide for?
Enforcement measures and, in addition, fines. The authorities must be able to issue warnings, adopt binding instructions, order the entity to cease a conduct, to bring its measures into compliance with Article 21 or to fulfil the obligations of Article 23 within a specified period, and to inform the recipients of its services of a significant cyber threat (Articles 32 and 33 of the Directive). These measures must be “effective, proportionate and dissuasive”.
For an infringement of Article 21 or 23, national law must allow administrative fines of a maximum of at least €10 million or 2% of the total worldwide annual turnover in the preceding financial year of the undertaking for an essential entity, and of at least €7 million or 1.4% for an important entity, whichever is higher (Article 34). These are minimums imposed on Member States when setting their maximum fines, not fines already applicable in France. Member States may also provide for periodic penalty payments. For an essential entity, the authority may also, after measures have proved ineffective, request the suspension of a certification or authorisation, or a temporary prohibition on exercising managerial responsibilities (Article 32(5)).
The regime currently in force for operators of essential services provides for criminal fines targeting their executives: €100,000 for failing to comply with the security rules after a formal notice, €75,000 for failing to report an incident, €125,000 for obstructing an inspection (Article 9 of the Act of 26 February 2018). The firm assists entities during inspections, responds to formal notices and challenges penalties.
How should we handle the security of our suppliers and subcontractors?
It is one of the minimum measures: supply chain security, including relationships with direct suppliers and service providers (Article 21(2)(d)). The entity takes into account “the vulnerabilities specific to each direct supplier and service provider”, the overall quality of their products and of their cybersecurity practices, including their secure development procedures (paragraph 3).
Delegating does not discharge responsibility. Under the GDPR, the Council of State held that the vulnerability behind a data leak was “the direct consequence of Optical Center's failure to carry out regular checks on the technical and organisational measures taken by its processor responsible for the security of its website” (our translation), and upheld the fine (CE, 10e ch., 26 April 2022, No. 449284). The contract matters as much as oversight: in a dispute arising from a data centre fire, the Douai Court of Appeal applied the hosting provider's limitation clauses and held that nothing required a backup at a geographically distant site, in the absence of a contractual stipulation or a proven industry standard; the client, which was claiming several million euros, obtained €1,800.48 (CA Douai, ch. 2 sect. 2, 24 April 2025, No. 23/00858).
The firm drafts security clauses: measurable requirements, incident notification within time limits compatible with those of Article 23, audit rights, regulated subcontracting, backups and recovery plan, negotiated liability caps, reversibility. A clause that deprives the debtor's essential obligation of its substance is deemed unwritten (Article 1170 of the Civil Code (code civil)), but this still has to be demonstrated. See our IT contracts lawyer page.
We are an IT service provider or hosting provider: what does NIS2 change for us?
Two things. First, your activity may fall directly within the Directive: under digital infrastructure, Annex I covers cloud computing service providers, data centre service providers and content delivery network providers, and under ICT service management (business-to-business), managed service providers and managed security service providers. These providers fall under the jurisdiction of the Member State of their main establishment in the Union, where decisions related to cybersecurity risk-management measures are predominantly taken (Article 26 of the Directive), and must submit registration information to the competent authority (Article 27).
Second, your clients that are subject to NIS2 will pass their requirements on to you by contract. The professional's duty to advise already weighs heavily. Towards a client that is itself a professional, it exists “where its competence does not give it the means to assess the exact scope of the technical characteristics of the system in question”, and it is then for the professional seller “to prove that it has fulfilled the duty to advise requiring it to enquire about the buyer's needs” (our translation) (Cass. com., 6 May 2026, No. 25-12.541, a dispute outside the IT sector). Applied to security, this duty led the Aix-en-Provence Court of Appeal, ruling on a protective attachment and without deciding the merits, to regard as well-founded in principle a claim against a health data hosting provider that had neither taken out nor recommended a backup at a remote site, although the clause limiting compensation to material losses was applied and the attachments were lifted (CA Aix-en-Provence, ch. 1-9, 6 February 2025, No. 24/01848).
The firm helps service providers classify their own situation, respond to security questionnaires, negotiate commitments they can keep and preserve evidence of their recommendations. A written security proposal, refused by the client, changes the outcome of a dispute. See our IT litigation lawyer page.
Our provider failed to secure our system: what does NIS2 change for our remedies?
NIS2 does not create a specific action against the provider: the remedy remains that of ordinary contract law, under which the debtor is ordered to pay damages for non-performance of its obligation unless it shows force majeure (Article 1231-1 of the Civil Code). The Directive does, however, change what the regulated entity must require and check. Supply chain security is one of the minimum measures, including in relationships with direct suppliers and service providers (Article 21(2)(d) of the Directive), and the entity must take into account the vulnerabilities specific to each of them and the quality of their cybersecurity practices (paragraph 3). A contract that sets measurable security requirements, an incident notification period compatible with Article 23 and an audit right gives the court a precise benchmark for assessing the breach. Conversely, an entity that neither expressed its needs nor monitored its supplier risks a sharing of liability, as in the Reims Court of Appeal judgment cited above (CA Reims, 1re ch. civ. et com., 28 April 2026, No. 24/01502), and, under the GDPR, failure to monitor a processor has already justified a penalty (CE, 10e ch., 26 April 2022, No. 449284).
The provider's contractual liability, its duty to advise, limitation clauses and gross negligence are covered on our IT litigation lawyer page; criminal complaints, insurance and crisis management after an attack, on our cybersecurity lawyer page.
Do executives and employees need NIS2 training?
Yes. The Directive requires that the members of management bodies “are required to follow training” and encourages similar training for employees on a regular basis, so that everyone gains sufficient knowledge to identify risks and assess cybersecurity risk-management practices (Article 20(2) of the Directive). Basic cyber hygiene practices and training are also among the minimum measures of Article 21 (point (g)).
Lack of training already has a cost under employment law. After a cyberattack, the Paris Court of Appeal ordered the employer to pay €5,000 in damages for breaching its duty to adapt and train an IT department employee, noting that in fifteen years he had “not been trained in technical areas of competence that were not his own but which he was forced to exercise de facto” (our translation) (CA Paris, pôle 6, ch. 8, 18 December 2025, No. 22/04541). The same judgment holds his dismissal to be without real and serious cause.
Individual vigilance also counts. According to the Court of Cassation, in payment matters, a user who discloses his or her security credentials in response to an email showing signs that would lead a normally attentive user to doubt its origin is grossly negligent, “regardless of whether or not he had been warned of the risks of phishing” (our translation) (Cass. com., 28 March 2018, No. 16-20.018). Working with security teams, the firm designs the legal component of executive training: obligations, liability, what to do in the event of an incident, evidence of decisions. See also our article on CEO fraud.
What are the fees for a NIS2 compliance lawyer?
Fees are set out in a written fee agreement, in accordance with Article 10 of the Act of 31 December 1971: before committing, you know what the engagement covers and what it costs.
The firm favours a fixed fee per stage: scope memo, review of governance and security policies, incident notification procedure, review or drafting of supplier clauses, legal training for management, assistance during an inspection, response to a formal notice, litigation with a service provider or defence of an executive. Technical services, such as security audits or penetration tests, are provided by specialised firms and are not included. For each stage, the agreement specifies the deliverables provided to management and the agreed timetable. Any new engagement gives rise to an amendment, with no unexpected invoicing.
For a first opinion based on your documents, the preliminary case review at €80 incl. VAT, through the form on this page, leads to a written analysis within 24 business hours. First contact on +33 6 89 11 34 45.
References
Official texts and related pages
The sources for this page, checked on 1 November 2026, and the firm's related areas of practice.
Official texts
- Directive (EU) 2022/2555 of 14 December 2022 (NIS2): scope (Articles 2 and 3), governance (Article 20), measures (Article 21), notification (Article 23), jurisdiction (Article 26), supervision and fines (Articles 32 to 34), transposition (Article 41)
- Recommendation 2003/361/EC: definition of small and medium-sized enterprises (Annex, Article 2)
- Regulation (EU) 2016/679 (GDPR): security of processing and notification of breaches (Articles 32 and 33)
- Bill on the resilience of critical infrastructure and the strengthening of cybersecurity: legislative file (Légifrance) and National Assembly file
- ANSSI, progress of transposition and ANSSI page on NIS2: stages, ReCyF
- Articles 5, 6, 7, 8 and 9 of Act No. 2018-133 of 26 February 2018: operators of essential services, security rules, incident reporting, inspections, penalties
- Articles L. 1332-6-1 and L. 1332-6-2 of the Defence Code: security of information systems of operators of vital importance
- Articles 1170 and 1231-1 of the Civil Code: essential obligation, contractual liability
- Articles L. 223-22 and L. 225-251 of the Commercial Code: liability of executives
- Article 10 of Act No. 71-1130 of 31 December 1971: fee agreement
Decisions cited
- Cass. com., 26 November 2025, No. 24-21.022: executive's separable misconduct
- Cass. com., 6 May 2026, No. 25-12.541: proof of the professional seller's duty to advise
- Cass. com., 28 March 2018, No. 16-20.018: phishing and gross negligence
- CA Paris, pôle 6, ch. 8, 18 December 2025, No. 22/04541: governance deficit after a cyberattack, training
- CA Reims, 1re ch. civ. et com., 28 April 2026, No. 24/01502: ransomware, provider's fault, sharing of liability
- CA Douai, ch. 2 sect. 2, 24 April 2025, No. 23/00858: data centre fire, limitation clauses
- CA Aix-en-Provence, ch. 1-9, 6 February 2025, No. 24/01848: health data hosting, recovery plan
- CE, 10e ch., 26 April 2022, No. 449284: oversight of the processor, penalty despite notification
An entity to classify, an incident to notify, a supplier to oversee?
The firm can be reached 24/7. Send us a description of your activity, the group organisation chart, your security policies, your suppliers' contracts or a dated account of the incident: Hassan Kohen reviews whether NIS2 applies, the obligations and the time limits, then tells you the appropriate course of action: compliance, notification, contract negotiation, response to an inspection or action against a service provider.