InnerWeb
Skip to main content

OSDP Secure Channel best practices at a production plant

OSDP Secure Channel does not switch on by itself: a reader in installation mode sends data in clear text. The installer and the access control administrator must deliberately exchange the key, check the operating mode and document the acceptance. Below are practices for the deployment stage and for maintenance, with a checklist for reader acceptance.

AES-128
encryption in OSDP Secure Channel
2020
adoption of OSDP as IEC 60839-11-5

What Secure Channel gives and what it does not

OSDP Secure Channel encrypts the communication between the reader and the controller with AES-128. This removes the basic weakness of Wiegand: the card number sent in clear text, which can be intercepted and replayed. OSDP was adopted as the IEC 60839-11-5 standard in 2020, and version 2.2 of the SIA OSDP specification aligns the document format with the IEC version.

However, Secure Channel does not protect the card itself. If the card is 125 kHz or another unprotected technology, it can be cloned in front of the reader. Encryption of the link is a necessary condition, but not a sufficient one.

Practice 1: do not leave installation mode

OSDP in installation mode, without Secure Channel, sends data in clear text. Encryption must be explicitly enabled and the key exchanged in both the reader and the controller. This is a step that is easy to skip when the crew finishes the installation under deadline pressure: the reader works, the doors open, and the protocol stays in clear mode.

A good practice is to list the activation of Secure Channel as a separate item in the acceptance protocol. The access control administrator confirms in the controller that the given reader works in encrypted mode and signs the result.

Data visible to someone listening on the line (example)

Data visible to someone listening on the line (example)Before and after chart: in installation mode the message is 100 percent readable, in Secure Channel 0 percent.020406080100% of message fields readableInstallation mode: Readable message: 100 % of message fields readable100Installation modeSecure Channel: Readable message: 0 % of message fields readable0Secure Channel
Source: Conceptual illustration: in clear mode the message is readable, in Secure Channel it is encrypted with

Practice 2: a key other than the default

Encryption protects the transmission, but security also depends on how the keys are protected. The manufacturer's default key should not remain in operation, because it is known to anyone who has the documentation. The administrator generates a key for the plant or for a group of readers and loads it into both the reader and the controller.

Record where the key is stored, who has access to it and how the exchange is carried out. Replacing a reader or the departure of an installer are moments when the key must be treated as potentially disclosed.

Practice 3: acceptance with evidence

Acceptance of an OSDP reader covers a functional test, an encryption test and a supervision test. An OSDP controller constantly supervises the state of the reader, which makes disconnection or tampering detectable, but only if the alarm is configured and reaches the person who will handle it.

The audit evidence is the acceptance protocol with a list of readers, the operating mode, the date of the key exchange and the result of the disconnection test. It does not promise compliance with a particular regulation, but it shows that the plant controls the configuration.

On a bus with several readers

On a single RS-485 bus, OSDP can run several readers in a chain. During acceptance, test each reader separately, not only the first one in the chain, because an address or key error shows up on a specific device.

Practice 4: maintenance and events

In maintenance, plan a review of the configuration at least once a year and after every reader replacement. A change of the reader-to-controller protocol does not require changes on the InnerWeb side, as long as the access control system keeps sending events, so after service it is enough to check that the punch stream still arrives.

InnerWeb does not produce or replace readers. It is an independent system complementing the plant's existing systems, and responsibility for the encryption configuration remains with the installer and the access control administrator.

Checklist

Video

Frequently asked questions

Does Secure Channel switch on automatically?

No. Installation mode sends data in clear text, and encryption must be explicitly enabled with a key exchange in both the reader and the controller.

When should the Secure Channel key be replaced?

After a reader replacement, after an installer with access to the key leaves, and as part of the periodic review of the configuration.

After enabling Secure Channel, do I have to change the integration with InnerWeb?

No, as long as the access control system keeps sending punch events. It is still worth checking that the event stream has not been interrupted.

Sources

Are you deploying OSDP at the plant?

Describe your reader layout and access control system. We will help define which punch events should reach InnerWeb once encryption is enabled.

Let's talk