<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Input Validation on Nalar</title>
    <link>https://nalar.dev/tags/input-validation/</link>
    <description>Recent content in Input Validation on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/input-validation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Secure File Upload Handling</title>
      <link>https://nalar.dev/secure-file-upload-handling/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/secure-file-upload-handling/</guid>
      <description>&lt;p&gt;File uploads cross a security boundary. A file supplied by a user may have a misleading name, unexpected content, excessive size, malicious active content, or a structure designed to exploit the software that processes it.&lt;/p&gt;&#xA;&lt;p&gt;Secure upload handling therefore requires more than checking a filename extension. Treat every uploaded file as untrusted until the application has validated, stored, processed, and served it according to an explicit policy.&lt;/p&gt;&#xA;&lt;h2 id=&#34;start-with-a-narrow-upload-policy&#34;&gt;Start with a narrow upload policy&lt;/h2&gt;&#xA;&lt;p&gt;Define what the feature actually needs to accept. An avatar service may need only a small set of image formats, while a document workflow may need PDF files and nothing else.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
