With the NIS2 directive coming into force, many organisations in Europe face the need to adapt their security and compliance processes to much higher requirements. One of the key areas that is becoming central to this transformation is identity and access management (IGA – Identity Governance & Administration). In this article we look at what requirements NIS2 sets, why IGA is essential and how the sara.next solution can support organisations in preparing for these changes.
What is NIS2 and why does it matter?
The NIS2 directive (Network and Information Systems 2) is an update of the earlier NIS directive, aimed at raising the EU's level of resilience to cyber threats by setting obligations for "essential" and "important" entities from the point of view of critical infrastructure. In practice this means that entities covered by the directive must implement comprehensive security programmes – among other things, manage access, carry out audits, have incident response procedures and ensure management accountability.
As an analysis by One Identity points out: "The NIS2 Directive strengthens … access control, incident handling, supply-chain security, among others." (One Identity, 2024).
Why is IGA so crucial in the context of NIS2?
- NIS2 requires control over who has access to systems and data – IGA makes it possible to model, assign and review permissions in the organisation.
- The directive imposes obligations to document and report actions – IGA provides auditable trails of user actions and access.
- Requirements for continuous identity management, also with regard to suppliers and supply chains – proper management of non-human identities and external access becomes critical.
How to prepare an IGA implementation as part of NIS2 compliance?
Mapping permissions and identifying risks
Start by analysing which applications, systems and roles are critical in the context of the organisation. Establish who has which access and whether it matches business needs and minimum security requirements.
Implementing access review and certification processes
Regular access reviews and their documentation are one of the pillars of NIS2 compliance. They make it possible to eliminate excessive or unused permissions.
Applying the principle of least privilege and automating provisioning/off-boarding
Automating the process of granting, changing and removing access makes it possible to minimise errors and delays, which in the context of NIS2 means greater organisational resilience.
Integrating IGA with IT/HR processes and identity directories
An IGA solution should be fully integrated with HR systems and directories (Active Directory, Azure AD), and supervised through the management of business and technology roles.
Reporting, audit and monitoring
Ongoing reports, dashboards with certification results, auditing of user actions and tracking of anomalies are essential to demonstrate compliance and respond properly to incidents.
How does sara.next support NIS2 compliance?
- The central panel for managing applications and roles makes it possible to model permissions, assign roles and define processes in line with the principle of least privilege.
- Features for automating access reviews and generating auditable reports ensure audit readiness and compliance documentation.
- Integrations with directories and HR systems make it possible to implement a consistent user lifecycle – from onboarding, through role changes, to off-boarding.
- Automatic management of external access and monitoring of the permissions of non-human identities support the directive's requirements related to the supply chain and partners.
Recommendations for organisations
Phase 1: A prototype IGA implementation Start with a prototype IGA implementation for one critical domain (e.g. finance or production) and expand it scalably on that basis. 1–2 weeks Phase 2: KPIs and measuring progress Set KPIs that measure compliance progress: the percentage of access reviewed, the number of accounts removed, the response time to a role change. 1–2 weeks Phase 3: Management involvement (NIS2) Include the role of management in internal communication – NIS2 requires the board to be accountable for cybersecurity. 1 week Phase 4: Training and communication Provide regular training and communication so that users understand that roles and permissions should not be treated as permanent. 1–2 weeks Phase 5: Monitoring and analysis of exceptions Implement mechanisms for continuous monitoring and automatic analysis of exceptions – this increases detectability and speed of response. 2–3 weeks Compliance with the NIS2 directive is a challenge, but also an opportunity to raise the level of security and the effectiveness of identity management in the organisation. By implementing modern IGA with a solution such as sara.next, organisations can not only meet legal requirements, but above all gain an advantage in access management, risk reduction and auditability. It is time to prepare today – because tomorrow's compliance requires action today.
Sources
- Omada Identity, “Seven Ways NIS2 Requirements Are Driving the Need for Modern IGA”, 2024.
- ConductorOne, “The NIS2 Directive: What to Know and What It Means for Identity”, 2024.
- Elimity, “The 8 Crucial Identity Security Controls for NIS2-Compliance”, 2024.
- PointSharp, “Identity and Access Management: The Foundation for NIS2 Compliance”, 2024.
- OpenIAM, “Solutions for NIS2 Compliance – Meet the EU’s cybersecurity mandate”, 2024.