<?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 Patoune-IT</title><link>https://www.patoune-it.fr/en/tags/security/</link><description>Recent content in Security on Patoune-IT</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 28 May 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://www.patoune-it.fr/en/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Shortening patch cycles: why 48h is no longer optional for critical CVEs</title><link>https://www.patoune-it.fr/en/mythos/2026-05-28-patch-cycles-48h/</link><pubDate>Thu, 28 May 2026 10:00:00 +0200</pubDate><guid>https://www.patoune-it.fr/en/mythos/2026-05-28-patch-cycles-48h/</guid><description>The most critical vulnerabilities are being exploited within hours. Here is how to restructure your patch cycles to respond in under 48 hours.</description></item><item><title>Connecting to an Azure database without direct access using socat and kubectl port-forward</title><link>https://www.patoune-it.fr/en/posts/2026-05-27-azure-db-kubectl-portforward/</link><pubDate>Wed, 27 May 2026 10:00:00 +0200</pubDate><guid>https://www.patoune-it.fr/en/posts/2026-05-27-azure-db-kubectl-portforward/</guid><description>&lt;p>In professional environments, Azure databases (PostgreSQL, MySQL, SQL Server…) are often exposed exclusively via a &lt;strong>Private Endpoint&lt;/strong>: they are only reachable within the Azure private network, with no public IP. The result: from your development workstation, it is impossible to connect directly using a client like DBeaver or &lt;code>psql&lt;/code>.&lt;/p>
&lt;p>However, the AKS cluster (Azure Kubernetes Service) running in the same VNet does have access. This guide explains how to leverage that fact to create a secure tunnel to the database, without modifying any network rules or opening a single public port.&lt;/p></description></item></channel></rss>