DESFire vs MIFARE Plus: How to Choose a Card Family

Choose DESFire for a new system that needs several applications, files and keys on one card. Choose MIFARE Plus when you already run MIFARE Classic readers and want to move to AES without replacing everything at once. Both are NXP families, both use ISO/IEC 14443 type A, and both can use 128-bit AES, but they are built for different jobs.

What MIFARE Plus is built for

Plus exists to upgrade security in existing deployments. NXP describes it as a way to migrate contactless infrastructure to higher security step by step, using a Security Level (SL) concept.

Two members matter most:

• Plus EV2 supports both 48-bit Crypto-1 and 128-bit AES, and is certified Common Criteria EAL5+.
• Plus SE is aimed at adding an AES upgrade to MIFARE Classic installations.

If your doors, readers and back end already speak Classic, Plus lets you swap the cards first and tighten security later.

What DESFire is built for

DESFire is a multi-application smart card. NXP lists identity, access control, loyalty, micropayment and transport ticketing as typical uses. The family supports DES, 2K3DES, 3K3DES and AES in hardware. DESFire EV3 is certified CC EAL5+, and the single-application DESFire Light is certified CC EAL4.

Inside the card, the model is different from a Classic-style layout. According to Wakdev's EV3 reference, each application has its own 3-byte ID, up to 14 keys and 16 key sets, and up to 32 files. Six file types exist: standard data, backup data, value, linear record, cyclic record and Transaction MAC. For the generation differences, see our comparison of DESFire EV2 vs EV3.

Security levels: the real difference

This is where the two families split. A Plus card has levels. In SL1 it stays compatible with Classic and uses the 48-bit Crypto-1 cipher. In SL3, per Wikipedia's MIFARE article, it uses 128-bit AES.

That matters because Crypto-1 is compromised. The same article reports it can be broken in about 200 seconds on a 2008 laptop given a small amount of keystream, and that a 2015 attack recovered keys from the hardened Classic EV1, after which NXP recommended moving to higher-security products. A Plus card left in SL1 keeps those Classic-era weaknesses. It only delivers AES protection once your system actually runs at SL3.

DESFire has no Crypto-1 mode to fall back on. You still choose the algorithm, and the legacy DES options remain available, so configure AES. Wakdev recommends AES secure messaging for new projects, with three-pass mutual authentication and an 8-byte CMAC or encryption on exchanges.

Memory, files and applications

DESFire EV3 comes in 2, 4, 8 or 16 kB versions. There is no fixed cap on application count; memory is the limit. That makes it practical to give a building pass, a canteen balance and a loyalty record separate keys and separate owners on one card.

EV3 also adds a Transaction Timer against man-in-the-middle delay attacks, plus Secure Dynamic Messaging for per-tap authenticated NDEF data. It stays backward compatible with EV2, EV1 and D40.

Phones and maker tools

Both families use NFC-A, so most NFC phones detect them. Reading a card isn't the same as managing it, though. Creating applications and handling keys needs specialized commands, not a plain tag-writing app. If you are testing, see whether a phone can read a DESFire card and why a DESFire card shows no NDEF records.

How to choose

• New build, several applications, own key management: DESFire EV3, with AES.
• Existing Classic readers you can't swap yet: Plus EV2 or Plus SE, then raise the security level as readers are updated.
• Single-purpose card, simple file layout: DESFire Light is designed for single-application cases.
• Plain tags for NDEF projects: neither. A standard NTAG is cheaper and simpler.

We build NFCore for everyday tag work on iPhone and Android; card families like these usually need dedicated reader tooling.

Frequently Asked Questions

Is MIFARE Plus the same as MIFARE Classic?

No. Plus is designed to replace Classic and can run in a Classic-compatible mode (SL1), but in SL3 it uses 128-bit AES instead of Crypto-1.

Does DESFire use AES?

Yes. It supports DES, 2K3DES, 3K3DES and AES, and AES is the recommended choice for new projects.

Can I use either with a phone?

Both use ISO/IEC 14443 type A, so many NFC phones can detect them. Managing keys and applications needs specialized commands.