---
title: Barracuda CloudGen Firewall
description: >-
  Barracuda CloudGen Firewall is an NGFW that protects networks and Internet
  traffic
breadcrumbs: Docs > Integrations > Barracuda CloudGen Firewall
---

# Barracuda CloudGen Firewall
Supported OS Integration version1.1.0   Barracuda CloudGen Firewall OverviewOther Event types of CloudGen FirewallSome more Event types of CloudGen Firewall
## Overview{% #overview %}

Barracuda CloudGen Firewall is a next-generation firewall (NGFW) family from Barracuda Networks designed to protect and optimize modern, distributed networks whether on-premises, in the cloud, or across hybrid environments. This integration monitors [cloudgen_firewall](https://www.barracuda.com/products/network-protection/cloudgen-firewall).

## Setup{% #setup %}

### Prerequisites{% #prerequisites %}

1. Administrative access to Barracuda CloudGen Firewall installed on your server.
1. The Datadog Agent installed and running (on a server or container that can receive syslog messages).
1. Network Access between the firewall and the Datadog Agent (usually port 514, but may be a custom value).
1. Syslog support enabled in the Datadog Agent (with a TCP or UDP listener configured).

### Validation{% #validation %}

1. Confirm the Datadog Agent is listening on the correct port (`514` in the following examples):

`sudo netstat -tunlp | grep 514`

If using TCP and UDP listeners, use the following command:

`sudo lsof -i :514`

1. Confirm logs are reaching the Agent from the correct log source:

`tail -f /var/log/datadog/syslog.log`

**Note**: If the file doesn't exist, verify that syslog logs are being written by your configuration.

1. Use the tcpdump command to confirm network traffic on the Datadog Agent host:

`sudo tcpdump -i any port 514`

After running this command, you should see traffic from the CloudGen Firewall IP address. If you don't see any such traffic, check the firewall rules between CloudGen and the Datadog Agent. Confirm the correct protocol (UDP or TCP) is being used on both sides.

### Configuration{% #configuration %}

1. Collecting logs is disabled by default in the Datadog Agent. Enable it in the `datadog.yaml` file with:

   ```yaml
     logs_enabled: true
   ```

1. Add this configuration block to your `cloudgen_firewall.d/conf.yaml` file to start collecting your cloudgen_firewall logs:

   ```yaml
     logs:
       - type: file
         path: /var/log/cloudgen_firewall.log
         source: barracuda_cloudgen_logs
         service: <SERVICE_NAME>
   ```

Change the `path` and `service` parameter values for your environment.

1. [Restart the Agent](https://docs.datadoghq.com/agent/guide/agent-commands.md#start-stop-and-restart-the-agent).

### Installation{% #installation %}

The cloudgen_firewall check is included in the [Datadog Agent](https://app.datadoghq.com/account/settings/agent/latest) package.

## Data collected{% #data-collected %}

### Metrics{% #metrics %}

The Barracuda CloudGen Firewall integration does not include any metrics.

### Logs{% #logs %}

The Barracuda CloudGen Firewall logs contain key information such as the event timestamp, source and destination IPs and ports, protocol used, firewall action (allow or deny), the matched rule name, user identity (if available), log type (such as firewall, VPN, authentication), network interface, device name, status of the operation, and many more. This helps you to monitor traffic behavior, access control, and system activity.

### Events{% #events %}

The cloudgen_firewall integration does not include any events.

## Troubleshooting{% #troubleshooting %}

Need help? Contact [Datadog support](https://docs.datadoghq.com/help/).