Signal at work: Where NIS2 risks arise
Signal and other messengers can protect business communications while also raising new questions for risk management. Germany’s NIS2 Implementation Act has applied to affected entities since 6 December 2025. A private messenger or a compromised device does not in itself automatically trigger a NIS2 report. The risks, the safeguards in place and the impact of an incident are decisive.
Key takeaways
- Messengers belong in risk assessments. Affected entities must take appropriate and proportionate measures to protect their information security.
- Not every device incident must be reported. A NIS2 report is required when a significant security incident occurs.
- Management bears responsibility. It must implement the risk management measures and supervise their implementation.
What NIS2 requires for messenger use
The BSI Act requires particularly important and important entities to take appropriate, proportionate and effective risk management measures. These include policies for risk analysis, incident handling and, where appropriate, secure voice, video and text communications.
The law does not prescribe a particular messenger or impose a general requirement for an MDM container or a twelve-month chat log. Which measures are appropriate depends on how they are used and the risks facing the entity concerned. End-to-end encryption alone does not answer the question of how devices, access and business information are protected.
Assessing personal devices and business data
A company should first establish which messengers are used for which tasks. Relevant questions include whether employees exchange confidential contract information through them or need a channel to coordinate their response to disruptions. This assessment can help determine which information may be shared through which channel and who in the company is responsible.
Depending on the risk, implementation options include managed devices, access controls and established procedures for lost devices. The assessment should also cover how necessary business information remains available and who revokes access when an employee leaves. A written policy and a review of how it works in practice help make decisions traceable.
Where personal data is involved, the applicable data protection obligations must also be considered. The technical and contractual arrangements depend on the specific service and how it is used.
When an incident must be reported
A lost or compromised device must be investigated. The next step is to assess whether a significant security incident has occurred for the purposes of the NIS2 reporting obligation. This may be the case, for example, if an incident has caused or could cause severe operational disruption or financial loss. Potential significant damage to other people or organisations is also relevant.
For entities subject to reporting requirements, § 32 BSIG requires an early warning without undue delay and no later than 24 hours after becoming aware of the incident. A notification containing an initial assessment follows within 72 hours. A final report must generally be submitted no later than one month after that notification. If the incident is still ongoing at that point, a progress report must initially be submitted.
The internal process should establish who receives reports, assesses their significance and arranges notification. Other reporting obligations may also apply and must be assessed separately.
Management responsibility
The management of affected entities must implement the risk management measures and supervise their implementation. It must also attend training regularly. This includes addressing business communication risks within the existing security organisation.
Personal liability does not automatically arise simply because Signal or another messenger is permitted. § 38 BSIG governs liability towards the entity where a breach of duty has culpably caused damage. The company law rules applicable to the entity’s legal form apply. Management should therefore keep a traceable record of decisions on risks, measures and their review.
Frequently asked questions
Each question is locked. Tap to unlock the answer.
Does NIS2 ban Signal or WhatsApp?
The BSI Act does not impose a blanket ban on these services. Affected entities must assess whether their specific use and the safeguards in place are appropriate to the risks involved.
Must a compromised smartphone always be reported?
No. A NIS2 report requires a significant security incident. The entity must promptly assess the actual and potential impact.
Is device management mandatory under NIS2?
The law does not prescribe a specific MDM solution for every smartphone used for business. Device management can be an appropriate measure depending on usage and risk.
Editor’s Picks
Editor’s PickAdaptive MFA Under Fire: Risk Engines Miss 7M-Device Code Wave
More from the MBF Media Network
Digital ChiefsTech Mandates on the Supervisory Board: NIS2, the EU AI Act, and the Skills GapMyBusinessFutureNIS2 Implementation: What Mid-Sized Companies Still Need to DocloudmagazinSeparating NIS2 and DORA Compliance: A Compliance Cluster in Kubernetes
More from the MBF Media network
- NIS2 and the EU AI Act reveal the skills gap
- NIS2 implementation: A checklist for SMEs now
- Keeping NIS2 and DORA separate: Compliance clusters in Kubernetes
Image credit: AI-generated (November 2026)
Image source: AI-generated (November 2026)
Translated from the German original using artificial intelligence. The German version is authoritative.



