InnerWeb
Skip to main content

Migrating from MIFARE Classic: Implementation Notes for IT and Security

MIFARE Classic has worked at plant gates for years, so a migration is associated with the risk of downtime. However, the Crypto1 cipher was publicly broken in 2008, and the manufacturer recommended moving away from it in new systems. Below are the migration stages, pitfalls and conditions that let you change cards without stopping entries during a shift.

48 bit
key of the Crypto1 cipher
2008
year of publishing the attack on Crypto1

Why migrate

MIFARE Classic uses the proprietary Crypto1 stream cipher with a 48-bit key. The cipher was reconstructed from the chip layout and broken; the results were published in 2008 at the ESORICS conference. The described attacks allow recovering a sector key after recording one or two partial authentications from a reader, in a time on the order of seconds.

If the access system relies only on the UID number, a Classic card can additionally be reproduced on clone cards with a modifiable UID. A plant with Classic cards therefore has a risk similar to that of 125 kHz cards, despite the cipher.

Order of actions

The order matters more than the speed. Each stage builds on the previous one and has an exit criterion.

Stage 1: inventory

Establish the number of Classic cards, the types of readers and controllers, and what the KD system stores on the card: the UID alone or data in sectors. Without this knowledge it is impossible to assess whether the readers support the new card.

Stage 2: dual-technology readers

Replace or update the readers so that they support Classic and DESFire at the same time. In this state the plant can issue new cards while the old ones keep working until the end of the migration. This solves the problem of stopped entries.

Stage 3: issuing new cards in groups

The DESFire EV3 card in the ISO/IEC 14443 type A standard with AES 128-bit replaces Classic. Issue it in groups, starting with the areas of highest risk, for example entrances to warehouses and maintenance areas.

Stage 4: disabling Classic

After the last group is replaced, disable Classic support in the readers and block the old numbers in the system. Only this step closes the gap, because until then a copy of a Classic card still opens the gate.

Sample share of DESFire cards across migration stages

Sample share of DESFire cards across migration stagesLine chart: the share of DESFire cards rises from 0 to 100 percent across five migration points.020406080100%StartStage 2Stage 3aStage 3bStage 4Start: 0 %0Stage 2: 0 %0Stage 3a: 40 %40Stage 3b: 80 %80Stage 4: 100 %100
Source: Sample calculation: migration plan in two issuing groups

Pitfalls

The first pitfall is leaving the transition state in place forever. Dual-technology readers without a date for disabling Classic keep the gap open, even though the plant feels the migration is finished. Record the end date in the plan.

The second pitfall is assuming it is enough to change the card itself. If the system stores in Classic sectors data that another application needs, that data has to be moved to a DESFire application. The third is changing card numbers: the employee's account in the authorization system should stay the same, and only the card assigned to it changes.

Integration with the authorization and time tracking system

InnerWeb does not manufacture or replace access control readers and cards. It receives card swipe events from the KD system through a webhook and links them with qualifications, authorizations, attendance and time tracking. Changing the card technology on the KD side does not change the logic on the InnerWeb side.

During the transition, events from Classic and DESFire cards reach the system through the same channel. What matters is that the account identifier in the event stays the same after the card is replaced.

Conditions for success

A migration succeeds when it has an owner on the security and IT side, a schedule with a date for disabling Classic, and a transition period with readers of both technologies. A short message to staff about when and where to collect the new card also helps, so that queues do not form at the gate.

How to measure migration progress

Measure migration progress with three numbers: the share of issued DESFire cards, the number of gates with dual-technology readers, and the number of Classic card swipes per week. The last number should fall to zero, and after Classic is disabled every swipe of such a card is an event to be investigated.

The weekly report for the head of security and IT takes one page. It shows the status of the stage, the next group to be replaced and a list of exceptions, for example cards of people on leave. Exceptions have a closing date, so the transition state is not prolonged.

Video

Frequently asked questions

Can the readers be kept when migrating from Classic?

Only if they support DESFire with AES. The inventory will show which readers need an update or replacement on the KD vendor side.

Does InnerWeb replace cards and readers?

No. They are supplied by the KD vendor. InnerWeb integrates with the existing KD system and receives swipe events.

When is the migration complete?

When Classic support is disabled in the readers and the old numbers are blocked in the system. Until then a copy of a Classic card can still open the gate.

Sources

Card migration without downtime at the gate

We will help synchronize the migration stages with authorizations and training in the InnerWeb system. Book a call with our team.

Let's talk