<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Containers on r4x7&#39;s Blog</title>
    <link>https://r4x7.pages.dev/en/categories/containers/</link>
    <description>Recent content in Containers on r4x7&#39;s Blog</description>
    <generator>Hugo -- 0.154.5</generator>
    <language>en</language>
    <lastBuildDate>Wed, 01 Apr 2026 18:00:00 +0200</lastBuildDate>
    <atom:link href="https://r4x7.pages.dev/en/categories/containers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>k8sAudit - Automated scanner of Kubernetes cluster</title>
      <link>https://r4x7.pages.dev/en/posts/tools/k8s-audit-tool/</link>
      <pubDate>Wed, 01 Apr 2026 18:00:00 +0200</pubDate>
      <guid>https://r4x7.pages.dev/en/posts/tools/k8s-audit-tool/</guid>
      <description>&lt;h3 id=&#34;introduction&#34;&gt;Introduction&lt;/h3&gt;
&lt;p&gt;&lt;code&gt;k8s_audit.py&lt;/code&gt; is a security auditing tool for Kubernetes clusters focused on misconfiguration enumeration and penetration testing in containerised environments. All operations are strictly read-only: the tool never modifies cluster state, making it safe to run against production environments without risk of disruption or unintended side effects.&lt;/p&gt;
&lt;p&gt;The tool is organised into twelve independent audit modules, each targeting a specific attack surface within a Kubernetes cluster. Modules can be run individually or in any combination, allowing the scope of the audit to be tailored to the specific needs of each environment. The available modules are:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Manual enumeration of a Kubernetes cluster with kubectl</title>
      <link>https://r4x7.pages.dev/en/posts/linux/kubernetes-pentesting/</link>
      <pubDate>Sun, 01 Mar 2026 18:00:00 +0100</pubDate>
      <guid>https://r4x7.pages.dev/en/posts/linux/kubernetes-pentesting/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;When auditing a Kubernetes cluster for the first time, whether as part of an internal pentesting exercise, a configuration review, or simply to understand what is running in production, most of the real problems do not show up in fancy automated scanners but in patient reading of the cluster state. Excessive permissions, privileged containers nobody remembers deploying, secrets in environment variables, TLS certificates about to expire, and &lt;code&gt;hostPath&lt;/code&gt; volumes mounting sensitive node paths are recurring findings that anyone can detect with &lt;code&gt;kubectl&lt;/code&gt; and a bit of method.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
