<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Least Privilege on Nalar</title>
    <link>https://nalar.dev/tags/least-privilege/</link>
    <description>Recent content in Least Privilege 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/least-privilege/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Apply Least Privilege to Application Access</title>
      <link>https://nalar.dev/apply-least-privilege-to-application-access/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/apply-least-privilege-to-application-access/</guid>
      <description>&lt;p&gt;Least privilege is the practice of giving an identity only the access required to perform its current job. The identity may be a person, application, service account, CI job, or automated process.&lt;/p&gt;&#xA;&lt;p&gt;The principle sounds simple, but useful implementations go beyond creating a few roles. Permissions change over time, applications accumulate capabilities, and emergency exceptions often become permanent. Least privilege therefore needs both careful design and regular maintenance.&lt;/p&gt;&#xA;&lt;h2 id=&#34;start-from-required-actions-not-convenient-roles&#34;&gt;Start from required actions, not convenient roles&lt;/h2&gt;&#xA;&lt;p&gt;A common mistake is to begin with a broad role such as &lt;code&gt;admin&lt;/code&gt;, &lt;code&gt;editor&lt;/code&gt;, or &lt;code&gt;operator&lt;/code&gt; and assign it because it makes an application work quickly.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
