<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevSecOps on Prepakis Georgios | Kernelstub | Security Researcher</title><link>https://blog.kernelstub.dev/tags/devsecops/</link><description>Recent content in DevSecOps on Prepakis Georgios | Kernelstub | Security Researcher</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 12 Nov 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.kernelstub.dev/tags/devsecops/index.xml" rel="self" type="application/rss+xml"/><item><title>Comparing tfsec and Checkov for Hardening Infrastracture</title><link>https://blog.kernelstub.dev/posts/comparing-tfsec-and-checkov-for-hardening-infrastracture/</link><pubDate>Wed, 12 Nov 2025 00:00:00 +0000</pubDate><guid>https://blog.kernelstub.dev/posts/comparing-tfsec-and-checkov-for-hardening-infrastracture/</guid><description>&lt;h2 id="why-iac-hardening-matters"&gt;Why IaC Hardening Matters&lt;/h2&gt;
&lt;p&gt;Here&amp;rsquo;s the thing about infrastructure as code that makes it both wonderful and terrifying: once you write a mistake into a Terraform module, that mistake doesn&amp;rsquo;t stay put. It gets copied. A junior engineer finds your &lt;code&gt;s3-bucket&lt;/code&gt; module in the internal registry, sees it&amp;rsquo;s already &amp;ldquo;battle tested,&amp;rdquo; and reuses it in three more projects without reading past the variable names. If that module happened to leave logging disabled or granted a role &lt;code&gt;&amp;quot;*&amp;quot;&lt;/code&gt; on &lt;code&gt;&amp;quot;*&amp;quot;&lt;/code&gt;, you haven&amp;rsquo;t made one mistake, you&amp;rsquo;ve made a template for making that mistake forever.&lt;/p&gt;</description></item></channel></rss>