<?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>Security on Shubham Singh</title>
    <link>https://1shubham7.blog/tags/security/</link>
    <description>Recent content in Security on Shubham Singh</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://1shubham7.blog/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What I Learned Reading All 71 Articles of the Cyber Resilience Act</title>
      <link>https://1shubham7.blog/what-i-learned-reading-the-cyber-resilience-act/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/what-i-learned-reading-the-cyber-resilience-act/</guid>
      <description>I read the whole of Regulation (EU) 2024/2847, every article and every annex, and mapped KubeAid and LinuxAid against it for my employer. These are the things that surprised me, the mental model I ended up with, and what I would tell the next engineer who has to do the same reading.</description>
    </item>
    
    <item>
      <title>CiliumNetworkPolicy Anti-Patterns: 8 Ways Correct-Looking YAML Silently Drops Traffic</title>
      <link>https://1shubham7.blog/cnp-antipatterns/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/cnp-antipatterns/</guid>
      <description>Lessons from writing CiliumNetworkPolicies for the KubeAid-addons chart - toServices port traps, labels Cilium ignores, toFQDNs without a DNS rule, default-deny surprises, and why every namespace needs exactly one default-deny.</description>
    </item>
    
    <item>
      <title>Site Reliability Engineer (Obmondo)</title>
      <link>https://1shubham7.blog/experience/obmondo/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/experience/obmondo/</guid>
      <description>Outline Worked as an SRE, handling production systems and managing Kubernetes clusters and Linux servers across both internal and customer environments. As the youngest SRE at Obmondo, regularly took ownership of production alerts and incidents, performing root cause analysis and implementing long-term fixes. Led the rewrite of the most business-critical internal tool, improving its reliability, testing, and integration into GitOps workflows. Authored and improved a large part of the company’s ISMS, strengthening both the company’s and customers’ information security.</description>
    </item>
    
    <item>
      <title>Kubernetes Audit Logging: Stages, Levels, and Policy Design</title>
      <link>https://1shubham7.blog/audit-logging/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/audit-logging/</guid>
      <description>A breakdown of how kube-apiserver audit events actually work - request stages, audit levels, writing policies, and how SREs tune them differently for prod vs dev clusters.</description>
    </item>
    
    <item>
      <title>Getting Started with CISO Assistant on Kubernetes</title>
      <link>https://1shubham7.blog/ciso-assisstant/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/ciso-assisstant/</guid>
      <description>Deploying CISO Assistant via Helm, creating your first superuser, adding users, and how evidence storage actually works.</description>
    </item>
    
  </channel>
</rss>
