<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Identity-Governance on Ru Campbell MVP</title>
    <link>https://campbell.scot/tags/identity-governance/</link>
    <description>Recent content in Identity-Governance on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 19 Nov 2023 14:01:41 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/tags/identity-governance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Privileged Identity Management (PIM) – Common Microsoft 365 Security Mistakes Series</title>
      <link>https://campbell.scot/pim-common-microsoft-365-security-mistakes-series/</link>
      <pubDate>Sun, 19 Nov 2023 14:01:41 +0000</pubDate>
      <guid>https://campbell.scot/pim-common-microsoft-365-security-mistakes-series/</guid>
      <description>&lt;p&gt;Entra ID&amp;rsquo;s P2 license (previously Azure AD Premium P2) unlocks the Privileged Identity Management (PIM). PIM is part of broader &lt;em&gt;identity governance&lt;/em&gt; features, and is most known for enabling just-in-time admin rights. For example, you are &lt;em&gt;eligible&lt;/em&gt; to become an administrator for a maximum of &lt;em&gt;X&lt;/em&gt; hours, at which point the permissions expire and you need to reactivate.&lt;/p&gt;
&lt;p&gt;This blog covers five of the common misconfigurations and misunderstandings I see with customers. Intuitive as PIM may appear, there are some gotchas you need to be aware of. It is a follow up from my previous &lt;a href=&#34;https://campbell.scot/conditional-access-common-microsoft-365-security-mistakes-series/&#34;&gt;Conditional Access – Common Microsoft 365 Security Mistakes Series&lt;/a&gt; article.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Conditional Access - Common Microsoft 365 Security Mistakes Series</title>
      <link>https://campbell.scot/conditional-access-common-microsoft-365-security-mistakes-series/</link>
      <pubDate>Thu, 05 Oct 2023 21:11:27 +0000</pubDate>
      <guid>https://campbell.scot/conditional-access-common-microsoft-365-security-mistakes-series/</guid>
      <description>&lt;p&gt;Conditional Access (CA) is front and center of any attempt to secure Microsoft 365. If you&amp;rsquo;ve spent any time securing your tenant and Entra resources, you&amp;rsquo;ll know what Conditional Access is by now, so we&amp;rsquo;ll assume at least a level 200 understanding, skip the introduction, and instead dive into the most common mistakes I see when helping folks out with it.&lt;/p&gt;
&lt;p&gt;These aren&amp;rsquo;t listed in any particular order, and the devil&amp;rsquo;s in the details, so make sure you read the full post instead of just skimming the bullet points! There are also &lt;em&gt;way&lt;/em&gt; more than five mistakes you can make with Conditional Access, but let&amp;rsquo;s start with these.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Getting Started with Azure AD Identity Governance – Part 3: Privileged Identity Management (PIM)</title>
      <link>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-3-privileged-identity-management-pim/</link>
      <pubDate>Sun, 16 Aug 2020 14:13:09 +0000</pubDate>
      <guid>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-3-privileged-identity-management-pim/</guid>
      <description>&lt;p&gt;This blog is the last in a small series on Azure AD Premium P2&amp;rsquo;s Identity Governance toolkit.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-1-entitlement-management/&#34;&gt;Part 1: Entitlement Management&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-2-access-reviews/&#34;&gt;Part 2: Access Reviews&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-3-privileged-identity-management-pim/&#34;&gt;Part 3: Privileged Identity Management (PIM) (this post)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;PIM is an Azure AD P2 feature that enables just-in-time (JIT) admin rights in Azure and Azure AD.  Historically, best practice has been for users to have a separate account for admin tasks, as protection against the primary account if breached.  While this is still supported under PIM, it&amp;rsquo;s less of a requirement - PIM makes admin rights time bound on the same account and optionally require approval to activate.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Getting Started with Azure AD Identity Governance – Part 2: Access Reviews</title>
      <link>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-2-access-reviews/</link>
      <pubDate>Sun, 02 Aug 2020 14:46:34 +0000</pubDate>
      <guid>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-2-access-reviews/</guid>
      <description>&lt;p&gt;This blog is the second in a small series on Azure AD Premium P2&amp;rsquo;s Identity Governance toolkit.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-1-entitlement-management/&#34;&gt;Part 1: Entitlement Management&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-2-access-reviews/&#34;&gt;Part 2: Access Reviews (this post)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-3-privileged-identity-management-pim/&#34;&gt;Part 3: Privileged Identity Management (PIM)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;Historically, the apps, groups, and rights a user had were all under central and constant management by IT.  Azure AD and modern management have pushed this towards &amp;lsquo;self-service&amp;rsquo;, including guest users, which improves productivity.  The goal of Azure AD access reviews is to improve the management of user rights and access, in this modern environment, throughout their lifecycle in your tenant.  It empowers you with automated tools to control their groups, apps, and roles (admin rights).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Getting Started with Azure AD Identity Governance - Part 1: Entitlement Management</title>
      <link>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-1-entitlement-management/</link>
      <pubDate>Sun, 26 Jul 2020 17:27:32 +0000</pubDate>
      <guid>https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-1-entitlement-management/</guid>
      <description>&lt;p&gt;This blog is the first in a small series on Azure AD Premium P2&amp;rsquo;s Identity Governance toolkit.&lt;/p&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-1-entitlement-management/&#34;&gt;Part 1: Entitlement Management (this post)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-2-access-reviews/&#34;&gt;Part 2: Access reviews&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://campbell.scot/getting-started-with-azure-ad-identity-governance-part-3-privileged-identity-management-pim/&#34;&gt;Part 3: Privileged Identity Management (PIM)&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;Azure AD entitlement management is a bit of an overlooked gem.  It&amp;rsquo;s a feature that automates the processes for giving users access to resources. The typical scenario is a user has just joined a new department or is a new employee.  Over time, the resources their team need access to have sprawled across the M365 estate and it would be laborious to give permission to them all manually - if you even remember them all.  Additionally, you want to ensure the user&amp;rsquo;s access is time-controlled so that as their role changes, their access does too.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
