- 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 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 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
- Vectra Cloud Collector
- Zscaler ZIA Cloud Collector
- Webhook Cloud Collectors
- Wiz Issues Cloud Collector
- Wiz API Cloud Collector
- Troubleshooting Cloud Collectors
Configure the Cloudflare Cloud Collector
Set up the Cloudflare Cloud Collector to continuously ingest events from the account based and zone based data sources that include Audit logs, HTTP requests, and Gateway DNS events.
Use the following steps to set up the Cloudflare Cloud Collector.
Before you configure the Cloudflare Cloud Collector, ensure that you complete the prerequisites.
Log in to the New-Scale Security Operations Platform with your registered credentials as an administrator.
Navigate to Collectors > Cloud Collectors.
Click New Collector.
Click Cloudflare.
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 format by default.
(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.
Click Install.
The message box displays the URL to which logs are sent.
Copy the URL containing authentication token by clicking the copy icon.
Record the URL for later use when you configure Cloudflare instance on the Cloudflare platform to forward logs to Exabeam.
Proceed to Configure Cloudflare to forward logs to Exabeam.
Configure Cloudflare instance to Forward Logs to Exabeam
Use the following steps to configure the Cloudflare Cloud Collector to receive data into the New-Scale Security Operations Platform.
Log in to the Cloudflare platform with your registered credentials as an administrator.
Navigate to Account > Analytics & Logs > Logpush.
To push the logs to the Cloudflare cloud collector, click Create a Logpush job.
Select the destination HTTP destination where you want to push the logs.
In the HTTP endpoint box, paste the URL containing authorization token that you obtained by configuring the Cloudflare cloud collector.
Click Continue.
Select the dataset that include account level logs: Gateway network, Access requests, Audit logs, Gateway HTTP, and Gateway DNS, and Zone level logs: HTTP request, Firewall events.
Configure a logpush job for the selected dataset.
Select the fields to be included in the log.
Click Submit.
The Logpush job that you created is listed on the Logpush page. The events that are generated for the selected dataset are pushed to the Cloudflare cloud collector. You can view the logs and volume on the Cloud Collectors Overview page.
If you want to monitor data separately for individual datasets or data sources, create multiple Cloudflare Cloud collector instances.