IN
Infoblox•Software Product

Threat Defense

Profile checked & reviewed: Oct 15, 2026

Official Website

Factual Product Summary

Threat Defense from Infoblox focuses on DNS-layer threat prevention and investigation. It is DNS-layer protection technology used for using name-resolution traffic as a security control point. Capabilities - Protective DNS intelligence: Brings the documented threat intelligence into decisions about risky DNS destinations. - Protective DNS filtering: Uses DNS request handling as a control point for access to risky destinations. - Malicious domain blocking: Restricts access to domains that meet the configured threat or filtering rules. - DNS request visibility: Provides information about the DNS activity included in the deployment. - Threat intelligence support: Uses the documented threat information to inform DNS-based protection decisions. Use and operational context Threat Defense is relevant to organizations governing access to risky destinations when the requirement centers on using name-resolution traffic as a security control point. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review DNS routing, filtering policy, exceptions and the effect of protective decisions on legitimate applications. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Threat Defense focuses on using name-resolution traffic as a security control point. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.

Documented Technical Capabilities

Core enterprise capabilities verified directly from official vendor engineering documentation.

7 capabilities verified
DNS-layer threat prevention
Investigation
Protective DNS intelligence
Protective DNS filtering
Malicious domain blocking
DNS request visibility
Threat intelligence support

Documented Capabilities & Sourced Claims

Every claim is checked against official engineering documentation or compliance reports.

0 claims verified
Detailed capability claims are currently undergoing source extraction.

Deployment & Specifications

Deployment Models
Cloud service / SaaS
Supported Platforms
Not documented in our sources
Customer Segments
Not documented in our sources
Service Geography
Not documented in our sources

Pricing Transparency

Status: Pricing not publicly documented

About the Vendor

Infoblox offers a portfolio covering using name-resolution traffic as a security control point. The entries in this catalog include BloxOne Threat Defense and Threat Defense. BloxOne Threat Defense focuses on dns threat detection and protective dns controls. Threat Defense focuses on dns-layer threat prevention and investigation. When reviewing Infoblox, compare the named products individually: a platform family, a specific module and a managed service can have different scopes and purchasing requirements. Selection should account for DNS routing, filtering policy, exceptions and the effect of protective decisions on legitimate applications. Portfolio detail - BloxOne Threat Defense: the catalog lists DNS-layer threat defense, Protective DNS filtering, Malicious domain blocking. - Threat Defense: the catalog lists Protective DNS intelligence, Protective DNS filtering, Malicious domain blocking. For procurement, map each required capability to a named offering and confirm the edition, dependencies and delivery responsibility with the vendor. Product-level entries below provide the operational context and evaluation questions for that comparison.