13.3: Perimeter and physical access control

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

1. For the purpose of Article 21(2)(i) of Directive (EU) 2022/2555, the relevant entities shall prevent and monitor unauthorised physical access, damage and interference to their network and information systems.

2. For that purpose, the relevant entities shall:

  1. on the basis of the risk assessment carried out pursuant to point 2.1, lay down and use security perimeters to protect areas where network and information systems and other associated assets are located;
  2. protect the areas referred to in point (a) by appropriate entry controls and access points;
  3. design and implement physical security for offices, rooms and facilities,
  4. continuously monitor their premises for unauthorised physical access.

3. The relevant entities shall test, review and, where appropriate, update the physical access control measures on a regular basis or following significant incidents or significant changes to operations or risks.

This requirement is part of the framework:  
NIS2 Implementing Regulation

Other requirements of the framework

50565
13.3: Perimeter and physical access control
Best practices
How to implement:
13.3: Perimeter and physical access control
This policy on
13.3: Perimeter and physical access control
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. For the purpose of Article 21(2)(i) of Directive (EU) 2022/2555, the relevant entities shall prevent and monitor unauthorised physical access, damage and interference to their network and information systems.

2. For that purpose, the relevant entities shall:

  1. on the basis of the risk assessment carried out pursuant to point 2.1, lay down and use security perimeters to protect areas where network and information systems and other associated assets are located;
  2. protect the areas referred to in point (a) by appropriate entry controls and access points;
  3. design and implement physical security for offices, rooms and facilities,
  4. continuously monitor their premises for unauthorised physical access.

3. The relevant entities shall test, review and, where appropriate, update the physical access control measures on a regular basis or following significant incidents or significant changes to operations or risks.

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
13.3: Perimeter and physical access control
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
13.3: Perimeter and physical access control
of the framework  
NIS2 Implementing Regulation
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Visitor instructions and log
Critical
High
Normal
Low
Physical access control to building, offices and other premises
Critical
High
Normal
Low
Protecting connections from physical tampering or damage
Critical
High
Normal
Low
5
requirements
Physical security
Property security

Protecting connections from physical tampering or damage

This task helps you comply with the following requirements

Camera surveillance in real estates
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.