InnerWeb
Skip to main content

SAM module in a reader: when to require it in a tender

The SAM module is a secured chip in the reader that stores master keys and performs card authentication. For the purchasing department this means an extra item in the price of the reader and an extra key management process. Below are seven recommendations on when this cost makes sense and when a simpler reader is enough.

128 bit
AES key in DESFire EV3 card authentication

Who this page is for

The recommendations are aimed at the purchasing department, the access control integrator and the IT administrator who prepare a tender for readers or an extension of the card system. We assume that the plant already has a controller and intends to assess whether to require a SAM in new readers.

InnerWeb does not sell readers or cards and does not take part in this purchase as a supplier. It integrates with the access control system that the plant selects, so the recommendations below describe the criteria on the contracting authority's side.

What a SAM does and what it does not do

The SAM module in the reader stores master keys in a secured chip and performs card authentication, so that the keys never leave the reader. DESFire EV3 cards work in the ISO/IEC 14443 type A standard with AES 128-bit encryption and mutual authentication, and the SAM protects the reader side of that exchange.

A SAM does not replace key diversification or a good contract with the card supplier. Diversification limits the effects of a leak of one card's key, while the SAM limits the risk of a leak of master keys from the reader. These are two complementary safeguards.

Recommendations: require a SAM or not (number out of 7)

Recommendations: require a SAM or not (number out of 7)Horizontal bar chart: two recommendations to require a SAM, two not to require it, and three concerning contract clauses.0123recommendationsRequire a SAMRequire a SAM: 2 recommendations2Do not require a SAMDo not require a SAM: 2 recommendations2Contract clausesContract clauses: 3 recommendations3
Source: Division of the seven recommendations on this page (editorial division)

Seven recommendations for purchasing

The recommendations are ordered from the most decisive. For each one we indicate who usually makes the decision.

1. Require a SAM where cards open high-risk zones

If a card opens zones where a wrong entry has consequences for people or for the process, it is worth keeping the master keys in a secured chip. The decision belongs to the head of security and IT.

2. Require a SAM where master keys must stay out of the controller

A controller in a corridor is physically easier to reach than a server. If the security policy forbids master keys outside the server, a SAM meets this requirement on the reader side.

3. Do not require a SAM where the card only identifies with a second factor

Where entry requires an additional confirmation and the card is one of two elements, the cost of a SAM may be disproportionate. The decision is made by IT.

4. Do not require a SAM in 125 kHz readers

125 kHz cards of the EM and Prox type give a fixed number without authentication and without encryption, so a SAM has nothing to protect. Here the question is about replacing the technology, not about an add-on.

5. State in the tender who manages the keys

A reader with a SAM requires a process: who loads the keys, where the copies are, and what happens when a card is lost. Without this clause in the tender the offers cannot be compared.

6. Compare offers together with diversification

Ask the supplier whether the card key is derived from the master key and the UID. An offer with a SAM but without diversification protects less than its price suggests.

7. Write the integration of access events into the tender

Regardless of the SAM, the tender should require the transfer of swipe events by webhook or API, because InnerWeb and other supplementary systems connect them with permits, qualifications and attendance.

When a reader without a SAM is enough

In an office with low risk, at doors that protect only convenience, a reader without a SAM with DESFire EV3 cards and key diversification may be a sufficient version. The condition is an explicit acceptance of the risk and a record of where the master keys are kept.

If the need for a SAM appears later, some suppliers offer readers with a socket for the module. It is worth asking about this at the tender stage, because the surcharge for a socket is often lower than replacing the whole reader.

Video

Frequently asked questions

Is a SAM needed if the card has AES?

AES protects the communication of the card. The SAM protects the master keys on the reader side. Without a SAM the master keys sit in the reader or the controller, which is acceptable only at low risk.

Will a SAM help with 125 kHz readers?

No. 125 kHz cards give a fixed number without authentication, so there are no keys to protect.

Does InnerWeb supply readers with a SAM?

No. InnerWeb is a software manufacturer and integrates with readers chosen by the plant and its access control supplier.

Sources

A tender with integrated access events

Let us talk about which events from your access control system the tender should require, so that they feed permits and attendance.

Let's talk