InnerWeb
Skip to main content

SAM module in KD readers: implementation notes

The SAM module in a reader stores the master keys in a secured chip and performs the card authentication, so the keys never leave the reader. Before you order readers, the integrator and the IT department need to settle a few things that cannot be fixed after delivery: the version, how the keys are loaded, and who is responsible.

4
stages: settling, keys, pilot, integration
Source: own elaboration
5
questions for the supplier before the request for quotation
Source: own elaboration

What the SAM module does and what it does not do

The SAM module in a reader stores the master keys in a secured chip and performs the card authentication, so that the keys never leave the reader. NXP documentation for SAM AV3 describes this. For the plant it means that even physically obtaining a reader does not give access to the keys in plain form.

The module does not solve organisational problems: it does not replace the key administrator role, it does not monitor the card register, and it does not know whether a card belongs to the person presenting it. It is an element of key protection, not an access control system.

InnerWeb does not manufacture or replace access control readers and does not supply SAM modules. The plant agrees them with the KD supplier, and we receive the tap events from its system. The notes below concern the plant's conversation with the supplier, not an InnerWeb offer.

Stage 1: what to settle before the request for quotation

The first question to the supplier: does the proposed reader model have the SAM module built in, or as an option fitted in a slot? The second: which card versions does it support in the mode that uses keys from the module, EV2, EV3, or both?

The third question concerns the keys: who loads the keys into the modules, at which station, with which tool, and who has access to it. If the answer is that the supplier's technician does it on site, the plant loses control over the role of the key administrator.

  • reader model and the way the SAM module is fitted
  • card versions supported in the mode that uses keys from the module
  • who, how and where loads the keys into the modules
  • number of readers in the plant and the stock of modules
  • service contract and the procedure for replacing a faulty module

Sample schedule for deploying readers with a SAM module (assumption)

Sample schedule for deploying readers with a SAM module (assumption)Horizontal bars: 3, 6, 2 and 5 weeks.0246weeksSettling and request forquotationSettling and request for quotation: 3 weeks3DeliveryDelivery: 6 weeks6Pilot on a single readerPilot on a single reader: 2 weeks2Deployment of the restDeployment of the rest: 5 weeks5
Source: Sample calculation: times assumed for planning, to be replaced with the supplier's data

Stage 2: key diversification and the key model

Key diversification means that the card key is calculated from the master key and the unique UID of the card, so the leak of one card key does not open the others. The SAM module usually performs this calculation inside the chip. In the request, it is worth asking for a description of the diversification algorithm and confirmation that it meets the requirements set by the plant.

If card personalisation takes place at a different station from the readers, the modules in the readers and the personalisation tool must calculate the same key. A mismatch in configuration only shows up with the first batch of cards: the readers reject valid cards.

Stage 3: pilot on a single reader

Before ordering the whole pool, run a single reader with a SAM module at one gate: personalise a dozen test cards, tap them, reject a card with a different key, back up the keys and try to restore them. Also check the behaviour during a power loss and after a reader restart.

Record the pilot results in a protocol: reader version, module version, card version, and the result of each test. The protocol is the basis for acceptance and the evidence in a conversation with the supplier if a fault occurs after deployment.

Invite a security representative who will use the gate every day to the pilot. They will notice points the integrator will not: the response time of the reader when wearing gloves, the mounting height for a forklift driver, and the behaviour when a queue of people enters at shift change. Ergonomic fixes are cheapest before the whole pool is ordered.

Pitfalls during deployment

The first pitfall is ordering readers with a SAM module without ordering spare modules. A faulty module disables the gate, and delivery time is sometimes counted in weeks. A spare stock of a few percent of the pool is cheaper than a shutdown during the night shift.

The second pitfall is the key backup. If the master key exists only in the modules, the loss of all modules means losing the ability to issue cards. A backup kept separately, with an access register, is a necessary condition.

The third pitfall is assuming that the SAM module removes the need to control the card register. The module protects the key, but it will not protect against a lost card that was not blocked or against a duplicate account of a person.

Stage 4: integration with the plant's systems

Once the readers are running, the tap events should reach the systems that use them. InnerWeb receives the card tap event from the access control system through a webhook and links it with qualifications, permits, attendance and working time registration. The sequence of work is described in a separate note on the webhook.

From the perspective of the SAM module, the integration changes nothing: the keys stay in the reader, and the system receives the authentication result and the number of the active card. It is still worth agreeing with the supplier that the number passed on is not a key or a derivative of a key.

Video

Frequently asked questions

Does every reader need a SAM module?

No. It is used only where the security policy requires it, for example at main gates.

Does InnerWeb supply SAM modules?

No. InnerWeb is a software producer and does not manufacture or replace readers.

What happens if a module fails?

The reader loses the ability to authenticate cards, so a stock of modules and a replacement procedure are needed.

Does diversification require a SAM module?

No, but the module allows the calculation to be performed inside the chip without exposing the master key.

Sources

Prepare your questions for the KD supplier

We will help compile the list of questions about the SAM module and prepare a protocol for a pilot on a single reader.

Let's talk