# Verkada EV3 on 3rd Party Wireless Locks

This article provides an overview of how Verkada EV3 credentials work with supported third-party wireless lock integrations. It also outlines the encryption key requirements and key security considerations to review before deployment.

***

### Supported wireless locks <a href="#h_ce4e193b08" id="h_ce4e193b08"></a>

* Assa Abloy Aperio locks
* Schlage:
  * AD series: AD300, AD400
  * NDEB, LE, LEB, and MT

### Before you begin <a href="#h_aa48fbf567" id="h_aa48fbf567"></a>

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 Partner. To begin this process, please contact your Account Executive.

***

### Security considerations <a href="#h_79c8de5d5d" id="h_79c8de5d5d"></a>

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 configurations containing these keys will be distributed to a broader group, including Solutions Engineers and Partners, and only one key is reserved per integration partner, they are inherently less secure than the encryption keys used on Verkada readers.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.verkada.com/access-control/installation/wiring-best-practices-for-third-party-wireless-locks/verkada-ev3-on-3rd-party-wireless-locks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.