Studio Project workflows for Infoblox Threat Defense (BloxOne) security policy and filtering
Infoblox Threat Defense (BloxOne) is a cloud-native DNS security service that protects networks and roaming users at the DNS layer — enforcing security policies, category and application filtering, custom allow/block lists, and threat-intelligence feeds to stop malicious and unwanted domains before a connection is made.
This project provides the OpenAPI spec for automating against the Infoblox Threat Defense (BloxOne) API via an Integration Model.
| Asset | Description |
|---|---|
| OpenAPIs/ | Infoblox Threat Defense (BloxOne) API OpenAPI spec — -latest plus the full dated spec |
| Studio Projects/Infoblox Threat Defense (BloxOne) | 25 workflows covering common CRUD automation |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| Infoblox Threat Defense (BloxOne) API | 1 |
| Infoblox Threat Defense (BloxOne) Integration Model | Required to build automation against the OpenAPI spec |
Import the OpenAPI spec from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at csp.infoblox.com.
Authentication is an API key in the Authorization header:
Authorization: Token <your-infoblox-api-key> Generate an API key in the Infoblox Cloud Services Portal under Administration → API Keys.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"apiKeyAuth": {
"value": "<your-api-key>"
}
},
"server": {
"protocol": "https",
"host": "csp.infoblox.com",
"base_path": "/api/atcfw/v1"
}
} | Spec | Version | Operations | Description |
|---|---|---|---|
infoblox_threat_defense_bloxone-latest.json | latest (curated) | 60 | Trimmed to 60 of 61 upstream operations — see breakdown below |
infoblox_threat_defense_bloxone-1.json | 1 | 61 | Full, unmodified vendor spec |
infoblox_threat_defense_bloxone-latest.jsonActively-maintained spec (x-vendor-api-version: 1). Trimmed to 60 of 61 upstream operations covering DNS security policy management (security policies and rules, application/category/network filters, named and internal domain lists, threat feeds, content categories, PoP regions, access codes, and application/address-block approvals).
Operations included, by category:
infoblox_threat_defense_bloxone-1.jsonFull, unmodified vendor spec for Infoblox Threat Defense (BloxOne) API version 1 (61 operations) — the vendor's complete API surface, preserved as-is. See infoblox_threat_defense_bloxone-latest.json above for the curated subset if you just need common CRUD automation.
Backed by the Infoblox Threat Defense (BloxOne):latest Integration Model (see infoblox_threat_defense_bloxone-latest.json above). The project contains 25 workflows organized into 5 folders, one atomic workflow per API operation, covering the common-CRUD subset of the curated spec.
| Folder | Workflows | Scope |
|---|---|---|
| Security Policies | List, Create, Get, Update, Delete Security Policy | Security policy lifecycle |
| Named Lists | List, Create, Get, Update, Delete Named List | Custom/threat-intel list lifecycle |
| Network Lists | List, Create, Get, Update, Delete Network List | Network list lifecycle |
| Application Filters | List, Create, Get, Update, Delete Application Filter | Application filter lifecycle |
| Category Filters | List, Create, Get, Update, Delete Category Filter | Category filter lifecycle |
| Dependency | Notes |
|---|---|
Infoblox Threat Defense (BloxOne):latest Integration Model | Import from infoblox_threat_defense_bloxone-latest.json before importing the project |
Infoblox Threat Defense (BloxOne) integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named Infoblox Threat Defense (BloxOne) — update the adapter_id value in each workflow task if yours is named differently |