<?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>Secrets-Management on Joshua Antony | Tech Blog</title><link>https://blogs.joshuaantony.com/tags/secrets-management/</link><description>Recent content in Secrets-Management on Joshua Antony | Tech Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 11 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blogs.joshuaantony.com/tags/secrets-management/index.xml" rel="self" type="application/rss+xml"/><item><title>The Day I Realized Every Developer Could Read Prod DB Credentials: A Microservices Migration Story</title><link>https://blogs.joshuaantony.com/posts/monolith-vs-microservices-secrets-exposure/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://blogs.joshuaantony.com/posts/monolith-vs-microservices-secrets-exposure/</guid><description>In the ATG monolith, production DB credentials lived behind a JBoss SSH gate — effectively unreachable without infra access. After modernizing to microservices on Azure Kubernetes, every developer&amp;rsquo;s Azure account could read prod DB, Redis, and Service Bus secrets from Key Vault with a single CLI command. VPN and device whitelisting gated the network path, but not the humans. The migration didn&amp;rsquo;t just change our architecture — it quietly widened the insider blast radius.</description></item></channel></rss>