Kubernetes

Introduction

I’m excited to share that I’ve been accepted into the AWS Community Builders program for the 2026 cohort in the Security category. For me, this is a natural next step after becoming a Wazuh Ambassador - another milestone in a journey that has always been centered around open-source security and cloud infrastructure.

I’m excited to announce that I have officially joined the Wazuh Ambassador Program. This is a significant milestone in my journey with open-source security, and I’m honored to represent and contribute to a platform that has become central to my professional work.

My Journey with Wazuh

My path with host-based intrusion detection started long before Wazuh existed – with OSSEC, its predecessor. When Wazuh emerged as a fork and began evolving into the comprehensive security platform it is today, I transitioned along with it. That was over 10 years ago, and Wazuh has been an integral part of my security infrastructure work ever since.

Introduction

Navigating the world of compliance can feel like trying to read a map in a language you don’t speak. When you throw Kubernetes into the mix, it gets even trickier. That’s why we’ve put together this straightforward, human-friendly checklist to help you get your Amazon EKS clusters ready for a SOC 2 Type II audit.

Moving on, let’s look at the other controls for EKS SOC Type 2.

For container security best practices, see our guide on Container Image Security with Wazuh and Trivy.

CC3: Risk Assessment

EKS-Specific Risk Assessment

Identify, evaluate, and document security, operational, and compliance risks specific to Amazon EKS clusters and workloads to ensure that appropriate controls are implemented, monitored, and improved in alignment with SOC 2 Trust Services Criteria.

Professional Summary

Senior Site Reliability Engineer with 14+ years building, scaling, and maintaining critical infrastructure across diverse technology environments.