InnerWeb
Skip to main content

Checklist: internal audit of QR passes at the plant

An internal auditor or the head of security usually has one day and three places to look at: the gate, reception and the system. The checklist below organises what to check in each of them, so that the security of QR passes can be assessed and evidence for the report collected.

12
points of the audit checklist
Source: checklist on the page
12 h
stay limit before automatic closing
Source: feature card

Scope of the audit and preparation

The audit of QR passes covers three layers: the identity of the token and its protection, the process of issuing and revoking, and the behaviour of the gate. Before the visit at the plant, ask for a description of the badge issuing procedure, a list of roles in the security panel and access to the gate attempt history for the chosen period.

Prepare several test badges: an active one, a revoked one and one printed for a person without trainings. With them you will check the behaviour of the gate without involving real guests.

Gate: what to check on site

At the gate you want to know whether the scan is a decision of the system and not an action of the guard. The scan at the gate determines entry, exit or refusal from the current verdict and the state "on site", without a separate "let in" button. Every attempt, including refusals, should be recorded.

The gate verdict consists of four components: no overdue trainings, no missing qualifications for dangerous work, an approved permit for today and an active account. During the test check whether a refusal corresponds to the missing component and not to a random cause. A revoked and an invented code should give the same answer "unknown code".

Scanner resilience and input data

A USB scanner is a keyboard, so the system must treat the string as text. Ask to see the result of the resilience test against malicious and overly long strings. The gate should reject strings longer than 512 characters before it starts to recognise them.

Audit points by place of control

Audit points by place of controlPie chart: four audit points each for the gate, reception and the system.Gate: 4 points (33.3%)Reception: 4 points (33.3%)System: 4 points (33.3%)12pointsGate4 points (33.3%)Reception4 points (33.3%)System4 points (33.3%)
Source: Number of checklist points on this page

Reception: issuing and revoking

At reception you check whether the first label print for a person without a badge issues a new badge and records the fact of printing, and whether replacing the code revokes the old one. Revocation does not overwrite the old row: the new token is created alongside, and the old one stays in the history as revoked.

Pay attention to the appearance of the label. It should look neutral: 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. Also check whether the e-mail with the QR code goes out only after the trainings required at the gate have been completed, and whether a person without e-mail and phone receives a print from the guard.

System: roles, tokens, history

In the system you verify that the token is not returned in the responses of the security panel. The panel should show only derived facts, such as whether the person has an active badge and when it was printed. Check that the label print page is available only in the guard or administrator role, because it contains tokens in the print addresses.

Review the history of gate attempts and badge replacements. Look for people with several active badges at the same time: the rule "at most one active badge per person" should exclude this. Also check whether people who did not leave through the gate are closed automatically after 12 hours on site.

Audit report: how to assess the results

For each point of the list record one of three outcomes: compliant, deviation to be explained, or error to be corrected. Attach the evidence: a screenshot, an entry from the history or a record from the test on a test badge. Such a report provides evidence for the internal audit and for the review of information security.

The report does not promise compliance with a specific regulation. It supports the assessment of whether the pass mechanisms work in line with the plant's assumptions, and it indicates which elements of the procedure require improvement on the organisation's side.

Checklist

Video

Frequently asked questions

How often should the QR pass audit be repeated?

It depends on the plant's policy. A good starting point is an audit at acceptance, after each major change in the gate configuration, and periodically once a year.

Can the auditor use real guest badges?

It is better to prepare test badges. For an active, a revoked and a printed one for a person without trainings, three samples are enough, and no data of real people is involved.

Does the checklist also apply to encrypted cards?

Partly. The points about the gate verdict, the recording of attempts and revocation are common. The points about the token, the label and the print apply only to QR badges.

Let's prepare the QR pass audit at your plant

We will help prepare test badges and access to the attempt history, so that the audit can be completed in one day.

Let's talk