Skip to main content
If you’re already familiar with TAXII, use these configuration values for commonly used TAXII clients. We support STIX/TAXII version 2.1.

Server Endpoints

Your TAXII client may ask for one or both of these values:

Authentication

All TAXII requests use HTTP Basic authentication:

Available Collections

Available collections include:
You need a Pulsedive API key for all requests, including access to the free test collection. Create a free account to get your API key.

Platform Configuration

Configure Pulsedive’s TAXII server with these platform-specific settings for popular threat intelligence tools. For step-by-step guides to these and other integrations, visit Integrations.
Try before you buy: Evaluate our TAXII service using the free test collection with live Pulsedive data. You only need a free API key. Get one by signing up for a free account.

Microsoft Sentinel

Use Microsoft Sentinel’s native TAXII data connector with the server endpoints and authentication details above. For Pulsedive’s step-by-step guide, visit Integrate with Microsoft Sentinel. Visit Microsoft’s official blog post for another walkthrough.

OpenCTI (Native TAXII Import)

OpenCTI supports native automated import for several formats, including TAXII. For Pulsedive’s step-by-step guide, visit Integrate with OpenCTI. Configure OpenCTI’s TAXII 2.1 import using these values:
  • TAXII Server URL: https://pulsedive.com/taxii2/api/
  • Username: taxii2
  • Password: <YOUR_API_KEY>
  • Collection IDs: Select from the collection IDs above

OpenCTI (Legacy TAXII2 Connector)

For older OpenCTI versions that don’t support native automated import for TAXII (pre-6.x), use the TAXII2 connector. Configure these environment variables:
Legacy connectors use collection names instead of IDs. The names above correspond to the Test, Indicator, and Threat collections, respectively. Adjust these values depending on which collections you want to ingest.