- 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 Umbrella Cloud Collector
- Cribl Cloud Collector
- CrowdStrike Cloud Collectors
- GCP Pub/Sub 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
- 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
- Salesforce Cloud Collector
- SentinelOne Alerts Cloud Collector
- SentinelOne Cloud Funnel Cloud Collector
- SentinelOne Threats Cloud Collector
- SentinelOne Cloud Collector
- Splunk Cloud Collector
- Symantec Endpoint Security Cloud Collector
- Trend Vision One Cloud Collector
- Zscaler ZIA Cloud Collector
- Webhook Cloud Collectors
- Wiz Issues Cloud Collector
- Wiz API Cloud Collector
- Troubleshooting Cloud Collectors
Cribl Cloud Collector
The Cribl cloud collector streamlines the ingestion of logs from Cribl Stream (release 4.3.1 or later) into the Exabeam Security Operations Platform so those logs can be used in downstream Exabeam processes.
Note
Parsing of data collected from Cribl is only supported for New Scale Search and Advanced Analytics i63 or later.
Previously, Cribl logs could only be ingested by configuring a generic Webhook cloud collector. This new Cribl-dedicated cloud collector provides improved scalability and stability while processing Cribl logs and it also allows logs to be reprocessed.
The Cribl cloud collector relies on an Exabeam Google Cloud Storage (GCS) bucket behind the scenes. When you create a new Cribl cloud collector, the provisioning of the GCS bucket is handled automatically and you are presented with the authentication keys and other information necessary to configure an Exabeam destination in your Cribl Stream pipeline.
After you have completed the configuration procedure in Cribl Stream, Cribl data begins flowing into the Exabeam GCS bucket. From the GCS bucket the data is pushed to the Cribl Cloud Collector in your Cloud Collectors service and becomes available for use in downstream processes.
Onboarding a Cribl cloud collector requires completing tasks in both the Exabeam Cloud Collectors service and in Cribl Stream (release 4.3.1 or later):
Create a Cribl cloud collector in the Exabeam Cloud Collectors service.
Configure an Exabeam destination in Cribl Stream. See the Exabeam section in the Cribl Destinations documentation.
To determine if any specific log configuration is necessary, see Scenarios that Require Specific Configurations.
Note
If you previously used the Generic Webhook Cloud Collector, migrate to the Cribl Cloud Collector.