NIS2 Article 23(2) requires essential and important entities to tell the recipients of their services, without undue delay, what measures or remedies those recipients can take in response to a significant cyber threat — and, where appropriate, to inform them of the threat itself. Unlike the CSIRT filing under Article 23(1), this notice goes to customers, in the language they actually use, across every market you serve. There is no central template and no shared deadline clock, which means the translation happens under time pressure with legal review in the loop.
Bluente is an AI document translation platform whose specific competence is format preservation: tables, numbering, footnotes and layout survive the trip across 120+ languages. This guide covers what Article 23(2) asks for, why the customer-facing tier is harder than the regulator filing, and how to have the multilingual notice ready before you need it.
What Does NIS2 Article 23(2) Actually Require?
Article 23 splits reporting into two audiences, and organisations routinely prepare for one and improvise the other.
Article 23(1) is the authority track: an early warning to the CSIRT or competent authority within 24 hours of becoming aware of a significant incident, a fuller incident notification within 72 hours, and a final report within one month. This is a structured filing to a regulator.
Article 23(2) is the recipient track. Member States must ensure that entities communicate, without undue delay, to recipients of their services who are potentially affected by a significant cyber threat, any measures or remedies those recipients can take in response — and, where appropriate, inform them of the threat itself.
The two differ in almost every practical dimension. The regulator filing is standardised, structured, and read by specialists. The recipient notice is unstructured, read by non-specialists, and public the moment it lands.
This is general information about a regulatory framework, not legal advice. Confirm the requirements applicable to your entity with counsel and with each national competent authority, since NIS2 is transposed member state by member state.
Why Is the Customer Notice Harder Than the Regulator Filing?
Four reasons, and they compound.
The audience is not technical. A CSIRT filing can say "unauthenticated RCE in an internet-facing appliance". A customer notice has to say what happened and what to do, in language a non-specialist can act on. That register is much harder to translate faithfully than a technical filing, because plain language is more culturally loaded, not less.
The clock is undefined. "Without undue delay" has no fixed hour count, which in practice means the standard is whatever is defensible after the fact. Waiting two days for translations is not a good answer.
The language set is set by your customer base, not by law. Article 23(1) goes to named national authorities. Article 23(2) goes to whoever buys from you, which for a European B2B provider is routinely eight to fifteen languages including markets you have no local entity in.
It is a legal document that reads like marketing. Every sentence is scrutinised for admission of liability, and every translated sentence has to carry the same hedging. A translation that turns "may have been affected" into "was affected" is a materially different statement.
Which Documents Does an Incident Notification Actually Involve?
The notice is rarely a single email. A realistic Article 23(2) response set includes:
The customer notification itself, usually an email plus a portal or status-page post
A technical advisory listing affected versions, indicators of compromise, and remediation steps
A customer-facing FAQ, which is where most of the actual questions get answered
Internal briefing notes for support and account teams, so front-line answers match the written notice
A regulator filing under Article 23(1), often in parallel to several member states
Contractual notices to customers whose agreements impose their own notification terms
These are DOCX, PDF, and PPTX files with tables of affected versions, numbered remediation steps, and version-controlled formatting. Bluente translates them across 120+ languages with tables and numbering intact — most files complete in under two minutes — so the advisory that goes out in Dutch has the same version table as the one that goes out in Italian.
How Do You Prepare the Multilingual Notice Before an Incident?
Do the translation work when you are not on a clock. Three assets carry most of the load.
1. A pre-approved notification template per notice type. Draft the customer notice, the advisory shell, and the FAQ skeleton with placeholders for incident-specific facts. Get them through legal once, in the source language, then translate the templates into your full language set and have local counsel or in-market staff review them once. On incident day you are translating the variable content, not the whole document.
2. A locked incident glossary. Terms like "significant incident", "affected", "potentially affected", "remediation", "workaround", "mitigating measure", and your own product and service names must render identically every time. This is where liability sits: the difference between "affected" and "potentially affected" is the difference between two legal positions. Bluente supports custom glossaries with do-not-translate entries for product and legal-entity names, with up to 95% accuracy on specialised terminology.
3. A pre-agreed language list mapped to customers. Decide in advance which markets get which languages, and where English is acceptable. Doing this during an incident is how markets get missed.
What Should the Translation Workflow Look Like on the Day?
Sequence it so translation is never the last step.
Freeze the source text and mark it as version 1. Every translation traces to a version.
Translate all languages in one batch, not sequentially by market. Sequential translation produces staggered disclosure, which looks like selective disclosure.
Route to in-market review in parallel, with a fixed short window and a named reviewer per language. Reviewers check meaning and hedging, not style.
Publish simultaneously across markets. If one language is slower, publish the English version everywhere with a stated translation timeline rather than delaying the rest.
Version every update the same way. Incidents generate revisions, and a revised English advisory paired with a stale German one is worse than no German at all.
The failure mode to design against is drift: three updates in, the English page says one thing and the Spanish page says something from two days ago. Batch translation of the full document set on every revision is the only reliable fix.
Is It Safe to Send Incident Documents to an AI Translation Platform?
It is a fair question, since incident documentation is among the most sensitive material an organisation produces — it names vulnerable systems, affected customers, and remediation status before the fix is fully deployed.
The requirements are the ones you would apply to any third party touching incident data: no retention of the document, no use of the content for model training, encryption in transit and at rest, and a documented compliance position. Bluente operates zero data retention with automatic deletion within 24 hours, end-to-end encryption, and SOC 2 Type II, GDPR, and ISO 27001 compliance. Documents are never used to train AI models, ours or third-party. NDAs can be signed same-day and a security pack sent ahead of any technical review.
Anything that cannot leave your environment at all is a different conversation — but note that the customer notice, by definition, is about to become public.
Frequently Asked Questions
Q: What does NIS2 Article 23(2) require? It requires essential and important entities to communicate, without undue delay, to recipients of their services who are potentially affected by a significant cyber threat, any measures or remedies those recipients can take — and where appropriate, to inform them of the threat itself.
Q: How is Article 23(2) different from Article 23(1)? Article 23(1) governs reporting to the CSIRT or competent authority on a defined clock: 24-hour early warning, 72-hour notification, one-month final report. Article 23(2) governs communication to your own customers, with no fixed hour count and no standard template.
Q: What language must the customer notification be in? NIS2 does not set a single language rule, and transposition varies by member state. In practice the notice needs to reach recipients in a language they can act on, which is determined by your customer base rather than by a fixed list.
Q: How fast does the translation need to be? "Without undue delay" has no fixed hour count, so translation time is difficult to defend as a reason for a gap. Pre-translated templates plus same-day batch translation of the incident-specific content is the workable pattern.
Q: How do you keep multilingual advisories consistent across updates? Version the source, re-translate the full document set on every revision as a single batch, and publish simultaneously. Partial updates produce a stale-language problem that is worse than not publishing in that language at all.
Q: Is incident documentation safe to translate with an AI platform? Use a platform with documented zero data retention, automatic deletion within 24 hours, end-to-end encryption, and SOC 2, GDPR, and ISO 27001 compliance, and confirm that documents are never used to train AI models.
Related Reading
How to Translate AS9102 First Article Inspection Reports in 2026
How to Translate an Employee Handbook for a Multilingual Workforce
Translate Meeting Transcripts and Recordings Into 120+ Languages (2026)
Sources and Further Reading
Primary standards, regulations and specifications referenced above:
How to Use AI on Confidential Documents Without Violating Client Privacy — practitioners describing this problem in r/Entrepreneurs
Last reviewed 23 August 2026. Written by the Bluente document engineering team, who build and test the format-preservation pipeline described above. We update these guides when the underlying standards, regulations or file formats change.
Start translating documents for free. Bluente preserves your formatting across 120+ languages in under 2 minutes. Try BluTranslate free — no credit card required.