This article explains how to use Verkada EV3 credentials with supported wireless lock integrations. It also highlights the security considerations and implications of integrating Verkada EV3 with these third-party integrations, to ensure you can make informed decisions before deployment.

To use Verkada EV3 credentials with third-party wireless lock integrations, encryption keys must be manually added to the locks that will utilize Verkada EV3 credentials. This process cannot be completed by the end user and must be performed by a Verkada Solutions Engineer or Verkada Partner. To begin this process, please contact your Account Executive.

With the DESFire EV3 smartcard technology, Verkada’s EV3 credentials can hold 16 encryption keys. To support EV3 on third-party wireless locks, one of these keys is reserved exclusively for use with locks manufactured by Allegion and its subsidiaries (including Schlage and SimonsVoss). Another is reserved exclusively for locks manufactured by Assa Abloy and its subsidiaries. These keys are completely segmented, to ensure that encryption keys used on Allegion or Assa Abloy locks are never used on wired Verkada readers and vice versa.

A digital configuration or a configuration card containing the Allegion or Assa Abloy encryption key is required to apply the encryption keys to these third-party locks. Because the configurations containing these keys will be distributed to a broader group, including Solutions Engineers and Partners, and only one key is reserved for each integration partner, they are inherently less secure than the encryption keys used on Verkada readers.

Need more help? Contact Verkada Support.