Current ThreatQ Version Filter
Understanding Integrations and Access
ThreatQ supports several integration types. Their installation paths and day-to-day controls differ, so identify the type before you begin.
| Type | What is Does | How it is Managed |
|---|---|---|
| Configuration-Driven Feed (CDF) | Pulls threat intelligence from provider endpoints into ThreatQ. Includes Commercial and OSINT feeds. | Install a YAML file through My Integrations, then configure and enable it. Scheduling is available for supported CDFs. |
| STIX/TAXII Feed | Connects to a TAXII server and retrieves data from a collection. | Add from the Add New Integration dialog, provide connection details, then configure and enable. |
| Operation | Queries an external security service to enrich a supported ThreatQ object. | Install a wheel file through My Integrations; run it from a compatible object’s details page. |
| Action | A YAML snippet used by ThreatQ TDR to build custom workflows. | Install as an action package; actions are enabled automatically after installation or upgrade. |
| Custom Connector | A separately installed connector for ingestion needs not covered by Marketplace CDFs. | Typically installed through the command line and scheduled with CRON. Appears under Labs. |
| App | Runs outside the ThreatQ platform and communicates with third-party applications. | Follow the app-specific guide; it is not installed through the UI steps in this guide. |
Who Can Manage Integrations
The default ThreatQ roles with access to integration management are Administrative and Maintenance. Custom roles require the relevant Integrations permissions. Some tasks also require a task-specific permission.
| Task | Custom role permission |
|---|---|
| Install or uninstall integrations | Integrations - Install & Uninstall Integrations |
| Change integration settings | Integrations - Edit Integration Configurations |
| Run an operation | Integrations - Run Operations |
| Manage action-type integrations | Orchestration - Edit Orchestration Workflow |
The default role requirements vary by task. Running operations also requires a role that can access the applicable object. See the permission details in the relevant workflow if access is denied.