Forward Logs from Cortex Data Lake to a Syslog Server
Learn how to forward logs from Cortex Data Lake to a syslog server.
To meet your long-term storage, reporting and monitoring, or legal and compliance needs, you can configure Cortex Data Lake to forward all logs or a subset of logs to a syslog receiver.
Cortex Data Lake can forward logs in multiple formats:
CSV, LEEF, or CEF. For each instance of Cortex Data Lake, you can forward logs to up to 200 syslog destinations.
Cortex Data Lake communicates with the receiver using TLS 1.2 and the default cipher suites that Java uses. Upon connection Cortex Data Lake validates that the receiver has a certificate signed by a trusted root CA or a private CA. To complete the TLS handshake and establish the connection, the receiver must present all the certificates from the chain of trust.
- Enable communication between Cortex Data Lake and your syslog receiver.Ensure that your syslog receiver can connect to Cortex Data Lake and can present a valid CA certificate to complete the connection request.
- Allow an inbound TLS feed to your syslog receiver from the following IP address ranges:United States - Americas126.96.36.199/28Netherlands - Europe188.8.131.52/28United Kingdom184.108.40.206/28DE (Germany)220.127.116.11/28IN (India)18.104.22.168/28SG (Singapore)22.214.171.124/28CA (Canada)126.96.36.199/28JP (Japan)188.8.131.52/28AU (Australia)184.108.40.206/28United States - Government220.127.116.11/28If you have allowed specific IP addresses for inbound traffic, you must also allow the above IP address ranges to forward logs to your syslog receiver.
- Obtain either a certificate from a well-known, public CA or a self-signed certificate and install it on your receiver. Please make sure that if you are using a certificate signed by a private CA, it contains CRL or OCSP information needed for certificate revocation checks.Because Cortex Data Lake validates the server certificate to establish a connection, you must verify that the receiver is configured to properly send the TLS certificate chain to Cortex Data Lake. If the app cannot verify that the certificate of the receiver and all CAs in the chain are trustworthy, the connection cannot be established. See the list of trusted certificates.
- Sign Into the hub at https://apps.paloaltonetworks.com/.
- Select the Cortex Data Lake instance that you want to configure for syslog forwarding.If you have multiple Cortex Data Lake instances, click the Cortex Data Lake tile and select an instance from the list of those available.
- Selectto add a new Syslog forwarding profile.Log ForwardingAdd
- Enter a descriptiveNamefor the profile.
- Enter theSyslog ServerIPv4 address or FQDN.Ensure that the value entered here matches the Subject Alternative Name (SAN) of the certificate installed on your syslog server.
- Enter thePorton which the syslog server is listening.The default port for syslog messages over TLS is 6514.
- Select theFacility.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 the IETF standard for the log format (CSV, LEEF, or CEF) that you will choose in the next step.
- (Optional) Enable client authentication.Do this if company or regulatory policy requires client authentication when forwarding logs to your server.
- Return to the main Log Forwarding page.
- Downloadthe certificate chain.
- Upload the certificate chain to your server.Refer to the documentation for your server management software to find out how to do this.
- (Optional)Uploadthe private Root CA and intermediate CAs (If an intermediate CA exists). Do not upload the certificate issued for the syslog server—only CA certificates are needed to verify the chain from the syslog server.Only do this if you installed a private CA-signed or self-signed certificate on your receiver. The file containing the certificates must be in PEM format.
- Test Connectionto ensure that Cortex Data Lake can communicate with the receiver.This checks TLS connectivity to verify that transmission is possible.If the test fails, you will not be able to proceed.
- Specify theFormatin which you would like to forward your logs.
- Specify theDelimiterthat you would like to separate the fields in your log messages.
- (Optional) To receive aSTATUS NOTIFICATIONwhen Cortex Data Lake is unable to connect to the syslog server, enter the email address at which you’d like to receive the notification.You will continue to receive these notifications every 60 minutes until connectivity is restored. If the connectivity issue is addressed within 72 hours, no logs will be lost. However, any log older than 72 hours following the service disconnection could be lost.
- (Optional) Enter aPROFILE TOKENto send logs to a cloud syslog receiver.If you use a third-party cloud-based syslog service, you can enter a token that Cortex Data Lake inserts into each syslog message so that the cloud syslog provider can identify the source of the logs.
- Follow your cloud syslog provider’s instructions for generating an identifying token.
- Enter theProfile Token.Tokens have a maximum length of 128 characters.
- Select the logs you want to forward.
- Adda new log filter.
- Select the log type.The Threat log type does not include URL logs or Data logs. If you wish to forward these log types, you must add them individually.
- (Optional)Create a log filter to forward only the logs that are most critical to you.You can either write your own queries from scratch or use the query builder. You can also select the query field to choose from among a set of common predefined queries.If you want to forward all logs of the type you selected, do not enter a query. Instead, proceed to the next step.
- Saveyour changes.
- Saveyour changes.
- Verify that theStatusof your Syslog forwarding profile isRunning( ).
- Verify that you can view logs on the syslog receiver.
When configuring event source mapping in your SIEM, be aware that the hostname value can change in the hostname field of the syslog message sent from Cortex Data Lake.
Oct 8 15:26:51 stream-logfwd20-602226222-10061338-i2hh-harness-r9kt logforwarder LEEF:2.0|Palo Alto Networks|Next Generation
might change to
Oct 8 15:26:51 stream-logfwd20-602226222-10061338-i2hh-harness-a7b1logforwarder LEEF:2.0|Palo Alto Networks|Next Generation
A change to your log forwarding configuration or a new feature/fix could change the hostname value and break event source mapping if you are using an exact match on the hostname.
If hostname exact matching is required by the SIEM, consider using a middle syslog host to rewrite the log forward to a static hostname so that changes to hostname values don't affect log source mappings.
Recommended For You
Recommended videos not found.