InnerWeb
Skip to main content

Checklist: migrating 125 kHz cards to DESFire

Replacing older cards with encrypted DESFire cards is more an organisational project than a technical one: the gates must keep working all the time, and the workforce holds two kinds of carriers in the meantime. The checklist below guides IT and security through the pilot phase and the gradual changeover.

AES-128
key standard of the DESFire EV3 card
14 keys
per application according to the chip manufacturer
8 bytes
length of the CMAC code

Why migrate at all, and what does it cover

125 kHz cards respond with a fixed number without authentication, so any device placed close to the card can copy it. The MIFARE DESFire EV3 card is a contactless card compliant with ISO/IEC 14443, and the chip manufacturer describes AES-128 encryption for it and authentication before access to application data.

The migration changes the carrier and the configuration of the readers, but it does not change the rule that entry is decided by permissions on the system side: valid trainings, qualifications and an active account. InnerWeb does not manufacture readers or cards: it receives tap events from the client's KD system, so the migration takes place at the KD vendor, and our software reads its result.

Stage 1: inventory and design decisions

Before you order the first card, establish how many readers already handle 13.56 MHz and which models they are, because a 125 kHz reader will not read a 13.56 MHz card. Ask the KD vendor whether the readers can work in dual-frequency mode during the transition.

  • The number of readers and controllers and the frequencies they support.
  • The number of active 125 kHz cards and staff turnover during the migration.
  • Who owns the master keys of the applications and where their backup copy is kept.
  • Whether the card is to serve only for entry, or also for other applications (time recording, printers, canteen).

DESFire EV3 card key parameters

DESFire EV3 card key parametersHorizontal bar chart: up to 14 application keys, one card master key, 8-byte CMAC051015numberApplication keys (max.)Application keys (max.): 14 number14Card master keyCard master key: 1 number1CMAC length (bytes)CMAC length (bytes): 8 number8
Source: NXP, MIFARE DESFire EV3

Stage 2: design of the keys and applications on the card

A DESFire EV3 card has many applications, and each has its own keys: according to the manufacturer, one master key per card and up to 14 keys per application, in the AES-128 standard. Application keys are separated from the card master key, and data integrity is ensured by an 8-byte CMAC code.

This means different vendors can maintain their own applications without knowing the keys of the others. Plan the split before the purchase: an application for access control with one vendor, an application for other services with another, and the master key in the hands of the site.

Stage 3: pilot on one gate and a group of 20 people

Run the pilot on one low-traffic gate and with a group of people whose entry can be checked by hand. For the pilot gate set dual-frequency mode, and encode the access application on the new cards.

Measure three things: the share of taps completed with correct authentication, the read time, and the number of reports from employees. Tap events should reach the OHS system by the same route as before, and the card number in the form kod_obiektu-numer must match the accounts in the system.

Stage 4: gradual changeover and closing the old cards

After a successful pilot, replace cards department by department, starting with those who have access to sensitive zones. Cancel the old 125 kHz cards in the system only after confirming that the employee uses the new one, because a cancelled card must not pass as valid.

Finally, switch off 125 kHz support in the readers and update the procedure for a lost card. Keep the history: cancellation should not delete the record of when the card was valid.

Checklist

Video

Frequently asked questions

Does the migration require replacing all readers?

Not always. It depends on the frequencies the current readers support, and the decision rests with the KD vendor. Dual-frequency mode allows a gradual changeover.

Does InnerWeb replace cards and readers?

No. We are a software producer and receive tap events from the client's KD system; the cards and readers come from your vendor.

Do card vendors learn each other's keys?

No, if the applications are separated. The application keys are separated from the master key, so each vendor knows only the keys of its own application.

Can the old cards be left until they expire?

Yes, but only with an agreed closing date, because until then the risk of copying the 125 kHz card number remains.

Sources

Let's plan a card migration pilot

Book a call with IT and security: we will agree how taps from the new cards reach the OHS system without gate interruptions.

Let's talk