Identity Governance & Administration
sara.next
  1. sara.next
  2. Solutions
  3. NIS2: control and accountability of entitlements

Solutions · By requirement

NIS2: control and accountability of entitlements

How to put requests, approvals, reviews and access revocation in order in an organisation subject to cybersecurity requirements.

  • requests and approvals
  • periodic reviews
  • evidence of control

Context

Access is part of risk management, not just account administration

In organisations subject to NIS2 requirements, entitlement-related risk arises where people, processes and systems meet. An employee changes department, a contractor finishes a contract, an administrator gains permissions to the production environment, and the application owner has no up-to-date knowledge of who has access and why. Even correct authentication does not solve the problem of excessive or outdated permissions.

sara.next supports the Identity Governance & Administration layer: recording and approving requests, modelling roles and permission attributes, running periodic reviews and documenting decisions. It is a governance layer that complements identity directories, SSO, MFA and the technical safeguards of target systems.

Operational example

Time-bound access to a production system

A maintenance employee receives time-bound access to a production system. The resource owner approves the scope of the role, the technical team makes the change, and the next review confirms whether further access is justified. After a change of position, a modification or removal request goes for execution. The organisation retains a history from which the decisions can be reconstructed.

EmployeeResource ownerTechnical teamsara.nextRequesttime-bound access · roleApprovalrole scopeExecutionchange in the systemReviewjustification of accessChange of positionmodification or removalHistorydecisions that can be reconstructed
Illustrative diagram. Execution can be manual or automatic — if the appropriate integration has been configured.

An implementation expert's view

Owners and rules first, then automation

The most common mistake is starting the project by importing all accounts. First you need to agree:

  1. application owners,
  2. approval rules,
  3. the catalogue of permissions,
  4. how the actual execution of changes is confirmed.

Only then automate. Otherwise the IGA system merely digitises a disorganised process.

Scope

Limits of the solution

NIS2 covers much more than access management: including incident management, business continuity, supply chain security and risk management.

Notesara.next supports a selected area of access control; it does not on its own ensure compliance with NIS2.

The scope of obligations depends on the applicable national legislation and the classification of the entity.

Discuss the permission model and the scope of your first IGA implementation

During a technical consultation we will go through your applications, roles and the scope of the first implementation stage.