<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kroxylicious on PeterMendis</title>
    <link>https://cloud-connect.ca/tags/kroxylicious/</link>
    <description>Recent content in Kroxylicious on PeterMendis</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2025, Peter Mendis; all rights reserved.</copyright>
    <lastBuildDate>Sun, 08 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cloud-connect.ca/tags/kroxylicious/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Encrypting Data at Rest for Kafka Workloads with Kroxylicious</title>
      <link>https://cloud-connect.ca/post/kroxylicious-kafka-encryption-at-rest/</link>
      <pubDate>Sun, 08 Nov 2026 00:00:00 +0000</pubDate>
      
      <guid>https://cloud-connect.ca/post/kroxylicious-kafka-encryption-at-rest/</guid>
      <description>
        
          
            &lt;p&gt;In enterprise event streaming, securing data at rest is a non-negotiable compliance requirement. Whether adhering to PCI-DSS, HIPAA, or strict financial industry mandates, organizations must guarantee that sensitive data stored within Apache Kafka cannot be accessed by unauthorized parties.&lt;/p&gt;
&lt;p&gt;However, standard storage-level encryption leaves significant blind spots, and client-side encryption is notoriously hard to scale across polyglot microservice architectures.&lt;/p&gt;
&lt;p&gt;This is where &lt;strong&gt;Kroxylicious&lt;/strong&gt; enters the picture. In this post, we will explore how Kroxylicious leverages protocol-aware proxying to provide transparent, envelope-based encryption at rest for Kafka workloads.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>
