<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Trestle Articles</title>
    <link>https://trestlescan.com/articles/</link>
    <description>Guides on finding, fixing, and preventing leaked secrets: responding when a key leaks, how secret scanning works, and how Trestle can help.</description>
    <language>en</language>
    <lastBuildDate>Mon, 22 Jun 2026 01:00:00 GMT</lastBuildDate>
    <atom:link href="https://trestlescan.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>API key leak prevention: how to keep secrets out of your code</title>
      <link>https://trestlescan.com/articles/api-key-leak-prevention/</link>
      <guid isPermaLink="true">https://trestlescan.com/articles/api-key-leak-prevention/</guid>
      <description>A practical, vendor-neutral guide to API key leak prevention: why credentials leak, what it costs, and the layered defenses that stop secrets from escaping your codebase.</description>
      <category>Guide</category>
      <pubDate>Mon, 22 Jun 2026 01:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Four secret scanners compared on four codebases</title>
      <link>https://trestlescan.com/articles/secret-scanners-compared/</link>
      <guid isPermaLink="true">https://trestlescan.com/articles/secret-scanners-compared/</guid>
      <description>Trestle, Gitleaks, TruffleHog, and detect-secrets run with default settings over four public codebases. Every scanner catches an obvious API key. The differences show up with the secrets that don&apos;t look like secrets: hashed passwords, weak passwords, credit card numbers, and values that get sent to the browser.</description>
      <category>Tool comparison</category>
      <pubDate>Wed, 17 Jun 2026 01:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
