<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sast on Danilo Falcão da Silva</title><link>https://falcao.org/tags/sast/</link><description>Recent content in Sast on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 22 May 2026 10:00:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/sast/index.xml" rel="self" type="application/rss+xml"/><item><title>Replacing Snyk with Open Source: SAST, DAST and SCA in 2026</title><link>https://falcao.org/posts/open-source-sast-dast-sca-2026/</link><pubDate>Fri, 22 May 2026 10:00:00 -0300</pubDate><guid>https://falcao.org/posts/open-source-sast-dast-sca-2026/</guid><description>&lt;p>I don&amp;rsquo;t pay for Snyk. Not because it&amp;rsquo;s bad — it&amp;rsquo;s a genuinely good
product — but because there is a free stack that catches the vast
majority of the same issues directly in CI, and the remaining gap
hasn&amp;rsquo;t been worth roughly &lt;strong>$600 per developer per year&lt;/strong> to close.
On a team of fifteen engineers, that&amp;rsquo;s the price of a small EC2
fleet you actually need.&lt;/p>
&lt;p>This post is about the open-source security tooling I actually wire
into pipelines: &lt;strong>Trivy&lt;/strong> for containers, dependencies and IaC,
&lt;strong>Semgrep&lt;/strong> for application code, &lt;strong>Nuclei&lt;/strong> and &lt;strong>OWASP ZAP&lt;/strong> for
the live app, and a few honourable mentions. It&amp;rsquo;s not an exhaustive
catalogue. It&amp;rsquo;s the stack I keep coming back to.&lt;/p></description></item></channel></rss>