<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on Ctrl &#43; Champagne</title>
    <link>/tags/security/</link>
    <description>Recent content in Security on Ctrl &#43; Champagne</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 16 Feb 2025 13:45:56 +0000</lastBuildDate>
    <atom:link href="/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Scan It Like You Mean It 🚀</title>
      <link>/posts/vulnscan/</link>
      <pubDate>Sun, 16 Feb 2025 13:45:56 +0000</pubDate>
      <guid>/posts/vulnscan/</guid>
      <description>&lt;h2 id=&#34;automated-vulnerability-scanning-for-dependencies--packages&#34;&gt;Automated Vulnerability Scanning for Dependencies &amp;amp; Packages&lt;/h2&gt;&#xA;&lt;h3 id=&#34;do-we-need-to-explain-why&#34;&gt;Do we need to explain why?&lt;/h3&gt;&#xA;&lt;p&gt;🔥💥💣🚨⚡☠️🧨&lt;/p&gt;&#xA;&lt;p&gt;That&amp;rsquo;s what I thought.&lt;/p&gt;&#xA;&lt;h3 id=&#34;configure-your-pipeline-with-snyk&#34;&gt;Configure your pipeline with Snyk&lt;/h3&gt;&#xA;&lt;p&gt;There is a plethora of tools available out there for security scans and/or vulnerable&#xA;dependencies - Dependabot, Trivy, sonarQube/Lint, Anchore, etc. Most of which can be&#xA;integrated into your IDE or CI/CD.&lt;/p&gt;&#xA;&lt;p&gt;For this use case, Snyk has been selected.&#xA;Snyk is able to scan code, open-source dependencies, container images, and infrastructure as code&#xA;configurations to helps developers prioritize and fix security vulnerabilities.&#xA;The free version comes with a max limit scans per month.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Automating Digital Certificates renewal</title>
      <link>/posts/digitcert/</link>
      <pubDate>Tue, 11 Feb 2025 13:45:56 +0000</pubDate>
      <guid>/posts/digitcert/</guid>
      <description>&lt;h2 id=&#34;kubernetes-cert-manager-for-letsencrypt-certificates&#34;&gt;Kubernetes cert-manager for LetsEncrypt certificates&lt;/h2&gt;&#xA;&lt;h3 id=&#34;digital-certificates-raison-dêtre-and-usage&#34;&gt;Digital Certificates raison d&amp;rsquo;être and usage&lt;/h3&gt;&#xA;&lt;p&gt;Certificates are exchanged as part of the TLS handshake.&#xA;This allows the client to ensure the entity it is trying to establish a connection with is authentically the &lt;em&gt;genuine&lt;/em&gt; server.&lt;/p&gt;&#xA;&lt;p&gt;Note: see other posts under this tag for a few words on TLS handshakes and mentions of the attacks it protects against.&lt;/p&gt;&#xA;&lt;p&gt;A certificate contains: the issuer details, its expiration date, the entity&amp;rsquo;s public key for asymmetric encryption and a signature (encrypted server&amp;rsquo;s public key).&lt;/p&gt;</description>
    </item>
    <item>
      <title>The QUICk brown fox jumps over the lazy dog</title>
      <link>/posts/quic/</link>
      <pubDate>Mon, 10 Feb 2025 13:45:56 +0000</pubDate>
      <guid>/posts/quic/</guid>
      <description>&lt;h2 id=&#34;the-fast-alternative-to-tcptls&#34;&gt;The &lt;em&gt;fast&lt;/em&gt; alternative to TCP+TLS&lt;/h2&gt;&#xA;&lt;h3 id=&#34;what-is-quic&#34;&gt;What is QUIC?&lt;/h3&gt;&#xA;&lt;p&gt;The Quick UDP Internet Connection (QUIC) protocol is an encrypted connection protocol operating on the Layer 4 - Transport Layer of the OSI model.&lt;/p&gt;&#xA;&lt;p&gt;Developed at Google around 2012, it has only been adopted as a standard by IETF in 2021.&lt;/p&gt;&#xA;&lt;p&gt;The current and widely used solution of HTTPS using TLS is built is on top of the TCP protocol.&#xA;The &lt;a href=&#34;https://en.wikipedia.org/wiki/Transmission_Control_Protocol&#34;&gt;TCP handshake&lt;/a&gt; and the &lt;a href=&#34;https://en.wikipedia.org/wiki/Transport_Layer_Security&#34;&gt;TLS handshake&lt;/a&gt; need to be completed to establish a path to communicate between a server and a client.&#xA;As a result, multiple rounds trips to initiate a connection and negotiate the encryption parameters are required - two at the very least, depending on the TLS version used.&lt;/p&gt;</description>
    </item>
    <item>
      <title>HSTS &amp; .dev domain</title>
      <link>/posts/hsts/</link>
      <pubDate>Sat, 08 Feb 2025 13:45:56 +0000</pubDate>
      <guid>/posts/hsts/</guid>
      <description>&lt;h2 id=&#34;a-brief-overview-of-hsts-protocol-or-why-i-chose-the-dev-domain&#34;&gt;A brief overview of HSTS protocol or why I chose the .dev domain&lt;/h2&gt;&#xA;&lt;h3 id=&#34;quick-intro&#34;&gt;Quick intro&lt;/h3&gt;&#xA;&lt;p&gt;What happens when you&amp;rsquo;re back from a family weekend in a cabin in the woods with no internet?&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;d probably check my dog&amp;rsquo;s instagram account first.&#xA;On the browser: instagram.com and &amp;hellip; my browser is making a call to &lt;code&gt;http://instagram.com&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;Exactly! I haven&amp;rsquo;t explicitly used &lt;code&gt;https&lt;/code&gt;, so where does this leave me? Exposed to all sorts of man-in-the-middle attacks that wikipedia can list for us in a scary way - &lt;a href=&#34;https://en.wikipedia.org/wiki/Session_hijacking%22&#34;&gt;session hijacking&lt;/a&gt;, &lt;a href=&#34;https://en.wikipedia.org/wiki/Downgrade_attack&#34;&gt;protocol downgrade attack&lt;/a&gt;, etc.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
