- 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. In the Context Management service, you can set up a corresponding context table to store the data.
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 sections to find information about setting up a STIX/TAXII Cloud Collector:
Commonly Used STIX/TAXII Vendors – Provides information necessary to set up some of the most commonly used STIX/TAXII vendors.
Configuration Procedure – Provides step-by-step instructions for configuring a STIX/TAXII cloud collector.
Commonly Used STIX/TAXII Vendors
The chart below provides information about supported authorization methods, necessary credentials, and recommendations to create cloud collectors that ingest data from some of the most widely used STIX/TAXII vendors.
Vendor | Supported Authorization Methods | Discovery URLs | Recommendations |
---|---|---|---|
Anomali | Basic | Auto Discovery URL: https://optic.threatstream.com/taxii2/ Manual API Root URLs: https://api.threatstream.com/api/v1/taxii21/feeds/collections/ https://api.threatstream.com/api/v1/taxii21/trusted_circles/collections/ https://api.threatstream.com/api/v1/taxii21/search_filters/collections/ | In Anomali, create a custom search filter with aging and confidence filters. |
AlienVault | Basic | Auto Discovery URL: https://otx.alienvault.com/taxii/ Manual API Root URL: https://otx.alienvault.com/taxii/root/collections/ | |
PAN Feed Unit 42 | Basic | Auto Discovery URL: https://stix2.unit42.org/taxii/ Manual API Root URLs: https://stix2.unit42.org/playbooks/collections/ https://stix2.unit42.org/reports/collections/ | |
PulseDive | Basic | Auto Discovery URL: https://pulsedive.com/taxii2/ Manual API Root URL: https://pulsedive.com/taxii2/api/collections/ | |
Recorded Future | Basic | Auto Discovery URL: https://api.recordedfuture.com/taxii2/ Manual API Root URL: https://api.recordedfuture.com/taxii2/default/collections/ |
Configuration Procedure
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.
COLLECTION DISCOVERY TYPE – Select the method to use to identify the available collections. Options include: .
Auto Discovery – Automatically generate a list of available collections. To use this option, enter a URL in the DISCOVER SERVICE URL field to indicate where the list of collections can be discovered. A Retrieve Collections List dropdown menu will be made available in the Collection field further down in the panel and you will be able to select from a list of collections.
Manual – Enter a value in the API ROOT URL field to indicate the TAXII feed server from which the collector will ingest data. You will need to enter a specific Collection further down in the panel.
COLLECTION NAME – Optionally, enter the name of the collection on the TAXII server.
AUTHENTICATION TYPE – The
Basic
authentication method is used during Discovery and Collection phases.USERNAME – If you select the
Basic
authentication type, enter an authentication username.PASSWORD – Enter an authentication password.
COLLECTION – If you selected the Auto Discovery option for the discovery type, click the Retrieve Collections List drop down menu and select a collection from the list. If you selected the Manual discovery option, enter an identifier for the specific collection on the TAXII server from which the collector will ingest data.
Note
Early Access
When the cloud collector has been created, you cannot currently return to use the Retrieve Collections List drop down menu to choose another collection.
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.
(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.
To create a corresponding STIX/TAXII context table, navigate to the Context Management service in the New-Scale Security Operations Platform and create a STIX/TAXII context table manually. For more information, see STIX/TAXII Context Tables in the Context Management Guide.
Note
Early Access
Currently, the corresponding context table must be created manually. In a future release, an auto-create option will be introduced to create the context table automatically when the collector is created.