Two contactless smartcards standing upright in a labeled test stand beside an electronic lock PCB on a dark workbench, cool blue laboratory light, shallow depth of field, no people, no readable text, no logos
Technology

MIFARE Classic versus DESFire: choosing the right 13.56 MHz card

Both card families operate at 13.56 MHz, yet their security margins differ by a generation. The distinction matters whenever a card protects a paying room or a sensitive door.

MIFARE Classic and MIFARE DESFire are NXP-origin card families operating at 13.56 MHz, and both appear constantly in smart-lock specifications. Classic EV1 cards organize memory into sectors protected by the proprietary Crypto-1 stream cipher, a design whose weaknesses were publicly demonstrated in security research starting in 2008; compatible clones and UID-changeable cards are widely available. DESFire cards instead organize data into applications and files protected by AES keys, with the DESFire EV1, EV2 and EV3 generations adding hardened silicon, optional Leakage Resilient Primitive in EV2 and continued evolution in EV3. Crucially, many cheap lock deployments never use either cryptography — they simply read the card serial number, in which case the card IC contributes little security. This guide compares the families honestly, explains when authenticated Classic is still encountered, and shows how to specify card evidence for new projects. Supported card logic for each lock model is documented per quotation.

Key facts

Classic vs DESFire at a glance

FrequencyBoth are 13.56 MHz ISO/IEC 14443 Type A cards; frequency alone never tells you which family or security level is in use.
Classic memoryClassic EV1 offers 1 KB or 4 KB in fixed sectors with simple access keys, familiar from older transit and access systems.
Classic cryptoCrypto-1 is proprietary and its weaknesses have been publicly documented; genuine keys do not protect against the whole attack history.
DESFire structureDESFire uses applications and files with AES keys, giving structured multi-tenant deployments room for separate access domains.
GenerationsDESFire EV1, EV2 and EV3 each hardened the platform; EV2 introduced optional LRP, and buyers should ask which generation a project certifies.
CSN trapA DESFire card read in serial-number mode is only as strong as its UID management; authentication must be switched on to gain the security.
Our policyWe state which card ICs and authentication modes each named model supports and never imply DESFire-grade security from CSN-only Classic operation.
Answer unit

When does each card family justify itself?

New high-value deployments should specify authenticated DESFire or an equivalent modern scheme. Classic remains a migration reality around legacy transit and access ecosystems, while CSN-only Classic is acceptable only for low-risk convenience access.

RequirementCard approachPractical note
New enterprise or campus accessAuthenticated DESFire EV2/EV3 with managed keysStrong AES-based application security and clear key ownership.
Hotel with modern encoder system13.56 MHz cards per the lock vendor schemeConfirm whether the lock uses CSN or keyed operation before buying cards.
Transit-linked city card reuseDepends on the transit operator cardInteroperability is a key-sharing agreement, not a reader specification.
Legacy Classic estateDual-acceptance readers during migrationKeeps current cards working while new DESFire badges are issued.
Low-risk amenity roomsCSN 13.56 MHz cards with active revocationCheap and simple if lost cards are deleted promptly from every lock.
Events and temporary accessDated mobile credentials or disposable CSN tagsExpiry at the lock level matters more than the card IC.
Where it applies

Projects, products and evidence

The card family is chosen per opening risk, not per building fad. Mixed estates are normal: high-value doors authenticate, amenity doors can use simpler credentials, and the reader hardware spans both during transition.

OpeningTypical doorLock approach
Corporate headquartersHollow-metal doors with panel-managed accessDESFire application keys coordinated with the card bureau.
University campusResidence halls, labs and librariesDESFire for core buildings; coexistence with legacy student cards.
Mid-scale hotelTimber guest-room doors with RFID locksVendor card scheme matched to encoder and PMS, cards replaced per stay.
Apartment amenitiesGym and package-room doorsCSN cards or tags accepted when revocation is part of move-out.
Transit-adjacent sitesReaders near metro or office pass systemsAccept the city card only after formal key and format agreements.
Temporary construction accessPortable locks and dated tagsExpiry and audit at the lock outweigh the card IC choice.
Documentation pack

What to request with a card-based lock order

Card claims are easy to overstate on a datasheet. For named SKUs we provide the technical statements below in writing, so procurement can compare proposals using the same questions.

ComponentTypical logicNotes
Card IC compatibilityGenuine Classic, DESFire generations and clone-card behavior in the reader.Ask for the IC names, not just a 13.56 MHz logo.
Authentication modeWhether the lock verifies keys or reads CSN only.This single setting defines most clone resistance.
Key managementHow master and application keys are created, stored and replaced.Keys must belong to the site owner, not default to the installer.
Encoder and reader docsEncoder model, card format and reader acceptance rules.Needed before the first card batch is printed.
Migration statementDual-family acceptance behavior for estates moving off Classic.Allows staged re-badging without locking anyone out.
Integration workflow

Specifying card security in five steps

  1. Classify door riskMark perimeter, revenue and life-safety doors separately from amenity rooms.
  2. Audit current cardsIdentify family, generation and whether readers use CSN or keys.
  3. Set key ownershipDefine who generates, holds and rotates access keys in the new system.
  4. Sample-test the cardsValidate genuine and replacement cards, plus any transit or phone credential.
  5. Document and roll outFile the compatibility statement and train front desks on card issuance.
FAQ

Questions about MIFARE Classic and DESFire

Why is MIFARE Classic considered weaker than DESFire for access control?

MIFARE Classic protects its sectors with Crypto-1, a proprietary cipher whose weaknesses were published in peer-reviewed and community security research beginning in 2008, and practical card cloning tools have since become inexpensive. DESFire uses AES-based authentication organized around applications and files, with hardened silicon and later additions such as the optional Leakage Resilient Primitive in EV2. The honest nuance is that a poorly configured DESFire reader operating on card serial numbers gains none of this strength, while a correctly keyed Classic estate can still be managed acceptactorily in low-risk, legacy contexts — but new projects should not design on Classic when modern alternatives are available.

Does a DESFire badge guarantee the lock cannot be opened with a clone?

Only if the lock actually authenticates the DESFire application with the correct keys. A reader configured for serial-number mode treats the UID as the credential, and UID values can be presented by other devices, so the cryptographic strength of the card is simply unused. Clone resistance requires three things together: a card family that supports mutual authentication, a lock and reader configured to demand it, and controlled ownership of the keys. Procurement should therefore ask suppliers to state the operating mode in writing and to demonstrate a failed transaction with a non-provisioned card during acceptance testing, rather than trusting the card logo printed on the reader.

Can we keep using existing MIFARE Classic cards when replacing the locks?

Frequently yes during a migration. Multi-technology readers can accept both 125 kHz prox or Classic cards and new DESFire cards, which lets an estate replace locks in stages while staff and tenants keep using current badges. The project should document how long dual acceptance will run, because every month of CSN-only Classic acceptance on a high-risk door extends the exposure window. Once every holder has a new authenticated credential, the reader configuration is changed to require the stronger card family. We support this staged pattern with named reader models and configuration guides, and the exact acceptance matrix is confirmed per quotation.

Who should own and manage the cryptographic keys for a DESFire deployment?

The building owner or its appointed access operator should control the master and application keys, with the installer or integrator acting under a documented key-handling procedure. Keys are typically created on secure media, stored with separation of duties and rotated when a contractor changes or a site is sold. Default or factory-shared keys erase most of the advantage of moving to DESFire. In multi-tenant buildings, separate application keys can isolate parking, office access and amenities so one compromised domain does not expose the others. Our factory delivers locks in a defined initial state and supports customer key ceremonies; the key-management plan should exist before the first reader is configured.

Which card should a new mid-scale hotel choose for its next lock rollout?

A new hotel should start from the PMS and lock platform rather than from a card brand: confirm which encoder the front desk will use, which lock models are approved for the guest doors, and whether card operation is CSN-based or keyed, then select the card the platform provisions. Most modern hospitality schemes run on 13.56 MHz cards, and authenticated schemes add protection when the brand standard requires it. Properties also increasingly run mobile keys alongside cards as a guest option while keeping cards as the universal fallback. We provide the compatibility matrix between lock model, encoder and credential channels in writing per quotation and recommend a front-desk pilot before full rollout.

Need help choosing a card scheme for a lock project?

Share your current card type, encoder model and door risk levels with your RFQ. We document card IC support, authentication mode and migration options for each lock family, with samples for bench testing.

Request Spec Sheet + QuoteTechnology overview

Last updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team

Your Cart
Your experience on this site will be improved by allowing cookies Cookie Policy
Chat on WhatsApp