Starting point: four firms and one entry book
Consider a mid-sized manufacturing plant where the server room runs the production control system, the plant network and the data archive. Four service firms are allowed to work on the equipment: the server vendor, the backup power firm, the precision air conditioning firm and the network integrator. Each of them has its own maintenance schedule and its own failures.
Today an entry looks like this: the technician reports at the gate, security writes the name in a book, and the IT manager learns about the visit from the calendar, or not at all. The book does not say why someone came in, who let them into the room or when they left. When the auditor asks for evidence of physical access control, the team assembles it by hand, sheet by sheet.
The scale is small, so the problem is easy to ignore. Sample calculation: 4 firms with an average of 6 entries per month give 24 entries per month and 288 per year. Each of them should have a reason, an approver and set hours. With 288 entries a year, gaps in paper records are almost certain.
The solution: entry on a permit with a time window
Instead of a book entry, the technician receives an electronic work permit. It defines the task, the location and the time window, and it moves through the preparation, main works and closing phases. The permit is opened by a person on the plant side, for example the IT manager or the maintenance coordinator, so the reason for entry exists before the visit, not after it.
When a service firm works as a contractor, the client side and the contractor work on the same permit. The assigned tasks are visible on the firm's screen, so nobody has to send scans by email. Risks and protective measures from a catalogue linked to the location can be attached to the permit, for example a requirement to cut the power before opening a cabinet.
In this scenario the server room is a separate area on the map with its own set of risks. Service work on power and service work on the network have different protective measures, so the permit is not one generic form.
Service entries to the server room in the example
Gate and door of the server room: a verdict, not an interpretation
At the plant gate, security scans a QR badge or an RFID card. The security screen shows a verdict: whether the person may be on site, based on valid training, qualifications, a permit in progress and an active account. Security does not interpret the full view of permits. It sees the decision and the list of missing items.
Every scan is an act of control and is recorded in the entry and exit log. This distinction matters: the log is not an add-on to the visit but its by-product. Since security scans anyway, nobody has to copy the data a second time.
The server room door is usually handled by the plant's existing access control system. InnerWeb does not manufacture readers and does not replace them. It receives card badge events from the client's access control (KD) system through a webhook and links them with qualifications, permits, attendance and time and attendance (RCP) data. A badge event at the server room door therefore lands in the same log as a scan at the gate.
The log as evidence: what the auditor will see
An auditor usually asks three things: who entered, why, and whether someone approved it. In the log, all three answers sit side by side: the badge event or scan with its time, the permit with its task and window, and the person who opened the permit. Changes to permits, training results and automation rules are saved together with their author and time, and the list of audited objects is explicit.
The audit trail answers the question of who changed the data. Records written only by the system, such as heartbeats and notification logs, are deliberately excluded from it, because their history is itself source data. It is worth telling the auditor this upfront, so they do not ask about entries that should not exist.
The framework requirement is known: Article 21(1) of the NIS2 Directive requires measures that protect network and information systems and their physical environment from incidents. The entry log is not a compliance certificate. It is evidence for the audit that access control to the server room works in practice.
The effect in numbers and conclusions
Back to the sample calculation. Compiling the audit log by hand from paper books, at 15 minutes per entry for 288 entries a year, means 72 hours of work, roughly 9 working days of 8 hours. With a log generated by the system, that time shifts from copying entries to reviewing exceptions.
The conclusions for the IT manager are three. First, we start with the permit, not the book: the reason for entry has to exist before the visit. Second, the log should be one log, not separate ones for the gate and for the server room door. Third, we do not touch the readers or cards, because the whole effect is achieved at the level of events.
Video
Frequently asked questions
Does the entry log replace the book at the reception desk?
In this scenario, yes. Every scan on the security screen is recorded in the entry and exit log. The client may keep paper for a transition period, but the source of evidence is the log.
Do the readers at the server room door have to be replaced?
No. InnerWeb integrates with the client's existing access control system and receives card badge events through a webhook. It does not manufacture or replace readers.
Does the log prove NIS2 compliance?
Not on its own. It provides audit evidence that access control to the server room works, which supports meeting the requirement for physical protection of the environment of systems under Article 21.
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