<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IaC on Landry Zetam - Tech Blog</title><link>https://blog.landryzetam.net/tags/iac/</link><description>Recent content in IaC on Landry Zetam - Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.landryzetam.net/tags/iac/index.xml" rel="self" type="application/rss+xml"/><item><title>Lint Your Network Before It Exists: IaC Policy Scanning for VPCs</title><link>https://blog.landryzetam.net/posts/lint-your-network-before-it-exists/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.landryzetam.net/posts/lint-your-network-before-it-exists/</guid><description>&lt;p>Most network security failures aren&amp;rsquo;t exotic. They&amp;rsquo;re a security group left open to the whole internet on port 22, a subnet that auto-assigns public IPs to everything you launch into it, or a virtual network with flow logs never turned on so you have no record of what happened. The surprise isn&amp;rsquo;t that these slip through — it&amp;rsquo;s that you can catch every one of them &lt;em>before a single resource exists&lt;/em>, by linting the infrastructure code the same way you lint application code.&lt;/p></description></item></channel></rss>