Forward Logs from

Cortex Data Lake

to an HTTPS Server

Sign In
to the hub.
Select the
Cortex Data Lake
instance that you want to configure for HTTPS 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.
Select
Log Forwarding
Add
to add a new HTTPS forwarding profile.

Enter a descriptive
Name
for the profile.
Enter the
URL
that you copied in step 13 for the HTTPS receiver.
The URL entered must begin with
https
. At the end of the top-level domain, you can specify a port number. The default port is 443.
For Splunk HEC, ensure that the URL ends with
/event
.
If you're forwarding logs to Google Chronicle, you must enter the URL that corresponds to your
Cortex Data Lake
region:
US	https://malachiteingestion-pa.googleapis.com/v2/unstructuredlogentries:batchCreate
EU	https://europe-malachiteingestion-pa.googleapis.com/v2/unstructuredlogentries:batchCreate
Asia	https://asia-southeast1-malachiteingestion-pa.googleapis.com/v2/unstructuredlogentries:batchCreate

(
Optional
) Upload a self-signed certificate if you do not want to use a publicly signed certificate.
(
Optional
)
Upload
the private Root CA and intermediate CAs (If an intermediate CA exists). Do not upload the certificate issued for the https server—only CA certificates are needed to verify the chain from the https 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.
Download
the 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.
Configure Client Authorization.
Do this if you're forwarding logs to a cloud HTTPS receiver, or if your HTTPS server requires a username and password.
Select the

Type

of client authorization and enter the necessary credentials.

HTTPS Receiver	Type	Credentials
Splunk HEC	Splunk Authorization	HEC Token
HTTPS Server (Password-protected)	Basic Authorization	Username Password
Exabeam	Exabeam Authorization	Access Token
Microsoft Sentinel	Sentinel Authorization	Workspace ID Primary Key Find your workspace ID and key
Google Chronicle	Chronicle Authorization	Customer ID Service Account This should be a properly formatted JSON document. If you don’t know your Service Account credentials, contact Google Chronicle support.
HTTPS Server	None	None
Test Connection
to ensure that
Cortex Data Lake
can communicate with the receiver.
This sends an empty log to the configured destination to verify that transmission is possible.
If the test fails, you won't be able to proceed.
Click
Next
.
(
Optional
) To receive a
STATUS NOTIFICATION
when
Cortex Data Lake
is unable to connect to the HTTPS receiver, enter the email address at which you’d like to receive the notification.
You will continue to receive these notifications every 60 minutes until the service restores connectivity. If the connectivity issue resolves within 72 hours, the service won't lose logs. However, the service could lose any log older than 72 hours following the service disconnection.
Enter a unique PROFILE TOKEN if your receiver needs to distinguish logs coming from different tenants.
Select the logs you want to forward.
Add
a 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.
Log filters function like queries in Explore, with the following differences:
No double quotes (
“”
).
No subnet masks. To return IP addresses with subnets, use the
LIKE
operator. Example:
src_ip.value LIKE “192.1.1.%”
.
If you want to forward all logs of the type you selected, don't enter a query. Instead, proceed to the next step.
Save
your changes.
Save
your changes.
Verify that the
Status
of your HTTPS forwarding profile is
Running
( ).
Immediately after creating or editing your profile, the
Status
might be
Provisioning
for up to 10 minutes.
Verify that you can view logs on the HTTPS receiver.
For Splunk Common Information Model (CIM) fields and Enterprise Security, follow the guide at https://splunk.paloaltonetworks.com to install the Palo Alto Networks Splunk add-on and create a Splunk HEC input.
(
Optional
) You can use the running HTTPS forwarding profile to forward past logs spanning up to 3 days.