<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Push Protection on Romano Roth</title><link>https://romanoroth.com/en/tags/push-protection/</link><description>Recent content in Push Protection on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Tue, 14 Feb 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/push-protection/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub DevSecOps Part 7: Finding Secrets in Your Code with Secret Scanning</title><link>https://romanoroth.com/en/blogs/github-devsecops-secret-detection/</link><pubDate>Tue, 14 Feb 2023 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/github-devsecops-secret-detection/</guid><description>&lt;p>API keys, tokens, and passwords still leak into repositories all the time — sometimes by accident, sometimes by a developer who genuinely did not know better. In Part 7 of our GitHub DevSecOps series, Patrick Steger and I switch on GitHub&amp;rsquo;s built-in Secret Scanning, add a custom pattern of our own, try out push protection, and look honestly at what the feature finds and where it falls short.&lt;/p></description></item></channel></rss>