11.3: Privileged accounts and system administration accounts

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

1. The relevant entities shall maintain policies for management of privileged accounts and system administration accounts as part of the access control policy referred to in point 11.1.

2. The policies referred to in point 11.3.1 shall:

  1. establish strong identification, authentication such as multi-factor authentication, and authorisation procedures for privileged accounts and system administration accounts;
  2. set up specific accounts to be used for system administration operations exclusively, such as installation, configuration, management or maintenance;
  3. individualise and restrict system administration privileges to the highest extent possible,
  4. provide that system administration accounts are only used to connect to system administration systems.

3. The relevant entities shall review access rights of privileged accounts and system administration accounts at planned intervals and be modified based on organisational changes, and shall document the results of the review, including the necessary changes of access rights.

This requirement is part of the framework:  
NIS2 Implementing Regulation

Other requirements of the framework

50528
11.3: Privileged accounts and system administration accounts
Best practices
How to implement:
11.3: Privileged accounts and system administration accounts
This policy on
11.3: Privileged accounts and system administration accounts
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 maintain policies for management of privileged accounts and system administration accounts as part of the access control policy referred to in point 11.1.

2. The policies referred to in point 11.3.1 shall:

  1. establish strong identification, authentication such as multi-factor authentication, and authorisation procedures for privileged accounts and system administration accounts;
  2. set up specific accounts to be used for system administration operations exclusively, such as installation, configuration, management or maintenance;
  3. individualise and restrict system administration privileges to the highest extent possible,
  4. provide that system administration accounts are only used to connect to system administration systems.

3. The relevant entities shall review access rights of privileged accounts and system administration accounts at planned intervals and be modified based on organisational changes, and 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.3: Privileged accounts and system administration accounts
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.3: Privileged accounts and system administration accounts
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
Regular reviews of the account administration policy
Critical
High
Normal
Low
2
requirements
System management
Access control and authentication

Regular reviews of the account administration policy

This task helps you comply with the following requirements

Periodic review of access rights
Critical
High
Normal
Low
2
requirements
System management
Access control and authentication

Periodic review of access rights

This task helps you comply with the following requirements

Assigning roles related to access management and managing privileged access
Critical
High
Normal
Low
3
requirements
System management
Access control and authentication

Assigning roles related to access management and managing privileged access

This task helps you comply with the following requirements

Use of dedicated admin accounts in critical data systems
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.