<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Landry Zetam - Tech Blog</title><link>https://blog.landryzetam.net/tags/security/</link><description>Recent content in Security 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/security/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><item><title>Building a Production-Grade Home Network with UniFi VLANs</title><link>https://blog.landryzetam.net/posts/unifi-vlan-home-network/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://blog.landryzetam.net/posts/unifi-vlan-home-network/</guid><description>&lt;p>Your home network doesn&amp;rsquo;t have to be a flat, insecure mess where your smart toaster can talk to your NAS. With UniFi gear and some intentional design, you can build network segmentation that rivals enterprise setups—without the enterprise price tag. This is how I architected a 10-VLAN home network that isolates everything from security cameras to a 7-node Kubernetes cluster.&lt;/p>
&lt;hr>
&lt;h2 id="part-1-the-design-philosophy">Part 1: The Design Philosophy&lt;/h2>
&lt;h3 id="why-segment-at-all">Why Segment at All?&lt;/h3>
&lt;p>Most home networks run everything on a single subnet. Your laptop, your Ring cameras, your kids&amp;rsquo; tablets, and your IoT light bulbs all share the same network space. This creates several problems:&lt;/p></description></item><item><title>Complete Kubernetes Security Pipeline - Kube-bench and Kubescape to Obsidian</title><link>https://blog.landryzetam.net/posts/kubernetes-security-pipeline-kubebench-kubescape/</link><pubDate>Fri, 19 Dec 2025 00:00:00 +0000</pubDate><guid>https://blog.landryzetam.net/posts/kubernetes-security-pipeline-kubebench-kubescape/</guid><description>&lt;p>What if your Kubernetes cluster could write comprehensive security reports directly into your second brain every night? Not just one perspective, but two complementary views: infrastructure security &lt;em>and&lt;/em> workload security. I built exactly that—a pipeline combining kube-bench (CIS benchmarks) and kubescape (NSA/MITRE frameworks) that publishes human-readable reports to Obsidian automatically. Here&amp;rsquo;s how the complete system works.&lt;/p>
&lt;hr>
&lt;h2 id="part-1-why-you-need-both-tools">Part 1: Why You Need Both Tools&lt;/h2>
&lt;h3 id="the-security-visibility-gap">The Security Visibility Gap&lt;/h3>
&lt;p>Running a Kubernetes homelab means wearing many hats. Security scanning tools exist, but most people either:&lt;/p></description></item><item><title>Building a Kubernetes Security Reporter for Obsidian</title><link>https://blog.landryzetam.net/posts/kubernetes-security-reporter-obsidian/</link><pubDate>Wed, 17 Dec 2025 00:00:00 +0000</pubDate><guid>https://blog.landryzetam.net/posts/kubernetes-security-reporter-obsidian/</guid><description>&lt;p>What if your Kubernetes cluster could automatically write security reports directly into your second brain? Today I built exactly that—a system that runs CIS benchmark scans against my K3s cluster and publishes the results as beautifully formatted Obsidian notes. No more checking dashboards or parsing JSON files; just open your vault and see your cluster&amp;rsquo;s security posture.&lt;/p>
&lt;hr>
&lt;h2 id="part-1-the-problem">Part 1: The Problem&lt;/h2>
&lt;h3 id="security-visibility-in-a-homelab">Security Visibility in a Homelab&lt;/h3>
&lt;p>Running a Kubernetes homelab means wearing many hats: developer, operator, and security engineer. Tools like &lt;a href="https://github.com/aquasecurity/kube-bench">kube-bench&lt;/a> exist to scan your cluster against CIS benchmarks, but they typically output JSON or text that sits in a PersistentVolume gathering dust.&lt;/p></description></item><item><title>Enabling DNS-01 TLS for Internal Kubernetes Services</title><link>https://blog.landryzetam.net/posts/dns01-tls-kubernetes-internal-services/</link><pubDate>Tue, 16 Dec 2025 00:00:00 +0000</pubDate><guid>https://blog.landryzetam.net/posts/dns01-tls-kubernetes-internal-services/</guid><description>&lt;p>Ever visited a website and seen that little padlock icon in your browser? That&amp;rsquo;s TLS at work, encrypting the connection between you and the server. But what happens when you want that same security for services running on your home network that aren&amp;rsquo;t accessible from the internet? Today I solved this exact problem, and I want to walk you through not just &lt;em>how&lt;/em> I did it, but &lt;em>why&lt;/em> each piece matters.&lt;/p></description></item><item><title>Securing GitOps: SOPS Secret Management in k8s with FluxCD</title><link>https://blog.landryzetam.net/posts/secrets-management-with-sops-flux-gitops/</link><pubDate>Thu, 07 Aug 2025 00:00:00 +0000</pubDate><guid>https://blog.landryzetam.net/posts/secrets-management-with-sops-flux-gitops/</guid><description>&lt;h2 id="the-problem-secrets-in-gitops">The Problem: Secrets in GitOps&lt;/h2>
&lt;p>When I started my Kubernetes homelab journey, I quickly hit a wall that every GitOps practitioner faces: &lt;strong>How do you store secrets in Git without compromising security?&lt;/strong>&lt;/p>
&lt;p>The GitOps philosophy is beautifully simple - everything should be in Git. Your entire cluster state, all your applications, configurations, and yes, even secrets. But committing passwords, API keys, and certificates to a public (or even private) repository feels fundamentally wrong. It is wrong.&lt;/p></description></item></channel></rss>