<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitLeaks on Romano Roth</title><link>https://romanoroth.com/en/tags/gitleaks/</link><description>Recent content in GitLeaks on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Wed, 28 Sep 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/gitleaks/index.xml" rel="self" type="application/rss+xml"/><item><title>GitLab DevSecOps Part 7: Finding Secrets in Your Code with Secret Detection</title><link>https://romanoroth.com/en/blogs/gitlab-devsecops-secret-detection/</link><pubDate>Wed, 28 Sep 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-devsecops-secret-detection/</guid><description>&lt;p>Hard-coded passwords and API keys are still one of the most common ways credentials leak. They get committed by accident, stay in the git history forever, and only show up when someone is already exploiting them. In Part 7 of our GitLab DevSecOps series, Patrick Steger and I add Secret Detection to the same pipeline we have been growing — one line of YAML — and then look at what GitLeaks actually finds, what it quietly misses, and what to do about it.&lt;/p></description></item></channel></rss>