<?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>Posts on rgxsec @ caravela</title><link>https://rgxsec.github.io/posts/</link><description>Recent content in Posts on rgxsec @ caravela</description><generator>Hugo -- 0.146.5</generator><language>en-us</language><lastBuildDate>Sat, 02 May 2026 17:05:17 +0100</lastBuildDate><atom:link href="https://rgxsec.github.io/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>IaC code security scanning pipeline - part 2</title><link>https://rgxsec.github.io/posts/iaccodesecscan2/</link><pubDate>Sat, 02 May 2026 17:05:17 +0100</pubDate><guid>https://rgxsec.github.io/posts/iaccodesecscan2/</guid><description>&lt;p>Back for the part two, where I will automate the security scanning of manually written IaC files, when these are pushed into a repository on github leveraging github worflows. I will go through some of the major security misconfigurations, existing threat vectors and solutions to mitigate them. Using semgrep for a specific scenario where other tools limitations hinder us.&lt;/p>
&lt;p>&lt;img alt="Cover" loading="lazy" src="https://rgxsec.github.io/posts/iaccodesecscan2/gemini.png">&lt;/p>
&lt;p>Code source: &lt;a href="https://github.com/rgxsec/marizaws-project">https://github.com/rgxsec/marizaws-project&lt;/a>&lt;/p>
&lt;h3 id="tools">Tools:&lt;/h3>
&lt;ul>
&lt;li>Checkov&lt;/li>
&lt;li>Trivy&lt;/li>
&lt;li>TruffleHog&lt;/li>
&lt;li>Semgrep&lt;/li>
&lt;/ul>
&lt;p>Each of this tools has its own special skill, &lt;strong>checkov&lt;/strong> speciality is to map misconfig findings to compliance standards like CIS AWS Benchmark, NIST, SOC2, PCI-DSS ect, besides having a very large library of built-in policies for Terraform; &lt;strong>trivy&lt;/strong> is more like a swiss army knife, it can scan anything, dockerfiles, container images, kubernetes manifests etc, it also links the findings to real CVEs and attack threats; &lt;strong>trufflehog&lt;/strong> is superb at looking and finding secrets and credentials in specific formats on IaC files and also in git history. &lt;strong>Semgrep&lt;/strong> highly customizable, rule based for each dedicated circunstance or problem.&lt;/p></description></item><item><title>RTF doc analysis</title><link>https://rgxsec.github.io/posts/rtfdocuanalysis1/</link><pubDate>Thu, 30 Oct 2025 08:30:39 +0000</pubDate><guid>https://rgxsec.github.io/posts/rtfdocuanalysis1/</guid><description>&lt;p>&lt;em>An attempt to lay path for rtf document analysis - Part 1&lt;/em>&lt;/p>
&lt;h3 id="lore-size-xs">Lore size xs&lt;/h3>
&lt;p>The purpose of its origin was to serve as a cross-platform text format between Macintosh and Windows systems, and was developed by Microsoft in 1987.&lt;/p>
&lt;p>I think the &lt;strong>rich&lt;/strong> part comes from the fact that RTF isn&amp;rsquo;t just a text document, it uses plain-text markup language commands, to embed objects (smirk) and to instruct applications (yes, multiple) on how data should be displayed, among few other things.&lt;/p></description></item><item><title>IaC code security testing tools</title><link>https://rgxsec.github.io/posts/iaccodesecscan/</link><pubDate>Sun, 11 May 2025 10:10:11 +0100</pubDate><guid>https://rgxsec.github.io/posts/iaccodesecscan/</guid><description>&lt;p>I decided to create this post since I was looking to cloud in a security perspective and noticed this would be a fun thing to try and get hands-on experience in CI\CD and the magical activity of Terraforming, uh seems so cool and wizardy.&lt;/p>
&lt;h3 id="objective">Objective&lt;/h3>
&lt;p>The objective is to create a &lt;strong>Terraform config file&lt;/strong> with &lt;strong>insecure&lt;/strong> configs on purpose. Test code security scanning tools, such as &lt;strong>checkov&lt;/strong> and &lt;strong>tfsec&lt;/strong> and then in a part 2 in the comming future, hopefully ;) time is an elusive thing, automate the process using CI\CD pipelines, something like &lt;strong>Github actions&lt;/strong>.&lt;/p></description></item></channel></rss>