Why the checklist is needed before ordering
With ordinary cards, an error in the specification costs a replacement of the batch. With encrypted cards it costs more, because a card issued with a key that nobody should know stays in circulation until it is withdrawn. That is why questions about keys and formats must be asked before the card is encoded.
The list below does not replace a security design, but it quickly distinguishes a vendor who has a process from one who only has an offer.
Card and reader technology
The chip maker describes DESFire EV3 as a high security solution for contactless city services, including access control. Simply having the feature in the offer is not enough: you need to check which functions the vendor actually enables.
- Do the readers support AES 128-bit authentication with a CMAC code?
- Is proximity checking enabled as protection against relay attacks?
- Is the random UID switched on, and how does it affect person recognition in the system?
- Do the readers work to ISO/IEC 14443 and do they have current software?
Number of control questions in the checklist groups
Keys and diversification
This is the most important part of the list. Key diversification relies, among other things, on a key derivation function according to NIST SP 800-108: each card has a key derived from the master key and its own UID. Ask who generates the master key, where it is stored, and whether you can have it as your property.
Require a written description of the rotation and blocking procedure. A vendor who cannot say what happens after a card is lost does not yet have a finished process.
- Who generates and who stores the master key?
- Are the keys diversified per card?
- Is the master key your property, and can it be handed over to another vendor?
- How does key rotation work, with version numbers?
Applications on the card and integration with the supplementary system
If the card is to handle several functions, agree a split into separate applications with separate keys. DESFire EV3 lets you hold many independent applications, each with its own keys, so there is no reason to share one key between entry, car park and canteen.
Also ask whether the access system can send punch events through a webhook to the supplementary system. InnerWeb is a software vendor, does not supply cards or readers, and receives punch events from your existing access control system. The format of the event should be described in the contract.
Contract, service and exit from the vendor
The last group of questions concerns uncomfortable situations: what if the vendor disappears, raises prices or cannot handle a fault. Cards and readers replaced every few years make for a long relationship, so it is worth securing the portability of keys and data.
Ask for a delivery schedule, a reserve of cards for losses and a procedure for complaining about a defective batch. Write into the contract the response time for a fault in the main gate reader.
Checklist
Video
Frequently asked questions
Does InnerWeb supply encrypted cards?
No. We are a software vendor and do not produce cards or readers. We integrate with the access system you choose.
Which point on the list is the most important?
Management of the master key. Without ownership and a described procedure, even a secure card gives a false sense of protection.
Can a card be bought without key diversification?
It can, but disclosing one key would expose the whole workforce. At larger scale, diversification is the recommended practice.
Sources
Let's prepare requirements for the card vendor
We will help you specify the requirements for access events that must flow into the supplementary system. Book a call with the InnerWeb team.
Let's talk