---
title: "Security: Overview"
description: "In the security section, we will review the security features in RavenDB and explain how to manage your secured server or cluster."
url: "https://docs.ravendb.net/6.2/server/security/overview"
version: "6.2"
---

# Security: Overview

> RavenDB publishes an official agent skill for coding assistants at https://docs.ravendb.net/skills/ravendb/SKILL.md (also installable with `npx skills add ravendb/skills`). The skill describes itself as: "Read this before writing any RavenDB query, client call or /databases/ request. Covers server setup, document modelling, the Node.js, .NET and Python clients, RQL, indexes, vector search and AI agents. Code written from recall tends to run and return the wrong rows, because RQL resembles SQL and the clients take field names as plain strings."

## Security: Overview

In the security section, we will review the security features in RavenDB and explain how to manage your secured server or cluster.

## Authentication

RavenDB uses X.509 certificate-based authentication.
X.509 certificates are standardized, secured and widely used in many applications. They allow you to use TLS/SSL and HTTPS which keeps your communications encrypted and secured.

The idea of authentication in RavenDB is based on a fact that the server holds a server certificate, which is either signed by a trusted SSL Certificate Authority or self-signed. The server certificate is used by an administrator to generate client certificates with assigned permissions. Client certificates can be used for authentication, and authorization is granted according to the assigned permissions.

> **Warning:** Important {#important}
>
> RavenDB **does not** use PKI infrastructure to trust certificates and uses a more strict approach. It will allow access to client certificates which are explicitly registered in the RavenDB server **or** certificates which have the same issuer and Public Key Pinning Hash as a certificate which is already trusted.
> Registering a certificate means one of the following:
>
> - The certificate was generated by the server
> - The certificate was registered explicitly by an administrator.
> - The certificate was registered implicitly for having the same [Public Key Pinning Hash](https://docs.ravendb.net/6.2/server/security/authentication/certificate-renewal-and-rotation.md#implicit-trust-by-public-key-pinning-hash) as a registered certificate.
>
> In any case, it must appear in the certificates view in Studio. Visit the [Certificate Management](https://docs.ravendb.net/6.2/server/security/authentication/certificate-management.md) section for more information.

In Studio, administrators can use the [Certificates View](https://docs.ravendb.net/6.2/server/security/authentication/certificate-configuration.md) to easily manage their certificates. It can be used to generate client certificates, register existing client certificates, import and export server certificates, rename, assign permissions and more.

**Read more:**

- [Manual Certificate Configuration](https://docs.ravendb.net/6.2/server/security/authentication/certificate-configuration.md)
- [Certificate Management](https://docs.ravendb.net/6.2/server/security/authentication/certificate-management.md)
- [Client Certificate Usage](https://docs.ravendb.net/6.2/server/security/authentication/client-certificate-usage.md)
- [Certificate Renewal & Rotation](https://docs.ravendb.net/6.2/server/security/authentication/certificate-renewal-and-rotation.md)
- [Let's Encrypt Certificates](https://docs.ravendb.net/6.2/server/security/authentication/lets-encrypt-certificates.md)
- [Common Errors & FAQ](https://docs.ravendb.net/6.2/server/security/common-errors-and-faq.md)

## Authorization

Authorization in RavenDB is based on the same X.509 certificates.

Every client certificate is associated with a security clearance and access permissions per database.

**Read more:**

- [Security Clearance & Permissions](https://docs.ravendb.net/6.2/server/security/authorization/security-clearance-and-permissions.md)

## Encryption

RavenDB offers full database encryption using [libsodium](https://download.libsodium.org/doc/), a well-known battle tested encryption library.

Encryption is implemented at the storage level, with XChaCha20-Poly1305 authenticated encryption using 256 bit keys.

When database encryption is on, all the features of a database are automatically encrypted - documents, indexes and every piece of data that is written to disk.

**Read more:**

- [Encryption at Rest](https://docs.ravendb.net/6.2/server/security/encryption/encryption-at-rest.md)
- [Database Encryption](https://docs.ravendb.net/6.2/server/security/encryption/database-encryption.md)
- [Server Store Encryption](https://docs.ravendb.net/6.2/server/security/encryption/server-store-encryption.md)
- [Secret Key Management](https://docs.ravendb.net/6.2/server/security/encryption/secret-key-management.md)
