11.2: Management of access rights

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

1. The relevant entities shall provide, modify, remove and document access rights to network and information systems in accordance with the access control policy referred to in point 11.1.

2. The relevant entities shall:

  1. assign and revoke access rights based on the principles of need-to-know, least privilege and separation of duties;
  2. ensure that access rights are modified accordingly upon termination or change of employment;
  3. ensure that access to network and information systems is authorised by the relevant persons;
  4. ensure that access rights appropriately address third-party access, such as visitors, suppliers and service providers, in particular by limiting access rights in scope and in duration;
  5. maintain a register of access rights granted;
  6. apply logging to the management of access rights.

3. The relevant entities shall review access rights at planned intervals and shall modify them based on organisational changes. The relevant entities shall document the results of the review including the necessary changes of access rights.

This requirement is part of the framework:  
NIS2 Implementing Regulation
Best practices
How to implement:
11.2: Management of access rights
This policy on
11.2: Management of access rights
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 provide, modify, remove and document access rights to network and information systems in accordance with the access control policy referred to in point 11.1.

2. The relevant entities shall:

  1. assign and revoke access rights based on the principles of need-to-know, least privilege and separation of duties;
  2. ensure that access rights are modified accordingly upon termination or change of employment;
  3. ensure that access to network and information systems is authorised by the relevant persons;
  4. ensure that access rights appropriately address third-party access, such as visitors, suppliers and service providers, in particular by limiting access rights in scope and in duration;
  5. maintain a register of access rights granted;
  6. apply logging to the management of access rights.

3. The relevant entities shall review access rights at planned intervals and shall modify them based on organisational changes. The relevant entities shall document the results of the review including the necessary changes of access rights.

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.2: Management of access rights
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.2: Management of access rights
of the framework  
NIS2 Implementing Regulation
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Regular reviewing of data system access rights
Critical
High
Normal
Low
Segregation of information security related duties
Critical
High
Normal
Low
15
requirements
Risk management and leadership
Cyber security management

Segregation of information security related duties

This task helps you comply with the following requirements

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.