<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security Headers on Nalar</title>
    <link>https://nalar.dev/tags/security-headers/</link>
    <description>Recent content in Security Headers 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/security-headers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Use HTTP Security Headers as Defense in Depth</title>
      <link>https://nalar.dev/use-http-security-headers-as-defense-in-depth/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/use-http-security-headers-as-defense-in-depth/</guid>
      <description>&lt;p&gt;HTTP security headers let a server tell browsers which security rules should apply to a response. They can restrict where content loads from, prevent MIME type guessing, reduce referrer leakage, and enforce encrypted transport.&lt;/p&gt;&#xA;&lt;p&gt;They are useful defense in depth, not a replacement for input validation, output encoding, authentication controls, or secure session handling. A strong header policy can limit the impact of some mistakes, but it cannot make an unsafe application secure by itself.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
