- Cloud Collectors Overview
- Administration
- Administrative Access
- Shareable Service Accounts
- Add Accounts for AWS Cloud Collectors
- Add Accounts for Cisco Duo Cloud Collector
- Add Accounts for Google Cloud Collectors
- Add Accounts for Microsoft Cloud Collectors
- Add Accounts for Okta Cloud Collectors
- Add Accounts for Salesforce Cloud Collectors
- Add Accounts for Splunk Cloud Collectors
- Add Accounts for Trend Micro Cloud Collectors
- Add Accounts for Wiz
- Define a Unique Site Name
- Sign Up for the Early Access Program
- Onboard Cloud Collectors
- Abnormal Security Cloud Collector
- AWS CloudTrail Cloud Collectors
- AWS CloudWatch Cloud Collector
- AWS CloudWatch Alarms Cloud Collector
- AWS S3 Cloud Collector
- AWS SQS Cloud Collector
- Azure Activity Logs Cloud Collector
- Azure Log Analytics Cloud Collector
- Azure Event Hub Cloud Collector
- Azure Storage Analytics Cloud Collector
- Box Cloud Collector
- Cato Networks Cloud Collector
- Cisco Duo Cloud Collector
- Cisco Meraki Cloud Collector
- Cisco Secure Endpoint Cloud Collector
- Cisco Umbrella Cloud Collector
- Cloudflare Cloud Collector
- Cribl Cloud Collector
- CrowdStrike Cloud Collectors
- GCP Pub/Sub Cloud Collector
- Google Workspace Cloud Collector
- LastPass Cloud Collector
- Microsoft Defender XDR (via Azure Event Hub) Cloud Collector
- Microsoft Entra ID Context Cloud Collector
- Microsoft Entra ID Logs Cloud Collector
- Microsoft 365 Exchange Admin Reports Cloud Collector
- Supported Sources from Microsoft 365 Exchange Admin Reports
- Migrate to the Microsoft 365 Exchange Admin Reports Cloud Collector
- Prerequisites to Configure the Microsoft 365 Exchange Admin Reports Cloud Collector
- Configure the Microsoft 365 Exchange Admin Reports Cloud Collector
- Troubleshooting the Microsoft 365 Exchange Admin Reports Cloud Collector
- Microsoft 365 Management Activity Cloud Collector
- Microsoft Security Alerts Cloud Collector
- Microsoft Sentinel (via Event Hub) Cloud Collector
- Mimecast Cloud Collector
- Netskope Alerts Cloud Collector
- Netskope Events Cloud Collector
- Okta Cloud Collector
- Okta Context Cloud Collector
- Palo Alto Networks Cortex Data Lake Cloud Collector
- Proofpoint On-Demand Cloud Collector
- Proofpoint Targeted Attack Protection Cloud Collector
- Recorded Future Cloud Collector
- Recorded Future Context Cloud Collector
- Rest API Cloud Collector
- Salesforce Cloud Collector
- SentinelOne Alerts Cloud Collector
- SentinelOne Cloud Funnel Cloud Collector
- SentinelOne Threats Cloud Collector
- SentinelOne Cloud Collector
- ServiceNow Cloud Collector
- Sophos Central Cloud Collector
- Splunk Cloud Collector
- STIX/TAXII Cloud Collector
- Symantec Endpoint Security Cloud Collector
- Trend Vision One Cloud Collector
- Trellix Endpoint Security Cloud Collector
- Vectra Cloud Collector
- Zscaler ZIA Cloud Collector
- Webhook Cloud Collectors
- Wiz Issues Cloud Collector
- Wiz API Cloud Collector
- Troubleshooting Cloud Collectors
Configure the Palo Alto Networks Cortex Data Lake Cloud Collector
Palo Alto Networks Cortex Data Lake collects and stores the network logs generated by security products, including next-generation firewalls, Prisma Access, and Cortex XDR. Configure Palo Alto Networks Cortex Data Lake to forward logs to New-Scale Security Operations Platform to ingest firewall data for monitoring network activities, and for long-term storage, reporting, or legal and compliance requirements.
To set up the Cloud Collector to ingest data from Palo Alto Networks Cortex Data Lake:
Obtain the authentication token and URL to use a token-based authentication model
Configure Palo Alto Networks Cortex Data Lake to forward HTTPS logs to Exabeam
Obtain the Authentication Token and URL
Log in to the New-Scale Security Operations Platform with your registered credentials as an administrator.
Click New Collector.
Click Palo Alto Networks Cortex Data Lake.
Enter the following information for the cloud collector:
Name – Specify a name for the Cloud Collector instance.
Format – The format for receiving data is set to JSON by default. The default format cannot be modified.
The New-Scale Security Operations Platform accepts and parses the JSON Array log format in which PAN Cortex Data Lake forwards logs.
(Optional) SITE – Select an existing site or to create a new site with a unique ID, click manage your sites. Adding a site name helps you to ensure efficient management of environments with overlapping IP addresses.
By entering a site name, you associate the logs with a specific independent site. A sitename metadata field is automatically added to all the events that are going to be ingested via this collector. For more information about Site Management, see Define a Unique Site Name.
(Optional) TIMEZONE – Select a time zone applicable to you for accurate detections and event monitoring.
By entering a time zone, you override the default log time zone. A timezone metadata field is automatically added to all events ingested through this collector.
To confirm that the New-Scale Security Operations Platform communicates with the service, click Test Connection.
Click Install.
A confirmation message informs you that the new Cloud Collector is created. The message box also displays the authentication token and the URL to which logs are sent.
Copy the Authentication Token by clicking the copy icon. Record the token for later use when you configure Palo Alto Networks Cortex Data Lake Cloud Collector on the Palo Alto Networks Cortex Data Lake platform.
To view the cloud collector summary, click Go to Overview. If you want to add more cloud collector instances, click Add more collectors.
The Overview tab displays the Palo Alto Networks Cortex Data Lake Cloud Collector instance that you installed.
Configure Palo Alto Networks Cortex Data Lake to Forward HTTPS Logs to Exabeam
To configure the Palo Alto Networks Cortex Data Lake to receive data into the New-Scale Security Operations Platform, on the Palo Alto Networks Cortex Data Lake portal, follow the steps mentioned in the Forward Logs from Cortex Data Lake to an HTTPS Server section in the Palo Alto Networks Cortex Data Lake documentation.
Note
The Exabeam certificate is trusted by Palo Alto Networks to establish communication between Cortex Data Lake and Exabeam. Hence, do not configure TLS server certificates.