InnerWeb
Skip to main content

FAQ: security of QR visitor passes at a production plant

The security inspector usually asks three things: whether the code can be guessed, whether it can be copied and what the system does when a copy is used. The answers below describe how the QR pass works in InnerWeb and separate what the system limits from what the plant procedure must ensure.

256 bits
of randomness in the badge token
Source: feature card
64
hexadecimal characters of the token
Source: feature card
12 h
stay limit before automatic closing
Source: feature card

Can the code be guessed

The first concern of an auditor is a sequence number built into the code: if badges are numbered one after another, someone could type the next number and get a valid code. In InnerWeb this is not the case, because the badge token is generated only from 32 random bytes of a cryptographic generator. This gives 64 hexadecimal characters, that is 256 bits of randomness, and no counter, personal number or date goes into the token.

For a practitioner this means that knowing one code does not help in guessing the next one. The space of possible values is so large that guessing is not a realistic attack, and not because someone hid a pattern. There is no pattern.

Does the code contain a name or a personal number

No. The QR code encodes the address of the system instance with the token in the form of the /q/ path and a random string. The first name, last name and company appear on the label as ordinary print, but they are not part of the token. Therefore analysing the image of the code alone does not reveal who the holder is.

Does the security panel show the token

No. The token is not returned in any API response of the security panel. The panel receives only derived facts: whether the person has an active badge and when it was printed. The guard therefore sees the status, not the value that could be rewritten or photographed from the screen.

Can the code be copied

The honest answer is: a QR code as an image can always be copied, just as the number on a contactless card can be cloned in weak technologies. No print is protection against a photograph. The protection is what the system does with the scanned token and how quickly it can be disabled.

A copy is as important as the original for as long as the badge is active. Therefore three elements are key: a short lifetime of the badge, fast revocation and a record of every attempt at the gate.

What happens to a copy after revocation

Revocation does not overwrite the old row. The system issues a new token and the old one stays in the history as revoked. Scanning a revoked code at the gate gives the same answer as a non-existent code, "unknown code", so the copy stops working and does not reveal that it was once valid.

Can one person have several active badges

The rule "at most one active badge per person" is enforced by a transaction with a row lock at issuing time, not by a uniqueness constraint in the database. After the code is replaced, the previous one stops being active, so a lost badge does not stay in circulation next to the new one.

Security parameters of the QR pass

Security parameters of the QR passBar chart: 64 token characters, minimum code size 13 mm, stay limit 12 hours, check every 3 hours.020406080valueToken charactersToken characters: 64 value64Minimum QR size (mm)Minimum QR size (mm): 13 value13Stay limit (hours)Stay limit (hours): 12 value12Stay check every (hours)Stay check every (hours): 3 value3
Source: InnerWeb feature cards: badge token, label, automatic closing of stay

Screenshot and photo of the badge

The most common practical situation: a guest or contractor receives the code by e-mail, takes a screenshot and sends it to a colleague. It is worth starting with the fact that the e-mail with the QR code is sent only after the trainings required at the gate have been completed, and each person receives it at most once thanks to an atomic marker in the database. There are therefore no waves of repeated sends that would increase the number of copies in mailboxes.

The screenshot itself is a copy of the same token. It is limited by the gate verdict: it consists of four elements, namely no overdue trainings, no missing qualifications for dangerous work, an approved permit for today and an active account. A colleague who uses someone else's screenshot therefore passes verification on the data of the code owner, not their own, and every attempt is recorded, including refusals.

  • A screenshot is not detected as such: the system sees the same token.
  • Recording every attempt gives evidence for explaining who used the code and when.
  • Fast revocation and printing a new badge close the window of risk.

What a person sees when scanning someone else's code with a phone

The public address with the token does not check whether the token exists. A valid code, a revoked code and an invented string of the right shape produce the same process and a redirect of the same form. A passer-by with a phone will not learn whether the code found is active, and cannot use this page as a search engine for valid codes.

On the training tablet and at the gate the same message "unknown code" (404) applies to a code that is unknown, revoked or invented, without returning the scanned string. Scanning on the tablet logs nothing by itself: the tablet shows the first name, last name and company of the code owner, and the training starts only after confirmation by a person. This intermediate layer protects against accidental logging in of another person.

What the system ensures and what the plant must ensure

A good answer for the inspector does not promise tightness. The system limits risks through a random token, no disclosure of validity, revocation with history and recording of attempts. The plant complements this with a procedure: who collects the badge, when it is returned and how quickly a loss is reported.

The badge should have a neutral look: the plant logo and a QR code with the name and company, without the name of the server. The code size should not go below 13 mm. As a result a lost label does not indicate which system it leads to, and it contains no sensitive data beyond the name and company.

  • Lost badge: report to reception, revocation, new print.
  • Guest badge returns to reception at the end of the visit.
  • A person who did not leave through the gate is closed automatically after 12 hours on site.

How it relates to the encrypted card

An encrypted card has stronger protection against cloning of the medium, but costs more and requires readers and key management. InnerWeb does not produce readers or cards: it receives card swipe events from the plant's access control system and links them with qualifications, permits and attendance. A QR badge and a card can work side by side, for example QR for guests and contractors, a card for the staff.

The choice between them depends on the risk profile. For short visits and high contractor turnover, a short-lived token with fast revocation is often more practical than a medium that must be personalised and recovered.

Checklist

Video

Frequently asked questions

Is a screenshot of the QR code enough to enter the plant?

The screenshot is a copy of the same token, so the system does not distinguish it from the original. The entry decision, however, rests on the gate verdict: trainings, qualifications, today's permit and the active account of the code owner. Every attempt, including refusals, is recorded.

Can someone generate another person's code knowing their own?

No, because the token comes from 32 random bytes, not from a counter or a personal number. Knowing one token gives no information about others.

What to do when a guest loses a badge?

Reception revokes the badge and prints a new one. The old token stays in the history as revoked, and scanning it gives the message "unknown code".

Does the system tell the owner of a found code that it is valid?

No. A valid, a revoked and an invented code produce the same process on the public address, so it cannot be used to check whether codes are active.

Let's talk about QR passes at your plant

We will show how the token, revocation and the record of attempts at the gate work, and help prepare questions for the security audit.

Let's talk