InnerWeb
Skip to main content

Choosing a DESFire Card for a Plant: Recommendations for the Tender

The purchasing team of an access control integrator often receives a request from a plant for an "encrypted card" without parameters. Such a wording lets the vendor offer anything. Below are the MIFARE DESFire EV3 parameters worth writing into the tender, and the reasoning behind each of them.

14 keys
per application in DESFire
7 bytes
UID length in DESFire EV3

Who should write the parameters down, and why

A tender without parameters compares prices of cards with different resistance to cloning. Writing specific technical requirements narrows the offer to cards that actually meet the goal: the card authenticates to the reader and the reader to the card, transmission is encrypted, and keys are separated for different systems.

These recommendations concern cards that the KD integrator buys from the chip vendor. InnerWeb does not manufacture or replace cards and readers; it integrates with the client's KD system, so the choice of card belongs to the client and the integrator.

Parameters to put into the tender

The parameters below follow from the chip manufacturer's description and allow the card class to be defined unambiguously.

Standard and band

Require a MIFARE DESFire EV3 card in the ISO/IEC 14443 type A standard, in the 13.56 MHz band. A range of a few centimeters limits accidental reads from a distance.

Cipher and authentication

Specify a hardware AES 128-bit cipher with three-pass mutual authentication. The card still supports the older DES, 2K3DES and 3K3DES algorithms, but for new projects AES is recommended, so require in the tender a configuration without the older algorithms.

Data and transmission protection

DESFire EV3 provides encryption of the radio transmission, CMAC codes for data authenticity, proximity checks against relay attacks and a check of chip originality. Each of these points can be written as a separate requirement.

Keys and applications

The card allows one master key and up to 14 keys per application. Require a description of how the vendor will configure applications for KD, time tracking and other systems, so that keys are separated.

Card identifier

DESFire EV3 has a 7-byte UID and an option of a random identifier that protects the privacy of the cardholder. State whether the random identifier should be enabled, and check whether the KD system handles this mode.

Key length: MIFARE Classic and DESFire EV3

Key length: MIFARE Classic and DESFire EV3Comparison: a 48-bit key in MIFARE Classic and a 128-bit key in DESFire EV3.050100150bitMIFARE Classic (Crypto1): Key length: 48 bit48 bitMIFARE Classic (Crypto1)DESFire EV3 (AES): Key length: 128 bit128 bitDESFire EV3 (AES)
Source: ESORICS 2008 (Crypto1), NXP (DESFire EV3)

Questions for the vendor beyond the specification

Beyond the card parameters, ask who generates and stores the keys, in what form the vendor delivers cards already initialized, and what the procedure is if the master key is lost. Record the answers in the contract or in an annex to it.

Also ask about the compatibility of the plant's readers with the chosen card. A reader without AES support will not use the card's capabilities, and the plant will face the cost of an additional replacement.

Role of the authorization and training system

The InnerWeb training module for installations with RFID cards lets you identify an employee's account by a card swipe, and in an emergency by selecting the company and typing at least 3 characters of the first or last name. The choice of DESFire on the KD side does not change this logic, because InnerWeb receives events from KD and does not communicate with the card directly.

How to assess vendor answers

When comparing offers, put the answers in a table: chip version, algorithm, number of applications and keys, UID mode, the way cards are initialized, and responsibility for keys. An offer missing any of these points is incomplete, even if the price is low. A vendor who cannot describe how keys are separated should not receive an order for encrypted cards.

Also ask for a trial batch. A few cards are checked by the IT team together with security: reading on the plant's readers, behavior with a random identifier and cooperation with the KD system. Only after the test is a full batch ordered. The test does not require changes in InnerWeb, because the system receives KD events regardless of the card technology.

Video

Frequently asked questions

Should the tender exclude DES and 3DES?

It is worth doing. The card supports them, but for new projects AES is recommended, so the requirement enforces a configuration without the older algorithms.

Why a random card identifier?

It protects the privacy of the holder, because a fixed UID would allow the card to be tracked. The KD system must support such a mode, however.

Does InnerWeb choose the card for the plant?

No. The choice belongs to the client and the KD integrator. InnerWeb integrates with the existing KD system.

Sources

A tender for encrypted cards

If you are preparing a tender for a KD integrator, we can match the integration of card events to your authorization system. Book a call.

Let's talk