Who these recommendations are for and what the board decides
The recommendations are addressed to a board member or director responsible for information security and business continuity. The board does not decide who opens which door. It decides the scope of the policy, the roles, the level of evidence and the fact that results come back to it in regular reports.
Two documents provide the framework. Article 21(1) of the NIS2 Directive requires measures that protect network and information systems and their physical environment from incidents. Among the measures in Article 21(2) are policies on access control, human resources security and asset management. The ISO/IEC 27001:2022 standard, in its group of physical controls, covers security perimeters, physical entry and working in secure areas.
An important caveat: an ISO/IEC 27001 certificate does not prove compliance with the Polish Cybersecurity Act (KSC) or with NIS2. The standard is used as an evidence framework for the audit, not as a substitute for the requirements. The board should commission it that way.
Recommendations 1-3: scope, roles, authentication
Recommendation 1: define the list of critical rooms. A server room, an electrical switchroom, OT cabinets on the lines and the backup room are usually the minimum. The list is part of the policy and has an owner. Without it, every audit starts with a dispute over what is critical.
Recommendation 2: base access on roles, not on names. Permissions in InnerWeb come from roles with inheritance and a matrix of scopes, roles are granted along a seniority ladder, and a role higher than one's own cannot be granted. The board approves the structure of roles, and the plant director applies it.
Recommendation 3: enable multi-factor authentication for accounts that approve access. An email code or TOTP is switched on per installation, with a trusted device period. NIS2 names multi-factor authentication where it is appropriate, and an account that approves entries to the server room is such a place.
Control groups in Annex A of ISO/IEC 27001:2022
Recommendations 4-5: evidence and changes
Recommendation 4: require an entry log with reasons. Every scan on the security screen is an act of control and is recorded in the entry and exit log, and the permit defines the task, the location and the time window. The board does not need to see every entry, but it should know that the evidence exists and can be produced on request.
Recommendation 5: require a change trail. Changes to permits, to the taxonomy of hazardous work, to training results and to automation rules are saved together with their author and time. The audit trail answers the question of who changed the data. The log records local time in the Europe/Warsaw zone from October 2026, and entries from the winter seasons 2023/24-2025/26 are shifted by one hour, which the auditor should know in advance.
Recommendations 6-7: integration and review
Recommendation 6: do not replace equipment without a need. The plant already has an access control system. InnerWeb receives card badge events from that system through a webhook and links them with qualifications, permits, attendance and time and attendance (RCP) data. It does not manufacture or replace access control readers. The board saves budget and avoids downtime in access control.
Recommendation 7: set the review rhythm. Scheduled reports are sent daily, weekly or monthly by email, with tables and a PDF attachment carrying the client's logo, and optionally an XLSX file. Each rule has its own location scope and its own recipients. For the board, a monthly exceptions report is enough: entries outside the window, entries without a reason, expired permissions.
At each review ask three numbers: how many entries to critical rooms there were in the period, how many had a permit, and how many needed an explanation. The gap between the first and the second number is a measure of the policy's maturity.
How to judge whether the policy works
A good test before signing the policy: ask the plant director to show one service entry to the server room, from the invitation to the closing of the work. If the demonstration needs three systems and a call to security, the policy exists only on paper. If a permit and a badge event are enough, the board has evidence.
The second test concerns exceptions. What happens when a failure requires entry in the middle of the night? The policy should provide an emergency path with a reason recorded afterwards, not a workaround. A recorded exception is valuable, because it shows the auditor that control works under pressure too.
Video
Frequently asked questions
Is an ISO 27001 certificate enough for NIS2?
No. The certificate does not prove compliance with the KSC or with NIS2. The standard is used as an evidence framework for the audit, and the requirements of the act and the directive have to be met separately.
Does the board need to know the details of the entry log?
No. It should know that the log exists, who keeps it and what the monthly exceptions report looks like. The details are the job of the plant director and IT.
Does the policy require new readers?
It does not. The InnerWeb system receives card badge events from the existing KD system, so the policy can rely on the current equipment.
Sources
Let's talk about evidence of server room entries
We will show in a demo how badge events from your access control system connect with the permit and the log. No reader replacement and no card changes.
Let's talk