<?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>Dast on My Blog</title><link>https://hugo-blog.aitbytes.dev/tags/dast/</link><description>Recent content in Dast on My Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 11 Jun 2026 07:00:00 +0000</lastBuildDate><atom:link href="https://hugo-blog.aitbytes.dev/tags/dast/index.xml" rel="self" type="application/rss+xml"/><item><title>What GitLab Ultimate's Security Scanners Can and Can't Catch</title><link>https://hugo-blog.aitbytes.dev/posts/2026-06-11-gitlab-security-scanners-reality/</link><pubDate>Thu, 11 Jun 2026 07:00:00 +0000</pubDate><guid>https://hugo-blog.aitbytes.dev/posts/2026-06-11-gitlab-security-scanners-reality/</guid><description>&lt;p&gt;There&amp;rsquo;s a specific kind of disappointment that happens the first time a security team runs GitLab Ultimate&amp;rsquo;s built-in scanners against an application they&amp;rsquo;ve been hardening with Fortify for three years.&lt;/p&gt;
&lt;p&gt;The scanner reports clean. The security team knows the application has edge cases. The scanner just can&amp;rsquo;t find them.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s not a bug. It&amp;rsquo;s a category error. And if you&amp;rsquo;re evaluating GitLab Ultimate&amp;rsquo;s security features, understanding this distinction is the difference between a tool that meaningfully improves your security posture and one that generates false confidence.&lt;/p&gt;</description></item></channel></rss>