---
title: Cisco ASA
description: Gain insights into Cisco ASA logs
breadcrumbs: Docs > Integrations > Cisco ASA
---

# Cisco ASA
Supported OS Integration version1.0.0            Cisco ASA OverviewCisco ASA OverviewCisco ASA User ActivityCisco ASA User ActivityCisco ASA Firewall DetailsCisco ASA Firewall DetailsCisco ASA Network ActivityCisco ASA Threat Detection
## Overview{% #overview %}

[Cisco ASA](https://www.cisco.com/c/en_in/products/security/adaptive-security-appliance-asa-software/index.html) is a robust firewall platform that provides enterprise-class protection with high availability and scalable performance. It adapts to evolving security needs and supports dynamic routing for modern networks and data centers.

Integrate Cisco ASA with Datadog to gain insights into threat detection, user authentication, user authorization, user management, dynamic traffic insights, connection insights, ARP collision insights, application firewall, transparent firewall and identity firewall using pre-built dashboard visualizations. Datadog uses its built-in log pipelines to parse and enrich these logs, facilitating easy search and detailed insights. The integration can also be used for Cloud SIEM detection rules for enhanced monitoring and security.

**Disclaimer**: Your use of this integration, which may collect data that includes personal information, is subject to your agreements with Datadog. Cisco is not responsible for the privacy, security or integrity of any end-user information, including personal data, transmitted through your use of the integration.

## Setup{% #setup %}

### Configuration{% #configuration %}

#### Enable log collection{% #enable-log-collection %}

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

   ```yaml
   logs_enabled: true
   ```

1. Add this configuration block to your `cisco_asa.d/conf.yaml` file to start collecting your Cisco ASA logs.

   ```yaml
   logs:
    - type: tcp # or 'udp'
      port: <PORT>
      service: cisco-asa
      source: cisco-asa
   ```

See the sample [`cisco_asa.d/conf.yaml`](https://github.com/DataDog/integrations-core/blob/master/cisco_asa/datadog_checks/cisco_asa/data/conf.yaml.example) file for available configuration options.

**Note**: Do not change the `source` and `service` values, as these parameters are integral to the pipeline's operation.

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

#### Set syslog configuration from Cisco ASA CLI{% #set-syslog-configuration-from-cisco-asa-cli %}

1. Connect to the Cisco ASA CLI.

1. Enter privileged EXEC mode by running:

   ```shell
   enable
   ```

When prompted, enter the password.

1. Enable global configuration mode:

   ```shell
   configure terminal
   ```

1. Enable logging:

   ```shell
   logging enable
   ```

1. Configure syslog log forwarding:

Replace the placeholders with actual values:

   - **interface\_name**: interface that the syslog server is associated with
   - **ip\_address**: IP address of the syslog server
   - **port**: port where the syslog server is listening

For UDP:

   ```shell
   logging host <interface_name> <ip_address> udp/<port>
   ```

For TCP:

   ```shell
   logging host <interface_name> <ip_address> tcp/<port>
   ```

1. Set logging level to debugging:

   ```shell
   logging trap debugging
   ```

1. Enable RFC 5424 timestamp format:

   ```shell
   logging timestamp rfc5424
   ```

**Note**: The `port` value should be similar to the port provided in the `Log Collection` section.

### Validation{% #validation %}

[Run the Agent's status subcommand](https://docs.datadoghq.com/agent/guide/agent-commands/#agent-status-and-information) and look for `cisco_asa` under the Logs Agent section.

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

### Logs{% #logs %}

The Cisco ASA integration collects threat detection, user authentication, user authorization, user management, dynamic traffic insights, connection insights, ARP collision insights, application firewall, transparent firewall, and identity firewall logs.

### Metrics{% #metrics %}

The Cisco ASA does not include any metrics.

### Events{% #events %}

The Cisco ASA integration does not include any events.

## Troubleshooting{% #troubleshooting %}

**Permission denied while port binding:**

If you see a **Permission denied** error while port binding in the Agent logs, see the following instructions:

1. Binding to a port number under 1024 requires elevated permissions. Grant access to the port using the `setcap` command:

   1. Grant access to the port using the `setcap` command:

      ```shell
      sudo setcap CAP_NET_BIND_SERVICE=+ep /opt/datadog-agent/bin/agent/agent
      ```

   1. Verify the setup is correct by running the `getcap` command:

      ```shell
      sudo getcap /opt/datadog-agent/bin/agent/agent
      ```

With the expected output:

      ```shell
      /opt/datadog-agent/bin/agent/agent = cap_net_bind_service+ep
      ```

**Note**: Re-run this `setcap` command every time you upgrade the Agent.

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

**Data is not being collected:**

Make sure that traffic is bypassed from the configured port if the firewall is enabled.

**Port already in use:**

If you see the **Port <PORT\_NUMBER> Already in Use** error, see the following instructions. The example below is for a PORT_NUMBER equal to 514:

On systems using syslog, if the Agent listens for logs on port 514, the following error can appear in the Agent logs: `Can't start UDP forwarder on port 514: listen udp :514: bind: address already in use`.

This error occurs because by default, Syslog listens on port 514. To resolve this error, take **one** of the following steps:

- Disable syslog, or
- Configure the Agent to listen on a different, available port.

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