<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubescape on Landry Zetam - Tech Blog</title><link>https://blog.landryzetam.net/tags/kubescape/</link><description>Recent content in Kubescape on Landry Zetam - Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 19 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.landryzetam.net/tags/kubescape/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>