Before acceptance: documents
Ask the installer for a list of readers with their addresses, reader and controller models, the RS-485 bus diagram and a description of how Secure Channel is enabled. Without the list it is not possible to confirm that all doors were checked, and the acceptance result is incomplete.
Prepare an acceptance form with the columns: reader address, encryption mode, tamper test, swipe test, date and signature.
Encryption enabled
OSDP in installation mode sends data in plain text, and encryption requires an explicit enabling and key exchange in the reader and the controller. Check in the controller the status of the secure channel for each address: it should show Secure Channel (AES-128), not the initial mode.
Save a dump or report with a date as evidence. For doors where the report is not available, require a demonstration by the installer with an entry in the acceptance protocol.
Acceptance control areas (number of points)
Supervision and tampering
The OSDP controller supervises the reader status continuously, so disconnection or sabotage should produce an event. Run a test: in an agreed window, disconnect the reader on one door and check whether the event carries the correct address and reaches the responsible person.
With a Wiegand installation there is no such alarm without additional wiring, so the absence of an OSDP event means a configuration error, not a feature of the protocol.
Keys handed over
Encryption protects the transmission, but security depends on the protection of keys. At acceptance check that the key is not the default one, that the installer handed it over to the contracting authority in a way recorded in the protocol, and that it does not remain in his notes or on his laptop. Record who has access to the key.
Establish the date of the first key rotation and the person responsible for it.
Swipe events and time recording
Pass a card through several doors and check in the system that the swipes appear with the correct time, reader, person and card number. In a plant with InnerWeb, the events reach InnerWeb from the access control system by HTTPS webhook and are linked with qualifications, permits and attendance.
A change of the reader-to-controller protocol requires no changes on the InnerWeb side, as long as the access control system keeps sending events, so the test comes down to confirming that the event stream was not interrupted by the migration. The working time module in InnerWeb is delivered switched off by default and is enabled by an administrator setting, so check its state before the time recording test.
Closing the acceptance
Acceptance ends with a protocol listing the irregularities and the deadlines for their removal. Doors with open remarks should not be considered handed over. The completed form with the evidence and dates is the document that serves future audits.
Checklist
Video
Frequently asked questions
Is a test that the card opens the door enough?
No. Check the encryption mode, supervision, the keys and the swipe events.
How do I test tampering?
In an agreed window, disconnect the reader on one door and check the event with the reader address and the alarm recipient.
Who keeps the key after acceptance?
The contracting authority. The installer should not keep it, and the handover is recorded in the protocol.
Does InnerWeb need changes after the migration?
No, as long as the access control system keeps sending swipe events.
Sources
Let's talk about integrating with your access control system
We will describe which events from the InnerWeb access control system can be received and how to connect them with permits, attendance and working time recording. We will propose a demonstration on your data.
Let's talk