Define identities across critical services
Include staff, administrators, contractors, application identities and automation used across cloud and on-premises systems. Assign owners and map identities to services they can affect. Local accounts and supplier-created identities should not disappear merely because they are outside the main directory.
The Directive establishes risk-based requirements, not a universal identity-management product or architecture. Check the implementing law and guidance applicable to each entity.
Approve permissions according to responsibilities
Assign clear approval authority and use role-based rights where suitable. Distinguish authentication, which verifies identity, from authorisation, which determines permitted actions. Strong sign-in protection does not correct excessive permissions.
Review temporary and privileged rights, document emergency elevation and avoid automatically copying broad access from another employee.
Manage joiners, transfers and leavers
Coordinate employment changes with account creation, privilege adjustment and removal across relevant systems. Set review dates for contractors and verify account termination in applications outside central identity management.
Service accounts and application credentials need accountable owners, lifecycle controls and secure handling even though no individual worker signs in using them.
Secure authentication recovery
Choose appropriate authentication for exposed or privileged systems. Protect enrolment and recovery against impersonation, record bypasses, and train personnel to reject unexpected approval requests.
Article 21(2)(j) calls for multifactor or continuous authentication where appropriate; it does not establish one identical method for every system.
Test and report IAM effectiveness
Sample permissions against approvals and check whether dormant, privileged and supplier accounts remain justified. Test access removal after departures and review exceptions.
Document findings, remediation owners and repeat checks. Signed policy acknowledgements do not demonstrate that real permissions match authorised roles.
Points of clarification
Does NIS2 prescribe one mandatory product or inventory format?
No. Control design should reflect applicable national and sector-specific rules and the organisation's risks.
Is an approved policy enough to prove effectiveness?
No. Operational evidence, testing and corrective actions help demonstrate how the controls work.