---
title: Ingest TAXII Threat Intelligence
description: >-
  Connect Cloud SIEM to TAXII 2.1 servers so Datadog polls your threat
  intelligence collections on a schedule and uses their indicators to enrich
  your logs.
breadcrumbs: >-
  Docs > Datadog Security > Cloud SIEM > Ingest and Enrich > Ingest TAXII Threat
  Intelligence
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Ingest TAXII Threat Intelligence

## Overview{% #overview %}

If your threat intelligence provider or Threat Intelligence Platform (TIP) publishes indicators through a [TAXII 2.1](https://docs.oasis-open.org/cti/taxii/v2.1/taxii-v2.1.html) server, you can connect Cloud SIEM to that server directly. Datadog polls the collections you choose on a schedule and uses their indicators to [enrich your logs](https://docs.datadoghq.com/security/cloud_siem/ingest_and_enrich/threat_intelligence.md).

Client certificates (mTLS), bearer tokens, and OAuth are not supported; a TAXII server must use basic authentication or no authentication.

To push indicators from your own scripts or jobs instead, see [Ingest STIX Threat Intelligence](https://docs.datadoghq.com/security/cloud_siem/ingest_and_enrich/stix_threat_intelligence.md).

## How it works{% #how-it-works %}

A TAXII server hosts one or more collections, each of which is a feed of STIX 2.1 objects. After you add a server and its collections:

1. Datadog polls each collection that has polling enabled, at the interval you set for that collection, and fetches new objects incrementally.
1. Datadog uses the collection's indicators to enrich logs while polling is enabled.

A collection with a large backlog can take several polling cycles to complete its first sync. Enrichment applies to logs that Cloud SIEM receives after the indicators are available.

Each organization can have up to 20 collections with polling enabled at a time. You can still add more collections beyond that limit, but you must leave scheduled polling disabled for them. Enabling polling on a collection after reaching the limit returns an error, and that collection's polling stays disabled until you disable polling on another one.

### Indicator handling{% #indicator-handling %}

| Indicator type    | STIX pattern object      |
| ----------------- | ------------------------ |
| IP address        | `ipv4-addr`, `ipv6-addr` |
| Domain            | `domain-name`            |
| SHA-256 file hash | `file:hashes.'SHA-256'`  |

Datadog skips other indicator types. Datadog extracts exact values from `=` and `IN` comparisons in the STIX pattern, and also accepts `OR` expressions, importing each value as a separate indicator. `AND` between bracketed expressions, negation, ranges, wildcard matching, regular expression matching, subnet relations, existence checks, temporal qualifiers, and `FOLLOWEDBY` are not supported. Datadog skips all indicators with patterns containing unsupported expressions.

The optional `valid_until` field sets an expiration for the indicator, and Datadog removes the indicator after that time. An indicator published without `valid_until` does not expire automatically.

An indicator published with `"revoked": true` is deleted from the reference table.

## Prerequisites{% #prerequisites %}

- Cloud SIEM is enabled for your organization
- One or both of the following [permissions](https://docs.datadoghq.com/account_management/rbac/permissions.md#integrations):
  - Integrations Read to view TAXII servers and collections
  - Integrations Manage to add, change, or delete them
- From your TIP: the server's API root URL, credentials if the server requires them, and the UUID of each collection you want to ingest

## Add a TAXII server{% #add-a-taxii-server %}

{% alert level="info" %}

- Check the server's name, API root URL, and authentication method before you save it. You can't change these after saving.
- Stored credentials aren't viewable, but you can replace them later. See Replace credentials.
- Datadog validates the API root URL and credentials when the first enabled collection is polled, not when you save the server.

{% /alert %}

1. In Datadog, go to Integrations and open the TAXII tile.
1. Click Configure, then click New.
1. Enter a Name for the server; for example, `Production threat intelligence`.
1. Enter the TAXII API root URL; for example, `https://taxii.example.com/api/taxii2/`. The URL must use HTTPS.
1. Under Authentication, select Basic authentication or None. For basic authentication, enter the Username or API token and Password from your provider. If your provider issues a single API token, enter it in Password.
1. Click Save.

## Add a collection{% #add-a-collection %}

1. Go to Integrations > TAXII > Configure, select the server from the TAXII servers list, then click Add Collection.
1. Enter the Collection UUID and a Display name. Datadog does not discover a server's collections automatically, so get the UUID from your provider.
1. Set the Initial lookback (days). The default is 30 days. The lookback is based on when objects were added to the collection, and you cannot change it later.
1. Select a Polling interval: 30 minutes, 1 hour (default), 6 hours, or 24 hours.
1. Leave Enable scheduled polling selected to start ingesting immediately.
1. Click Add Collection.

## Collection status{% #collection-status %}

Datadog shows each collection's status in the Collections table on the server's page (Integrations > TAXII > Configure, then select the server).

| Status              | Meaning                                                                                  |
| ------------------- | ---------------------------------------------------------------------------------------- |
| Healthy             | The most recent poll succeeded.                                                          |
| Pending             | Polling is enabled, but no poll has completed yet.                                       |
| Error               | The most recent poll failed, or no poll has succeeded within twice the polling interval. |
| Not polling         | Polling is disabled.                                                                     |
| Enabling, Disabling | A polling change is being applied.                                                       |
| Deleting            | The collection and its indicators are being removed.                                     |
| Delete failed       | The removal did not finish. Delete the collection again to retry.                        |

A server is Healthy when at least one of its collections is healthy, Error when none are healthy and at least one has an error, and Pending otherwise.

## Disable or enable polling{% #disable-or-enable-polling %}

On the server's page (Integrations > TAXII > Configure), use the toggle in the Poll column of the Collections table to disable or enable polling.

- Disabling stops polling and removes the collection's indicators from Cloud SIEM enrichment, without deleting them.
- Enabling resumes polling and restores enrichment. Enabled collections count toward the limit of 20.

## Replace credentials{% #replace-credentials %}

For servers that use basic authentication:

1. Go to Integrations > TAXII > Configure, select the server, then click Replace Credentials.
1. Enter the complete new username and password.
1. Click Save.

The new credentials apply from the next poll. If they are invalid, the server's collections show Error.

## Delete a collection or server{% #delete-a-collection-or-server %}

On the server's page (Integrations > TAXII > Configure, then select the server), you can delete a collection or the entire server:

- Delete Collection, under the collection's row in the Collections table, stops polling, removes the collection's indicators, and stops enrichment. The server's other collections are not affected.
- Delete TAXII Server, at the top of the page, deletes all of the server's collections and their indicators, then the server and its credentials.

To stop enrichment but keep the indicators, disable polling instead.

## Further reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [Bring your own threat intelligence to Cloud SIEM](https://docs.datadoghq.com/security/cloud_siem/ingest_and_enrich/threat_intelligence.md)
- [Ingest STIX Threat Intelligence](https://docs.datadoghq.com/security/cloud_siem/ingest_and_enrich/stix_threat_intelligence.md)
- [Investigate indicators with the IOC Explorer](https://docs.datadoghq.com/security/cloud_siem/triage_and_investigate/ioc_explorer.md)
