<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>DevOps on Ctrl &#43; Champagne</title>
    <link>/tags/devops/</link>
    <description>Recent content in DevOps 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/devops/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>
  </channel>
</rss>
