What a badge is and what is inside the code
The QR badge carries a randomly generated token: 32 bytes, that is 64 hexadecimal characters. It is not derived from a person's number or a date, so it cannot be guessed or calculated from other data. This is the basic difference from codes based on an employee number.
The public address on the badge reveals nothing to anyone about the person or the site. A stranger whose phone scans a lost badge will not learn who its owner is. Losing a badge therefore does not mean a leak of personal data, only the need to replace the code.
Step by step: voiding and issuing a new badge
The procedure for security or the administrator consists of several steps, performed in the same order every time. This leaves a consistent trace in the register, and the auditor sees the same pattern for every replacement.
- Identify the person by name, company or the photo on the person's card
- Void the badge: the system creates a new one and keeps the history of the previous ones
- Print the new label, neutral, with the site logo and without the server name
- Hand the badge to the person or wait for the message with the new code
- Record the reason for replacement in a note, if the site procedure requires it
Length of the badge token
What happens to the old code
Voiding a badge creates a new one and keeps the history of the previous ones. This means the old token stays in the register as inactive, but it no longer identifies the person as authorised to enter. Scanning it at the gate does not give a green verdict.
A blocked entry attempt goes into the register as a refusal entry, but it does not count as presence on site or on the evacuation list. For the auditor this is evidence: it shows when someone tried to enter with the old code and that the system did not let them through.
Evidence for the auditor: what to show
An access control auditor usually asks three things: whether the code can be guessed, whether it stops working after being lost, and whether the history is complete. The system has an answer to each of these in the register and in the function description.
Show the random token of 64 hexadecimal characters, the badge voiding entry with its date, and the refusal entries for the old code if anyone tried to use it. Replacement does not destroy the history of entries and exits, so it is possible to reconstruct who was on site and when before the badge was lost.
Good practice when replacements are frequent
If badges are lost often, investigate the cause: the carrier may be too small or the label unreadable. The print scale depends on the label size in the printer driver, so changing to a larger carrier does not require any changes in the system.
For guests with neither email nor phone, a badge printed by security is always needed, so a stock of labels at the gate is part of the procedure, not a luxury.
Checklist
Video
Frequently asked questions
Does a lost badge reveal the person's data?
No. The public address on the badge does not reveal anything to anyone about the person or the site.
Does the entry history disappear after replacement?
No. Voiding a badge creates a new one and keeps the history of the previous ones.
Can the code be guessed?
No. The token is random, has 32 bytes, that is 64 hexadecimal characters, and does not come from a number or a date.
Show the auditor a badge replacement
We will walk through the lost badge scenario with you in a demonstration and prepare the audit evidence.
Let's talk