InnerWeb
Skip to main content

What is a card UID and why it is not enough to grant entry

The UID is a unique identification number stored in the chip of a proximity card, and the reader picks it up first. The number itself is not a secret, so a system that admits people on the UID alone checks a claim, not proof of identity. This guide explains the term and shows what to do with 125 kHz and MIFARE Classic cards, which still work at many plants.

7 B
UID length of the DESFire EV3 chip
128 bit
AES key in DESFire EV3 authentication

The UID: what the reader actually reads

The UID (unique identifier) is a number assigned to the card chip by its manufacturer. In contactless cards at 13.56 MHz compliant with ISO/IEC 14443, the reader fetches it before any further exchange with the card. The DESFire EV3 chip has a 7-byte UID, a longer number than the 4-byte identifiers of older cards.

In practice the UID is often confused with three other things: the card number printed on the plastic, a plant code stored in the card memory, and a cryptographic key. The UID is none of these. It is the serial number of the chip, which can be read without authentication if the card works in a mode that exposes it.

Why the UID alone is not enough

125 kHz cards of the EM and Prox type give the reader a fixed number without authentication and without encryption, so any reader working at that frequency can read it. Whoever owns such a reader holds a copy of the identifier, and the duplicate can be programmed onto a blank card.

MIFARE Classic cards face a similar problem. On cards with a changeable UID the number can be rewritten, so a system that relies only on the UID can be fooled. For the head of security this means that the door log from such a gate proves only that someone presented the right number to the reader, not that the card owner did.

  • 125 kHz card: fixed number, no authentication, no encryption.
  • MIFARE Classic with a changeable UID: the number can be written onto another card.
  • DESFire EV3: AES 128-bit with mutual authentication, the UID is only one component.

UID and key length in bits

UID and key length in bitsBar chart: a 4-byte UID is 32 bits, a 7-byte DESFire EV3 UID is 56 bits, and an AES key is 128 bits.050100150bits4-byte UID: 32 bits32 bits4-byte UID7-byte UID DESFire EV3: 56 bits56 bits7-byte UID DESFire EV3AES key: 128 bits128 bitsAES key
Source: Conversion of bytes to bits: 4 B = 32 bits, 7 B = 56 bits; AES 128-bit per NXP

Random identifier: privacy, not a key

DESFire EV3 offers an optional random identifier (random ID). The card then does not reveal its fixed UID during a read, so nobody can track the holder by a number visible at every reader. This is a privacy feature.

A random identifier is not a key derivation mechanism and does not replace authentication. If a supplier contract states that the random ID keeps the keys secure, the clause should be corrected. Security comes from AES authentication and properly managed keys, and the UID enters the picture only as an input to diversification.

The UID as a key diversification input

The correct use of the UID is different from admitting people on its basis. With diversification the key of a card is derived from a master key and the unique UID of that card, so a leaked key from one card does not open the others. The derivation function is described, among others, in NIST SP 800-108.

The takeaway for purchasing: asking whether the card has a UID is pointless, because every card has one. The real question is whether the UID is only a component of key derivation and whether authentication rests on AES.

What to do with 125 kHz and MIFARE Classic cards

Replacing all cards in one day is usually not realistic. The practical path is a transition period: dual-frequency cards combine a 125 kHz and a 13.56 MHz chip in one body, so they work on old and new readers. New gates and doors with a higher risk get readers that support DESFire EV3, and the old ones stay in place until the replacement is complete.

InnerWeb is a software manufacturer: it does not produce or replace readers and access cards, but integrates with the client's existing access control system. Its role is therefore not to choose the card, but to receive the door events from the access control system and connect them with qualifications, permits, attendance and working time records.

Audit questions for cards at the plant

Before talking to the access control supplier, establish how many entry points read only the number and how many authenticate the card cryptographically. This split is the basis for setting replacement priorities.

  • Which readers support only 125 kHz?
  • Where does MIFARE Classic work, and do its cards have a changeable UID?
  • Does the controller decide on entry based only on the number?
  • Which doors protect zones with elevated risk?

Checklist

Video

Frequently asked questions

Is the card UID secret?

No. The reader reads it without authentication, so it is not treated as a secret. Security depends on keys and authentication, and the UID works as a serial number.

Is a random identifier enough instead of keys?

No. A random identifier hides the fixed UID from tracking, but it does not derive keys and does not authenticate the card.

Does InnerWeb replace readers with DESFire?

No. InnerWeb is a software manufacturer and integrates with the client's existing access control system. Replacing readers is the job of the access control supplier.

Sources

Connect door events with permits

Let us talk about how events from your access control system can feed qualifications, permits and attendance, without replacing readers.

Let's talk