MIFARE DUOX Explained: One NFC Chip With Two Kinds of Security
MIFARE DUOX is an NXP contactless chip that pairs ECC with AES-256. Here is what each half does, where it is used, and how it relates to DESFire.
What MIFARE DUOX is
MIFARE DUOX is a secure contactless chip from NXP that carries both asymmetric (elliptic curve) and symmetric (AES-256) cryptography on one IC. NXP announced it on 19 November 2024 and describes it as the first NFC contactless IC in its class to combine the two.
It is a smart card chip, not a sticker tag. It speaks ISO/IEC 14443 Type A and appears as an NFC Forum Tag Type 4, so a phone with NFC can see it at the radio level. Talking to it in any useful way is another matter. That takes the right keys.
Two kinds of cryptography on one chip
Symmetric (AES-128 and AES-256). Both sides share a secret key. It is fast, which is why it has long been the workhorse of contactless cards. The catch is key distribution: every reader that needs to talk to a card needs the matching secret.
Asymmetric (ECC). Each side has a key pair and a certificate. DUOX supports the NIST P-256 and brainpoolP256r1 curves and ECDSA signatures with SHA-256, according to the NXP product page. A reader can check a card's certificate without holding a shared secret for that card.
NXP says DUOX uses a public key infrastructure concept to simplify key distribution and management. André Perchthaler, Senior Director for MIFARE at NXP, said the aim is to reduce that complexity "without compromising on contactless transaction speed". On the card, that shows up as two preinjected asymmetric key pairs with certificates, plus slots for symmetric keys per card and per application.
Proximity Check and Transaction Signature
Two features target problems that plain card authentication does not solve.
- Proximity Check measures round-trip time to help detect a relay attack, where a card's conversation is forwarded across a distance.
- Transaction Signature lets the card sign a transaction so the other side can prove it really came from that card.
Neither makes a system immune to attack. The overall design still matters. For background on how relaying and replaying work, see our guide to NFC sniffing and replay risks.
EV charging and the DUOX EV variant
NXP names EV charging authentication and secure car access as lead uses. For charging, it offers MIFARE DUOX EV part types that ship with an EV charging application per VDE-AR-E 2532-100, with keys and certificates issued by the NXP EV-Charging CA.
Per RFID News, certificate validation happens in the online backend rather than in the reader firmware at the charging station. That keeps the reader hardware simpler and leaves less exposed at the point of use.
Specs and certifications at a glance
| Item | MIFARE DUOX |
|---|---|
| User memory | 2, 4, 8 or 16 kB |
| Data retention | 25 years |
| Write endurance | Up to 1,000,000 cycles |
| Interface | ISO/IEC 14443 Type A, 13.56 MHz |
| Temperature | -40 °C to +105 °C |
| Certification | Common Criteria EAL 6+ (hardware and software) |
| Automotive | ISO/SAE 21434 compliant, MISRA-C compliant |
All figures are from NXP. Operating distance depends on the reader and antenna, up to 100 mm.
How it relates to DESFire
NXP doesn't bill DUOX as a DESFire replacement. NXP lists it as compatible with the MIFARE DESFire application and file layout and with EV2 secure messaging, and it adds a multi-application file system with post-issuance application installation. One card can hold, say, a building badge and a charging credential from different issuers.
If you are comparing chips, our DESFire EV2 vs EV3 article covers that family, and NTAG 424 DNA covers the tag-class option for authenticated taps.
What to take from it
DUOX matters mostly if you're building access, charging or car-key systems. If you only write URLs and text to stickers, you will not meet it. If you do work with secured cards, the practical change is key management: certificates instead of a shared secret for every reader.
Frequently Asked Questions
When was MIFARE DUOX announced?
NXP announced it on 19 November 2024. The EV charging part types have drawn more coverage since.
Is MIFARE DUOX a replacement for DESFire?
NXP does not describe it that way. It is a separate chip that stays compatible with the DESFire application and file layout and with EV2 secure messaging.
Can a phone read MIFARE DUOX?
It uses ISO/IEC 14443 Type A and NFC Forum Tag Type 4, so an NFC phone can detect it and read its basic identity. Anything protected needs the right keys and an app that supports them.