taxii-server-opntx

name	taxii-server-opntx
description	Deploy and configure an OpenTAXII server to share and consume STIX-formatted cyber threat intelligence using the TAXII 2.1 protocol for automated indicator exchange between organizations.
domain	cybersecurity
subdomain	threat-intelligence
tags	["taxii","stix","opentaxii","threat-sharing","cti","indicator-exchange","taxii-server","automation"]
version	1.0
author	mahipal
license	Apache-2.0
nist_csf	["ID.RA-01","ID.RA-05","DE.CM-01","DE.AE-02"]

Implementing TAXII Server with OpenTAXII

Overview

TAXII (Trusted Automated eXchange of Intelligence Information) is an OASIS standard protocol for exchanging cyber threat intelligence over HTTPS. OpenTAXII is an open-source TAXII server implementation by EclecticIQ that supports TAXII 1.x, while the OASIS cti-taxii-server provides a TAXII 2.1 reference implementation. This skill covers deploying a TAXII server, configuring collections for threat intelligence feeds, publishing STIX 2.1 bundles, and integrating with SIEM/SOAR platforms for automated indicator ingestion.

When to Use

• When deploying or configuring implementing taxii server with opentaxii capabilities in your environment
• When establishing security controls aligned to compliance requirements
• When building or improving security architecture for this domain
• When conducting security assessments that require this implementation

Prerequisites

• Python 3.9+ with medallion, stix2, taxii2-client, opentaxii, cabby libraries
• Docker and Docker Compose for containerized deployment
• Understanding of STIX 2.1 objects (Indicator, Malware, Attack Pattern, Relationship)
• Familiarity with REST APIs and HTTPS configuration
• TLS certificates for production deployment

Key Concepts

TAXII 2.1 Architecture

TAXII 2.1 defines three services: Discovery (find available API roots), API Root (entry point for collections), and Collections (repositories of CTI objects). Collections support two access models: the Collection endpoint allows consumers to poll for objects, and the Status endpoint tracks the result of add operations. TAXII uses HTTP content negotiation with application/taxii+json;version=2.1.

Sharing Models

TAXII supports hub-and-spoke (central server distributes to consumers), peer-to-peer (bidirectional sharing between partners), and source-subscriber (producer publishes, consumers subscribe) models. Each collection can have read-only, write-only, or read-write access controls.

STIX 2.1 Content

TAXII transports STIX 2.1 bundles containing Structured Threat Information objects: Indicators (detection patterns), Observed Data, Malware, Attack Patterns, Threat Actors, Intrusion Sets, Campaigns, Relationships, and Sightings. Each object has a unique STIX ID, creation/modification timestamps, and optional TLP marking definitions.

Workflow

Step 1: Deploy TAXII 2.1 Server with Medallion

# Install medallion (OASIS reference implementation)



 json

config = {
    : {
        : ,
        : 
    },
    : {
        : ,
        : ,
        : 
    },
    : {
        : 
    }
}


taxii_data = {
    : {
        : ,
        : ,
        : ,
        : ,
        : []
    },
    : {
        : {
            : ,
            : ,
            : [],
            : ,
            : {
                : {
                    : ,
                    : ,
                    : ,
                    : ,
                    : ,
                    : []
                },
                : {
                    : ,
                    : ,
                    : ,
                    : ,
                    : ,
                    : []
                },
                : {
                    : ,
                    : ,
                    : ,
                    : ,
                    : ,
                    : []
                }
            }
        }
    }
}

 (, )  f:
    json.dump(config, f, indent=)
 (, )  f:
    json.dump(taxii_data, f, indent=)
()