<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>PKI on Rameez's Website</title><link>https://rameezrehman408.github.io/tags/pki/</link><description>Recent content in PKI on Rameez's Website</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 29 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rameezrehman408.github.io/tags/pki/index.xml" rel="self" type="application/rss+xml"/><item><title>The Certificate Expiry Apocalypse: Why Manual TLS Management is a Security Anti-Pattern</title><link>https://rameezrehman408.github.io/posts/tls-automation-mandate/</link><pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate><guid>https://rameezrehman408.github.io/posts/tls-automation-mandate/</guid><description>Let’s be honest: if your deployment workflow still involves an engineer manually downloading a .crt, pasting it into a web server configuration, and praying to the gods of uptime that they don&amp;rsquo;t forget to do it again in 90 days&amp;hellip; you aren&amp;rsquo;t running a production environment. You are running a time bomb.
The industry is undergoing a massive compression in certificate lifespans. We’ve moved from years to months, and now—driven by the momentum of Let&amp;rsquo;s Encrypt and pressure from browser vendors (Apple, Google) favoring high-frequency rotation—we are rapidly approaching an era where 90-day lifespans will feel like an eternity.</description></item></channel></rss>