# Authentication Overview

Secure your Verkada Command organization with multiple authentication options. Choose the method that best fits your security requirements.

***

## Choose your authentication method

| Method                                                                                              | Best for                                          | Security level |
| --------------------------------------------------------------------------------------------------- | ------------------------------------------------- | -------------- |
| [Two-Factor Authentication](/command/security/authentication-overview/two-factor-authentication.md) | Quick security boost for password-based login     | Medium         |
| [Passkeys](/command/security/authentication-overview/passkeys-for-login.md)                         | Passwordless login using device biometrics        | High           |
| [Single Sign-On (SSO)](/command/security/identity-providers.md)                                     | Enterprise organizations using identity providers | High           |
| [Enterprise Controlled Encryption](/command/security/enterprise-controlled-encryption.md)           | Maximum security with customer-managed keys       | Maximum        |

{% hint style="info" %}
Verkada recommends enabling SSO with OIDC for the best balance of security and user experience.
{% endhint %}

***

## Authentication methods

By default, users use their email and password to log in. To enhance security, several additional login options are available.

### OpenID Connect (OIDC)

OIDC is an authentication protocol built on OAuth 2.0 that enables secure user identity verification. It allows applications to authenticate users through a trusted identity provider (IdP) without storing credentials. OIDC enhances security by providing standardized identity tokens, enabling single sign-on (SSO) and seamless platform integration.

{% hint style="info" %}
Verkada recommends enabling OIDC instead of SAML when available.
{% endhint %}

### SAML/OAuth

SAML allows you to log in using a third-party authenticating service, such as Okta, Microsoft Entra ID, Google Workspace, or OneLogin. This method provides a single point of management for authentication across multiple applications.

Verkada Command is compatible with any SAML 2.0 provider. Learn more about setting up [identity providers](/command/security/identity-providers.md).

### 2-Factor Authentication

2-Factor Authentication (2FA) requires you to retrieve a code via SMS or through an authenticator app to log in. See [Two-Factor Authentication](/command/security/authentication-overview/two-factor-authentication.md) for detailed setup instructions.

***

## Provisioning

### SCIM

If you have a large number of users, you may opt to use System for Cross-Domain Identity Management (SCIM) to automatically provision and manage users. This is particularly advantageous if your company uses [Microsoft Entra ID](/command/security/identity-providers/microsoft-entra-id.md) or [Okta](/command/security/identity-providers/okta.md) as your Identity Provider.

SCIM allows you to sync users and groups between Verkada Command and your IdP, where you can easily add, remove, or modify multiple users and groups simultaneously.

See the [Identity Providers](/command/security/identity-providers.md) section for detailed SCIM setup instructions.

***

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=VXlMhHfLwoI).
{% endhint %}


---

# 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/command/security/authentication-overview.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.