InnerWeb
Skip to main content

Reconstructing swipes after a lost card: a case from the gate ledger

The card went missing on Friday and the block was ordered on Monday morning. The security supervisor must establish whether anyone used it in the meantime. We describe a post-incident review scenario in which the gate ledger shows entries, exits and refusals.

12 h
threshold for automatic closing of an attendance entry
Source: product specification
3 h
frequency of the automatic exit command
Source: product specification

Starting point: the window between loss and block

A review of swipes only makes sense when we know two moments: the last certain use of the card by its owner and the moment of the block. Everything recorded in that window has to be examined for anomalies. The longer the window, the more data to review and the greater the risk that an unauthorised person entered the site.

This is a post-incident scenario for a production plant, not a description of a specific event. InnerWeb remains a system complementary to the client's access control (KD) system: it does not make readers, but it receives card punch events from the KD system through a webhook and links them with qualifications, permits, attendance and time recording.

What the gate records: entry, exit and refusal

A scan at the gate is not an ordinary punch but an act of control. A green verdict records an entry or an exit. A red one records a refusal entry, which does not count as presence on the site. For the review this is key, because refusals with a lost card are a signal that someone tried to use it.

The refusal entry includes, in the verdict snapshot, the reason and the names of missing trainings and qualifications. The supervisor therefore sees not only the fact of the attempt, but also why the gate rejected it, for example because the card was revoked or a training was missing.

Ledger automation parameters

Ledger automation parametersThe automatic exit command runs every 3 hours and closes entries older than 12 hours.02.557.51012.5hCommand runs every: 3 h3 hCommand runs everyEntry closing threshold: 12 h12 hEntry closing threshold
Source: Security panel function documentation

How to read the ledger step by step

The review should follow a fixed order so that no source is skipped. Below is the sequence used in the scenario.

The key question is whether, after the last certain use by the owner, any scan of this card appeared, and whether that scan matches the place where the owner was actually staying.

  • establish the last certain use of the card by its owner and the moment of the block,
  • filter all entries of this card in that interval, separately entries, exits and refusals,
  • compare the times with the owner's shift schedule,
  • check whether consecutive scans follow each other faster than the route between points allows,
  • record the result in the register of lost card reports.

Pitfalls: duplicates and automatic exits

The ledger contains entries that do not come from a person. Scanning the same code again is rejected as a duplicate: the server applies a 5-second window and the interface a 2584 ms window, so a series of reads within a few seconds does not mean a series of entries.

The second pitfall is the automatic exit. A command run every 3 hours closes the entries of people who have stayed on the site for more than 12 hours and marks them as closed automatically. Such an exit is not a scan at the gate, so the analyst should not treat it as evidence of a physical exit from the site.

Conclusion and evidence for the audit

The result of the review should be one of three: no use after the loss, use by the owner before the report, or unexplained use. The first two close the case. The third starts the classification of the incident as theft or cloning and the notification of the persons named in the procedure.

The audit trail records who and when changed permits for work, the taxonomy of hazardous work, training records and automation rules, so if permissions were changed after the incident, the change can be reconstructed. The system provides evidence for the audit, but the assessment of the event remains the decision of the security supervisor.

Checklist

Video

Frequently asked questions

Does a refusal mean that someone stole the card?

No. A refusal means the gate rejected a scan for a specific reason. Only comparing it with the owner's schedule and the place of the scan shows whether it was an attempt to use someone else's card.

How do we know that an exit was automatic?

An entry closed by the automatic exit command is marked as closed automatically, so it is distinguishable from a scan at the gate.

Does InnerWeb determine theft on its own?

No. The system provides evidence from the ledger, and the classification of the event is made by a person according to the plant's procedure.

See the gate ledger in a demo

We will show how entries, exits and refusals look and how to link them with events from your KD system.

Let's talk