processing-stix-taxii-feeds

Parses and validates STIX 2.1 bundles from TAXII 2.1 servers for threat intelligence pipelines.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill processing-stix-taxii-feeds
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: processing-stix-taxii-feeds
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/threat-intelligence/processing-stix-taxii-feeds
Command: npx skills add https://github.com/xalgord/xalgorix --skill processing-stix-taxii-feeds

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires stix2, taxii2-client.

What problem does it solve?

Ingesting threat intelligence from TAXII feeds often leads to silent data loss, duplicate indicators, and malformed STIX bundles breaking downstream SIEM or TIP imports. This Skill provides a structured workflow to discover collections, paginate feeds, validate STIX 2.1 objects, and route them to consuming platforms without losing or mis-handling intelligence.

Core Features & Use Cases

  • TAXII Collection Discovery & Polling: Enumerate TAXII 2.1 server collections and fetch incremental objects using added_after filters with pagination and UTC overlap windows.
  • STIX Bundle Validation: Parse bundles with the stix2 library, check spec_version, required indicator fields, confidence ranges, and resolve relationship references before import.
  • Routing & Bi-directional Sharing: Map indicators, malware, threat-actors, and courses-of-action to SIEM, EDR, TIP, or SOAR destinations while enforcing TLP marking restrictions, and publish validated local intelligence back to shared collections.
  • Use Case: Onboard a CISA AIS or FS-ISAC feed by polling its TAXII collection every 24 hours, deduplicating indicators by observable value, filtering revoked or expired entries, and pushing clean indicators into Splunk ES and MISP.

Quick Start

Ask the AI to connect to your TAXII 2.1 server, fetch the last 24 hours of STIX objects from a chosen collection, validate the indicators, and route them to your SIEM.

Frequently Asked Questions about processing-stix-taxii-feeds

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch STIX objects from a TAXII 2.1 server in Python?

Use the taxii2-client library to connect to the server, enumerate API roots and collections, then call get_objects with an added_after timestamp. Wrap calls in as_pages to handle pagination and avoid silently dropping objects.

How to validate a STIX 2.1 bundle before importing it?

Parse the bundle with the stix2 library, check the spec_version field since 2.0 and 2.1 schemas differ, and confirm required indicator fields like pattern, pattern_type, and valid_from exist. Also verify relationship source_ref and target_ref IDs resolve within the bundle.

Does MISP support TAXII 2.1 feed integration?

Yes, MISP includes a native TAXII 2.1 server and client, and the MISP-TAXII-Server plugin can publish MISP events as STIX. OpenCTI also provides a built-in TAXII 2.1 connector with native STIX 2.1 import and export.

Why does my TAXII feed ingestion miss objects between polls?

Missing objects usually come from unhandled pagination via the next link header or clock skew on the added_after filter. Use UTC timestamps exclusively and add a 5-minute overlap window, then reconcile object counts per poll to detect gaps.

When should I not use STIX/TAXII processing for threat feeds?

Avoid this approach for proprietary vendor formats like Recorded Future JSON or CrowdStrike IOC lists, which need vendor-specific parsers rather than STIX processing. It is designed for OASIS STIX 2.0/2.1 content delivered over TAXII.