- 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 Meraki Cloud Collector
- Cisco Umbrella Cloud Collector
- Cloudflare Cloud Collector
- Cribl Cloud Collector
- CrowdStrike Cloud Collectors
- GCP Pub/Sub Cloud Collector
- Google Workspace Cloud Collector
- LastPass 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
- Mimecast 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
- Recorded Future Context Cloud Collector
- Rest API Cloud Collector
- Salesforce Cloud Collector
- SentinelOne Alerts Cloud Collector
- SentinelOne Cloud Funnel Cloud Collector
- SentinelOne Threats Cloud Collector
- SentinelOne Cloud Collector
- ServiceNow Cloud Collector
- Sophos Central Cloud Collector
- Splunk Cloud Collector
- STIX/TAXII Cloud Collector
- Symantec Endpoint Security Cloud Collector
- Trend Vision One Cloud Collector
- Vectra Cloud Collector
- Zscaler ZIA Cloud Collector
- Webhook Cloud Collectors
- Wiz Issues Cloud Collector
- Wiz API Cloud Collector
- Troubleshooting Cloud Collectors
Configure the STIX/TAXII Cloud Collector
Set up the STIX/TAXII Cloud Collector to continuously ingest threat intelligence data, such as threat detections and indicators of compromise, from any external source that supports the STIX/TAXII framework. You can choose to ingest threat intelligence data about either IP addresses or Domains that may be known to be malicious. As part of the process of configuring a STIX/TAXII collector, you can opt to automatically create a corresponding context table in the Context Manager application.
In the context table, the STIX/TAXII threat intelligence data is normalized so that it can be mapped to Exabeam target attributes based on a common information model. This model defines standardized objects for security content across Exabeam products. The mapped data is used to enrich security content that can be leveraged by downstream services such as Search, Correlation Rules, and Dashboards. For more information about the context table and mapped attributes, see STIX/TAXII Context Tables, in the Context Management Guide.
Use the following steps to set up the STIX/TAXII Cloud Collector.
Before you configure the STIX/TAXII Cloud Collector, ensure that you meet 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 STIX/TAXII.
Enter the following information for the cloud collector.
NAME – Specify a name for the STIX/TAXII Cloud Collector.
API ROOT URL – Enter the URL for the TAXII feed server from which the collector will ingest data.
COLLECTION – Enter an identifier for the specific collection on the TAXII server from which the collector will ingest data.
COLLECTION NAME – Optionally, enter the name of the collection on the TAXII server.
AUTHENTICATION TYPE – Select an authentication method for use during Discovery and Collection phases. Options include
Basic
orOAuth 2.0
.USERNAME – If you select the
Basic
authentication type, enter an authentication username.PASSWORD – Enter an authentication password.
INDICATOR TYPE – Select the type threat indicators you want to collect. Options include
Domain
orIP
.MAXIMUM AGE IN DAYS – Set a maximum age in days for the threat intelligence data. Avoid maintaining threat indicators for too long because aging data can be inaccurate and result in false positives.
AUTOMATICALLY CREATE A CONTEXT TABLE – Toggle this option on if you want to automatically generate a corresponding context table in the Context Management application. The context table will have the same name as the cloud collector. You can only connect one context table to one STIX/TAXII collector.
(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.
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.