<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>KUBERNETES SECURITY - Aqua</title>
	<atom:link href="https://www.aquasec.com/category/kubernetes-security/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Cloud Native Security, Container Security &#38; Serverless Security</description>
	<lastBuildDate>Sun, 15 Jun 2025 15:50:21 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>What Gartner Wants Every CTO to Know About Kubernetes Security</title>
		<link>https://www.aquasec.com/blog/gartner-cto-top-10-to-know-container-kubernetes-security/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Mon, 16 Jun 2025 11:00:24 +0000</pubDate>
				<category><![CDATA[KUBERNETES SECURITY]]></category>
		<category><![CDATA[Container Security]]></category>
		<category><![CDATA[Kubernetes Security]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=25727</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/gartner-cto-top-10-to-know-container-kubernetes-security/" title="What Gartner Wants Every CTO to Know About Kubernetes Security" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2025/06/Social-blog-CTO-Guide-to-_Containers-Kubernetes-2.jpg" alt="What Gartner Wants Every CTO to Know About Kubernetes Security" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>In the new Gartner Top 10 FAQs for CTOs on container and Kubernetes infrastructure report, there’s a strategic planning assumption that “by 2029, more than 95% of global organizations will be running containerized applications in production, which is a significant increase from less than 50% in 2023.” So is that it? Will container and Kubernetes&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>The History of Kubernetes</title>
		<link>https://www.aquasec.com/blog/kubernetes-history-how-it-conquered-cloud-native-orchestration/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Thu, 25 Jul 2024 04:13:34 +0000</pubDate>
				<category><![CDATA[KUBERNETES SECURITY]]></category>
		<category><![CDATA[Kubernetes]]></category>
		<category><![CDATA[Kubernetes RBAC]]></category>
		<category><![CDATA[Kubernetes Security]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=21211</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/kubernetes-history-how-it-conquered-cloud-native-orchestration/" title="The History of Kubernetes" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2024/07/blog-main-history-of-kubernetes-1200x628-2024-final.jpg" alt="The History of Kubernetes" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>Did you know that Kubernetes originally had no built-in features for managing user permissions, or that support for storing data persistently didn&#8217;t appear until Kubernetes was four years old? If not, you might enjoy a dive into the history of Kubernetes on the tenth anniversary of the open source container orchestration system. This article highlights&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>Kubernetes Secrets: How to Create, Use, and Secure Them</title>
		<link>https://www.aquasec.com/blog/managing-kubernetes-secrets/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Mon, 15 Apr 2024 12:27:00 +0000</pubDate>
				<category><![CDATA[KUBERNETES SECURITY]]></category>
		<category><![CDATA[Kubernetes Security]]></category>
		<category><![CDATA[Secrets]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=15886</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/managing-kubernetes-secrets/" title="Kubernetes Secrets: How to Create, Use, and Secure Them" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2019/01/Kubernetes-Secrets-blog-FINAL.jpg" alt="Kubernetes Secrets: How to Create, Use, and Secure Them" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>If you deploy applications using Kubernetes – a platform that 96 percent of companies today report either using or considering – you&#8217;ll inevitably need to manage secrets securely inside Kubernetes. In some ways, this is a challenging task. Although Kubernetes provides some built-in capabilities to help manage secrets securely, these features have their limitations –&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>Introducing KBOM – Kubernetes Bill of Materials</title>
		<link>https://www.aquasec.com/blog/introducing-kbom-kubernetes-bill-of-materials/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Thu, 29 Jun 2023 08:57:48 +0000</pubDate>
				<category><![CDATA[KUBERNETES SECURITY]]></category>
		<category><![CDATA[Aqua Security]]></category>
		<category><![CDATA[Kubernetes]]></category>
		<category><![CDATA[Kubernetes Security]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=14376</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/introducing-kbom-kubernetes-bill-of-materials/" title="Introducing KBOM – Kubernetes Bill of Materials" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2023/06/Blog-Image-KBOM.jpg" alt="Introducing KBOM – Kubernetes Bill of Materials" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>SBOM (Software Bill of Materials) is an accepted best practice to map the components and dependencies of your applications in order to better understand your applications’ risks. SBOMs are used as a basis for vulnerability assessment, licensing compliance, and more. There are plenty of available tools, such as Aqua Trivy, that help you easily generate&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>Kubernetes Version 1.26: An Overview</title>
		<link>https://www.aquasec.com/blog/kubernetes-version-1-26-an-overview/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Thu, 08 Dec 2022 15:00:00 +0000</pubDate>
				<category><![CDATA[KUBERNETES SECURITY]]></category>
		<category><![CDATA[Kubernetes]]></category>
		<category><![CDATA[Kubernetes Security]]></category>
		<category><![CDATA[Vulnerability Management]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=14533</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/kubernetes-version-1-26-an-overview/" title="Kubernetes Version 1.26: An Overview" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2022/12/Blog-Image-Kubernetes-release-1.26.jpg" alt="Kubernetes Version 1.26: An Overview" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>Kubernetes Version 1.26 was released with 37 new enhancements including 11 Stable, 10 Beta, 16 Alpha, and 12 features deprecated or removed. In this blog, we will highlight its most notable features and show how using Trivy will help you find deprecated Kubernetes resources. registry.k8s.io, Generally Available The container image registry has changed from k8s.gcr.io&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>Securing Kubernetes Everywhere with EKS Anywhere (EKS-A) Bare Metal</title>
		<link>https://www.aquasec.com/blog/amazon-eks-anywhere/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Wed, 29 Jun 2022 12:45:00 +0000</pubDate>
				<category><![CDATA[KUBERNETES SECURITY]]></category>
		<category><![CDATA[AWS Security]]></category>
		<category><![CDATA[Kubernetes Security]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=14745</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/amazon-eks-anywhere/" title="Securing Kubernetes Everywhere with EKS Anywhere (EKS-A) Bare Metal" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2022/06/securing-eks-anywhere-launch-blog-image.jpg" alt="Securing Kubernetes Everywhere with EKS Anywhere (EKS-A) Bare Metal" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>With the release of Amazon EKS Anywhere (EKS-A) Bare Metal, Amazon Web Services has expanded the choices of infrastructure to deploy EKS Anywhere clusters using on-premise bare metal servers as a deployment target. In support of this, Aqua has worked to ensure that as customers adopt EKS Anywhere to automate Kubernetes cluster lifecycle management for&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>What’s New in Kubernetes Version 1.24</title>
		<link>https://www.aquasec.com/blog/kubernetes-1-24/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Mon, 25 Apr 2022 09:30:00 +0000</pubDate>
				<category><![CDATA[KUBERNETES SECURITY]]></category>
		<category><![CDATA[Kubernetes Security]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=14831</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/kubernetes-1-24/" title="What’s New in Kubernetes Version 1.24" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2022/04/04-22-Kubernetes-1.24-blog-image.jpg" alt="What’s New in Kubernetes Version 1.24" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>With another Kubernetes release upon us, there are, as ever, a load of new features to consider. These include features to help companies use Windows containers securely and improvements in Kubernetes’ supply chain security. In this post, we’ll take a look at some of the more significant features of this release. Dockershim deprecation Undoubtedly, the&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>Kubernetes RBAC: How to Avoid Privilege Escalation via Certificate Signing</title>
		<link>https://www.aquasec.com/blog/kubernetes-rbac-privilige-escalation/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Wed, 06 Apr 2022 09:30:00 +0000</pubDate>
				<category><![CDATA[KUBERNETES SECURITY]]></category>
		<category><![CDATA[Kubernetes RBAC]]></category>
		<category><![CDATA[Kubernetes Security]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=14889</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/kubernetes-rbac-privilige-escalation/" title="Kubernetes RBAC: How to Avoid Privilege Escalation via Certificate Signing" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2022/04/04-22-RBAC-CSR-API-privilege-escalation-blog-image.jpg" alt="Kubernetes RBAC: How to Avoid Privilege Escalation via Certificate Signing" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>Following on from our previous post on the risks of privilege escalation in Kubernetes via the node/proxy resource, we’re going to take a look at how users who have rights to the certificate signing request (CSR) API in Kubernetes might be able to use them to escalate their privileges in a cluster. In addition to&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>Privilege Escalation from Node/Proxy Rights in Kubernetes RBAC</title>
		<link>https://www.aquasec.com/blog/privilege-escalation-kubernetes-rbac/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Thu, 03 Mar 2022 11:30:00 +0000</pubDate>
				<category><![CDATA[KUBERNETES SECURITY]]></category>
		<category><![CDATA[Kubernetes RBAC]]></category>
		<category><![CDATA[Kubernetes Security]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=14960</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/privilege-escalation-kubernetes-rbac/" title="Privilege Escalation from Node/Proxy Rights in Kubernetes RBAC" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2022/03/03-22-RBAC-Node-Proxy-Rights-blog-image.jpg" alt="Privilege Escalation from Node/Proxy Rights in Kubernetes RBAC" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>One of the side effects of Kubernetes’ rich API and extensive functionality is that sometimes there are security implications to granting users permissions. Security architects should be aware of these side effects when designing platforms that use Kubernetes. In recent research with Iain Smart of NCC Group, we looked at how granting rights to node/proxy&#160;&mldr;]]></description>
		
		
		
			</item>
		<item>
		<title>Adopting Zero Trust in Kubernetes: The Fundamentals</title>
		<link>https://www.aquasec.com/blog/zero-trust-kubernetes/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Wed, 16 Feb 2022 12:55:59 +0000</pubDate>
				<category><![CDATA[CONTAINER SECURITY]]></category>
		<category><![CDATA[KUBERNETES SECURITY]]></category>
		<category><![CDATA[Container Security]]></category>
		<category><![CDATA[Kubernetes Security]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=14964</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/zero-trust-kubernetes/" title="Adopting Zero Trust in Kubernetes: The Fundamentals" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2022/02/02-22-Zero-trust-Kubernetes-blog-image.jpg" alt="Adopting Zero Trust in Kubernetes: The Fundamentals" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>In late January, the White House published a memo that lays the groundwork for creating a zero-trust architecture for federal agencies. With renewed attention from the US government, zero-trust networking is an area that many organizations are focusing on to improve their security posture. With that focus, it makes sense to understand where these principles&#160;&mldr;]]></description>
		
		
		
			</item>
	</channel>
</rss>
