- infoblox:blog-category/security
Your Best Security Control in AWS Is the One You Think of as Plumbing
Discover how Infoblox brings preemptive DNS threat protection to Amazon Route 53 Resolver DNS Firewall for stronger AWS security.
In 2010, I was running LocalCircles. Small team, no budget and a product that had to be live yesterday. So I spun up an EC2 instance, pointed Route 53 at it and went back to building. Took about an hour.
After that I was in the Route 53 console constantly, for years. A new subdomain for a feature we were testing. Records for the mail provider. A TTL I’d set wrong the first time. Every time something needed to point somewhere new, I was back in there.
Not once did I open it thinking about security. Every one of those visits was about addressing. Where does this name point? What’s the TTL? I was in there telling that resolver what to answer, over and over, for years. It never crossed my mind that I could also tell it what to refuse. It was plumbing. Something that either worked or it didn’t. Millions of us have treated it exactly that way.
I’d think about it differently today. That resolver I was configuring all along is the best place in an AWS environment to stop an attack. Every workload in the VPC asks it a question before it does anything else. Nothing does damage until something resolves a name.
The industry has caught up to that. Filtering DNS at the resolver is well understood now, and most teams with a serious AWS footprint already do some version of it. That part is settled.
The timing isn’t. Almost every approach to DNS filtering answers one question. Has this domain already been caught doing something bad? Good question. Good answer for yesterday’s attack. No answer at all for the domain registered 40 minutes ago that’s gone by tonight.
Infoblox solved that gap years ago. What’s new is where you can now put it—in Amazon Route 53. Infoblox Threat Defense™ for Amazon Route 53 Resolver DNS Firewall is now in free public preview. It blocks malicious and suspicious domains at the resolver layer, using intelligence built on attacker infrastructure we mapped before the domain was ever used on anyone. That’s not reactive; that’s preemptive. And you simply turn it on from the AWS console in seconds. No appliance. No agents. No traffic to reroute.
Why We Built It This Way
Let me be honest about how we got here, because the strategic version of this story isn’t the true one.
For years, the way to get Infoblox DNS security in front of an AWS workload was to bring that traffic to our resolvers. Forward the queries, apply the protection, get the full depth of what Infoblox Threat Defense can do.
That works. It works well. Plenty of our customers run exactly that today for their AWS traffic and are glad they do. If you want the deepest inspection, the richest policy control and one consistent set of DNS security across on-prem, other clouds and AWS together, forwarding to us is still the right architecture. We’re not walking away from it, or from the customers who chose it.
But I kept hearing the same thing in the rooms where the answer wasn’t a clean yes. Some teams routed a slice of their AWS traffic to us and left the rest uncovered, because the forwarding design was more than they wanted to take on for every VPC. Some told me the protection wasn’t the question, the change to their DNS architecture was. Some cloud platform teams just wouldn’t add a forwarding hop to a resolver path they had intentionally kept simple.
Those conversations all ended in the same place. Partial coverage, or none. Not because we lost on the security. Because we were asking for a design change first and delivering protection second.
That’s the real reason this exists. We were making customers choose between the coverage they wanted and the architecture they wanted. So we stopped making them choose and went to where their AWS traffic already resolves.
Why the Resolver Is the Right Place
Almost every cyberattack starts with a DNS query. Before malware phones home, before data leaves the network, before ransomware locks a system, something resolves a domain. That lookup, from an app or a workload or an AI agent, is where the attacker gets a foothold. It’s also the first moment a defender can do anything about it.
One block at the DNS layer cuts off every URL and IP behind a malicious domain, even while attackers rotate the infrastructure underneath. That’s not filtering after the fact. That’s stopping the connection before it’s attempted.
This matters more now because the old model is breaking. Most security tools still assume patient zero. Detect after the first victim, then block. AI-driven attacks let threat actors weaponize a vulnerability in hours and stand up single-use infrastructure they throw away after one target. When the attack is used once and discarded, there’s no first victim to learn from.
A blocklist answers “this domain is known bad” well. It can’t answer “this domain has never been used before and it’s about to be used on you.”
We made a different bet six years ago. We hired Dr. Renée Burton to build a threat intelligence group that does primary research on DNS, tracking the actors and the infrastructure themselves rather than aggregating everyone else’s feeds. Nobody else in this market was doing that, and it’s the reason we can talk about a domain before it’s ever used on anyone. That approach hasn’t changed since. It’s the same industry-leading intelligence our customers have been running for years, and now it runs at the resolver AWS already gave you.
Our threat intelligence maps attacker infrastructure across the internet before it’s weaponized, tracking over 402,000 real-time threat-actor clusters. The way I explain this to customers is that most security tools go after the dealers. The individual bad domains, one at a time, after somebody has already been hit. We go after the cartel—the threat actors and the infrastructure they stand up to supply those domains, which we can see the moment they build it.
Here’s what that buys you. We block domains about 68 days ahead of conventional threat feeds, so weeks or months before they show up on commercial blocklists. We catch five times more high- and medium-risk domains than other approaches at this layer. And our false-positive rate is about 0.0002 percent, so your team can trust the verdicts instead of tuning around them. Those come from Infoblox Threat Intel research and comparative testing at the Route 53 enforcement layer.
Two Chances to Stop the Same Attack
This is the part I’m most excited about and it’s easy to miss.
We launched Infoblox Managed Rules for AWS Network Firewall last year. That one protects the network firewall egress path. This one protects the DNS resolution layer. Same intelligence feeding both.
If a threat gets past one, it runs into the other. Two AWS-native enforcement points. One set of protections. Unified logging into your security information and event management (SIEM). Nothing new to deploy for either.
If you’re already running AWS-native controls, that’s protection that compounds without adding anything to operate.
What Your Team Gets
If you’re a security architect or on a cloud platform team, you can turn this on today and extend it across every workload in the VPC, containers and serverless included, without standing up inspection stacks or tuning feeds. Updates flow in continuously. Nothing to manage.
If you run a SOC, you get verdicts you can act on, logged inside the AWS workflows you already use.
And if you own the cloud budget, here’s the part that rarely comes up in a security conversation. During public preview there’s no Infoblox software charge. At general availability (GA), the Infoblox protection becomes a paid subscription, purchased through AWS alongside your standard AWS usage. No separate procurement. No new vendor to manage. No new line item. Security scales with your cloud footprint instead of fighting your budget for it.
What I Would Tell Myself in 2010
Nobody should have to choose between strong protection and a simple operating model. For most of the cloud era, customers have. The industry asked them to absorb that tradeoff, and we did too.
If I could get one message back to the guy setting up that first Route 53 zone, it’d be short. You’re going to spend years in that console telling that resolver what to answer. Nobody is going to tell you it’s the most important security control you have. One day you’ll be able to tell it what to refuse, in seconds, and it’ll turn away domains, preemptively, before they’ve hurt anyone at all.
That day is today. Go turn it on.
Infoblox Threat Defense for Amazon Route 53 Resolver DNS Firewall is in free public preview starting November 17, 2026. GA is targeting early next year.