Skip to main content

CollectorsCloud Collectors Administration Guide

Configure Slack Cloud Collector

Set up the Slack Cloud Collector to continuously ingest events from the Audit Logs API endpoints.

  1. Before you configure the Slack Cloud Collector, ensure that you complete the prerequisites.

  2. Log in to the New-Scale Security Operations Platform with your registered credentials as an administrator.

  3. Navigate to Collectors > Cloud Collectors.

  4. Click New Collector.

  5. Click Slack.

  6. Enter the following information for the cloud collector.

    • NAME – Specify a name for the Cloud Collector instance.

    • CLIENT ID – Enter the value for the client ID that you obtained while completing the prerequisites.

    • CLIENT SECRET – Enter the value for the client secret that you obtained while completing the prerequisites.

    • Click to authorize – Click to log in to the Slack account that you used to create the Slack app and click Authenticate.

      Note

      The Slack administrator must authenticate the connection request by entering the username and password to give required permission to the Exabeam Cloud Collector.

    • DATA SOURCES – Select the data source Audit Logs for the collector to fetch the audit log related data.

    • INGEST FROM – Select the time and date from which the collector must start ingesting events. If you leave this field blank and do not provide a threshold, all logs are ingested.

  7. (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.

  8. (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.

    Timezone_sitename_site_management_1.png

  9. Click Install.

    AWS_S3_2.png

    A confirmation message informs you that the new Cloud Collector is created.