11.5: Identification

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

1. The relevant entities shall manage the full life cycle of identities of network and information systems and their users.

2. For that purpose, the relevant entities shall:

  1. set up unique identities for network and information systems and their users;
  2. link the identity of users to a single person;
  3. ensure oversight of identities of network and information systems;
  4. apply logging to the management of identities.

3. The relevant entities shall only permit identities assigned to multiple persons, such as shared identities, where they are necessary for business or operational reasons and are subject to an explicit approval process and documentation. The relevant entities shall take identities assigned to multiple persons into account in the cybersecurity risk management framework referred to in point 2.1.

4. The relevant entities shall regularly review the identities for network and information systems and their users and, if no longer needed, deactivate them without delay.

This requirement is part of the framework:  
NIS2 Implementing Regulation

Other requirements of the framework

50523
11.5: Identification
Best practices
How to implement:
11.5: Identification
This policy on
11.5: Identification
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

1. The relevant entities shall manage the full life cycle of identities of network and information systems and their users.

2. For that purpose, the relevant entities shall:

  1. set up unique identities for network and information systems and their users;
  2. link the identity of users to a single person;
  3. ensure oversight of identities of network and information systems;
  4. apply logging to the management of identities.

3. The relevant entities shall only permit identities assigned to multiple persons, such as shared identities, where they are necessary for business or operational reasons and are subject to an explicit approval process and documentation. The relevant entities shall take identities assigned to multiple persons into account in the cybersecurity risk management framework referred to in point 2.1.

4. The relevant entities shall regularly review the identities for network and information systems and their users and, if no longer needed, deactivate them without delay.

Read below what concrete actions you can take to improve this ->
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to
11.5: Identification
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
11.5: Identification
of the framework  
NIS2 Implementing Regulation
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Management of identification and access methods
Critical
High
Normal
Low
5
requirements
System management
Access control and authentication

Management of identification and access methods

This task helps you comply with the following requirements

Management of device and system identities
Critical
High
Normal
Low
3
requirements
System management
Access control and authentication

Management of device and system identities

This task helps you comply with the following requirements

Avoiding and documenting shared user accounts
Critical
High
Normal
Low
Using unique user names
Critical
High
Normal
Low

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.