10.2: Verification of background

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

1. The relevant entities shall ensure to the extent feasible verification of the background of their employees, and where applicable of direct suppliers and service providers in accordance with point 5.1.4, if necessary for their role, responsibilities and authorisations.

2. For the purpose of point 10.2.1, the relevant entities shall:

  1. put in place criteria, which set out which roles, responsibilities and authorities shall only be exercised by persons whose background has been verified;
  2. ensure that verification referred to in point 10.2.1 is performed on these persons before they start exercising these roles, responsibilities and authorities, which shall take into consideration the applicable laws, regulations, and ethics in proportion to the business requirements, the asset classification as referred to in point 12.1 and the network and information systems to be accessed, and the perceived risks.

3. The relevant entities shall review and, where appropriate, update the policy at planned intervals and update it where necessary.

This requirement is part of the framework:  
NIS2 Implementing Regulation
Best practices
How to implement:
10.2: Verification of background
This policy on
10.2: Verification of background
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 ensure to the extent feasible verification of the background of their employees, and where applicable of direct suppliers and service providers in accordance with point 5.1.4, if necessary for their role, responsibilities and authorisations.

2. For the purpose of point 10.2.1, the relevant entities shall:

  1. put in place criteria, which set out which roles, responsibilities and authorities shall only be exercised by persons whose background has been verified;
  2. ensure that verification referred to in point 10.2.1 is performed on these persons before they start exercising these roles, responsibilities and authorities, which shall take into consideration the applicable laws, regulations, and ethics in proportion to the business requirements, the asset classification as referred to in point 12.1 and the network and information systems to be accessed, and the perceived risks.

3. The relevant entities shall review and, where appropriate, update the policy at planned intervals and update it where necessary.

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
10.2: Verification of background
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
10.2: Verification of background
of the framework  
NIS2 Implementing Regulation
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Policy for personnel background checks
Critical
High
Normal
Low
4
requirements
Personnel security
Changes in employment relationships

Policy for personnel background checks

This task helps you comply with the following requirements

Implementation and documentation of management reviews
Critical
High
Normal
Low
Security roles, responsibilities, and objectives derived from the organization's goals
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.