NIS2 Belgium: are law firms in scope?
Legal services appear in neither Annex I nor Annex II of the Belgian Law of 26 April 2024. A Belgian law firm is therefore not a NIS2 entity, whatever its size. What remains: professional secrecy, the GDPR, and your NIS2 clients' security questionnaire.
The short answer
In almost every case, no: a Belgian law firm is not a NIS2 entity. Legal services appear in neither Annex I nor Annex II of the Belgian Law of 26 April 2024, which transposes the NIS2 Directive[1]. The law requires two cumulative conditions: providing a service listed in those annexes, and exceeding the size thresholds of a medium-sized enterprise[2]. The first condition fails for the legal profession, so firm size never even becomes relevant. A 150-lawyer firm is no more in scope than a three-partner practice.
That does not mean nothing applies. Three things catch Belgian firms anyway: professional secrecy under Article 458 of the Criminal Code, the GDPR with its 72-hour notification to the Data Protection Authority, and the supply chain clause your NIS2 clients will impose contractually. And a very concrete reminder: on 29 October 2026 the bar association software of AVOCATS.BE was breached, and the data of roughly 27,500 contacts ended up for sale on the dark web[5].
Are you in scope?
Run your firm through these tests. A single clear yes in the first list changes the answer.
- Does your firm provide, even incidentally, a service from Annex I or II? Note that even the most incidental service is enough to pull the whole organisation into scope, unless the definition says otherwise[2]. A practice that also runs a digital platform, a hosting service or a trust service could be caught through that activity.
- Is your structure a qualified trust service provider? Qualified electronic signatures or timestamping: these providers are essential entities regardless of size, the 50-FTE threshold does not apply[3].
- Does a department of yours carry out business-to-business ICT service management? That sub-sector sits in Annex I[2].
- Have you been specifically designated by the CCB? The authority can identify an entity as essential or important, for instance where it is the sole provider of a service[3].
If you answered no throughout, your firm is not a NIS2 entity and does not have to register on Safeonweb@Work. The next list almost certainly does apply to you.
- Do your clients include a company of more than 50 staff in energy, transport, health, water, banking, digital infrastructure, manufacturing or postal services? That client is probably a NIS2 entity and will have to evidence the security of its direct supply chain.
- Do you process Article 9 and 10 GDPR data, meaning health, beliefs or criminal convictions? In criminal, family and employment law, the answer is yes.
- Do your lawyers open files from a personal laptop, at a client's offices or in court?
What actually applies to a Belgian law firm
Four regimes stack up, and none of them is NIS2.
| Regime | Authority | What it requires of the firm |
|---|---|---|
| Professional secrecy, Art. 458 Criminal Code | Your Bar (AVOCATS.BE, OVB) | A criminally enforced duty. It covers confidentiality but, as AVOCATS.BE itself states, it is not sufficient to achieve GDPR compliance[4]. |
| GDPR | Data Protection Authority (APD/GBA) | Privacy notice, information at the point of collection, records of processing, breach notification within 72 hours[4]. |
| NIS2 Law of 26 April 2024 | Centre for Cybersecurity Belgium (CCB) | In principle not applicable to a law firm: legal services are absent from Annexes I and II[2]. |
| NIS2 supply chain | Your clients, by contract | The CCB recommends that NIS2 entities contractually require a label or certification from their suppliers, such as CyFun®[3]. |
The Belgian specific: professional secrecy exempts you from nothing
This is the most widespread misunderstanding in the profession. The DPO of the OBFG puts it bluntly: hearing I am bound by professional secrecy, so I need do nothing for GDPR compliance is simply wrong[7]. Professional secrecy lightens certain obligations; it does not remove them.
The dividing line drawn by AVOCATS.BE is sharp and practically useful. Where data is processed in the strict exercise of the lawyer's mission, including opposing-party data, Article 23 GDPR allows a national limitation and professional secrecy is precisely that limitation; the lawyer is then not obliged to grant an access request. Outside the lawyer's mission, in HR, supplier or staff matters, the right of access applies in full[8].
The operational consequence, frequently missed: this distinction assumes your systems can state, file by file, whether a given record belongs to the lawyer's mission or to administration. A shared drive where everything is mixed makes a written, reasoned refusal impossible. Separating storage is therefore not technical housekeeping: it is the precondition for refusing an access request defensibly.
The AVOCATS.BE incident of 29 October 2026
The attack did not target a law firm but the bar association management software of AVOCATS.BE. Around 27,500 contacts other than lawyers were affected: notaries, court staff, bar employees, training organisers, and contacts in public administrations, universities and police services. The exposed data consisted of identification details, name, e-mail address, telephone and in some cases postal address; according to the institution, no sensitive data within the meaning of Articles 9 and 10 GDPR and no banking data. The records were subsequently offered for sale on the dark web[5].
Three lessons, none of them about NIS2:
- The weak link is the software vendor, not necessarily your own network. Your firm inherits the risk of its practice-management tool.
- The response was twofold: notification to the APD and to the CCB, plus a criminal complaint[5]. The CCB remains the national cyber contact point even for an organisation that is not a NIS2 entity.
- Mundane data is still dangerous: the institution itself notes it can be cross-referenced with other sources and used for phishing or identity theft[5]. For a law firm, a plausible fake e-mail from a fellow lawyer is the classic payment-fraud vector.
The real constraint: your NIS2 clients' questionnaire
Your NIS2 clients work to hard deadlines, and they will pass them on. In Belgium, essential and important entities had to register with the CCB by 18 March 2025 at the latest, and digital-sector entities by 18 December 2024[1]. For conformity assessment, 18 April 2026 applies to the Basic or Important level of the CyFun® framework, with a further period until 18 April 2027 for certification at Essential level[1].
In other words, your clients are mid-campaign on evidence. The CCB explicitly recommends that they contractually require a label or certification from suppliers[3]. A firm advising a hospital, a transport operator or a manufacturer will therefore receive a security questionnaire, not because it is subject to NIS2, but because its client is.
The answer to give: Our firm is not a NIS2 entity under the Law of 26 April 2024, legal services not being listed in Annexes I and II. We nonetheless meet your direct supply chain security requirements through the following measures... Then a short, verifiable list. Dodging the question, or answering we are bound by professional secrecy, loses the mandate.
The first five actions
- Settle the question in writing, once. A one-page note: services provided, comparison against Annexes I and II, conclusion outside NIS2 scope, date, signature of the responsible partner. It will serve every client questionnaire and prevent ten internal debates.
- Map your practice tools and their vendors. Case management, billing, e-mail, document exchange, electronic signature. The 29 October 2026 incident started exactly there[5]. For each tool: where the data sits, who has access, what the contract says about breaches.
- Write your data breach procedure before you need it. AVOCATS.BE explicitly recommends appointing a person or crisis team and formalising the procedure, because 72 hours is very short[4]. Plan for both recipients seen in the real incident: APD and CCB.
- Separate lawyer's mission processing from administrative processing. This is what makes a secrecy-based refusal of an access request defensible[8], and it mechanically limits the surface exposed during an intrusion.
- Build a reusable response pack for NIS2 clients. Multi-factor authentication, tested backups, access revocation when staff leave, laptop encryption, incident procedure. The CCB's CyFun® framework is free and publicly available[3]: aligning with it, even without certification, gives you a credible answer grid.
Going further
If you also practise across a border, the text changes but the method does not: see our guide to NIS2 and law firms in France. For a neighbouring profession facing the same Belgian client questionnaires, read NIS2 Belgium: accounting firms and fiduciaries. Brussels-based practices will find local context on our B2B appointment setting in Brussels page.
At CyberNovaLabs.io
We help firms answer client security questionnaires without losing a month to them, and automate what can be automated in file handling: see our AI and business automation offer. We do not provide legal advice: for the definitive classification of your structure, the Law of 26 April 2024 and the CCB govern. Our engagements are quoted on request.
Talk to CyberNovaLabs.io about your firm
Sources
- CCB Safeonweb@Work — La loi NIS2 (obligations, enregistrement, ligne du temps)
- CCB — NIS2: Scope (annexes I et II, seuils de taille)
- CCB — La directive NIS2 en Belgique (brochure, exceptions de taille, chaine d'approvisionnement, CyFun)
- AVOCATS.BE — L'avocat et le RGPD
- La Libre — Cyberattaque chez Avocats.be : les donnees de 27 500 contacts mises en vente sur le dark web (06/11/2026)
- CCB Safeonweb@Work — NIS2 Quickstart Guide
- La Tribune AVOCATS.BE — Le RGPD, l'avocat et l'obligation de transparence et de loyaute
- La Tribune AVOCATS.BE — Protection des donnees personnelles contre secret professionnel : demandes d'acces
Qualified meetings, no lock-in.
Criteria in writing before launch, pay per meeting or monthly, stop with a simple email.
Read next
NGINX: five critical flaws patched urgently (18/11/2026)
Five critical flaws in NGINX, the software receiving traffic for more than 225 million websites, were fixed on 18 November 2026. Four authorities warned the same day. Your site can be exposed without having a single defect of its own.
Read the article →November 20, 2026 · 8 min readNIS2 Luxembourg: are estate agencies and syndics in scope?
Real estate appears in neither Annex I nor Annex II of the Luxembourg Act of 5 May 2026. But your supervisory authority already exists: the AED, on money laundering. Position as of 20 November 2026.
Read the article →November 13, 2026 · 7 min readData security: the CNIL issues ten fines (09/11/2026)
Ten fines, no headline breach, no company named: the French regulator sanctioned organisations on the strength of inspections alone. The six failings it lists — no MFA, vendors permanently connected, unsupported servers — describe the IT estate of a great many SMEs. Here is what changes, country by country.
Read the article →November 11, 2026 · 7 min readSMS sign-in abused in Belgium: the CCB warning (10/11/2026)
No patch to install: a setting. The CCB observed successful attacks on several Belgian organisations where SMS was the first factor — a number, a code, no password. Microsoft stops delivering those codes on 1 February 2027.
Read the article →November 10, 2026 · 7 min readWordPress flaw exploited during the update itself (04/11/2026)
WordPress 7.1.4 has fixed, since 28 October, a remote code execution triggerable during a core upgrade. CISA flagged it as exploited on 3 November, NCSC-NL warned on 4 November. For an SME, patching is not enough: you also have to look back.
Read the article →November 10, 2026 · 7 min readAI email assistant: consent, audit trail, confidentiality
An assistant that reads and writes your email touches everything: client contracts, employee files, competitor quotes. Three things must be written down before go-live - the approval rule, the audit log, the confidentiality perimeter. Here is the specification, clause by clause, and the four regulators to know.
Read the article →