The short answer
A 125 kHz proximity card broadcasts a fixed number with no encryption, and it can be copied with inexpensive handheld tools, so it makes a poor end state for most buildings. A 13.56 MHz smart credential authenticates with the reader through an encrypted exchange. Not all 13.56 MHz is equal, though. Several early implementations were broken in published research, so security depends on the specific technology and on how the keys are managed. Mobile credentials over Bluetooth or NFC are issued and revoked from the management console, with nothing to print or collect. The tradeoffs are per user licensing and the practical reality that some tenants and staff won't install an app. Most commercial migrations install dual frequency readers so old and new credentials work at the same door until the last old credential is retired.
| 125 kHz prox | Fixed number, no encryption, easily copied |
|---|---|
| 13.56 MHz smart | Encrypted exchange; depends on the technology |
| Mobile | BLE or NFC, per user license, remote revocation |
| Reader protocol | OSDP v2 Secure Channel, IEC 60839-11-5:2020 |
| Migration tool | Dual frequency readers during cutover |
| License | CSLB #472017, C-7 Low Voltage Systems |
125 kHz proximity: what it is and why it persists
A 125 kHz proximity card is a passive antenna and a chip that does one thing: when a reader energizes it, it broadcasts a fixed number. There’s no encryption, no authentication and no challenge. The reader hears the number and passes it to the controller, and the controller looks it up in a list.
That design comes from an era when intercepting and replaying a low frequency signal took laboratory equipment. It doesn’t anymore. Handheld cloners are sold openly, and some retail key duplication kiosks will copy common prox formats. A writable card can then replay the captured number, and no reader or controller can tell it apart from the original. Access control software can’t help here, because from the door’s point of view nothing unusual happened.
Prox sticks around anyway, for practical reasons rather than technical ones. It’s installed in an enormous number of buildings. The cards and readers are inexpensive, the technology is universally interoperable, and it works with gloves, in the rain and through a wallet. Ripping it out is a project with a budget, and the risk it leaves behind stays invisible until there’s an incident.
In our view, prox is fine while a migration is underway, but it shouldn’t be the end state. For a building with a facilities budget and a multi year horizon, we’d recommend a written plan to retire it, even if that plan runs over three budget years.
13.56 MHz smart credentials, and why not all are equal
A 13.56 MHz smart credential does something a prox card can’t. Before any credential data moves, the card and the reader authenticate each other using keys stored on both sides. Because the exchange is different every time, a captured transmission can’t be replayed.
What often gets missed is that the frequency describes the radio, not the cryptography. Several early 13.56 MHz implementations were broken publicly. MIFARE Classic, which uses the proprietary Crypto1 cipher, was the subject of published academic attacks that made practical cloning possible. HID’s legacy iCLASS was also the subject of published cryptanalysis. Cards using those technologies are still in service in many buildings, and they’re still sold. So writing “13.56 MHz” on a drawing doesn’t get you anything by itself.
Instead, specify the actual technology and the key management model. MIFARE DESFire EV3 and HID Seos are the technologies commonly specified for new commercial work in California. Beyond the name, three questions decide whether the deployment is secure. Are the credentials programmed with keys unique to this customer, or with the manufacturer’s published default keys? Who holds those keys? And what happens to the system if the key holder is replaced? A DESFire deployment left on the manufacturer’s published default keys can be read by anyone who knows those keys. That leaves the building no better protected than it was on prox, at considerably more cost.
The link between the reader and the controller deserves the same attention. Wiegand has been the default interface for decades. It’s one way and unencrypted, and it can be tapped at the reader to capture credential data. OSDP version 2 with Secure Channel is bidirectional and encrypted. It also supervises the reader, so a removed or substituted reader raises an alarm, and it was published as an international standard, IEC 60839-11-5:2020. We recommend OSDP with Secure Channel on new work, and on retrofits where the existing cabling supports it.
Mobile credentials over Bluetooth and NFC
A mobile credential lives in an app on the user’s phone. It’s presented over Bluetooth Low Energy from a distance, or over NFC with a tap. The cryptography is comparable to a current smart card, so the differences that matter are operational.
To issue one, you send an email or text with an enrollment link. Nothing gets printed, encoded, mailed or handed across a leasing desk. Revocation happens from the management console and takes effect the moment the reader or controller syncs, so there’s no card to chase down. If your organization onboards and offboards people constantly, that alone can make the case for mobile.
The costs are real, though. Most platforms license mobile credentials per user, and some bundle them into the per door subscription. On cloud access platforms, that subscription runs roughly $150 to $600 per door per year (about $12 to $50 per door per month) as a California commercial planning range as of 2026. Readers that support both a phone and a card cost more than card only readers. And some portion of any population won’t install an app. That includes residents who don’t want a property management app on a personal phone, employees using a personal device without a policy that covers it, people with older phones the platform doesn’t support, and contractors who need access for two days.
We’d plan any mobile deployment with a physical fallback. A dual technology reader that accepts a smart card and a phone costs slightly more, and it handles most of those cases, including the dead battery lockout at 6 a.m.
PIN, multi-factor and biometrics at sensitive doors
A credential only proves that a person is carrying something. At a small number of doors, you want more than that.
A PIN keypad at the reader adds something the person knows to something they carry. It belongs at telecom and server rooms, pharmacy and medication storage, cash handling, records rooms and high value storage. Beyond the keypad reader itself, it costs almost nothing. If the budget only stretches one way, two factor at four doors is usually a better investment than a credential upgrade at forty.
Biometrics remove the shared credential problem entirely, because nobody can hand a fingerprint or a face to a coworker. They also bring in a category of data with its own exposure. The California Consumer Privacy Act as amended treats biometric information processed to identify a person as sensitive personal information, which carries notice and use limitation obligations. Whether to collect biometrics from employees or residents is a decision for the owner’s counsel, not for a specification writer. If a project does specify biometrics, settle a few things in advance: where the template is stored (on a card or on the reader), how it’s deleted when a person leaves, and what the notice says.
Comparing the credential options side by side
| Factor | 125 kHz prox | 13.56 MHz smart credential | Mobile (BLE or NFC) |
|---|---|---|---|
| How it authenticates | Broadcasts a fixed number in the clear | Encrypted mutual authentication with the reader | Encrypted exchange from an app on the phone |
| Copy resistance | Copied in seconds with inexpensive tools | Strong on current technology with customer keys; weak on broken legacy implementations | Strong; bound to the device and revocable |
| Credential cost | Lowest per card | A few dollars more per card | Per user license, usually annual |
| Reader cost | Lowest | Moderate | Moderate to high, especially dual technology |
| Issuance | Encode and hand over a card | Encode and hand over a card, plus key management | Send an enrollment link; the user does the rest |
| Revocation | Delete in software; the card still opens any other system reading that format | Delete in software; the card can’t be repurposed | Revoke from the console; nothing to collect |
| User experience | Works with gloves, in weather, through a wallet | Same | Hands free on Bluetooth, tap on NFC; a dead battery is a lockout |
| Lifecycle fit | Poor where turnover is high; cards are rarely returned | Good if a return process exists | Strong; no physical inventory to track |
| Where it belongs | Legacy only, during a migration | Default for new commercial systems | Staff, tenants willing to use an app, contractors and temporary access |
In short, prox falls behind on security, smart cards work almost everywhere, and mobile is the easiest to manage over time. Most commercial buildings end up running smart cards and mobile together on dual technology readers, so the reader decision ends up mattering more than the credential decision. Our access control systems page explains how we specify the readers, controllers and power supplies. The cloud vs on-premise access control guide covers where the credential database lives.
Running a phased migration without locking anyone out
An occupied building can’t go without entry security for even an afternoon. And a resident who can’t get in at 10 p.m. is a bigger problem than a cloned card. The sequence below is how we keep the doors secured while people switch over.
| Step | What happens | Who is affected |
|---|---|---|
| 1. Inventory | Survey every opening, reader model, wiring type and credential format, and count active credentials | Nobody; survey only |
| 2. Set the end state | Choose the smart credential technology, the key management model, whether mobile is included, and OSDP with Secure Channel where the wiring allows | Design team |
| 3. Install dual frequency readers | New readers accept both the existing prox and the new smart credential | Users see little change |
| 4. Issue new credentials in waves | Staff first, then tenants by floor, wing or building, with written notice and a staffed help window | One group at a time |
| 5. Watch the logs | A weekly count of prox reads shows how long the tail is | Administrator only |
| 6. Announce a cutoff date | Publish it, extend once if a group is behind, and staff the final week | Remaining holdouts |
| 7. Disable 125 kHz at the reader | Turn off the prox side in reader configuration, with a documented rollback held for 30 days | Anyone who ignored the notices |
| 8. Retire the format | Delete old credential records, dispose of returned cards, update as-builts and administrator documentation | Records only |
Steps 3 and 5 do most of the work. With dual frequency readers there’s no single cutover moment, and the weekly log count shows whether people have actually switched, so the cutoff rests on real numbers. Extending the cutoff once is normal, so plan for it rather than treating it as a failure.
We used this approach on occupied renovations at Little Tokyo Towers in Los Angeles and Horton House in San Diego. Residents stayed in place through the work at both, so entry security had to function every night of the project. Our guide to low voltage work in occupied buildings covers the resident notices and scheduling that go along with it.
Credential lifecycle in high turnover buildings
In a building with steady turnover, the workflow around the credential matters more than the technology. A DESFire deployment where nobody deactivates departed residents is less secure than a prox deployment with disciplined offboarding. An active credential in the wrong hands opens the door no matter how well it’s encrypted.
Four things decide whether the lifecycle works. The first is one system of record: the property management system, the HR directory or the access platform, with the others following it. Avoid three lists kept by hand where you can. The second is a trigger that fires automatically. That could be an identity provider sync that deactivates the badge when the account is closed, or a documented move out checklist with credential revocation as a signed line item. The third is an audit anybody can run, such as a monthly report of active credentials checked against the current rent roll or employee roster, with a written expectation of who reviews it. The fourth is a defined process for contractors, vendors and temporary staff that uses expiring credentials instead of permanent ones.
This is where mobile credentials earn their licensing cost. Revocation is quick, and there’s no card to recover from someone who’s already moved out. New residents also don’t have to show up at a leasing office during business hours to get access. In multifamily and affordable housing, turnover is constant and the leasing office acts as the system administrator, so you feel that difference every month, not just once at commissioning. Our access control installation cost guide covers cost planning for the whole system.
Next step
To plan a migration, we’ll need the door schedule, the credential format you use today and the count of active credentials. With those, we’ll send back a scope with the reader swaps, credential quantities, licensing and cutover sequence written out. You can start at request a bid. If you haven’t settled on a credential yet, tell us the turnover rate and who administers the system, and we’ll tell you which way we’d go and why.