<?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>Conditional-Access on Ru Campbell MVP</title>
    <link>https://campbell.scot/categories/conditional-access/</link>
    <description>Recent content in Conditional-Access on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 09 Feb 2024 17:30:41 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/categories/conditional-access/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Microsoft Defender for Cloud Apps - Common Microsoft 365 Security Mistakes Series</title>
      <link>https://campbell.scot/microsoft-defender-for-cloud-apps-common-microsoft-security-mistakes-series/</link>
      <pubDate>Fri, 09 Feb 2024 17:30:41 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-for-cloud-apps-common-microsoft-security-mistakes-series/</guid>
      <description>&lt;p&gt;Defender for Cloud Apps (MDA) is such a hidden gem. When talking with Microsoft 365 E5 customers, it&amp;rsquo;s amazing how few of them really grab MDA and squeeze all they can out of it. It&amp;rsquo;s often classified as a cloud access security broker (CASB) but that&amp;rsquo;s an oversimplication: the product can do so much more such as SaaS security posture management (SSPM) and, most topical in light of &lt;a href=&#34;https://www.microsoft.com/en-us/security/blog/2024/01/25/midnight-blizzard-guidance-for-responders-on-nation-state-attack/&#34;&gt;recent events&lt;/a&gt;, OAuth app governance.&lt;/p&gt;</description>
    </item>
    <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>Stop Making These Conditional Access Mistakes</title>
      <link>https://campbell.scot/stop-making-these-conditional-access-mistakes/</link>
      <pubDate>Tue, 16 May 2023 09:14:28 +0000</pubDate>
      <guid>https://campbell.scot/stop-making-these-conditional-access-mistakes/</guid>
      <description>&lt;p&gt;Conditional Access is the most important security feature you will configure in Azure AD. You need to get this right, or most other things don&amp;rsquo;t even matter.&lt;/p&gt;
&lt;p&gt;Compared to on-premises AD, which requires line of sight to a domain infrastructure often limited to physical or VPN access, Azure AD is wide open by default. Users can authenticate from anywhere, on any device.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Conditional Access: Skip MFA for Company Devices on the Company Network</title>
      <link>https://campbell.scot/conditional-access-skip-mfa-for-company-devices-on-the-company-network/</link>
      <pubDate>Wed, 31 Mar 2021 07:13:29 +0000</pubDate>
      <guid>https://campbell.scot/conditional-access-skip-mfa-for-company-devices-on-the-company-network/</guid>
      <description>&lt;p&gt;A common Conditional Access policy is to add trusted locations as an exception to multi-factor authorisation requirements.  The logic goes, if you accessing resources such as Office 365 from a location such as the corporate office, that&amp;rsquo;s an element of verification in itself that your login should be trusted, so we should improve your user experience by removing MFA.  Personally, I support the use of MFA &lt;em&gt;regardless&lt;/em&gt; of where you are authenticating (at the very least, if you have an Azure AD admin role assigned).  However, doing something like this is a great option if you are introducing MFA from scratch: you will improve user buy in the less you change their standard experience.  Then, increase the scope gradually.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
