AWS Route53: DNS Firewall docs: add resolved IP validation with Network Firewall
Summary
Reworded the DNS Firewall overview (domain-based filtering, 'Alternatively'), and added a new paragraph describing how DNS Firewall and Network Firewall can be used together for resolved IP validation, with a link to a new page.
Security assessment
The added text documents a defense-in-depth control (validating that a connection's destination IP matches the VPC Resolver's DNS answer) that helps mitigate DNS-based exfiltration and spoofing/redirection. It is guidance about a security feature rather than a fix for a specific vulnerability, so it is security documentation, not an incident response.
Evidence
+You can also use DNS Firewall and Network Firewall together for resolved IP validation. Network Firewall checks the DNS resolutions from VPCs that are associated with a DNS Firewall rule group to confirm that the VPC Resolver returned a connection's destination IP address. For more information, see [Resolved IP validation with Network Firewall](./resolver-dns-firewall-resolved-ip-validation.html).
Diff
diff --git a/Route53/latest/DeveloperGuide/resolver-dns-firewall.md b/Route53/latest/DeveloperGuide/resolver-dns-firewall.md index 73b1dff..db45aa2 100644 --- a//Route53/latest/DeveloperGuide/resolver-dns-firewall.md +++ b//Route53/latest/DeveloperGuide/resolver-dns-firewall.md @@ -11 +11 @@ With Resolver DNS Firewall, you can filter and regulate outbound DNS traffic for -DNS Firewall provides protection for outbound DNS requests from your VPCs. These requests route through VPC Resolver for domain name resolution. A primary use of DNS Firewall protections is to help prevent DNS exfiltration of your data. DNS exfiltration can happen when a bad actor compromises an application instance in your VPC and then uses DNS lookup to send data out of the VPC to a domain that they control. With DNS Firewall, you can monitor and control the domains that your applications can query. You can deny access to the domains that you know to be bad and allow all other queries to pass through. Alternately, you can deny access to all domains except for the ones that you explicitly trust. +DNS Firewall provides protection for outbound DNS requests from your VPCs. These requests route through VPC Resolver for domain name resolution. A primary use of DNS Firewall protections is to help prevent DNS exfiltration of your data. DNS exfiltration can happen when a bad actor compromises an application instance in your VPC and then uses DNS lookup to send data out of the VPC to a domain that they control. With DNS Firewall, you can monitor and control the domains that your applications can query. You can deny access to the domains that you know to be bad and allow all other queries to pass through. Alternatively, you can deny access to all domains except for the ones that you explicitly trust. @@ -23 +23 @@ You can use Firewall Manager to centrally configure and manage your DNS Firewall -DNS Firewall and Network Firewall both offer domain name filtering, but for different types of traffic. With DNS Firewall and Network Firewall together, you can configure domain-based filtering for application layer traffic over two different network paths. +DNS Firewall and Network Firewall both offer domain-based filtering, but they act at different points in a connection. @@ -31,0 +32,2 @@ DNS Firewall and Network Firewall both offer domain name filtering, but for diff +You can also use DNS Firewall and Network Firewall together for resolved IP validation. Network Firewall checks the DNS resolutions from VPCs that are associated with a DNS Firewall rule group to confirm that the VPC Resolver returned a connection's destination IP address. For more information, see [Resolved IP validation with Network Firewall](./resolver-dns-firewall-resolved-ip-validation.html). +