InnerWeb
Skip to main content

DESFire card applications: one card, many functions

One employee card can handle plant entry, the car park and the canteen, provided each function gets its own application with its own keys. This guide shows how to design such a split, which mistakes are made most often, and how to avoid a situation where the canteen key opens the doors to the production hall.

many
independent applications on one card, each with its own keys

What an application on the card is

DESFire EV3 works in the ISO/IEC 14443 type A standard and lets one card hold many independent applications. Each application has its own files and its own keys, so whoever knows the key of one application does not open the others.

This differs from a simple number carrier, where all systems read the same field. Splitting into applications gives organisational order: entry belongs to security, the car park to administration, the canteen to another supplier, and each manages its own key.

How to split the functions into applications

The design rule is simple: one function, one application, one set of keys and one owner. Avoid a shared application that all systems look into, because then the key becomes the weakest link.

Entry application

It stores the employee identifier used for the access decision. Its keys are known to the access control system and to the readers at the gates. It is this application that feeds the punch events which InnerWeb links with qualifications and permits.

Car park application

It handles the barrier and the vehicle register. It has its own keys, which do not give access to the hall. As a result, the car park provider receives no data from the entry application.

Canteen application

It holds the data needed for meal settlements. It should not contain the entry identifier or HR data. If the canteen handles payments, its keys are held only by the operator of that function.

Key diversification for each application

Good practice is a derived key: each card has an application key derived from the master key and its own UID, according to a key derivation function compliant with NIST SP 800-108. Disclosing the key of one card does not open the others.

With several applications you do this separately for each one: a separate master key, a separate generation process and a separate place of storage. Only then are the applications independent in the security sense, and not merely in the sense of memory layout.

Common mistakes and how to avoid them

The most common mistake is using the same key in several applications for the sake of implementation convenience. The second is leaving factory keys on auxiliary applications. The third is having no key replacement plan, even though keys have version numbers and can be rotated.

  • A separate master key for each application and each owner.
  • Zero factory keys in production.
  • A rotation plan with key version numbers.
  • A description of who may add a new application to an issued card.

What this means for InnerWeb and proof of entry

An encrypted card does not replace the access decision: it verifies the identity of the medium, while the permissions on the system side decide entry. InnerWeb is a software vendor and does not produce readers or cards. We receive punch events from the access control system through a webhook and link them with qualifications, permits, attendance and RCP.

On the security screen, a scan of a QR badge or RFID card gives a verdict built from valid training, qualifications for hazardous work, a permit in progress and an active account. Events from the car park or canteen application do not have to reach InnerWeb, which limits the scope of data processed on the platform.

Checklist

Video

Frequently asked questions

Can the car park and the entry share a key?

Technically they can, but they should not. A shared key means that a leak from the car park opens access to the hall.

Does adding an application require replacing the card?

It depends on the configuration and the free memory left on the card. The rules for adding applications should be agreed with the vendor before the first batch.

Which data reaches InnerWeb?

Only the punch events passed on from the access control system. Applications for other functions do not have to be visible to the platform.

Sources

Let's plan the split of functions on the card

We will help define which access events should feed qualifications and permits in InnerWeb. Book a short call with our team.

Let's talk