<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Session Security on Nalar</title>
    <link>https://nalar.dev/tags/session-security/</link>
    <description>Recent content in Session Security 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/session-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Harden Authenticated Sessions Against Hijacking</title>
      <link>https://nalar.dev/harden-authenticated-sessions-against-hijacking/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/harden-authenticated-sessions-against-hijacking/</guid>
      <description>&lt;p&gt;Authentication does not end when a password, passkey, or second factor is accepted. After login, most applications represent the user&amp;rsquo;s authenticated state with a session credential. Anyone who obtains that credential may be able to act as the user without repeating the original authentication.&lt;/p&gt;&#xA;&lt;p&gt;Session security therefore depends on protecting the credential throughout its lifecycle: creation, transport, use, rotation, expiration, and revocation.&lt;/p&gt;&#xA;&lt;h2 id=&#34;treat-the-session-identifier-as-a-credential&#34;&gt;Treat the session identifier as a credential&lt;/h2&gt;&#xA;&lt;p&gt;A session identifier should be unpredictable and generated with a cryptographically secure random generator. It should not encode sequential database IDs, timestamps, usernames, or other values an attacker can infer.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
