NXP - MIFARE DESFire EV1

The memory of the MIFARE DESFire EV1 is not organized into fixed blocks but as a hierarchical file system, whose structure is freely defined during personalization:

The size of each file is set at its creation, allowing the card to be precisely tailored to each project. Used as an NFC Forum Type 4 tag, the chip hosts an NDEF application whose file can occupy almost the entire memory: nearly 1,900 URL characters on the 2 kB version, and far more on the 4 and 8 kB versions. Capacity stops being a constraint (enough for a complete vCard or several combined records).

• Mutual authentication and encrypted channel: a three-pass mutual authentication (in DES, 2K3DES, 3K3DES or AES-128, executed by a hardware cryptographic engine) generates a unique session key; exchanges can then be signed with an 8-byte CMAC or fully encrypted over the radio channel.
• Multi-application file system: up to 28 isolated applications, each with its own keys and up to 32 files; a single card can combine transport, access control and loyalty without the issuers sharing their secrets.
• Five file types: standard or backup data files, value files with controlled credit and debit, linear and cyclic record files (the latter automatically overwriting the oldest entries, perfect for transaction history).
• Atomic transactions: an anti-tearing mechanism validates or cancels all the writes of a transaction as one unit, and an automatic rollback protects the file structure: the card never remains in an inconsistent state, even when removed from the field mid-operation.
• Random ID and key diversification: the optional random identifier prevents card tracking, and deriving card-unique keys from the UID strengthens resistance to cloning.
• EAL4+ certification: both hardware and embedded software are Common Criteria EAL4+ certified, with exception sensors and countermeasures against power analysis.

The DES modes and the compatibility with the first DESFire (MF3ICD40) remain for existing fleets; AES-128 is the recommended choice for any new deployment. The chip comes in two antenna capacitances, 17 pF and 70 pF (MF3ICDH references for small form factors). The MIFARE DESFire EV2 and EV3 continue the line with extended features.

The MIFARE DESFire EV1 uses NFC-A technology (ISO/IEC 14443A), supported by the vast majority of recent NFC smartphones. On Android, reading and writing work natively with NFC Tools, without any particular restriction. On iPhone, automatic background reading is available from the iPhone XS and XR onwards; models from the iPhone 7 can read and write the chip via NFC Tools on iOS 15.6 or later, by starting the scan manually from the app.

With NFC Tools, the chip supports reading technical information as well as reading and writing NDEF records once the card is formatted as Type 4 (blank cards delivered with factory keys can be prepared during the first write). Creating applications, managing keys and fine-tuning the files require specialized encoding through the chip's dedicated commands. The list of compatible models is available in the article on compatibility.

The three versions share strictly the same command set, the same security and the same performance: only the memory and the antenna capacitance vary. For new projects, the MIFARE DESFire EV2 and EV3 extend the line; on the consumer NFC tag side, the NTAG 424 DNA offers AES authentication in a sticker format.

How much data can be stored on a MIFARE DESFire EV1?

The card offers 2, 4 or 8 kB distributed into freely sized files. Used as a Type 4 tag, it dedicates almost all of its memory to the NDEF file, which corresponds to nearly 1,900 URL characters on the 2 kB version (far beyond common needs).

What is the difference between MIFARE DESFire EV1 and MIFARE Classic?

The MIFARE Classic relies on the proprietary Crypto1 cipher, which is old and whose weaknesses are publicly documented. The DESFire EV1 builds on open standards (3DES and AES-128), mutual authentication with session keys and a Common Criteria EAL4+ certification.

Is the MIFARE DESFire EV1 compatible with iPhones?

Yes. Background reading works from the iPhone XS and XR onwards, and both reading and writing are possible via NFC Tools from the iPhone 7 on iOS 15.6 or later.

Can a MIFARE DESFire EV1 be protected against rewriting?

Protection relies on the keys: each file defines its read and write access rights, which can require authentication or be set to "never" (writing then becomes permanently impossible). There is no OTP-bit locking as on NTAG chips: everything is configured through the access rights.

Official NXP datasheet (PDF)

Recommended NFC chips for NFC Tools

Buy MIFARE DESFire EV1 NFC chips