Skip to main content

CollectorsCloud Collectors Administration Guide

Configure the Netskope Alerts Cloud Collector

Set up the Netskope Alerts Cloud Collector to continuously ingest security alerts from Netskope REST API V2 endpoints. For more information see v2 REST API Scopes in the Netskope documentation.

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

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

  3. Navigate to Collectors > Cloud Collectors.

  4. Click New Collector.

    Netskope_Alerts_1.png

  5. Click Netskope Alerts.

  6. Enter the following information for the cloud collector.

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

    • API BASE URL – Enter the value for the API Base URL that you obtained while completing the prerequisites.

    • API TOKEN – Enter the value for the API token that you obtained while completing the prerequisites. For more information, see API Tokens in the Netskope documentation.

      Netskope_Alerts_2.png

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

    • REQUEST URL – In the Collect section, REQUEST URL displays the data export endpoint from which the Netskope Collector fetches security alerts. The URL considers multiple data sources that you define in the next Discovery - DATA SOURCES field.

    • DATA SOURCES – Add or delete the data sources supported by Netskope from which you want the collector to fetch alerts.

      Netskope_Alerts_4.png

      By default the following data sources supported by Netskope are prepopulated. You can modify this list to retain the data sources from which you want the collector to fetch security alerts.

      • /api/v2/events/dataexport/alerts/uba

      • /api/v2/events/dataexport/alerts/securityassessment

      • /api/v2/events/dataexport/alerts/quarantine

      • /api/v2/events/dataexport/alerts/remediation

      • /api/v2/events/dataexport/alerts/policy

      • /api/v2/events/dataexport/alerts/malware

      • /api/v2/events/dataexport/alerts/malsite

      • /api/v2/events/dataexport/alerts/compromisedcredential

      • /api/v2/events/dataexport/alerts/ctep

      • /api/v2/events/dataexport/alerts/dlp

      • /api/v2/events/dataexport/alerts/watchlist

  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. To confirm that the Exabeam Security Operations Platform communicates with the service, click Test Connection. 

  10. Click Install.

    AWS_S3_2.png

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