11.6: Authentication

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

1. The relevant entities shall implement secure authentication procedures and technologies based on access restrictions and the policy on access control.

2. For that purpose, the relevant entities shall:

  1. ensure the strength of authentication is appropriate to the classification of the asset to be accessed;
  2. control the allocation to users and management of secret authentication information by a process that ensures the confidentiality of the information, including advising personnel on appropriate handling of authentication information;
  3. require the change of authentication credentials initially, at predefined intervals and upon suspicion that the credentials were compromised;
  4. require the reset of authentication credentials and the blocking of users after a predefined number of unsuccessful log-in attempts;
  5. terminate inactive sessions after a predefined period of inactivity; and
  6. require separate credentials to access privileged access or administrative accounts.

3. The relevant entities shall to the extent feasible use state-of-the-art authentication methods, in accordance with the associated assessed risk and the classification of the asset to be accessed, and unique authentication information.

4. The relevant entities shall review the authentication procedures and technologies at planned intervals.

This requirement is part of the framework:  
NIS2 Implementing Regulation

Other requirements of the framework

50525
11.6: Authentication
Best practices
How to implement:
11.6: Authentication
This policy on
11.6: Authentication
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 implement secure authentication procedures and technologies based on access restrictions and the policy on access control.

2. For that purpose, the relevant entities shall:

  1. ensure the strength of authentication is appropriate to the classification of the asset to be accessed;
  2. control the allocation to users and management of secret authentication information by a process that ensures the confidentiality of the information, including advising personnel on appropriate handling of authentication information;
  3. require the change of authentication credentials initially, at predefined intervals and upon suspicion that the credentials were compromised;
  4. require the reset of authentication credentials and the blocking of users after a predefined number of unsuccessful log-in attempts;
  5. terminate inactive sessions after a predefined period of inactivity; and
  6. require separate credentials to access privileged access or administrative accounts.

3. The relevant entities shall to the extent feasible use state-of-the-art authentication methods, in accordance with the associated assessed risk and the classification of the asset to be accessed, and unique authentication information.

4. The relevant entities shall review the authentication procedures and technologies at planned intervals.

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.6: Authentication
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.6: Authentication
of the framework  
NIS2 Implementing Regulation
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Centralizing network authentication, authorization, and auditing (AAA)
Critical
High
Normal
Low
2
requirements
Technical cyber security
Network security

Centralizing network authentication, authorization, and auditing (AAA)

This task helps you comply with the following requirements

Use of dedicated admin accounts in critical data systems
Critical
High
Normal
Low
Maintaining chosen theme-specific policy documents
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.