MIFARE DESFire EV1, EV2 and EV3
All AmbiSecure engineering content tagged DESFire, newest first. Newer entries reflect current thinking; earlier entries come from the engineering archive.
MIFARE DESFire is a contactless smart-card family widely used in transit ticketing, access control, and closed-loop payment. It provides file-based application storage, AES-128 cryptography, and mutually authenticated Secure Messaging — the reason it displaced memory cards in fare systems that need clonability resistance and per-application keys.
This category covers DESFire engineering: the EV1/EV2/EV3 generational deltas, secure messaging modes, key management and diversification, and how DESFire fits transit and smart-city deployments. The practical focus is on getting authentication, file access rights, and key diversification correct, because those — not the cipher — are where real systems fail.
Articles tagged DESFire
Frequently asked questions
What changed between DESFire EV1, EV2, and EV3?
EV1 introduced AES-128 and the file-level key model; EV2 added Secure Messaging mode and Transaction MAC for tamper-evident sessions; EV3 added Secure Dynamic Messaging (SDM) for NDEF and tightened side-channel posture. Each is a real protocol delta.
What is key diversification and why is it needed?
Diversification derives a unique per-card key from a master key and the card's UID, so recovering one card's key does not compromise the whole fleet. It is essential for any large ticketing or access deployment.
Is DESFire suitable for transit ticketing?
Yes — it is one of the most common transit card technologies, offering fast contactless transactions, per-application keys, and secure messaging that resists cloning and replay.
What is a SAM and why does DESFire need one?
A Secure Access Module holds the card keys inside tamper-resistant hardware at the reader, so a validator can authenticate cards offline without exposing master keys in terminal software or memory.
Can DESFire and EMV coexist on the same validator?
Yes, and in most large networks they now do. Open-loop EMV handles bank cards while DESFire handles the closed-loop product, sharing one gate without sharing a trust model.