- Connector Migration Overview
- Cloud Collectors Overview
- Navigate the Cloud Collectors UI
- Which Collector to Use?
- Hybrid Deployment Experience
- Supported Regions for Cloud Collectors
- Access the Cloud Collectors Service
- Set up a New Cloud Connectors Instance
- 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
- 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 Apache Kafka Cloud Collector
Set up the Apache Kafka Cloud Collector to continuously collect security events from Kafka topics for log management for real-time streaming analytics and instant alert generation.
Before you configure the Apache Kafka 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 Apache Kafka Cloud Collector.
Enter the following information for the cloud collector.
NAME – Specify a name for the Cloud Collector instance.
KAFKA BOOTSTRAP SERVER – Enter <broker-fqdn>: <port> of the of the bootstrap server (or servers). The bootstrap server is the host name. The port is the port of the Kafka listener that uses SASL_SSL with SCRAM-SHA-512. For example, <boker-fqdn>: 9094.
KAFKA TOPIC – Enter the kafka topic name.
SCRAM USERNAME – Enter the username that is used for SASL authentication.
SCRAM PASSWORD – Enter the SCRAM password that is used for SASL authentication.
CERTIFICATE – Enter content from certificate of the certificate authority (CA) that signed your broker certificates, in PEM format.
ADDIITONAL PROPERTIES (Optional) – Enter Kafka consumer properties in Java properties format. The format must be one key=value per line. The JSON format is not supported. The consumer configuration properties group.id, and enable.auto.commit are managed by the cloud collector and cannot be modified.
(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.
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.