- Connector Migration Overview
- Cloud Collectors Overview
- Navigate the Cloud Collectors UI
- Hybrid Deployment Experience
- Supported Regions for Cloud Collectors
- Access the Cloud Collectors Service
- New Cloud Collectors
- Apache Kafka Cloud Collector
- Armis Cloud Collector
- Armis Context Collector
- AWS Eventbridge Cloud Collector
- AWS Inspector Cloud Collector
- AWS Redshift Cloud Collector
- AWS Shield Cloud Collector
- Bindplane Cloud Collector
- Claude Enterprise Cloud Collector
- Egnyte Cloud Collector
- Cybereason Cloud Collector
- Google Alert Center Cloud Collector
- Google Workspace Context Cloud Collector
- OneLogin Cloud Collector
- Palo Alto Networks SaaS Security Cloud Collector
- Rest API Context Cloud Collector
- Symantec CloudSOC Cloud Collector
- Symantec Cloud Secure Web Gateway Cloud Collector
- Symantec Email Security Cloud Collector
- Troubleshooting Cloud Collectors
Configure the Bindplane Cloud Collector
Set up the Bindplane Cloud Collector to continuously ingest events from Bindplane Stream pipeline.
Before you configure the Bindplane 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 Bindplane Cloud Collector.
Specify a name for the Cloud Collector instance.
Click Install. A connection string is automatically generated and a confirmation message informs you that the new cloud collector is created. The connection string is displayed in a field on the success message and will need to be copied for use in Bindplane Stream.
In the success message, click Copy (
) to record the automatically generated connection string.You can use the connection string you recorded while configuring your Bindplane Stream product.
Contact Bindplane support for further configurations.
When your Exabeam destination in Bindplane Stream is fully configured, data collected via Bindplane begins to flow into Exabeam Bindplane Cloud Collector. To verify that data is being collected successfully, navigate to a downstream Exabeam service, like Search, and ensure that the collected data is available.
(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.
A cloud collector determines whether Daylight Saving Time (DST) is active based on the current date and automatically adjusts the time by adding or subtracting one hour, ensuring more accurate time reporting.