Area 1: punches after the block
The first check is whether the blocked card was used after the block. Refusals after the block are a good sign, because they show that the block worked. Punches that ended in an entry after the block are a signal for escalation and a review of the access control system.
A gate scan is a control act: a green verdict records an entry or exit, while a red verdict records a refusal entry that does not count as presence on site. The security manager therefore reviews entries and refusals from the card separately. If there are no refusals and nobody tried to use the card, that is also information, and it is recorded in the file.
- Check that there are no entries from the blocked card after the time of the block.
- Record the number of refusals after the block and their gates.
- Check that no person from the earlier scan is still on the On site list.
Area 2: the person's account
The second check concerns the employee's account. The administrator checks that the new card is assigned to the correct account and that training results have not been split between two accounts. When the same person has two active accounts, the system transfers the training result to the account holding the card, but never merges accounts on the basis of the surname alone, so this remains a task to be done by hand.
The administrator also verifies that the scope of the person's permissions has not changed. Changes to permits, training records and automation rules are recorded in the audit trail, so the review is quick and covers the period from the report of the loss to the closing of the case.
- Check that the new card is assigned to the account that reported the loss.
- Check that the person does not have a second active account.
- Review the audit trail of permission changes from the period of the case.
Number of control points in each area
Area 3: the QR badge
The third check concerns badges. The rule of one active badge per person is enforced in the application by a transactional lock, but the security manager confirms in the panel that the temporary badge has been replaced by a permanent one or withdrawn. Cancelling creates a new record instead of overwriting the old one, so the person's badge history stays in the system and an old badge does not disappear without a trace.
It is also worth remembering the physical return or destruction of the temporary badge. The system cancels the code, but it cannot collect the card from the employee's pocket. Recording the destruction in the file closes this part of the case.
- Confirm that only one badge of the person is active.
- Confirm the return or destruction of the temporary badge.
- Check that the badge history contains a cancellation entry with a date.
Area 4: notices and security events
The fourth check concerns whether the right people have been informed. A refusal at the gate sends a notification stating what is missing, so the security manager can see who received it. Events from registration stations go into the security event log under names from an approved list and described in a catalogue for SIEM systems, and the administrator checks that they reached central monitoring.
If the case was classified as a suspected cloning, the security manager also confirms that the data protection officer and the security department have been notified.
Area 5: register and conclusions
The fifth check is the register of reports. The entry should show the time of the report, the time of the block, the time the replacement card was issued, the person who closed the case and the classification: lost, stolen or cloned. The difference between the time of the report and the time of the block is the risk window, which the plant measures and reports.
The last step is a conclusion on the process. If the window was longer than the plant assumed, the security manager records the cause and the action that will remove it. The physical block of the card sits with the access control system, so a conclusion about the block time goes to the access control system administrator, and a conclusion about access and presence goes to the administrator of the security system. InnerWeb is a software manufacturer, and the plant buys and integrates the cards and readers, so hardware conclusions concern the access control system supplier.
- Record the times of the report, the block and the issue of the replacement card.
- Record the classification of the incident.
- Record the cause and the action if the window was longer than assumed.
Checklist
Video
Frequently asked questions
Who closes the card case?
The security manager closes it after checking the five areas, and the system administrator confirms the account and the badge. When cloning is suspected, the data protection officer joins the closing.
Can the case be closed when the card has not been found?
Yes. Closing does not require finding the card, only blocking it, issuing a new one and confirming that there were no successful punches after the block.
How long does closing the case take?
With complete data in one system, about a dozen minutes. When the data has to be gathered from several places, it takes longer, which is why it is worth preparing the case file on the day the case is closed.
Close card cases with evidence in one place
We will show how punches, the account, the badge and the audit trail come together in closing a case. Book a conversation with the InnerWeb team.
Let's talk