Scenario: a gate reader and no alarm
A warehouse hall has several gates, and at each one a card reader is connected to a controller in a cabinet tens of metres away. The head of security notices that one reader was loose, and the system shows no event for its removal. There is a suspicion that someone probed the line or prepared a wiretap.
This is a conceptual scenario based on the publicly described properties of Wiegand. It shows which questions an auditor asks and which answers the technology gives, before anyone reaches for a multimeter.
What the nature of Wiegand means for wiretapping
Wiegand sends data from the reader to the controller in clear text, without encryption, so a person with access to the line can intercept the card number. It is enough to connect to the two data wires in a junction box or at the controller.
A credential sent over Wiegand can be copied and replayed, because the transmission has no authentication and no counter. This is a replay attack: the intercepted card number is sent to the controller as if the card had been presented. The controller has no way to tell a copy from the original.
Gates by line exposure (example)
Why a reader can be removed without an alarm
Wiegand does not let the controller check whether the reader is connected and working. Removing or destroying a reader without additional wiring does not raise an alarm. If the installer did not run a separate tamper line, the system stays unaware.
By comparison, an OSDP controller constantly supervises the state of the reader, which makes disconnection or tampering detectable. The difference is therefore not only in encryption, but in the fact that the bidirectional link confirms the presence of the reader in every polling cycle.
Audit plan, step by step
The audit is carried out for each gate separately, in a window without goods traffic, with participation of security and an electrician. The goal is to establish where the line is physically accessible and whether any supervision exists at all.
- inventory of readers: type, firmware version, direction, cable length to the controller
- check whether the cable runs in a closed tray or in a place reachable from floor level or from a shelf
- inspection of junction boxes and distribution boxes: seals, locks, signs of intrusion
- tamper test: removing a reader in the presence of security and checking whether an event appears in the access control system
- review of the event log from recent weeks for series of punches at unusual hours
- assessment of which gates carry goods traffic and third-party persons, and therefore a higher risk
Sample calculation: how many gates to cover in the first stage
Assume a warehouse with 12 gates equipped with Wiegand readers. The audit shows that 4 gates are in a zone accessible to drivers of external companies, 5 in the internal part and 3 next to the offices. These are example assumptions, not data from a specific site.
The first stage of the control covers the external gates, because that is where interception of the line is easiest. The remaining gates enter the OSDP migration plan in the following budget year, after the results of the tamper test have been collected.
Evidence for management and conclusions
The audit report should provide evidence for the management review: a list of gates, the result of the tamper test, an assessment of line exposure and the recommended order of work. It does not promise compliance, it shows the state and the plan.
The most important conclusion is simple: knowledge about tampering with a reader depends on the protocol. With Wiegand, tamper wiring and physical procedures must be added. With OSDP, supervision is built into the link. InnerWeb does not replace readers, but events from the access control system can feed the dispatcher and the plant event log.
Order of covering gates with the audit and migration
| Parameter | Value |
|---|---|
| Number of gates with a Wiegand reader | 12 gates |
| Gates in the external zone | 4 gates |
| Gates in the internal part | 5 gates |
| Gates next to the offices | 3 gates |
Result: Stage 1: 4 external gates, stage 2: 5 internal gates, stage 3: 3 gates next to the offices.
Note: Sample calculation; the figures are assumptions, not data from a specific site.
Video
Frequently asked questions
Does a line audit require stopping warehouse work?
Usually a window without traffic at the given gate is enough. The tamper test takes a few minutes per reader, and the inspection of cables and boxes can run in parallel.
Would OSDP encryption detect wiretapping?
It would not detect it, but it makes the intercepted data useless. OSDP Secure Channel encrypts the communication with AES-128, and reader supervision detects its disconnection.
What does InnerWeb do in such a scenario?
InnerWeb does not produce or replace readers. It receives events from the access control system and can connect them with the dispatcher and the plant event log.
Would replacing the cards alone solve the wiretapping problem?
No, if the reader-to-controller link stays on Wiegand. A secure card does not protect the line, and a secure line does not protect a 125 kHz card.
Sources
Do you suspect a reader has been tampered with?
Describe your gate layout and your access control system. We will help plan a line audit and connect the access control events to the plant event log.
Let's talk