InnerWeb
Skip to main content

QR code screenshot: how to limit lending a site pass

A screenshot is the simplest way to pass a QR code to a colleague who has no training. The security manager cannot block screenshots in someone else's phone, but can make sure a screenshot is not enough to enter or to pass training. Below are the practices that achieve this.

256 bits
random token that cannot be guessed
Source: InnerWeb function documentation
5 s
window for ignoring a repeated scan
Source: InnerWeb function documentation

Where the risk lies

A QR code on the phone can be photographed, sent in a messenger and shown at the gate from another device. This applies to any carrier that can be copied: a contactless card without protection, a printout, and also an image on the phone. The difference lies in what the system does after the scan.

If the scan logs the person in and lets them through automatically, without any check of who is holding the phone, the screenshot becomes a full pass. Good practice comes down to making sure the code alone is not the only proof of identity.

Practice 1: identity confirmation after the scan

A scan of the QR code on the training tablet does not log the person in by itself. The system shows the first name, last name and company of the code owner, and training starts only after confirming with the button 'Is this you?'. A person at the tablet who uses someone else's screenshot sees someone else's data and must consciously confirm something untrue.

Security can strengthen this effect: at the gate the gatekeeper sees the person's data on the panel screen and compares it with the person in front of them. One look is enough, and misuse requires deceiving a human, not only the scanner.

Sufficiency of a screenshot for entry or training (example rating, 0-100)

Sufficiency of a screenshot for entry or training (example rating, 0-100)Identity confirmation and revocation lower the rating of screenshot sufficiency from 90 to 20.020406080100ptsScan logs in without confirmation: Sufficiency of screenshot: 90 pts90 ptsScan logs in without confirmationScan with 'Is this you?' and revocation: Sufficiency of screenshot: 20 pts20 ptsScan with 'Is this you?' and revocation
Source: Example calculation: a qualitative assessment of assumptions, not a measurement

Practice 2: revocation and a new code

When security finds that a code is circulating between people, it revokes it. Revocation does not overwrite the old entry: the system issues a new code and the old one stops working. A screenshot of the old code becomes useless, and the history of events remains in the register.

Note also that the code is not drawn from the person's data. The token has 64 hexadecimal characters, that is 256 bits, generated by a random number generator, so it cannot be guessed or reconstructed. A copied code therefore requires access to the screen, not guessing.

Practice 3: register and quick reactions

Server-side debouncing ignores a repeated scan of the same person within 5 seconds, so accidental doubling does not clutter the register. Two entries by the same person in a short interval from different gates, however, are a signal for a check. The security manager should review such cases once a week.

The code is sent once per person, so there is one trace in the mailbox. Whoever asks for a second code will get it only after the first one is revoked and identity is confirmed, and the register will show when.

  • 'Is this you?' confirmation at the training on the tablet.
  • Comparison of the panel data with the person at the gate.
  • Revoking codes that circulate between people.
  • Weekly review of double entries from different gates.
  • Information for staff about the consequences of passing a code on.

Talking to the workforce instead of a ban

Technical safeguards work better when staff understand why they exist. A short note with the invitation that the code is assigned to the person, that the system shows the owner's data and that passing on a screenshot ends in revocation, reduces the temptation to lend it.

The plant can also write into the entry rules that the code is personal. This does not solve the problem technically, but it gives a basis for a disciplinary conversation when security notices misuse.

Checklist

Video

Frequently asked questions

Can screenshots be blocked?

Not in someone else's phone, so the safeguard relies on identity confirmation and code revocation, not on blocking screenshots.

What does a person with someone else's code see?

The first name, last name and company of the owner, and training starts after the 'Is this you?' button. Passing it on requires a conscious confirmation.

Does the old code stop working?

Yes. After revocation the system issues a new code, and the previous one does not open the gate or the training.

Let us secure the QR code against lending

We will show identity confirmation and code revocation on the example of your gate. Let's schedule a short call.

Let's talk