Strata Logging Service
Forward Logs to a Syslog Server
Table of Contents
Expand All
|
Collapse All
Forward Logs to a Syslog Server
Learn how to forward logs from
Strata Logging Service
to a
syslog server.Where Can I Use This? | What Do I Need? |
---|---|
|
|
To meet your long-term storage, reporting
and monitoring, or legal and compliance needs, you can configure
Strata Logging Service
to forward all logs or a subset of logs to a syslog
receiver. Strata Logging Service
can forward logs in multiple formats: CSV, LEEF, or CEF. For each
instance of Strata Logging Service
, you can forward logs to up to 200 syslog
destinations.If you are using the Palo Alto Networks
Splunk app, forward logs using HTTPS instead.
- (QRadar only) Add a log source in QRadar by using the TLS Syslog protocol.For details about how to do this, see the IBM documentation.
- Enable communication betweenStrata Logging Serviceand your syslog receiver.Ensure that your syslog receiver can connect toStrata Logging Serviceand can present a valid CA certificate to complete the connection request.
- Allow an inbound TLS feed to your syslog receiver from the IP address range that corresponds to your.Strata Logging Serviceregion
- 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.BecauseStrata Logging Servicevalidates the server certificate to establish a connection, you must verify that the receiver is configured to properly send the TLS certificate chain toStrata Logging Service. 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.
- Select theStrata Logging Serviceinstance that you want to configure for syslog forwarding.If you have multipleStrata Logging Serviceinstances, click theStrata Logging Servicetile and select an instance from the list of those available.If you are usingStrata Cloud Managerto manageStrata Logging Service, clickto manage log forwarding fromSettingsStrata Logging ServiceLog ForwardingStrata Logging Serviceinstance to an external server.
- 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) Upload a self-signed certificate if you do not want to use a publicly signed certificate.
- (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, self-signed certificate on your receiver, or the public CA is not in the list of trusted CAs. The file containing the certificates must be in PEM format.
- (Optional) Enable client authentication.Do this if company or regulatory policy requires client authentication when forwarding logs to your server.
- 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.
- Acknowledgeto reach out to your Palo Alto Networks team to enable log forwarding fromStrata Logging Servicein China to an external log server. Be aware that configuring log forwarding profiles to send logs to servers outside China can result in personally identifiable information leaving China.
- Test Connectionto ensure thatStrata Logging Servicecan communicate with the receiver.This checks TLS connectivity to verify that transmission is possible.If the test fails, you can not proceed.
- ClickNext.
- Specify theFormatin which you would like to forward your logs.The log format (CSV, LEEF, CEF, or JSON) that you should select depends on the destination of your log data.
- Specify theDelimiterthat you would like to separate the fields in your log messages. This option is disabled if you select JSON log format.
- (Optional) To receive aSTATUS NOTIFICATIONwhenStrata Logging Serviceis 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 at least once 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 thatStrata Logging Serviceinserts 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.
- (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.Log filters function like queries in Explore, with the following differences:
- No double quotes (“”).
- No subnet masks. To return IP addresses with subnets, use theLIKEoperator. Example: src_ip.value LIKE “192.1.1.%”.
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.For details about the log format, refer to the Syslog field descriptions (Select the PAN-OS Administrator’s Guide for your firewall version).
- (Optional) You can use the running Syslog forwarding profile to forward past logs spanning up to 3 days.
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
Strata Logging Service
.For example,
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.