InnerWeb
Skip to main content

Card incident: lost, stolen or cloned

A lost card and a cloned card need different responses, although at first they look the same: someone reports a problem with a card. We give recommendations on how management and the security supervisor can classify the event, so that the right response level and the right people to notify are chosen straight away.

15
events a year at a plant of 500 people
Source: sample calculation

Why classification is the first step

Classification decides who is notified and how deep the review goes. A lost card usually ends with a block and a new card. A stolen card requires checking whether anyone used it. A cloned card points to a weakness in the technology or key management and may affect more than one person.

InnerWeb is a software producer and does not replace readers or cards. It does provide the ledger: punch events from the access control (KD) system are linked with qualifications, permits and attendance, and this gives the material needed to tell the type of incident apart.

Recommendations 1-2: a lost card

Recommendation 1: classify the event as a loss when there are no scans at all after the reported time of loss, and the owner can point to the likely place. The response level is low: block, temporary badge, a register entry and notification of the security supervisor.

Recommendation 2: even at a low level, carry out a short review of swipes. A scan at the gate records an entry or exit on a green verdict and a refusal on a red one, so a filter of a few minutes on the card shows whether anything happened after the report.

Response level by incident class

Response level by incident classThe response level rises from 1 for a lost card, to 2 for a stolen card, to 3 for a cloned card.0123levelLost: 1 level1 levelLostStolen: 2 level2 levelStolenCloned: 3 level3 levelCloned
Source: Sample calculation: the 1-3 scale used in the recommendations

Recommendations 3-4: a stolen card

Recommendation 3: classify the event as theft when scans appear after the loss, when refusals occur with the card being used, or when the owner points to a specific event. The response level is medium: immediate block, a full review of the window from the last certain use, and notification of the security supervisor, HR and the line manager.

Recommendation 4: keep the evidence. A refusal at the gate includes the reason and the names of missing trainings and qualifications in its snapshot, and a refused entry sends a notification saying what is missing. These entries are material for any further escalation of the event.

Recommendations 5-6: a cloned card

Recommendation 5: report suspected cloning when the ledger shows scans of the same card in two places within a time that makes the journey impossible, or when the owner was absent and the card was used. The response level is high: block, a review of all cards of the same generation, and notification of management and the person responsible for information security.

Recommendation 6: do not close the matter by issuing a new card of the same technology. If you suspect cloning, consider migrating to an encrypted card, for example from the NXP MIFARE DESFire family compliant with ISO/IEC 14443, together with a review of key management. This is a decision for the integrator of the KD system, not for InnerWeb.

Recommendation 7: one decision card

Recommendation 7: record the classification as a single field in the register with three values and the date of the decision. A change of classification during a case, for example from lost to stolen, should leave a trace of who changed it and when.

A scale example: a plant of 500 people with an annual loss rate of 3 percent has 15 events a year, according to the sample calculation. Most of them are losses, so the low-level procedure must be quick, while the high level should be triggered rarely and deliberately.

Video

Frequently asked questions

How do you recognise a cloned card?

By scans of the same card in two places in a time that makes the journey impossible, or by use of the card while the owner was off site.

Must every incident be reported externally?

It depends on the law and the plant's policy. If a data protection breach is suspected, consult the data protection officer, because the legal assessment goes beyond the ledger.

Can the classification be changed?

Yes, but the change should leave a trace: who changed it, when and why.

Let's build a decision card for incidents

We will help turn the three incident classes into a register and notifications at your plant.

Let's talk