<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CVE-2026-47237 – Overly Permissive Istio Permissions Allow Kubeflow Authorization Token Stealing</title>
      <link>https://insinuator.net/2026/05/cve-2026-47237-overly-permissive-istio-permissions-allow-kubeflow-authorization-token-stealing/</link>
      <pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/05/cve-2026-47237-overly-permissive-istio-permissions-allow-kubeflow-authorization-token-stealing/</guid>
      <description>&lt;p&gt;Kubeflow is vulnerable to the theft of authorization tokens by any user of the&#xA;Kubeflow UI or APIs, such as the Dashboard, Pipelines API, or Notebooks. With&#xA;this token, the attacker can take over the user&amp;rsquo;s account and the data that is&#xA;processed by that user. The attacker needs a valid user with the &lt;code&gt;kubeflow-edit&lt;/code&gt;&#xA;or Contributor role in a random Kubeflow namespace to perform this attack. This&#xA;is given if &lt;em&gt;Automatic Profile Creation&lt;/em&gt; is enabled. A setup based on the&#xA;official manifests prior to version 1.10, and on most other packaged Kubeflow&#xA;distributions, is vulnerable.&lt;/p&gt;&#xA;&lt;p&gt;The Istio edit permissions were removed by Kubeflow in a timely manner. Affected&#xA;users should update to the latest version to mitigate this issue.&lt;/p&gt;</description>
    </item>
    <item>
      <title>KubeCon &#43; CloudNativeCon Europe 2026</title>
      <link>https://insinuator.net/2026/04/kubecon--cloudnativecon-europe-2026/</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/04/kubecon--cloudnativecon-europe-2026/</guid>
      <description>&lt;p&gt;Exactly one week ago, Sven and I had the incredible opportunity to give our very&#xA;first talk at KubeCon + CloudNativeCon&#xA;2026: &lt;a href=&#34;https://kccnceu2026.sched.com/event/2CW2U/how-to-break-multi-tenancy-again-and-again-and-what-we-can-learn-from-it-lorin-lehawany-sven-nobis-ernw?iframe=no&amp;amp;w=100%25&amp;amp;sidebar=yes&amp;amp;bg=no&#34;&gt;How To Break Multi-Tenancy Again and Again …and What We Can Learn From It&lt;/a&gt;.&#xA;We discussed the challenges of namespace-based multi-tenancy and presented&#xA;real-world exploits in&#xA;Kubeflow, &lt;a href=&#34;https://insinuator.net/2026/03/security-considerations-on-istios-crds-with-namespace-based-multi-tenancy/&#34;&gt;Istio&lt;/a&gt;,&#xA;and Traefik that bypass threat boundaries between namespaces and workloads.&#xA;Based on these problems, we developed a methodology to assess and address them.&#xA;You can find the methodology discussed in the talk in&#xA;detail &lt;a href=&#34;https://insinuator.net/2026/03/methodology-for-assessing-namespace-based-multi-tenancy-setups/&#34;&gt;in another blog post&lt;/a&gt; or&#xA;on &lt;a href=&#34;https://github.com/ernw/k8s-multi-tenancy&#34;&gt;GitHub&lt;/a&gt;. You can also find the&#xA;slides &lt;a href=&#34;https://github.com/ernw/k8s-multi-tenancy/blob/main/Slides%20-%20How%20To%20Break%20Multi-Tenancy%20Again%20and%20Again%20...and%20What%20We%20Can%20Learn%20From%20It-%20KubeCon%20+%20CloudNativeCon%20Europe%202026%20-%20final.pdf&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Methodology for Assessing Kubernetes Namespace-Based Multi-Tenancy Setups</title>
      <link>https://insinuator.net/2026/03/methodology-for-assessing-kubernetes-namespace-based-multi-tenancy-setups/</link>
      <pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/03/methodology-for-assessing-kubernetes-namespace-based-multi-tenancy-setups/</guid>
      <description>&lt;p&gt;This page introduces our structured methodology for assessing security risks in&#xA;Kubernetes environments that use Namespace-based Multi-Tenancy. It addresses&#xA;weaknesses that break Namespace-based isolation that not well studied, yet. We&#xA;found this issues during our research and presented them together with this&#xA;methodology in our&#xA;&lt;a href=&#34;https://kccnceu2026.sched.com/event/2CW2U/how-to-break-multi-tenancy-again-and-again-and-what-we-can-learn-from-it-lorin-lehawany-sven-nobis-ernw?iframe=yes&amp;amp;w=100%25&amp;amp;sidebar=yes&amp;amp;bg=no&#34;&gt;Talk at KubeCon + CloudNativeCon Europe 2026&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The methodology assumes that industry best practices, such as NetworkPolicies,&#xA;Role-Based Access Control (RBAC), and Pod Security Standards, are already in&#xA;place. These measures provide a necessary baseline level of protection against&#xA;well-known isolation threats. However, they are insufficient to address a class&#xA;of more subtle attack vectors arising from interactions between tenants and&#xA;shared components. Such attack vectors may still compromise the confidentiality,&#xA;integrity, and availability (CIA) of the cluster and its workloads, even in&#xA;well-hardened environments.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Considerations on Istio’s CRDs with Namespace-based Multi-Tenancy</title>
      <link>https://insinuator.net/2026/03/security-considerations-on-istios-crds-with-namespace-based-multi-tenancy/</link>
      <pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/03/security-considerations-on-istios-crds-with-namespace-based-multi-tenancy/</guid>
      <description>&lt;p&gt;We reported a possible Man-in-the-Middle (MitM) attack scenario in which&#xA;a &lt;code&gt;VirtualService&lt;/code&gt; can redirect or intercept traffic within the service mesh.&#xA;This affects Namespace-based Multi-Tenancy clusters where tenants have the&#xA;permissions to deploy Istio resources (&lt;code&gt;networking.istio.io/v1&lt;/code&gt;).&lt;/p&gt;&#xA;&lt;p&gt;In collaboration with Istio, we&#xA;published &lt;a href=&#34;https://istio.io/latest/blog/2026/security-considerations-on-namespace-based-multi-tenancy/&#34;&gt;a guest submission in Istio’s blog&lt;/a&gt; (as&#xA;well as below),&#xA;a &lt;a href=&#34;https://istio.io/latest/news/security/istio-security-2026-002/&#34;&gt;Security Bulletin&lt;/a&gt;,&#xA;and an update to&#xA;their &lt;a href=&#34;https://istio.io/latest/docs/ops/deployment/security-model/#k8s-account-compromise&#34;&gt;Security Model&lt;/a&gt; to&#xA;address this issue.&lt;/p&gt;&#xA;&lt;p&gt;This blog post highlights the risks of using Istio in multi-tenant clusters and&#xA;explains how users can mitigate these risks and safely operate Istio in their&#xA;deployments.&lt;/p&gt;</description>
    </item>
    <item>
      <title>TROOPERS20 Training Teaser: Swim with the whales – Docker, DevOps &amp;amp; Security in Enterprise Environments</title>
      <link>https://insinuator.net/2019/12/troopers20-training-teaser-swim-with-the-whales-docker-devops-amp-security-in-enterprise-environments/</link>
      <pubDate>Mon, 02 Dec 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/12/troopers20-training-teaser-swim-with-the-whales-docker-devops-amp-security-in-enterprise-environments/</guid>
      <description>&lt;p&gt;Containerization dominates the market nowadays. Fancy buzzwords like continuous integration/deployment/delivery, microservices, containers, DevOps are floating around, but what do they mean? What benefits do they offer compared to the old dogmas? You’re gonna find out in our training!&lt;/p&gt;&#xA;&lt;p&gt;We are going to start with the basics of Docker, Containers and DevOps, but soon you’ll end up with your own applications running inside containers with the images residing in your own registry. Of course, following the microservices approach, and the second day hasn’t even started.After the fundamental topics of containerization are understood, you’re going to create and operate your own Kubernetes cluster. A lot of fun and challenging exercises lie ahead, to give you hands-on experience with all the technologies.&lt;/p&gt;</description>
    </item>
    <item>
      <title>DevSecCon19 London – How to Secure OpenShift Environments and What Happens If You Don´t</title>
      <link>https://insinuator.net/2019/11/devseccon19-london-how-to-secure-openshift-environments-and-what-happens-if-you-dont/</link>
      <pubDate>Tue, 19 Nov 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/11/devseccon19-london-how-to-secure-openshift-environments-and-what-happens-if-you-dont/</guid>
      <description>&lt;p&gt;This week I was at &lt;a href=&#34;https://www.devseccon.com/london-2019/&#34;&gt;DevSecCon in London&lt;/a&gt; to present my current research on Red Hat OpenShift. In this talk, I gave a brief introduction to OpenShift, demonstrated some threats that exist for such environments, and dived into different configuration issues that may affect the security of OpenShift environments. The implications of misconfigurations of such an environment have been shown in live demos.&lt;/p&gt;&#xA;&lt;p&gt;You can find the slides for my talk here.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Catching fire with Docker, DevOps &amp;amp; Security in Enterprise Environments</title>
      <link>https://insinuator.net/2019/01/catching-fire-with-docker-devops-amp-security-in-enterprise-environments/</link>
      <pubDate>Fri, 04 Jan 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/01/catching-fire-with-docker-devops-amp-security-in-enterprise-environments/</guid>
      <description>&lt;p&gt;Docker has become the go-to technology in enterprise- and DevOps contexts. Yet, before mastering a skill, there is the thumb rule: one must learn the basics to have solid fundament before building a house on top.&lt;/p&gt;&#xA;&lt;p&gt;Simon and I start from the very beginning. We introduce you to the fundamental concepts of containers starting at process isolation and extending our tour to the whole ecosystem of Docker and further associated technologies. We will cover Docker, microservices, containers, DevOps, continuous integration/deployment/delivery – all those fancy buzzwords that can be read in the context of modern software development methodologies.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
