---
title: "HashiCorp Vault"
slug: "hashicorp-vault"
updated: 2025-12-10T15:47:17Z
published: 2025-12-10T15:47:17Z
canonical: "docs.databee.buzz/hashicorp-vault"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt
> Use this file to discover all available pages before exploring further.

# HashiCorp Vault

HashiCorp Vault provides organizations with identity-based security to automatically authenticate and authorize access to secrets and other sensitive data. For detailed information refer to the [HashiCorp Vault’s official documentation](https://developer.hashicorp.com/vault).

**Integration Method:** Data collector

**Tables**: API Activity (6003)

This integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| Audit | This event records the details of every request received and response sent by the Vault API |

This integration supports the following versions.

| HashiCorp ault API version | v1.0 |
| --- | --- |

## Prerequisites

- The user should have access to the HashiCorp Vault portal with an account that has the Global Administrator privileges.
- The user should have root access to the VM hosting the HashiCorp Vault application.
- The user should have access to the DataBee console.

## Configuration Overview

1. [Configure the HashiCorp](/user-manual/docs/hashicorp-vault#hashicorp-vault-configuration) Vault.
2. [Configure Data Collector](/user-manual/docs/hashicorp-vault#data-collector-configuration) on DataBee console.
3. Add the [HashiCorp Vault Feed](/user-manual/docs/hashicorp-vault#databee-configuration) integration the DataBee console.

## Data Collector Configuration

To receive logs from HashiCorp Vault, a Data Collector must be installed and configured. The data collector will receive logs forwarded from HashiCorp Vault and send them back to DataBee. For more information, refer to the [DataBee website](https://docs.databee.buzz/docs/data-collector#configure-data-collector-in-databee).

## HashiCorp Vault Configuration

1. Login to the VM where the HashiCorp Vault instance is hosted
2. Enter the following commands

> [!NOTE]
> **Note:**
> 
> After running the “vault audit list” command you should be able to see Syslog enabled in the list as shown in the screenshot below.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/hashicorp-vault-image-yml9fh2z.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A30Z&se=2026-10-30T12%3A35%3A30Z&sr=c&sp=r&sig=jwPkyqdeLxG7Bcfq4HiVrdroLqyBPbV2N2EU3T4ic2Q%3D)
  1. vault audit enable syslog tag="vault" log_level="info"
  2. vault audit list
  3. edit /etc/rsyslog.d/30-vault.conf
3. In the 30-vault.conf file, setup the following configuration, replace <public_ip> and <port> with your respective public ips and ports of syslog server. The syslog server is used to demultiplex logs for the data collector. Refer to [this article](/user-manual/docs/demultiplexing-logs-for-data-collector) for more details. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/hashicorp-vault-image-24qrdi4p.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A30Z&se=2026-10-30T12%3A35%3A30Z&sr=c&sp=r&sig=jwPkyqdeLxG7Bcfq4HiVrdroLqyBPbV2N2EU3T4ic2Q%3D)

For more information visit the [official syslog documentation](https://developer.hashicorp.com/vault/docs/audit/syslog).

## DataBee Configuration

1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/hashicorp-vault-image-wcdoil42.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A30Z&se=2026-10-30T12%3A35%3A30Z&sr=c&sp=r&sig=jwPkyqdeLxG7Bcfq4HiVrdroLqyBPbV2N2EU3T4ic2Q%3D)
2. Search for the **HashiCorp Vault** and click on it as shown below.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/hashicorp-vault-image-2xblqtzo.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A30Z&se=2026-10-30T12%3A35%3A30Z&sr=c&sp=r&sig=jwPkyqdeLxG7Bcfq4HiVrdroLqyBPbV2N2EU3T4ic2Q%3D)
3. Click on the **Data Collector** option for the collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/hashicorp-vault-image-8xtiirjg.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A30Z&se=2026-10-30T12%3A35%3A30Z&sr=c&sp=r&sig=jwPkyqdeLxG7Bcfq4HiVrdroLqyBPbV2N2EU3T4ic2Q%3D)
4. Click on the **Syslog** option for the polling mechanism. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/hashicorp-vault-image-qewxk6dz.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A30Z&se=2026-10-30T12%3A35%3A30Z&sr=c&sp=r&sig=jwPkyqdeLxG7Bcfq4HiVrdroLqyBPbV2N2EU3T4ic2Q%3D)
5. Enter feed contact information, select the collector which we’ve created previously and in the configuration page, confirm the following then click on the **Submit** button, and a new data source will be created.
  - **Format**: syslog-rfc5424
  - **Mode**: TCP
  - **PORT**: the listening TCP/UDP port used for receiving syslog data. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/hashicorp-vault-image-i01qgdc1.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A30Z&se=2026-10-30T12%3A35%3A30Z&sr=c&sp=r&sig=jwPkyqdeLxG7Bcfq4HiVrdroLqyBPbV2N2EU3T4ic2Q%3D)

## Troubleshooting Tips

- Ensure that you’re accessing the VM with a root user.
- Ensure that all the commands mentioned earlier are executed properly in the VM.
- Ensure that Data collector and port are mentioned correctly in configuration page.

#