> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/event-reporting/syslog.md).

# Syslog

Integrating Keeper SIEM push to standard Syslog endpoints

### Overview

Keeper supports event streaming into standard TCP Syslog collectors. External logging is real-time, and new events will appear within a few minutes. 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%2Fr5KwEB3F3wkhn77fx2tI%2Fimage.png?alt=media&#x26;token=cf7aa80a-d161-4140-a6dd-eb3768879976" alt=""><figcaption><p>Syslog Push Integration Settings</p></figcaption></figure>

Keeper supports 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"

**Example Payload**

{% code overflow="wrap" %}

```
<165>1 2022-10-13T21:05:51.996Z keepersecurity.com keeper - - - {"record_uid":"XXX","audit_event":"fast_fill","remote_address":"12.34.56.78","category":"usage","client_version":"Browser Extensions.16.4.7","username":"user@company.com","enterprise_id":123456}
```

{% endcode %}

{% 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 syslog server allows traffic from Keeper servers. See [Firewall Configuration](/enterprise-guide/event-reporting/firewall.md) page.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/enterprise-guide/event-reporting/syslog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
