<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Secret-Detection on Software Factory</title><link>/tags/secret-detection/</link><description>Recent content in Secret-Detection on Software Factory</description><generator>Hugo</generator><language>en</language><atom:link href="/tags/secret-detection/index.xml" rel="self" type="application/rss+xml"/><item><title>Secret Detection</title><link>/use/tools/gitlab/secure/secret-detection/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/use/tools/gitlab/secure/secret-detection/</guid><description>&lt;div style="display: flex; align-items: flex-start; gap: 1.5rem; margin-bottom: 1rem; max-width: 80%;"&gt;
 &lt;img src="/logo/gitlab.svg" alt="GitLab logo"
 width="100"
 style="flex-shrink: 0;"&gt;
 &lt;div&gt;&lt;p&gt;Code may use secrets to integrate with external services, such as webservices or databases.
These secrets can take various forms, including passwords, API keys, and SSH keys.&lt;/p&gt;
&lt;p&gt;If this sensitive information is committed to a source code repository,
it may become accessible to anyone who accesses the repository, posing a significant security risk.&lt;/p&gt;
&lt;p&gt;To mitigate this risk, GitLab provides a Secret Detection tool that scans your codebase for sensitive
information (check [full list of supported secret types]) and alerts you to potential security issues.&lt;/p&gt;</description></item></channel></rss>