<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>Trestle Articles</title>
  <subtitle>Guides on finding, fixing, and preventing leaked secrets: responding when a key leaks, how secret scanning works, and how Trestle can help.</subtitle>
  <link href="https://trestlescan.com/atom.xml" rel="self" />
  <link href="https://trestlescan.com/articles/" />
  <id>https://trestlescan.com/articles/</id>
  <updated>2026-06-22T01:00:00.000Z</updated>
  <author><name>Trestle</name><uri>https://trestlescan.com/</uri></author>
  <entry>
    <title>API key leak prevention: how to keep secrets out of your code</title>
    <link href="https://trestlescan.com/articles/api-key-leak-prevention/" />
    <id>https://trestlescan.com/articles/api-key-leak-prevention/</id>
    <published>2026-06-22T01:00:00.000Z</published>
    <updated>2026-06-22T01:00:00.000Z</updated>
    <summary>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.</summary>
    <category term="Guide" />
  </entry>
  <entry>
    <title>Four secret scanners compared on four codebases</title>
    <link href="https://trestlescan.com/articles/secret-scanners-compared/" />
    <id>https://trestlescan.com/articles/secret-scanners-compared/</id>
    <published>2026-06-17T01:00:00.000Z</published>
    <updated>2026-06-17T01:00:00.000Z</updated>
    <summary>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.</summary>
    <category term="Tool comparison" />
  </entry>
</feed>
