InnerWeb
Skip to main content

Access control integrator: server room badge events to an external register

The access control integrator receives a task from the client: show who entered the server room and when, in one register together with the permits. Below are recommendations on how to pass card badge events from server room doors to an external register, without replacing readers and without changing cards.

0
readers to replace in this variant
Source: feature card
1
webhook for badge events from the server room door
Source: feature card

Who this is for and on what terms

The recommendations are addressed to the integrator or vendor of the access control (KD) system that serves a manufacturing plant. The setup is simple: the KD system stays the source of truth for badge events at the doors, and InnerWeb is an independent complementary system that receives these events and links them with the rest of the context.

InnerWeb is a software maker, not a device maker. It does not manufacture or replace access control readers and integrates with the client's existing KD system. For the integrator this means no risk of door downtime and no changes to cards. The whole change concerns the event layer.

Recommendation 1: send events by webhook

InnerWeb receives card badge events from the client's access control system through a webhook. The integrator configures the KD system to send an event for every badge at selected doors: first the server room, then the other critical rooms. The event should carry the card identifier, the reader or door identifier, the time and the decision result.

A good practice is to send rejected badge events as well. An attempt to open the server room door with a card that has no permission is an event that the auditor and the IT department want to see. It is worth sending the event time together with the time zone, to avoid an error caused by the one-hour shift.

Before going live in production, plan a test on one door with a known set of test cards. Check whether the event arrives once and not twice, and whether a rejected badge has its own status.

Recommendation 2: do not touch cards and readers

The badge events should come from the existing readers and cards. If the plant uses 125 kHz cards, MIFARE or DESFire cards, InnerWeb does not force a change. The card technology and the keys are the responsibility of the KD system and its integrator. Migrating cards to encrypted versions is a separate project with its own justification, independent of the register.

This rule protects the integrator from a scope that grows on its own. The server room entry register should not become a pretext for replacing the whole installation, unless the client wants that. The scope should be clear: events go out, the register receives them, and nothing else changes.

Recommendation 3: what happens on the register side

InnerWeb links a card badge event with qualifications, permits, attendance and time and attendance (RCP) data. This gives the badge at the server room door a context: a person with a permit within the time window, or a person without a permit. Every scan on the security screen at the gate is recorded in the entry and exit log, so the register covers both the gate and the internal doors.

The integrator can propose three reports to the client: entries to critical rooms with a permit, entries without a permit and rejected badge events. Scheduled reports are sent by email with tables and a PDF attachment, optionally with an XLSX file, and each one has its own location scope and recipients.

Recommendation 4: resilience and exceptions

The integrator is responsible for what happens when the webhook does not arrive. Recommendation: queue events on the KD system side with retries, so that a connection break does not create gaps in the register. It is worth agreeing with the client on a time limit after which the absence of events from a critical door triggers a notification to IT.

On a plant network without outbound traffic, the path of events from inside to the on-premise installation has to be planned. This is a single network segment, so one firewall rule between the KD system and the InnerWeb host is usually enough. The details are described on the page about alarms from the server room on a network without outbound traffic.

Finally, an organizational recommendation: write the scope of the integration on one page. The doors covered, the event fields, the person responsible on the KD side and the person responsible on the client side. Such a document speeds up acceptance and protects both sides from disputes over scope.

Video

Frequently asked questions

Does InnerWeb require a specific access control vendor?

No. It requires the ability to send a card badge event by webhook. It does not supply or replace readers or cards.

What if the KD system does not support webhooks?

The integrator can add an intermediate layer that reads events from the database or log of the KD system and forwards them. It is worth agreeing on this with the client at the specification stage.

Do rejected badge events have to be sent too?

Definitely worth it. An attempt to enter with a card that has no permission for the server room door is an event that matters to IT and to the auditor.

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