<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>API Security on Nalar</title>
    <link>https://nalar.dev/tags/api-security/</link>
    <description>Recent content in API Security on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/api-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Store API Keys as Verifiers, Not Recoverable Secrets</title>
      <link>https://nalar.dev/store-api-keys-as-verifiers-not-recoverable-secrets/</link>
      <pubDate>Mon, 07 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/store-api-keys-as-verifiers-not-recoverable-secrets/</guid>
      <description>&lt;p&gt;An API key is often treated like a password: a client presents a secret string, and the server decides whether that string represents an authorized caller. Yet many systems store API keys in plaintext because the application needs to compare them later.&lt;/p&gt;&#xA;&lt;p&gt;That design creates an avoidable consequence. If an attacker obtains the credential database, every stored plaintext key may immediately become a usable credential. The database leak becomes an authentication compromise as well as a data leak.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
