What Article 21 says exactly about physical protection
NIS2 Directive Article 21 paragraph 1 requires technical, operational and organizational measures based on an all-hazards approach. They are meant to protect network and information systems and their physical environment against incidents. The wording about the physical environment is key for IT: the server room and the control room are part of that environment, so doors, cabinets and service hatches fall within the scope of the compliance discussion.
Among the measures listed in Article 21 paragraph 2 are human resources security, access control policies and asset management, and multi-factor authentication where appropriate. The provision does not prescribe a specific technology or a specific number of doors. It requires a policy that is applied, and evidence that it is applied.
Questions about scope: what is a server room and what is a control room
The first question from the board is usually whether it concerns only the main server room. It does not. For the directive what matters is where the systems are whose incident could disrupt the service or production. In an industrial plant, next to the IT server room there are network cabinets on the shop floor, automation controller cabinets and control rooms. Each of these places has a different exposure: the server room is locked, while a cabinet on the floor may be reachable by anyone who has a key.
A practical approach is an inventory of rooms and cabinets with an assessment of who enters them and for what purpose. The result goes into the access policy, which describes server rooms, control rooms and distributed cabinets separately. Only then does the board see which places need an entry log and which are enough to lock and check periodically.
Electronic permit phases and evidence elements for the server room
Questions about the entry log and the reason for the visit
The second question is how we know who entered the server room. A card read alone says that someone entered, but not why. The evidence the auditor expects is an entry linked with a reason: a service order, a permit or a planned visit with a supervisor. InnerWeb saves every scan at the security screen in the entry and exit log, and security sees a verdict based on valid trainings, qualifications, a permit in progress and an active account.
When the server room door is served by the client's access control system, InnerWeb does not replace the readers. It receives card read events through a webhook and links them with qualifications, permits, attendance and working time records. The IT team keeps its access control system and gets one summary of entries with their reasons.
Questions about service companies
The third question concerns contractors: whether a service company may enter on its own. In good practice it does not enter without a permit that defines the task, the place and the time window. The electronic work permit passes through the preparation, main work and closing phases, and the flow of permits issued to an external company lets the issuer on the plant side and the contractor work on the same document.
At the gate, a planned visit replaces the one-day permit requirement, but trainings, qualifications and an active account still decide on entry. The visit has a supervisor, and the system calls the supervisor once, at the first entry. For the server room this means the service technician is not an anonymous guest: they have a supervisor, a time window and a trace.
Questions about authentication and administrator permissions
The fourth question follows from Article 21 paragraph 2: whether a card is enough or multi-factor authentication is needed. The provision refers to it where appropriate, so the decision belongs to the risk analysis. In InnerWeb, a code sent by e-mail or TOTP is enabled per installation, with a trusted device period, which allows applying it to administrative accounts without burdening all users.
For permissions the seniority rule applies: permissions follow from roles with inheritance and a scope matrix, and roles are granted along a seniority ladder. Nobody can grant a role higher than their own. The board understands this argument immediately, because it answers the question of who controls the controllers.
Questions about evidence for the board and alarms without outbound traffic
The fifth question from the board is what will appear in the report. Periodic report rules send an e-mail daily, weekly or monthly with tables and a PDF attachment carrying the client's logo, and optionally an XLSX file, with a separate scope of locations and recipients for each rule. The board can receive a monthly summary of server room entries without asking IT for an export.
The last IT question concerns the network. Control rooms and server rooms are sometimes placed in segments without outbound traffic. When the client's network blocks all outbound traffic from the application host, alarm webhooks are written to a durable queue collected by an external poller, so the alarm is not lost without opening outbound traffic. The installation can run in the client's server room as an independent system that complements existing systems: access control, working time recording, HR and ERP.
Checklist
Video
Frequently asked questions
Does NIS2 require an entry log for the server room?
The directive does not prescribe this form of evidence. It requires measures adequate to the risk and access control policies. An entry log with a reason is a natural proof that the policy is applied.
Does a control room have the same requirements as a server room?
For the directive what counts is the exposure and the effect of an incident, not the name of the room. We describe the control room separately in the access policy, because it is often powered and operated differently from the server room.
Does the system replace access control in the server room?
No. InnerWeb does not manufacture or replace readers. It links events from the client's access control system with qualifications, permits and attendance.
Sources
Prepare your answers for the board
We will show how the access policy, the entry log and the periodic report form an answer to the question about physical protection under Article 21. Arrange a conversation with the InnerWeb team.
Let's talk