<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Identity Security on Nalar</title>
    <link>https://nalar.dev/tags/identity-security/</link>
    <description>Recent content in Identity Security on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 06 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/identity-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Review Access Before Privileges Become Permanent</title>
      <link>https://nalar.dev/review-access-before-privileges-become-permanent/</link>
      <pubDate>Sun, 06 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/review-access-before-privileges-become-permanent/</guid>
      <description>&lt;p&gt;Access control can be correct on the day a permission is granted and still become risky later. A developer changes teams but keeps access to an old production project. A contractor finishes an engagement while a group membership remains active. A service account stops using a privileged operation, but its role is never reduced.&lt;/p&gt;&#xA;&lt;p&gt;None of these cases requires a broken authorization check. The system may enforce every permission exactly as configured. The problem is that the configured access no longer matches the current need.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
