What is a UID, and how does a random identifier differ from it?
The UID is a unique number assigned to the chip at the factory. In DESFire EV3 it has 7 bytes. Older access systems treated it as an employee number: they read it without any protection and searched for it in the database.
The chip can also work with an optional random identifier (random ID). In that mode, each read without authentication returns a different value, so a number read from the air is not a trail that can be assigned to a person.
If the UID is random, how does the system know who punched the card?
Recognition takes place after mutual authentication. The reader knows the application key, opens the application and reads from it a stable employee identifier, or derives it from a diversified key. Only then is this value sent to the access system as a punch event.
The random UID is a privacy function: the card does not reveal a stable number on a read that could be linked to a person. It is not, however, a key derivation mechanism, so encryption must not rely on it.
- Read without authentication: a variable value, of no meaning to the system.
- Read after authentication: a stable identifier from the application, linked to the person's account.
- Key diversification: the card key is derived from the master key and the card's UID.
Parameters of the person search at a punch
What does a random UID change for HR and personnel?
For HR the key point is compliance with the data minimisation principle: a number read from a card by an outsider does not point to an employee, so the risk of tracking people outside the plant, for example at the entrances of other facilities, is reduced. In daily HR work nothing changes, provided the employee identifier was written to the card when it was issued and linked to the account in the system.
What changes is the process for a lost card. Since there is no fixed UID to enter on a block list, you block the identifier stored in the application or withdraw the card key. It is good to describe this procedure before the first card is lost.
How does InnerWeb link a card punch to a person?
InnerWeb does not read cards and does not produce readers. It receives card punch events from your access control system through a webhook and links them with qualifications, permits, attendance and RCP. The data about the person therefore comes from the access system, and we do not need to know the UID or the keys.
For integrations with RFID cards, the employee punches the card or selects the company and types part of a surname, from 3 characters, and the list shows up to 13 results. The search does not reveal the card number, which fits well with the idea of a random UID.
When the account with the card and the account with the training are different, the training result is transferred to the account with the card, so that the gate stops reporting missing training. The system never merges accounts based on the surname alone.
Which design mistakes most often break recognition?
The most common mistake is assuming that the reader will always see a stable number. If the configuration enables the random UID but the access system still searches for a record by UID, the person will not be recognised. The second mistake is the lack of a test after a reader software update.
- A punch test on every reader type after the random UID is enabled.
- A list of which application field carries the employee identifier.
- A blocking procedure based on the identifier from the application, not on the UID.
- A webhook event test in the supplementary system, including the queue when outgoing traffic is blocked.
Video
Frequently asked questions
Does a random UID make HR work harder?
Not in daily work, because the employee identifier is stored in the card application and linked to the account. It only requires a described procedure for blocking a lost card.
Is the card number visible in the InnerWeb search?
No. The search shows people by a fragment of their surname and does not reveal the card number.
Does a random UID replace encryption?
No. It is a privacy feature for reads, while encryption is provided by the AES keys and mutual authentication.
Does InnerWeb need to know card UIDs?
No. We receive the punch event from the access control system and link it with the person's account.
Sources
Let's check person recognition in your integration
We will go together through the path from a card punch to the person's account and the event in the system. Invite us to a short technical call.
Let's talk