# Access Card Cloning: How Cards Get Copied, How to Spot a Cloned Card and How to Prevent It

> How access card cloning works and how a cloned card shows up in door logs. See the six warning signals and a six-step plan to prevent badge cloning.

Source: https://digitalbridge.com.tr/en/blog/access-card-cloning-risk.html
Publisher: Digital Bridge Teknoloji (https://digitalbridge.com.tr)
Topic: Access Control & Attendance
Published: 2026-10-04 · Updated: 2026-10-23

**Access card cloning is copying the identity data on an employee's badge to another card or device so a door accepts the copy as genuine.** It works wherever the card ID is readable in the clear and the reader skips cryptographic verification. Defend with a modern card family, properly configured readers, a second factor on critical doors and log review.

## Key takeaways

- Card cloning is possible when the card ID is readable unencrypted or the reader checks only the serial number (UID).
- A cloned card goes unnoticed at the door; the system records the genuine holder, so traces appear only in access logs.
- According to HID Global's 2024 survey, one in three companies still support easily copied 125 kHz proximity cards.
- Six steps cut the risk: inventory, zone classification, a second factor, encrypted cards with key management, card lifecycle and regular log review.
- SmartPass does not stop cloning at the door; it shortens how long a lost or cloned card works and stores no card numbers.

## Why does nobody notice a cloned card?

The unsettling thing about a cloned access badge is how quiet it is. When the copy is presented, the system records that the genuine cardholder walked in. The guard sees nothing unusual and the access report shows an authorised entry.

Nobody has to steal the card, either. Badges sit on lanyards, in pockets and in bags, and they come within a few centimetres of strangers in lifts, on staff buses and in the canteen queue; with older cards, that brief moment can be enough. Sometimes no copy is needed at all: an employee who lends a card "just for a minute" produces the same result without any technical skill.

This article is not about which frequency to choose. It covers **how cloning risk arises on your site, how to detect it and how to close it**. For the frequency and card-family comparison, see our guide to [125 kHz vs 13.56 MHz cards](https://digitalbridge.com.tr/en/blog/rfid-125khz-vs-13-56mhz-cards.html).

## How do access cards actually get cloned?

Understanding the attack paths is the quickest way to see what each control actually fixes. Four routes come up again and again in the field:

- **The ID number is broadcast in the clear.** Many legacy 125 kHz [RFID (radio-frequency identification)](https://digitalbridge.com.tr/en/glossary.html#rfid) proximity cards transmit a fixed number with no encryption. Once it has been read and written to a blank card, the reader cannot tell the two apart.
- **The reader only checks the serial number (UID).** Even when a card carries encrypted memory, a reader configured to look only at the UID never uses that encryption. Cards and gadgets that emulate a UID exploit exactly this.
- **Broken legacy encryption.** The cryptography of some older 13.56 MHz card families was broken years ago in published research. They may be marketed as "encrypted", but they offer little resistance to copying.
- **Lent cards and cards nobody revoked.** Not technical, but the most common route of all. If a departed contractor's badge is still active, the outcome is identical to a clone.

In a [penetration test](https://digitalbridge.com.tr/en/blog/penetration-testing-guide.html) that covers physical security, card cloning is among the first techniques testers reach for, so the risk is far from theoretical.

## What does living with clonable access cards cost?

Legacy card technologies that are easy to copy are still common as of 2026. A survey of more than 1,200 respondents by HID Global found that one in three companies still support 125 kHz low-frequency proximity cards, and nearly 30% still run systems that use magnetic stripe cards ([HID 2024 State of Physical Access Control Report, via CampusIDNews](https://www.campusidnews.com/access-control-survey-shows-continuing-rise-in-biometrics-mobile-ai/)).

An access card is the physical counterpart of a password: it is the only thing proving who is at the door. That is why [physical access is part of cyber security](https://digitalbridge.com.tr/en/blog/physical-access-and-cyber-security.html). On the digital side we know how effective a stolen credential is:

> Verizon's 2026 Data Breach Investigations Report (DBIR) found that the use of stolen credentials held steady as an action in 36% of breaches. ([Verizon 2026 Data Breach Investigations Report](https://www.verizon.com/business/resources/T1ae/reports/2026-dbir-data-breach-investigations-report.pdf))

A server room or records store entered with a cloned card can turn a physical incident into a data breach. According to the [IBM Cost of a Data Breach Report 2026](https://www.ibm.com/reports/data-breach), the global average cost of a breach has reached $4.99 million. In Türkiye, where the KVKK (the national data protection law, similar in spirit to GDPR) requires data controllers to report personal data breaches, the Authority's [2025 Annual Report](https://www.kvkk.gov.tr/SharedFolderServer/CMSFiles/MTY5ZjMxYTVlZGY0Y2Y.pdf) records 328 breach notifications in 2025. An incident that starts at a door can fall within that duty; our guide to [the 72-hour breach notification](https://digitalbridge.com.tr/en/blog/data-breach-72-hours-kvkk.html) explains the process.

## How does a cloned card show up in access logs?

A cloned card goes unnoticed at the door, but it usually leaves traces in the event log. The table below lists the signals worth reviewing regularly and what each one suggests:

| Signal | Likely meaning | What to do |
|---|---|---|
| Same card at two distant doors within minutes | Two physical cards exist (a clone) | Suspend the card and speak to the holder |
| Second entry with no exit recorded | Card passed back or copied | Consider an anti-passback rule |
| Out-of-hours entry to an unusual zone | Excess rights or misuse | Match the event against CCTV |
| Entry on the card of someone on leave or sick | Card is in someone else's hands | Compare with time and attendance (PDKS) records |
| Repeated reads of a revoked card | Old or cloned card being tried | Review that reader's location and times |
| Successful entry on a leaver's card | Revocation process is not working | Fix the HR-to-access-control link |

Some cloned-card signals can be enforced as rules. The logic that blocks a second entry without an exit is covered in [anti-passback explained](https://digitalbridge.com.tr/en/blog/anti-passback-explained.html). Bringing door events together with server, email and network logs is the job of [SIEM and log management](https://digitalbridge.com.tr/en/blog/siem-log-management-basics.html); seeing physical and digital events on one timeline answers "clone or data glitch?" quickly.

The strongest way to confirm a suspicious access event is video. Pairing critical-door cameras with access events is easier with [central IP camera management](https://digitalbridge.com.tr/en/blog/ip-camera-onvif-central-management.html), and the footage itself must be retained in line with the rules in [CCTV recording and KVKK](https://digitalbridge.com.tr/en/blog/cctv-recording-kvkk.html).

## How do you prevent access card cloning? A six-step plan

Reducing access card cloning risk means tackling cards, readers and processes together, through the following six steps:

1. **Inventory cards and readers.** Which reader sits on which door, which card family does it read, and how does it verify the card? More often than not the weakness is a reader configured to read the UID only, not the card itself.
2. **Classify zones by risk.** A car park barrier and a server room do not need the same protection. Our article on [zone-based access in factories](https://digitalbridge.com.tr/en/blog/zone-based-access-in-factories.html) is a good starting point.
3. **Never let the card stand alone on critical doors.** Card plus PIN or card plus [biometric verification](https://digitalbridge.com.tr/en/glossary.html#biometric-verification) makes a cloned card useless by itself. The trade-offs are set out in [fingerprint vs card vs face recognition](https://digitalbridge.com.tr/en/blog/fingerprint-vs-card-vs-face-recognition.html).
4. **Upgrade the card family together with key management.** Modern encrypted cards only protect you when readers are set to perform cryptographic authentication. Who holds the keys, and how they are loaded at card issue, should be written down from day one.
5. **Close the card lifecycle.** Joiners, role changes, leavers and lost-card reports should reach the access system on the same day. The email equivalent of this problem is covered in [offboarding email access](https://digitalbridge.com.tr/en/blog/offboarding-email-access.html).
6. **Review logs and test regularly.** Turn the cloned-card signals table from the access log section into a weekly checklist, and commission a test that includes physical security at least once a year.

If your current access control system cannot support most of these six steps, our guide to [replacing legacy access control](https://digitalbridge.com.tr/en/blog/replacing-legacy-access-control.html) shows how to change cards and readers without downtime. For the fundamentals, start with our [card access control guide](https://digitalbridge.com.tr/en/blog/card-access-control-system-guide.html).

## How Digital Bridge approaches card security

Because Digital Bridge builds hardware and software in the same team, we treat card security as one job running from the door to the database:

- **Discovery and risk map.** We survey your readers, card types and zones on site, and report which doors are open to cloning and how each reader verifies cards. The technical feasibility study for hardware is free of charge.
- **Pilot.** We first trial the new card and reader set-up on a handful of critical doors, such as the server room, warehouse or archive, with real users. Under our [card access control](https://digitalbridge.com.tr/en/industrial-products/card-access-control.html) service we install readers, controllers, locks and turnstiles, and add [fingerprint access](https://digitalbridge.com.tr/en/industrial-products/fingerprint-access.html) where a second factor is needed.
- **Security and compliance.** Key management, log-monitoring rules and the scope of physical testing sit within our [cyber security consultancy](https://digitalbridge.com.tr/en/consultancy/cyber-security.html); retention of card data and access records is handled under [data protection compliance](https://digitalbridge.com.tr/en/consultancy/data-protection-compliance.html).
- **Integration.** We build [system integrations](https://digitalbridge.com.tr/en/technology-hardware/system-integrations.html) so that a leaver recorded in HR reaches the access system the same day, instead of relying on someone remembering an email.

## Narrowing cloning risk with SmartPass

[SmartPass](https://digitalbridge.com.tr/en/smartpass.html), the card access and time-and-attendance product Digital Bridge develops within the Smart360 family, works with cards readable over 13.56 MHz MIFARE and NFC; it reads only the card's identifier (UID) and writes no data to the card. That is why the real defence against cloning at the door is the choice of card family and reader; what SmartPass adds is shortening how long a cloned or lost card stays useful, and leaving a trail. A visitor's temporary card is limited to the visit's time window; once that expires it opens nothing, so a card that never comes back is useless too.

With SmartPass, card security continues in the database. Card numbers are not stored: each is turned into a one-way hash on the device the moment it is read, using a key unique to your organisation, and the database holds only the hash and the last four digits. Even someone with database access cannot extract a list of card numbers to clone. Every change is written to the audit log with previous and new values, and because access and audit records are hash-chained, a later deletion or alteration shows up when the chain is verified.

A concrete scenario: at midnight, the security lead sees an entry to the warehouse zone on the card of an employee who is on leave. Every access decision is logged with its source, so they can see which access point was used and when, and check it against camera footage. As soon as the card is marked lost or cancelled in the panel, the change applies on the server and the permission lists at the doors update within seconds; if needed, the access point can be locked from the panel. Leavers are covered the same way: when a person is deleted on the [Smart360 product family](https://digitalbridge.com.tr/en/smart360.html) side, their SmartPass card is cancelled and their personal details are removed.

To be clear, SmartPass's database-side safeguards do not on their own stop a card at the door from being copied. The card family, reader configuration and second factor on critical doors are addressed separately during Digital Bridge's discovery and pilot stages.

## How can you measure your card cloning risk?

If you do not know whether the access cards on your doors can be cloned, the first job is to find out. Send us the card and reader model and we will map the risk on your critical doors and outline a phased improvement plan. To arrange a site visit or request a proposal, use our [contact page](https://digitalbridge.com.tr/en/contact.html). To buy SmartPass, fill in the [SmartPass sales form](https://smart360.com.tr/teklif-iste?urun=smartpass).

For more guides in this area, visit our [Access Control & Attendance](https://digitalbridge.com.tr/en/blog/topic/gecis-kontrol.html) hub.

## Frequently Asked Questions

### Can my access card be cloned, and how can I tell?

You have to assess the card and the reader together. If the card is a legacy proximity card that broadcasts its ID unencrypted, or the reader only checks the serial number, the cloning risk is high. The manufacturer marking on the card and the reader model are usually enough for a first assessment; a definitive answer needs a review of the reader configuration and a controlled test.

### Is cloning an access card illegal?

Copying someone else's access card without permission and using it to enter a restricted area can have serious criminal and employment consequences in most jurisdictions, including Türkiye. An organisation testing its own system should do so under written authorisation with a clearly defined scope. For a legal view, consult your lawyer; this article is not legal advice.

### Do 13.56 MHz cards stop cloning completely?

No. The encryption of some older 13.56 MHz card families has been broken, and many installations configure readers to check only the card's serial number. In those cases a 13.56 MHz card is as easy to imitate as a legacy proximity card. You need a current encrypted card family, readers set up for cryptographic authentication and a second factor on critical doors.

### What should we do if we suspect a cloned card?

First suspend the card in the system and issue the holder a new one. Then match recent events on that card against camera footage and establish which zones were entered. If a zone holding personal data was accessed without authorisation, assess the event under your breach-response procedure. Finally, review every other door that uses the same reader type.

### How do we stop staff lending their cards to others?

There is no purely technical fix; policy, training and records work together. Make it clear in writing at onboarding that the card is personal, and require a PIN or biometric alongside the card on critical doors. Comparing access events with attendance and camera records on a regular basis makes lent cards visible and discourages the habit.

### How do you prevent access card cloning?

Access card cloning is prevented by addressing cards, readers and processes together rather than relying on one control. Start with an inventory of cards and readers and classify zones by risk. Add a PIN or biometric alongside the card on critical doors, and upgrade the card family together with encryption key management. Process leavers and lost cards the same day, and review access logs weekly.

### How does SmartPass store card numbers?

SmartPass does not keep card numbers in its database: each number is turned into a one-way hash on the device as it is read, using a key unique to your organisation, and only the hash and the last four digits are stored. Anyone who gains access to the database therefore cannot extract a list of card numbers. Records past their retention period lose the fields that identify a person, every change is logged with previous and new values, and reports show only the last four digits.
