Syslog
Syslog connections to the CipherTrust Manager can be configured using the following:
Note
CipherTrust Manager can have a total of 64 log forwarder connections. Each Elasticsearch, Loki, and Syslog connection is counted towards the 64 connection total.
Managing Syslog Connections using GUI
Host: IP address or hostname of the Syslog server.
Port: port number for connecting to the Syslog server.
Transport Format: select the transport mode for sending data. The TLS mode requires a trusted CA certificate in the PEM format.
Note
If you set the transport format to UDP, log messages are limited to a size of 1024 bytes. After this size, the log message is truncated.
CA Cert: either upload the CA certificate or paste the certificate content. Make sure the server certificate contains the valid IP SANs.
Upload CSR: select and click Upload CSR to upload the trusted CA certificate from your machine.
Text: select and paste the certificate content in the text field.
Message Format: select the log message format.
Click Test Credentials to check whether the connection is configured correctly. If the test is successful, the status is OK
else the status is Fail
.
Click Next to move to the Add Products screen of the Add Connection wizard.
Managing Syslog Connections using ksctl
The following operations can be performed:
Create/Get/Update/Delete a Syslog connection
List all Syslog connections
Test an existing Syslog connection
Test the new Syslog connection parameters before establishing the connection
Note
The host
, port
, and transport
are the mandatory parameters for Syslog connections. The supported transport
modes for sending data are tls
, tcp
, and udp
. The tls
mode requires a trusted CA certificate in the PEM format.
Note
In a multi-node clustered environment, the Syslog connections configuration is synchronized. Each node is aware of all the Syslog servers and Syslog messages are sent from the currently active node. This implies, that if an event that results in an audit record is performed on node 1, the Syslog message will originate from node 1. Similarly, if an audit event is conducted on node 2, the Syslog message will originate from node 2.
Log Message Formats
The supported message formats for Syslog are:
rfc5424 (default)
rfc3164
cef
leef
Examples
rfc5424 (plaintext)
rfc3164
cef
leef
Creating a Syslog Connection
To create a Syslog connection, run:
Syntax
The supported transport
mode for sending data are tls
, tcp
, and udp
. The tls
mode requires a trusted CA certificate in the PEM format. In udp
mode, log messages are limited to a size of 1024 bytes. After this size, the log message is truncated.
Example Request
Example Response
Getting Details of a Syslog Connection
To get details of a Syslog connection, run:
Syntax
Example Request
Example Response
Updating a Syslog Connection
To update a Syslog connection, run:
Syntax
The supported transport
mode for sending data are tls
, tcp
, and udp
. The tls
mode requires a trusted CA certificate in the PEM format.
Example Request
Example Response
Deleting a Syslog Connection
To delete a Syslog connection, run:
Syntax
Example Request
Example Response
There will be no response if the Syslog connection is deleted successfully.
Getting List of Syslog Connections
To list all the Syslog connections, run:
Syntax
Example Request
Example Response
Testing an Existing Syslog Connection
To test an existing Syslog connection, run:
Syntax
Example Request
Example Response
Testing a New Syslog Connection
To test the parameters of a New Syslog connection, run:
Syntax
Example Request
Example Response