2 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
This article presents DARWIS TAXII, a server for the Trusted Automated eXchange of Indicator Information, built in Rust. It supports both TAXII 1.x and 2.x protocols, includes a REST API, and offers features like JWT authentication and async processing. Users can manage configurations and data through YAML files and a command-line interface.
If you do, here's more
DARWIS TAXII is a high-performance server for managing the Trusted Automated eXchange of Indicator Information (TAXII) protocols, built using Rust. It offers full compatibility with the EclecticIQ OpenTAXII database, supporting both TAXII 1.x and 2.1 specifications. Key features include REST API support for collections and objects, native parsing and validation for STIX 2.x data, and robust authentication options such as JWT tokens and Basic Auth. The server uses asynchronous programming with Tokio and Axum to ensure high throughput, making it suitable for demanding environments.
Setting up DARWIS TAXII involves building the server with Rustβs cargo tool and configuring two essential files: `taxii.toml` for server settings and a data configuration file (either `full.yaml` or `accounts.yaml`). Installation instructions provide clear commands for copying example config files, editing them for specific settings, and running the server locally or via Docker. The Docker setup simplifies deployment, allowing users to start the server and PostgreSQL with a single command, and manage configurations through a handy CLI tool.
The CLI tool streamlines various management tasks, such as syncing data configurations, listing accounts, and applying database migrations. It supports both TAXII 1.x and 2.x management commands, making it versatile for different setups. The project follows the OpenTAXII convention, ensuring consistency with existing implementations. Access to a complete documentation site provides detailed guidance on all available commands and options, aiding users in customizing their deployment.
Questions about this article
No questions yet.