<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Firewall on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/firewall/</link><description>Recent content in Firewall on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 22 Oct 2026 15:46:09 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/firewall/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS Network Firewall adds Route 53 IP validation for non-HTTP protocols</title><link>https://curadevops.metacog.co.kr/insights/2026-10-22-aws-network-firewall-now-supports-route-53-resolved-ip-valid/</link><pubDate>Thu, 22 Oct 2026 15:46:09 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-22-aws-network-firewall-now-supports-route-53-resolved-ip-valid/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> This GA capability closes a real security gap by validating destination IPs against Route 53-resolved addresses, extending domain-based filtering to SFTP, SSH, and other protocols beyond HTTP/HTTPS. Evaluate adding Route 53 Resolved IP Validation to existing Network Firewall policies to harden egress controls and prevent SNI spoofing.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>