InnerWeb
Skip to main content

Access card risk review checklist

Before the annual security review, the internal auditor checks a dozen points: card technology, the way it is read, keys, readers, lost cards and evidence. The list below has ten items, each with a comment and the proof the plant should keep in its binder. It lets you assess card risk before the review, not only after the auditor's remarks.

10 items
in three parts of the checklist
Source: guide
13 results
limit of the card account search in the training system
Source: guide

How to use this checklist

The list is a self-assessment before the review. For each item the answer is yes, no or partly, and for any answer other than yes you record who fixes it and by when. A plant with a completed list and dates for the fixes shows the auditor that the risk is recognised and managed, even when not everything is fixed yet.

The list is completed by the security function together with the IT department. The items on technology and keys require technical knowledge, while the items on procedures require knowledge of shift work and the circulation of cards.

Part A: card technology and the way it is read

The first three items concern what the plant actually has in circulation. This is the foundation of the whole review, because all the following questions depend on the card technology.

The technology determines resistance to copying. 125 kHz cards transmit a fixed number without authentication and without encryption. MIFARE Classic uses the Crypto1 cipher with a 48-bit key, which has been broken. DESFire EV3 offers AES with a 128-bit key and mutual authentication.

  • 1. We know the card technology in circulation per employee group. Evidence: the technology register from the inventory.
  • 2. 125 kHz and MIFARE Classic cards are under control: we have a replacement plan or a justification for keeping them. Evidence: an entry in the risk register with a date and compensating measures.
  • 3. We know whether the access control system authenticates the card or reads only the UID. Evidence: written confirmation from the access control vendor.

Division of the 10 checklist items into parts

Division of the 10 checklist items into partsDivision of items: part A 3, part B 3, part C 4.A: technology and reading: 3 items (30%)B: keys, readers, integrations: 3 items (30%)C: procedures and events: 4 items (40%)10itemsA: technology and reading3 items (30%)B: keys, readers, integrations3 items (30%)C: procedures and events4 items (40%)
Source: Structure of the checklist on this page

Part B: keys, readers and integrations

The next group concerns what protects the card at the moment of reading. Even the best card fails when keys are stored carelessly or readers have an old configuration.

DESFire allows one master key per card and up to 14 keys per application, which makes it possible to separate the keys of different systems on one card. This is useful, but it requires a policy: who knows the master key and where it is kept.

  • 4. The master key of the cards and the application keys have an owner and a storage location, and access to them is restricted. Evidence: the key management procedure.
  • 5. The readers have a current configuration, and the reader-to-controller link is secured wherever the technology allows it. Evidence: the acceptance or inspection protocol for the readers.
  • 6. Swipes from the access control system reach the permit and training system in the agreed format. Evidence: the event specification and the test protocol at the gate.

Part C: procedures and handling of events

The technology is not enough if the procedures do not keep up. The auditor will ask about lost cards, the return of cards when an employee leaves, and how to handle events in which one card appears in two places at once.

A good test is to select five cards issued in the last year at random and trace their history: issue, activity, any blocking, return. The gaps in this chain best show how card supervision works.

  • 7. A lost card is blocked within the time set in the procedure, and a new one is issued after verifying identity. Evidence: the blocking log with reaction time.
  • 8. Cards of leaving employees and external contractors are collected and deactivated on the last day of work. Evidence: the list of leavers compared with the list of active cards.
  • 9. The plant monitors swipes for anomalies: the same card in two places, swipes outside a shift. Evidence: the anomaly report or the swipe review procedure.
  • 10. A search for an employee account by card does not reveal the card number and returns a limited number of results. Evidence: the system configuration.

How to assess the result and what to do with it

If most items are answered yes and the rest have a plan, the plant is well prepared. If the no answers cluster in Part A, the problem is a lack of knowledge about the card technology, and the first step is an inventory. If they cluster in Part C, the problem lies in the procedures, and it is worth starting with lost cards and leavers.

Item 10 comes from the configuration of the training module for installations with RFID cards: the card account search returns at most 13 results, only active accounts with an assigned card, and does not reveal the card number. This is an example of a solution consistent with the data minimisation principle, which the auditor can compare with their own system.

InnerWeb does not manufacture or replace readers and access control cards, and it integrates with the client's access control system, so items 1 to 5 concern the access control system, while items 6 and 10 concern the cooperation between the access control system and the permit and training system.

Checklist

Video

Frequently asked questions

How often should the card risk review be carried out?

At least once a year, before the security review, and after every change of card technology or readers. After an event involving someone else's card, the review is carried out immediately.

Must every item be answered yes?

No. What matters is that the plant knows its status and has a plan for improvement. The auditor also assesses whether the risk is recognised and whether someone is responsible for reducing it.

Who should complete the list?

The security function together with the IT department. The technology part requires knowledge of the readers and keys, and the procedural part requires knowledge of card circulation and shift work.

Sources

Preparing for the security review?

We will help assemble the evidence on the side of the permit and training system. Book a conversation or a demo.

Let's talk