Interpret the requirement in context
NIS2 Article 21(2)(j) refers to multifactor or continuous authentication solutions where appropriate, as well as secured communications. This is part of the broader Article 21 obligation for appropriate and proportionate cybersecurity risk-management measures.
It is misleading to treat every sign-in scenario as subject to one identical authentication mechanism. Consider service criticality, exposure, account privilege, accessibility and applicable national or sector-specific requirements.
Prioritise high-risk access paths
Assess remote access, cloud administration, privileged consoles, critical business applications and suppliers' connections. Identify users and systems that rely only on reusable passwords.
Phishing-resistant methods can provide stronger protection against credential interception than methods whose one-time codes may be relayed to attackers. Select mechanisms suitable for the architecture and risk.
Secure enrolment, resets and account recovery
Authentication strength depends on how factors are enrolled and replaced. Attackers may exploit weak help-desk identity checks to register their own authenticator or persuade users to approve unexpected requests.
Use controlled recovery procedures, approval records, protected fallback methods and alerts for material changes to authentication factors. Train staff to reject suspicious prompts and report lost devices promptly.
Include service and legacy constraints
Some systems cannot directly support contemporary authentication methods. Evaluate approved gateways, restricted management networks or other risk-based safeguards, recording residual exposure.
Noninteractive services and automated integrations may need certificate-based or other suitable machine authentication rather than employee-oriented prompts. Document ownership and secret lifecycle management.
Verify real coverage and response
Compare MFA policy and system configurations with the accounts and services actually in scope. Review bypass groups, privileged identities, emergency access and supplier accounts rather than relying solely on the number of enrolled users.
Exercise account recovery, inspect suspicious-sign-in reporting and verify that exceptions are reviewed. Retain test evidence and remediation decisions for management oversight.
Points of clarification
Does NIS2 prescribe a single technology for every entity?
No. Article 21 requires appropriate and proportionate measures, with national and relevant sector-specific rules also considered.
Is a written policy sufficient evidence?
No. Operational configuration, sampled testing, monitoring and verified remediation support effectiveness assessment.