# Exabeam (LogRhythm)

### Overview

Keeper supports event streaming into Exabeam (formerly LogRhythm) deployments. External logging is real-time, and new events will appear almost immediately. Setup instructions are below.

<figure><img src="https://4290574019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LO5CAzpxoaEquZJBpYz%2Fuploads%2FbhyAZ2ahtKYycj4wCtK8%2FScreenshot%202025-01-18%20at%203.50.23%E2%80%AFPM.png?alt=media&#x26;token=d260e5d3-3f9d-4523-9a3f-2a7d63272b83" alt=""><figcaption></figcaption></figure>

Exabeam uses a standard "Syslog" push capability over TCP.

**Ports**\
TCP Ports 514 and 6514 (TLS)

**Fields Exported**\
"audit\_event", "username", "client\_version", "remote\_address", "channel", "result\_code", "email", "to\_username", "client\_version\_new","username\_new", "file\_format", "record\_uid", "folder\_uid", "folder\_type", "shared\_folder\_uid", "attachment\_id", "team\_uid", "role\_id"

**Payload Format**\
Pipe-delimited, e.g. "audit\_event=login|username=<bob@foo.com>|..."

{% hint style="info" %}
Important: Ensure that the endpoint is using a valid signed SSL certificate that has a domain matching the subject name in the certificate. The certificate must also include the full certificate chain from your CA. Keeper's systems will refuse to connect to a self-signed certificate.\
\
Also, ensure that your Exabeam server allows traffic from Keeper servers. See [Firewall Configuration](https://docs.keeper.io/en/enterprise-guide/event-reporting/firewall) page.
{% endhint %}