Who these recommendations are for
The material is for people who must justify the choice: the plant director, the head of purchasing, the head of security and IT. It assumes the plant already has an access control system and is considering a new generation encrypted card, most often from the MIFARE DESFire EV3 family.
InnerWeb is a software producer. It does not sell cards or readers, so the guidance below does not serve to promote hardware. It describes what to check in the access control supplier's offer and how this fits into the complementary system.
Recommendations
The seven items are ordered in the sequence in which they usually come up in a conversation with management.
1. Require hardware AES encryption with 128-bit keys
The DESFire EV3 chip maker declares hardware AES with 128-bit keys and a key version number. The version number has practical value: it allows keys to be replaced after the first batch of cards is issued and tells key generations apart.
2. Check data authentication (CMAC)
DESFire EV3 ensures data authenticity with an 8-byte CMAC. Ask the supplier whether its readers and controllers use a mode that applies this protection, and not only read the card number.
3. Ask about proximity checking
Proximity checking is protection against relay attacks. For gates with high traffic and sensitive zones it is a reason to choose EV3. For other doors the decision can be simpler.
4. Plan the applications on the card
The card works under ISO/IEC 14443 type A and can hold several independent applications, each with its own keys. This means access to the plant, the canteen payment and other services can be separated cryptographically.
5. Require key diversification
Each card should have a key derived from the master key and its own UID, according to the key derivation function described among others in NIST SP 800-108. Then the leak of one card's key does not open the others.
6. Do not treat the random ID as key protection
The random identifier is a privacy feature: the card does not reveal a permanent UID during a read. It is not a key derivation mechanism, so it does not replace point 5.
7. Separate the access decision from the card
An encrypted card does not replace the access decision: it verifies the identity of the credential, and entry is decided by the permissions on the system side. In the offer, ask about the API and webhooks of the access control system, because they allow swipes to be linked with qualifications and permits in the complementary system.
Example weighting of offer evaluation criteria (points out of 100)
How to compare supplier offers
It is worth making the comparison in a table with the same criteria for every offer: encryption level, authentication mode, proximity check support, key management, availability of API and webhooks, card issuing method and dependence on a single supplier.
Pay attention to who owns the keys. If only the supplier knows the master key, the plant depends on it at every reorganisation and every contract change. A better offer assumes that the plant controls the keys or has a secure deposit for them.
Where InnerWeb fits in this decision
InnerWeb is an independent system that complements the client's existing systems: access control, time recording, HR, ERP. It does not replace them. It receives card swipe events from the access control system by webhook and links them with qualifications, work permits and presence. The platform also provides a REST API (versions 1 and 2, JWT).
For purchasing this is an important signal: changing the card does not force a change of the permissions system, and choosing an access control supplier does not lock the plant into one software ecosystem.
Video
Frequently asked questions
Does InnerWeb sell encrypted cards?
No. InnerWeb is a software producer and does not manufacture cards or access control readers. It receives swipe events from the access control system and links them with permissions.
Is a random identifier enough as protection?
No. It is a privacy feature that hides the permanent UID during a read. Security comes from the AES keys and authentication.
What about the cards the plant already has?
Their fate is decided by the migration plan. We describe the details and the sequence in the material on migrating from 125 kHz cards to DESFire.
Sources
Talk to us before the purchase
We will check together which interfaces the access control system should have so that the encrypted card feeds permissions in InnerWeb. Book a conversation.
Let's talk