<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Canonicalization on Nalar</title>
    <link>https://nalar.dev/tags/canonicalization/</link>
    <description>Recent content in Canonicalization on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/canonicalization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Normalize Security-Sensitive Input Before Making Decisions</title>
      <link>https://nalar.dev/normalize-security-sensitive-input-before-making-decisions/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/normalize-security-sensitive-input-before-making-decisions/</guid>
      <description>&lt;p&gt;Security checks often compare names, paths, identifiers, hosts, or other values against a rule. The rule may be correct and the comparison may look correct, yet the system can still make the wrong decision if different components interpret the same input differently.&lt;/p&gt;&#xA;&lt;p&gt;For example, one layer may treat two textual forms as equivalent while another treats them as different. A validator can approve one representation, then a later component can normalize or decode it into a different value before using it. The security check and the operation are no longer reasoning about the same thing.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
