<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CSRF on Nalar</title>
    <link>https://nalar.dev/tags/csrf/</link>
    <description>Recent content in CSRF on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/csrf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Practical CSRF Defense with SameSite Cookies and Tokens</title>
      <link>https://nalar.dev/practical-csrf-defense-with-samesite-cookies-and-tokens/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/practical-csrf-defense-with-samesite-cookies-and-tokens/</guid>
      <description>&lt;p&gt;Cross-site request forgery (CSRF) abuses the fact that browsers can automatically attach a user&amp;rsquo;s cookies to requests. If a state-changing endpoint trusts only the presence of an authenticated cookie, another site may be able to trigger that endpoint from the user&amp;rsquo;s browser.&lt;/p&gt;&#xA;&lt;p&gt;Modern cookie controls reduce the attack surface, but robust applications still need to reason about request semantics and trust boundaries.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understand-the-condition-that-makes-csrf-possible&#34;&gt;Understand the condition that makes CSRF possible&lt;/h2&gt;&#xA;&lt;p&gt;A typical CSRF attack needs three ingredients:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
