TAXII 2 Feed
Ingests indicator feeds from TAXII 2.0 and 2.1 servers.
Data Enrichment & Threat Intelligence · TAXII Feed · Feed
Details
| ID | TAXII 2 Feed |
|---|---|
| Provider | Open Source |
| Category | Data Enrichment & Threat Intelligence |
| From Version | 5.5.0 |
| Docker Image | demisto/taxii2:1.0.0.11040999 |
| Supported Modules | Agentix XSIAM |
README
Ingest indicator feeds from TAXII 2.0 and 2.1 servers.
Configure TAXII 2 Feed in Cortex
| Parameter | Description | Required |
|---|---|---|
| Name | True | |
| Discovery Service URL (e.g. https://example.net/taxii) | True | |
| Username / API Key | False | |
| Password | False | |
| API Root to Use | The API root to use (for example default or public). If left empty, the server default API root is used. If the server has no default root, the first available API root is used instead. | False |
| Collection Name To Fetch Indicators From | Indicators will be fetched from this collection. Run “taxii2-get-collections” command to get a valid value. If left empty, the instance will try to fetch from all the collections in the given discovery service. | False |
| Certificate File as Text | Add a certificate file as text to connect to the TAXII server. | False |
| Key File as Text | Add a key file as text to connect to the TAXII server | False |
| Run on Single engine | False | |
| Trust any certificate (not secure) | Located under Advanced Settings. | False |
| Use system proxy settings | Located under Advanced Settings. | False |
| Log Level | Debug/Verbose logging is recommended only during troubleshooting. Logging can affect integration performance. Recommended usage is to turn logging on during setup and troubleshooting, and then turn it off in production. These settings only affect the integration log. The server log is not affected. | False |
| Do not use in CLI by default | False | |
| Fetch indicators | False | |
| Classifier | Determines the type of incident that is created for events ingested from this integration instance. | False |
| Mapper (incoming) | Determines how event fields are mapped to the Cortex XSOAR incident fields. | False |
| Indicator Reputation | Indicators from this integration instance will be marked with this reputation. | False |
| Source Reliability | Reliability of the source providing the intelligence data. | True |
| Traffic Light Protocol Color | The Traffic Light Protocol (TLP) designation to apply to indicators fetched from the feed. | False |
| Max Indicators Per Fetch (disabled for Full Feed Fetch) | The maximum number of indicators that can be fetched per fetch. If this field is left empty, there will be no limit on the number of indicators fetched. | False |
| First Fetch Time | The time interval for the first fetch (retroactive). <number> <time unit> of type minute/hour/day/year. For example, 1 minute, 12 hour | False |
| STIX Objects To Fetch | Which STIX objects to fetch from the TAXII server. If left empty, all available object types will be fetched. | False |
| Max STIX Objects Per Poll | Set the number of stix object that will be requested with each TAXII poll (http request). A single fetch is made of several taxii polls. Changing this setting can help speed up fetches, or fix issues on slower networks. Please note server restrictions may apply, overriding and limiting the “requested limit”. | False |
| Enrichment Excluded | Select this option to exclude the fetched indicators from the enrichment process. | False |
| Indicator Expiration Method | False | |
| Feed Fetch Interval | False | |
| Bypass exclusion list | When selected, the exclusion list is ignored for indicators from this feed. This means that if an indicator from this feed is on the exclusion list, the indicator might still be added to the system. | False |
| Incremental Feed | Incremental feeds pull only new or modified indicators that have been sent from the integration. As the determination if the indicator is new or modified happens on the 3rd-party vendor’s side, and only indicators that are new or modified are sent to Cortex XSOAR, all indicators coming from these feeds are labeled new or modified. | False |
| Full Feed Fetch | When enabled, fetch-indicators will try to fetch the entire feed for every fetch. When disabled, fetch-indicators will try to fetch just the latest entries (since the last fetch). | False |
| Complex Observation Mode | Choose how to handle complex observations. Two or more observation expressions can be combined using a complex observation operator such as “AND”, “OR”. e.g. `[ IP = ‘b’ ] AND [ URL = ‘d’ ]` | False |
| Update custom fields | Choose whether to import the XSOAR custom fields. Note: this might overwrite the data pulled from other sources. | False |
| Tags | Supports CSV values. | False |
Using API token authentication
To use the integration with an API token you first need to change the Username / API Key (see '?') field to _api_token_key. You can then enter the API Token into the Password field - this value will be used as an API key.
Using a custom authentication header
If the TAXII 2 server you are trying to connect to requires a custom authentication header, you first need to change the Username / API Key (see '?') field to _header: and the custom header name, e.g. _header:custom_auth. You can then enter the custom auth header value into the Password field - this value will be used as a custom auth header.
Complex Observation Mode consideration
You can combine two or more observation expressions using a complex observation operator such as “AND”, “OR”, and “FOLLOWEDBY”, for example [ IP = 'b' ] AND [ URL = 'd' ]. These relationships are not represented in CORTEX XSOAR TIM indicators. You can create them while ignoring these relations, or you can ignore these expressions. If you choose to ignore these expressions, then no indicator will be created for complex observations.
Enrichment Excluded consideration
Setting the Traffic Light Protocol Color to red automatically excludes enrichment, even if Enrichment Excluded is unchecked.
Commands
You can execute these commands from the CLI, as part of an automation, or in a playbook.
After you successfully execute a command, a DBot message appears in the War Room with the command details.
taxii2-get-indicators
Allows you to test your feed and to make sure you can fetch indicators successfuly.
Base Command
taxii2-get-indicators
Input
| Argument Name | Description | Required |
|---|---|---|
| raw | Will return only the rawJSON of the indicator object. | Optional |
| limit | Maximum number of indicators to fetch. | Optional |
| added_after | Fetch only indicators that were added to the server after the given time. Please provide a <number> and <time unit> of type minute/hour/day. For example, 1 minute, 12 hour, 24 days. | Optional |
Context Output
| Path | Type | Description |
|---|---|---|
| TAXII2.Indicators.type | String | Indicator type. |
| TAXII2.Indicators.value | String | Indicator value. |
| TAXII2.Indicators.rawJSON | String | Indicator rawJSON. |
Command Example
!taxii2-get-indicators limit=3
Human Readable Output
| value | type |
|---|---|
| coronashop.jp | Domain |
| e6ecb146f469d243945ad8a5451ba1129c5b190f7d50c64580dbad4b8246f88e | File |
| 2014[.]zzux[.]com | Domain |
taxii2-get-collections
Gets the list of collections from the discovery service.
Base Command
taxii2-get-collections
Input
There are no input arguments for this command.
Context Output
| Path | Type | Description |
|---|---|---|
| TAXII2.Collections.ID | String | Collection ID. |
| TAXII2.Collections.Name | String | Collection Name. |
Command Example
!taxii2-get-collections
Human Readable Output
| Name | ID |
|---|---|
| Phish Tank | 107 |
| Abuse.ch Ransomware IPs | 135 |
| Abuse.ch Ransomware Domains | 136 |
| DShield Scanning IPs | 150 |
| Malware Domain List - Hotlist | 200 |
| Blutmagie TOR Nodes | 209 |
| Emerging Threats C&C Server | 31 |
| DT COVID-19 | 313 |
| Lehigh Malwaredomains | 33 |
| CyberCrime | 41 |
| Emerging Threats - Compromised | 68 |
taxii2-reset-fetch-indicators
WARNING: This command will reset your fetch history.
Base Command
taxii2-reset-fetch-indicators
Input
There are no input arguments for this command.
Context Output
There is no context output for this command.
Command Example
!taxii2-reset-fetch-indicators
Human Readable Output
Fetch was reset successfully. Your next indicator fetch will collect indicators from the configured “First Fetch Time”
Troubleshooting
When the feed is set to “Incremental Feed”, we recommend specifying a value for the Max Indicators Per Fetch parameter to prevent potential timeout issues.
Configuration parameters
feed— Fetch indicatorsfeedReputation— Indicator ReputationfeedReliability— Source Reliability (required)tlp_color— Traffic Light Protocol ColorfeedExpirationPolicy—feedExpirationInterval—feedFetchInterval— Feed Fetch IntervalfeedBypassExclusionList— Bypass exclusion listurl— Discovery Service URL (e.g. https://example.net/taxii2) (required)credentials— Username / API Keydefault_api_root— API Root to Usecollection_to_fetch— Collection Name To Fetch Indicators FromfeedIncremental— Incremental Feedfetch_full_feed— Full Feed Fetchlimit— Max Indicators Per Fetch (disabled for Full Feed Fetch)initial_interval— First Fetch Timeobjects_to_fetch— STIX Objects To Fetchcreds_certificate— Certificate File as Textcertificate— Certificate File as Textkey— Key File as Textlimit_per_request— Max STIX Objects Per Pollobservation_operator_mode— Complex Observation Modeupdate_custom_fields— Update custom fieldsinsecure— Trust any certificate (not secure)proxy— Use system proxy settingsfeedTags— TagsenrichmentExcluded— Enrichment Excluded
Commands (3)
-
taxii2-get-collectionsGets the list of collections from the discovery service.
-
taxii2-get-indicatorsAllows you to test your feed and to make sure you can fetch indicators successfuly.
-
taxii2-reset-fetch-indicatorsDeprecatedWARNING: This command will reset your fetch history.
category: Data Enrichment & Threat Intelligence provider: Open Source commonfields: id: TAXII 2 Feed version: -1 configuration: - defaultvalue: 'true' display: Fetch indicators name: feed type: 8 required: false section: Collect - additionalinfo: Indicators from this integration instance will be marked with this reputation. display: Indicator Reputation name: feedReputation options: - None - Good - Suspicious - Bad type: 18 required: false section: Collect - additionalinfo: Reliability of the source providing the intelligence data. display: Source Reliability name: feedReliability options: - A - Completely reliable - B - Usually reliable - C - Fairly reliable - D - Not usually reliable - E - Unreliable - F - Reliability cannot be judged required: true type: 15 section: Collect - additionalinfo: The Traffic Light Protocol (TLP) designation to apply to indicators fetched from the feed. display: Traffic Light Protocol Color name: tlp_color options: - RED - AMBER - GREEN - WHITE type: 15 defaultvalue: 'WHITE' required: false section: Collect - display: '' name: feedExpirationPolicy options: - never - interval - indicatorType - suddenDeath type: 17 required: false section: Collect advanced: true - display: '' name: feedExpirationInterval type: 1 required: false section: Collect advanced: true - defaultvalue: '240' display: Feed Fetch Interval name: feedFetchInterval type: 19 required: false section: Collect advanced: true - additionalinfo: When selected, the exclusion list is ignored for indicators from this feed. This means that if an indicator from this feed is on the exclusion list, the indicator might still be added to the system. display: Bypass exclusion list name: feedBypassExclusionList type: 8 required: false section: Collect advanced: true - display: Discovery Service URL (e.g. https://example.net/taxii2) name: url required: true type: 0 section: Connect - display: Username / API Key name: credentials type: 9 required: false section: Connect - additionalinfo: The API root to use (for example default or public). If left empty, the server default API root is used. If the server has no default root, the first available API root is used instead. display: API Root to Use name: default_api_root type: 0 required: false section: Connect - additionalinfo: Indicators will be fetched from this collection. Run "taxii2-get-collections" command to get a valid value. If left empty, the instance will try to fetch from all the collections in the given discovery service. display: Collection Name To Fetch Indicators From name: collection_to_fetch type: 0 required: false section: Connect - additionalinfo: Incremental feeds pull only new or modified indicators that have been sent from the integration. As the determination if the indicator is new or modified happens on the 3rd-party vendor's side, and only indicators that are new or modified are sent to Cortex XSOAR, all indicators coming from these feeds are labeled new or modified. defaultvalue: 'false' display: Incremental Feed name: feedIncremental type: 8 required: false section: Collect advanced: true - additionalinfo: When enabled, fetch-indicators will try to fetch the entire feed for every fetch. When disabled, fetch-indicators will try to fetch just the latest entries (since the last fetch). display: Full Feed Fetch name: fetch_full_feed type: 8 required: false defaultvalue: 'true' section: Collect advanced: true - additionalinfo: The maximum number of indicators that can be fetched per fetch. If this field is left empty, there will be no limit on the number of indicators fetched. display: Max Indicators Per Fetch (disabled for Full Feed Fetch) name: limit type: 0 required: false section: Collect - display: First Fetch Time name: initial_interval defaultvalue: 1 year type: 0 required: false additionalinfo: 'The time interval for the first retroactive fetch, formatted as <time unit of type minute/hour/day/year>. For example: 1 minute, 12 hours.' section: Collect - display: STIX Objects To Fetch name: objects_to_fetch type: 16 required: false defaultvalue: indicator,report,malware,campaign,attack-pattern,course-of-action,intrusion-set,tool,threat-actor,infrastructure options: - indicator - report - malware - campaign - attack-pattern - course-of-action - intrusion-set - tool - threat-actor - infrastructure - autonomous-system - domain-name - email-addr - file - ipv4-addr - ipv6-addr - mutex - url - user-account - windows-registry-key - identity - location - vulnerability - x509-certificate - software additionalinfo: 'Choose which STIX object types to fetch from the TAXII server. If left empty, all available object types will be fetched.' section: Collect - display: Certificate File as Text name: creds_certificate type: 9 required: false displaypassword: Key File as Text section: Connect - additionalinfo: Add a certificate file as text to connect to the TAXII server display: Certificate File as Text name: certificate type: 12 hidden: true required: false section: Connect - additionalinfo: Add a key file as text to connect to the TAXII server display: Key File as Text name: key type: 4 required: false hidden: true section: Connect - additionalinfo: Set the number of stix object that will be requested with each taxii poll (http request). A single fetch is made of several taxii polls. Changing this setting can help speed up fetches, or fix issues on slower networks. Please note server restrictions may apply, overriding and limiting the "requested limit". defaultvalue: '100' display: Max STIX Objects Per Poll name: limit_per_request type: 0 required: false section: Collect - additionalinfo: "Choose how to handle complex observations. Two or more observation expressions may be combined using a complex observation operator such as \"AND\" or \"OR\". For example: [ IP = 'b' ] AND [ URL = 'd' ]" display: Complex Observation Mode name: observation_operator_mode type: 15 required: false defaultvalue: Skip indicators with more than a single observation options: - Create indicator for each observation - Skip indicators with more than a single observation section: Collect advanced: true - display: Update custom fields name: update_custom_fields type: 8 required: false additionalinfo: "Choose whether to import Cortex XSOAR custom fields. Note: this may overwrite data pulled from other sources." section: Collect advanced: true - display: Trust any certificate (not secure) name: insecure type: 8 required: false section: Connect advanced: true - display: Use system proxy settings name: proxy type: 8 required: false section: Connect advanced: true - additionalinfo: Supports CSV values. display: Tags name: feedTags type: 0 required: false section: Collect advanced: true - display: Enrichment Excluded name: enrichmentExcluded type: 8 required: false defaultvalue: 'false' additionalinfo: Select this option to exclude the fetched indicators from the enrichment process. hidden: - xsoar_on_prem section: Collect description: Ingests indicator feeds from TAXII 2.0 and 2.1 servers. display: TAXII 2 Feed name: TAXII 2 Feed script: commands: - arguments: - auto: PREDEFINED defaultValue: 'false' description: Will return only the rawJSON of the indicator object. name: raw predefined: - 'true' - 'false' - defaultValue: '10' description: Maximum number of indicators to fetch. name: limit - description: Fetch only indicators that were added to the server after the given time. Please provide a <number> and <time unit> of type minute/hour/day. For example, 1 minute, 12 hour, 24 days. name: added_after description: Allows you to test your feed and to make sure you can fetch indicators successfuly. name: taxii2-get-indicators outputs: - contextPath: TAXII2.Indicators.type description: Indicator type. type: String - contextPath: TAXII2.Indicators.value description: Indicator value. type: String - contextPath: TAXII2.Indicators.rawJSON description: Indicator rawJSON. type: String - description: Gets the list of collections from the discovery service. name: taxii2-get-collections outputs: - contextPath: TAXII2.Collections.ID description: Collection ID. type: String - contextPath: TAXII2.Collections.Name description: Collection Name. type: String - deprecated: true description: 'WARNING: This command will reset your fetch history.' name: taxii2-reset-fetch-indicators dockerimage: demisto/taxii2:1.0.0.11040999 feed: true runonce: false script: '-' subtype: python3 type: python tests: - TAXII 2 Feed Test fromversion: 5.5.0 sectionorder: - Connect - Collect