AWS previews Infoblox threat intelligence rules inside Route 53 Resolver DNS Firewall
AWS says Infoblox Threat Defense is now in preview in Route 53 Resolver DNS Firewall, letting customers subscribe via AWS Marketplace to partner-managed DNS threat feeds. The Marketplace fee is waived during preview, but the rules require the paid DNS Firewall Advanced option.
Amazon Web Services has added Infoblox Threat Defense as a preview option in Amazon Route 53 Resolver DNS Firewall, according to an AWS architecture blog post published on 18 November. The integration lets customers apply Infoblox-maintained DNS threat intelligence to the outbound DNS queries their Amazon VPC workloads send, rather than curating domain blocklists themselves. [1]
AWS says customers subscribe through AWS Marketplace from within the existing DNS Firewall rule workflow, and that charges appear on the AWS bill without a separate billing relationship with Infoblox. Infoblox groups its protections into five risk-based categories: Critical, High, Medium, Low and Informational. [1]
On cost, AWS says the Infoblox Marketplace subscription carries no fee during the preview, but the managed rule requires the DNS Firewall Advanced pricing option, which bills hourly per rule group containing Advanced rules for each associated VPC. AWS did not state what the Infoblox subscription will cost after preview, pointing readers to the Marketplace listing. [1]
Subscribing authorises AWS to share DNS query metadata with Infoblox. AWS describes this as the domain names an Infoblox rule checks, and says the data is anonymised, mirroring its existing Palo Alto Networks partner-managed rule. Customers are directed to the Marketplace listing for the applicable terms. [1]
AWS recommends starting the rule in ALERT mode, reviewing matches in Resolver query logs, and then switching to BLOCK, beginning with the Critical and High categories. Because the ALLOW action is not supported on Advanced rules, exceptions must be handled through a separate custom domain list rule with a lower priority number. [1]
Operators should also note that DNS Firewall fails closed by default: if the firewall does not respond, Resolver blocks the query and returns SERVFAIL, which AWS acknowledges can interrupt name resolution. A FirewallFailOpen setting is available for teams that prioritise availability. [1]
Sources
- Amazon Web Services: Block DNS threats with Infoblox rules in Amazon Route 53 Resolver DNS FirewallSource published · TechDots found it
Statements labelled as a company's claim have not been independently confirmed by TechDots.
Get Cybersecurity stories by email
Related coverage
AWS reworks Well-Architected Framework, adding secure coding and backup resilience guidance
AWS says its updated Well-Architected Framework splits environment-wide guardrails from per-workload reviews, adds secure coding and ransomware-resilient backup practices, and trims workload best practices from 307 to 216 to ease automated reviews.
Cloudflare picks leader-optional QuePaxa algorithm to keep its global Meerkat control plane moving
Cloudflare says its experimental Meerkat consensus service runs on QuePaxa, a 2023 academic algorithm that does not depend on a single leader, to avoid stalls on volatile wide-area networks. The performance figures come from Cloudflare's own testing and have not been independently verified.
Cloudflare warns Quad9's exit from France could leave unaware DNS users offline
In a blog post, Cloudflare says Quad9 is pulling its free public DNS resolver out of France after a court imposed daily penalties for not blocking piracy-linked domains. Cloudflare, Google and Cisco are appealing a similar Belgian order with a January 2027 deadline.