If you want to send Cortex Xpanse notifications to a Syslog receiver, you can set up log forwarding to the receiver.
To send Cortex Xpanse notifications to your Syslog server, you need to first define the settings for the Syslog server.
Before you define the Syslog settings, enable access to the following Cortex Xpanse IP addresses for your deployment region in your firewall configurations:
Region
Log Forwarding IP Addresses
United States - Americas (US)
35.232.87.935.224.66.220
Germany (DE)
35.234.95.9635.246.192.146
Netherlands - Europe (EU)
34.90.202.18634.90.105.250
Canada (CA)
35.203.54.20435.203.52.255
United Kingdom (UK)
34.105.227.10534.105.149.197
Singapore (SG)
35.240.192.3734.87.125.227
Japan (JP)
34.84.88.18335.243.76.189
Australia (AU)
35.189.38.16734.87.219.39
United States - Government
104.198.222.18535.239.59.210
India (IN)
34.93.247.4134.93.183.131
Switzerland (CH)
34.65.228.95
34.65.74.83
Select → → → .
In Syslog Servers, add a + New Server.
Define the Syslog server parameters:
Unique name for the server profile.
Destination—IP address or fully qualified domain name (FQDN) of the Syslog server.
Port—The port number on which to send Syslog messages.
Choose one of the syslog standard values. The value maps to how your syslog server uses the facility field to manage messages. For details on the facility field, see RFC 5424.
Protocol—Select a method of communication with the Syslog server:
TCP—No validation is made on the connection with the Syslog server. However, if an error occurred with the domain used to make the connection, the Test connection will fail.
UDP—No error checking, error correction, or acknowledgment. No validation is done for the connection or when sending data.
TCP + SSL— Cortex Xpanse validates the syslog server certificate and uses the certificate signature and public key to encrypt the data sent over the connection.
Certificate—The communication between Cortex Xpanse and the Syslog destination can use TLS. In this case, upon connection, Cortex Xpanse validates that the Syslog receiver has a certificate signed by either a trusted root CA or a self-signed certificate. You may need to merge the Root and Intermediate certificate if you receive a certificate error when using a public certificate.
Note
Up to TLS 1.2 is supported.
If your Syslog receiver uses a self signed CA, Browse and upload your self-signed Syslog receiver CA.
Note
Make sure the self-signed CA includes your public key.
If you only use a trusted root CA leave the Certificate field empty.
Ignore Certificate Error— Cortex Xpanse does not recommend, but you can choose to select this option to ignore certificate errors if they occur. This will forward alerts and logs even if the certificate contains errors.
Test the parameters to ensure a valid connection and Create when ready.
You can define up to five Syslog servers. Upon success, the table displays the Syslog servers and their status.
(Optional) Manage your Syslog server connection.
In the Syslog Servers table
Locate your Syslog server and right-click to Send text message to test the connection.
Cortex Xpanse sends a message to the defined Syslog server which you can check to see if the test message indeed arrived.
If the message doesn’t arrive, Cortex Xpanse displays an error. View the error details and suggested solutions in Syslog Server Test Message Errors.
Locate the Status field.
The Status field displays a Valid or Invalid TCP connection. Cortex Xpanse tests connection with the Syslog server every 10min. If no connection is found after 1 hour, Cortex Xpanse send a notice to the notification center.
Note
If you find the Syslog data limited, Cortex Xpanse recommends running the Get Alert API for complete alert data.
Syslog Server Test Message Errors.
After you integrate with your Syslog receiver, you can configure your forwarding settings.