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 almost immediately. Setup instructions are below.
![](https://docs.keeper.io/~gitbook/image?url=https%3A%2F%2F4290574019-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F-LO5CAzpxoaEquZJBpYz%252Fuploads%252Fr5KwEB3F3wkhn77fx2tI%252Fimage.png%3Falt%3Dmedia%26token%3Dcf7aa80a-d161-4140-a6dd-eb3768879976&width=768&dpr=4&quality=100&sign=a73bccb9&sv=1)
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
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 page.
Last updated