<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Injection Prevention on Nalar</title>
    <link>https://nalar.dev/tags/injection-prevention/</link>
    <description>Recent content in Injection Prevention 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/injection-prevention/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Keep Data Separate from Interpreter Syntax</title>
      <link>https://nalar.dev/keep-data-separate-from-interpreter-syntax/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/keep-data-separate-from-interpreter-syntax/</guid>
      <description>&lt;p&gt;Applications constantly move data into systems that interpret syntax: databases parse queries, shells parse commands, browsers parse HTML, and template engines parse expressions. A security problem appears when data that should remain inert can change the structure of those instructions.&lt;/p&gt;&#xA;&lt;p&gt;That is the core of &lt;strong&gt;injection&lt;/strong&gt;. If an attacker can influence where instructions end and data begins, the receiving interpreter may perform work the developer never intended. The consequence depends on the interpreter: unauthorized database operations, unintended operating-system actions, or active content in a browser are all possible outcomes of the same design mistake.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
