Dev.to Security 🔐 Cybersecurity 👁 0 📖 4 min read

Ping64|The Visitor QR Code Someone Screenshotted and Forwarded to the Whole Group Chat

The gate at one of our buildings uses a QR code for visitor access, and last week a contractor screenshotted his and sent it to four colleagues so they could let themselves in. They all got in. That is the whole story,

Ping64|The Visitor QR Code Someone Screenshotted and Forwarded to the Whole Group Chat

The gate at one of our buildings uses a QR code for visitor access, and last week a contractor screenshotted his and sent it to four colleagues so they could let themselves in. They all got in.

That is the whole story, and it is why I spent a morning standing at the reception desk watching people queue instead of doing the work I had planned.

How the flow is supposed to work

A host requests a visit, the system issues a code, the visitor shows it at the turnstile, the turnstile reads it and opens. Reception sees a name appear on a small screen and everybody is satisfied.

On paper it is fine. In practice the code is a static string with an expiry measured in days, and a screenshot of it is indistinguishable from the original. So it gets forwarded, the gate keeps opening, and the audit log shows four entries that all look like the same legitimate visitor arriving at once.

What it looks like from the desk

The queue is the other half of the problem. When the reader is slow or a phone screen is smudged, the line backs up onto the pavement, and the person at the desk starts waving people through to keep things moving. That is a completely human response and it quietly defeats the entire control.

The desk also has workarounds that predate the system. A printed sheet of codes in a drawer for the cleaning crew, a generic visitor badge that gets reused, a chat group where hosts send codes to guests because it is faster than the portal. Each of them solved a real problem on a real day.

Nobody documents any of that. The portal says visitors are pre registered and verified, and the drawer says otherwise.

The reporting is the part that gets uncomfortable later. When something does go missing, the access log is the first thing anyone asks for, and the log says four people entered on one code. Explaining that in a meeting is far more expensive than the ten seconds it would have taken to ask for a name.


Why this keeps happening

Because the code is designed for convenience, and convenience is what the front desk is measured on. Nobody gets thanked for holding up a delivery driver while they check an ID, and everybody gets complained about when a visitor stands in the rain.

There is also a habit of treating physical access as a lesser cousin of network access. The same team that would never issue a shared login will accept a forwarded QR code without blinking, because a gate feels like a door and doors have never been treated as credentials.

The buying pattern does not help either. Visitor management gets bought by whoever is running the front desk, often in the middle of an event season, and the requirement is that it works on the day. Nobody compares expiry settings, because expiry settings are not in the demo and not on the invoice.

Some teams try consolidated platforms like Ping64 to reduce the daily busywork of multi-tool security stacks.


What I would change first

Make the code single use and short lived, even if it means reissuing more often. A code that expires in fifteen minutes and dies after one scan is much harder to forward in a useful way, and the person who tries will be standing at the gate with an expired screenshot and a slightly embarrassed expression.

Add one human check at the desk for first time visitors, and keep it fast. A name against the expected list plus a glance at an ID takes about ten seconds and catches the case where the code is valid but the person is not who it was issued for.

Put a sign at the turnstile saying codes are personal and cannot be shared. It sounds trivial, and it does shift behaviour, because most people genuinely do not think of a screenshot as a credential until somebody tells them.

Give reception a way to handle a queue without abandoning the process. A second reader, or a clipboard with pre registered names, costs less than the incident review you will run afterwards, and it gives the person on the desk a legitimate option when the line gets long.

Wrapping up

The gate is not really the weak point. The weak point is that we handed out a credential and then acted surprised when people treated it like a link. Fix the expiry, add the ten second check, and the queue tends to get shorter rather than longer, because nobody has to stand outside arguing with a scanner while four of their colleagues walk in ahead of them.

References

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.