> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/verkada-cameras/configuration/camera-network-settings/configure-port-based-device-authentication-for-cameras.md).

# Configure Port-based Device Authentication for Cameras

Configure port-based authentication for Verkada cameras

Verkada cameras can be configured with port-based device authentication that utilizes IEEE 802.1x. This feature is designed to help organizations secure their network devices and maintain high security standards.

{% hint style="danger" %}
The [D30](https://docs.verkada.com/docs/video-security-d30-datasheet.pdf), [D40](https://docs.verkada.com/docs/video-security-d40-datasheet.pdf), [D50](https://docs.verkada.com/docs/video-security-d50-datasheet.pdf), and [D80](https://docs.verkada.com/docs/video-security-d80-datasheet_1.pdf) do not support port-based authentication.
{% endhint %}

### Before you begin

{% hint style="warning" %}
To configure port-based authentication on a camera, the camera must initially connect to Command and update to the latest firmware using DHCP. Once the camera’s update is complete, it will be able to receive device certificates uploaded to Command and enrolled for 802.1x.
{% endhint %}

***

## Configuration

{% hint style="danger" %}
Only Org Admins can enable or modify 802.1x configuration settings.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin .**
{% endstep %}

{% step %}
**In the left navigation, select Login & Access > Port-based Device Authentication.**
{% endstep %}

{% step %}
**In the top right, click Enroll.**

a. Select the cameras you want to configure.\
b. Click **Next.**\
c. Upload a CA certificate (`.crt`), camera certificate (`.crt`), and camera private key (`.key`).\
d. Click **Submit.**

<div align="left" data-with-frame="true"><img src="https://1795869993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FylYKicREo6JpuOJH4teK%2Fuploads%2Fgit-blob-4d4fe757ac257c9286d0e687e417fdce46a80f19%2F51560649e142945a761e09eff80e52a56f9794d4.png?alt=media" alt=""></div>
{% endstep %}

{% step %}
**(Optionally) Enter a Private Key Password and select the needed security standards. The selected certificates will be applied to all selected devices. Repeat this process for each group to upload different certificates to specific devices.**
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Uploading new certificates to cameras already enrolled in port-based device authentication will overwrite the existing certificates.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/verkada-cameras/configuration/camera-network-settings/configure-port-based-device-authentication-for-cameras.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
