InnerWeb
Skip to main content

FAQ: OSDP Secure Channel and Wiegand

A security manager choosing readers for new doors asks the same questions every time: can Wiegand be intercepted, what does OSDP Secure Channel actually encrypt, and will an older controller handle it? Below are the answers in the order they come up in purchasing meetings, with a note on what the protocol alone does not solve.

Encryption: what Wiegand protects and what OSDP protects

Wiegand sends data from the reader to the controller as plain text. Anyone with access to the line, for example after removing the reader cover, can capture the card number and replay it, because the transmission has no authentication and no counter. This is the main reason new installations are designed around OSDP.

OSDP version 2 with Secure Channel encrypts the reader-to-controller link with AES-128. Encryption protects the link, but not the card: if the card uses 125 kHz or another unprotected technology, it can be cloned in front of the reader, and no protocol behind the reader can change that.

Secure Channel questions in practice

Is Secure Channel switched on straight after installation? No. OSDP in installation mode sends data in plain text, and encryption has to be enabled explicitly, with the key exchanged in both the reader and the controller. Door acceptance should therefore include a check that the reader runs in encrypted mode, not in the initial mode.

Is encryption enough? No, if the keys are poorly protected. Security depends on who knows the key, where it is stored and how it is changed. With weak key management the system stays exposed even when every reader declares AES-128.

Features: Wiegand vs OSDP v2 (1 = none, 2 = present)

Features: Wiegand vs OSDP v2 (1 = none, 2 = present)Comparison of three features: Wiegand has none of them, OSDP v2 has all three.012pointsEncryptionWiegand (Encryption): 1 points1OSDP v2 (Encryption): 2 points2Reader supervisionWiegand (Reader supervision): 1 points1OSDP v2 (Reader supervision): 2 points2Two-way communicationWiegand (Two-way communication): 1 points1OSDP v2 (Two-way communication): 2 points2
  • Wiegand
  • OSDP v2
Source: Description of OSDP and Wiegand protocols in public sources; nominal scale

Cables, lengths and the number of readers on a line

On one RS-485 bus, OSDP can run several readers in a chain, while Wiegand needs a separate bundle of wires for each reader. With dozens of doors, the difference shows in cable trays, wall ducts and installation labour.

The permissible OSDP cable length is in the range of several hundred metres, and for Wiegand about 150 m is usually assumed. These figures are indicative: they depend on the cross-section, shielding and topology, so the exact number should be confirmed in the specification of the reader and controller manufacturer, not taken from a general table.

Reader supervision and tampering

Wiegand does not let the controller check whether the reader is connected and working. Removing or destroying the reader without additional wiring raises no alarm. In OSDP the controller supervises the reader status continuously, so disconnection or sabotage appears as an event.

For security this changes the way the system works: instead of discovering a faulty reader when someone reports a door that will not open, the operator receives an event with the specific reader address. It is worth agreeing in advance who responds to that event and within what time.

Older controller and the access control supplier

Will OSDP work with an older controller? That depends on the controller, not on the reader. Some controllers have an OSDP input, some need an interface module, and some do not support it at all. The answer comes from the controller documentation and the confirmation of the access control supplier, not from a declaration on the reader side.

Standard: OSDP was adopted as IEC 60839-11-5 in 2020, and SIA OSDP version 2.2 aligns the format with the IEC version. In a tender it is therefore worth requiring version 2 with Secure Channel and naming the specification version, not just the protocol name.

Where InnerWeb fits

InnerWeb does not manufacture or replace access control readers. It integrates with the plant's existing access control system and receives card swipe events from it. Moving the reader-to-controller protocol from Wiegand to OSDP requires no changes on the InnerWeb side, as long as the access control system keeps sending events.

For the security manager this is an important purchasing point: reader migration is a project for the access control supplier, while the integration with permits, attendance and working time recording stays the same.

Video

Frequently asked questions

Can Wiegand be intercepted?

Yes. Data travels as plain text, so anyone with access to the line can capture the card number and replay it at the controller. The lack of authentication and of a counter in the transmission makes replay attacks easier.

Does OSDP encrypt everything straight away?

No. In installation mode the data is plain text. Secure Channel encryption (AES-128) has to be enabled and the key exchanged in the reader and the controller, which must be confirmed at acceptance.

Does OSDP require replacing cards?

The protocol itself does not, but it does not protect the card either. If the cards use 125 kHz, they can still be copied in front of the reader. Securing the card is a separate decision.

Can the old controller be kept?

Sometimes, if the controller supports OSDP or has a suitable interface. The controller documentation and the access control supplier confirm this.

Does InnerWeb supply OSDP readers?

No. InnerWeb is a software manufacturer and integrates with the client's access control system. The readers are supplied and installed by the access control supplier.

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