InnerWeb
Skip to main content

Card with an old UID and a new reader: a production plant scenario

After replacing readers with a newer type, some employee cards are no longer recognised, although they look exactly as before the replacement. This is a conceptual scenario for a production plant, not a description of a specific deployment. We show how the technician establishes the cause and how the plant organises the migration of cards during the transition period.

300 of 400
125 kHz cards in the example fleet (example calculation)
Source: kalkulacja przykładowa

Starting situation in the plant

The scenario assumes a production plant where most employees have 125 kHz EM/Prox cards. This type of card passes a fixed identification number to the reader without authentication and without encryption, so any reader compatible with this frequency can read that number. For years everything worked, because the readers were of the same kind.

The plant decides to replace the readers at two gates with newer ones, for the 13.56 MHz band with ISO/IEC 14443 type A support, in order to move to cards with authentication. After the replacement some employees report that their card does not work, while others pass without problems.

Why some cards stop working

The first cause is simple: the new reader works only on 13.56 MHz and does not see 125 kHz cards. Cards that have only a 125 kHz chip stop being recognised. Dual-frequency cards combine a 125 kHz chip and a 13.56 MHz chip in one body, so during the transition period they work on old and new readers.

The second cause concerns the UID number. Some 13.56 MHz cards in the plant are older cards whose number is read by the new reader in a different format than by the previous reader: for example in a different byte order or a different length. The system stored the number in the database in its old form, so the new reading does not match the record.

Why the UID alone is not enough

MIFARE Classic is vulnerable to cloning of the UID number on cards with a changeable UID, so a system relying only on the UID can be fooled. That is why migration to cards with authentication is the right direction, not just an adjustment to the new reader.

400-card fleet in the scenario: types of cards

400-card fleet in the scenario: types of cardsDonut chart: 300 cards of 125 kHz, 60 dual-frequency cards and 40 cards of 13.56 MHz125 kHz: 300 cards (75%)Dual-frequency: 60 cards (15%)13.56 MHz: 40 cards (10%)400cards125 kHz300 cards (75%)Dual-frequency60 cards (15%)13.56 MHz40 cards (10%)
Source: Example calculation based on the assumptions of the scenario: a fleet of 400 cards

How the technician establishes the cause

The technician starts with a simple split of the employees with the problem into two groups: those whose card is not seen by the reader at all, and those whose card is seen but rejected. The first group is the 125 kHz cards, the second is a mismatch in the UID format or a missing record.

Then the technician checks in the controller events whether the badge-in arrived at all. A badge-in with a number that is not in the database is a different case from no badge-in. Only after this distinction is an action chosen: card replacement, adding the number in the new format, or configuring the format in the reader.

Solution and migration

The plant sets a migration plan in three steps. First it issues dual-frequency cards to employees at the gates that stay on the old readers. Then it replaces the remaining 125 kHz cards with 13.56 MHz cards with authentication, for example DESFire EV3, which works under the ISO/IEC 14443 type A standard and offers a hardware AES 128-bit cipher. Finally it decommissions the old readers.

InnerWeb is a software producer: it does not manufacture or replace readers and access control cards, but integrates with the client's existing access control system. In this scenario the platform receives badge-in events from the access control system and still links them with qualifications and permits, regardless of which card is in use.

Effect and conclusions

The figures below come from an example calculation for a fleet of 400 cards: 300 cards of 125 kHz, 60 dual-frequency cards and 40 cards of 13.56 MHz. After the replacement, the readers at the two gates with the problem face 300 cards of 125 kHz, not the whole fleet. The migration plan limits the scope to that group.

The conclusions for the plant are as follows: before replacing a reader, inventory the types of cards, use dual-frequency cards during the transition, and after the move to authentication do not base access solely on the UID.

Video

Frequently asked questions

Is this a description of a specific deployment?

No. It is a conceptual scenario for a production plant, built from typical causes that technicians encounter after replacing readers.

Does a dual-frequency card solve the problem permanently?

It solves it during the transition period, because it works on old and new readers. In the long run it is worth moving to a card with authentication, rather than basing access on the UID alone.

Does InnerWeb replace readers in such a scenario?

No. InnerWeb integrates with the client's existing access control system and does not manufacture readers or access control cards.

Sources

Let us plan the card migration without downtime

We will help inventory the types of cards and draw up a transition plan with your technician and access control supplier. Contact us for a talk.

Let's talk