Both models work. Which one you can have depends on your controllers and readers, and never on us. Whichever model your systems allow, the keys are yours, held by you, escrowed to you, never ours to keep.
The platform moves encoding instructions, and never the keys themselves. No encoding point ever holds a key.
Keys live in a secure module, never in the readers themselves.
Needs controllers and readers that support a SAM, or a hosted vSAM service.
The classic model, and still the right answer on many installations.
Key rotation means touching every reader, and configuration cards are themselves a target.
Whichever model your systems allow, the keys are yours, held by you, escrowed to you, never ours to keep.
1 vault per key owner. No point where encoding happens ever holds a key.
Your DESFire keys, on your own infrastructure. Nobody else can read them.
A landlord, a tenant or a partner keeps its own keys, in its own vault.
Where you prefer a partner to hold and operate the vault for you.
At a badge desk or reception, for one-time issuing or re-encoding.
Unattended exchange, issue and return, at any hour.
For volume runs and re-encoding campaigns across a population.
Programmed remotely. A key change is not a site visit.
One badge can carry more than one organisation's keys. A tenant's own credential re-encoded at reception with the landlord's read key, without either party ever seeing the other's keys.
You do. Keys live in a vault or secure module under your control. Your own vSAM, your integrator's, or a SAM in your controllers. They are held by you and escrowed to you, and are never ours to keep.
The encoding profile and the authorisation for that session. The keys stay where they are. No encoding point in the chain, including desk encoders, terminals and edge controllers, holds a key.
With a SAM or vSAM model, no. Rotating or revoking a key is one controlled act, and multiple key sets let you rotate without a second badge campaign. With keys held in the readers, rotation does mean touching every reader. Which is the main reason we prefer the module.
Yes. A tenant's own credential can be re-encoded at a landlord's reception with the landlord's read key, without either party ever seeing the other's keys.
You judge something that runs on your own site. Your access systems and readers stay where they are. If it earns its place, we extend it site by site.
One siteOne populationYour readers stay