<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hardening on securityminded</title>
    <link>/tags/hardening/</link>
    <description>Recent content in Hardening on securityminded</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 08 Apr 2026 17:36:38 -0400</lastBuildDate>
    <atom:link href="/tags/hardening/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Blocking Harmful User Agents: Defender for Cloud Apps and Conditional Access</title>
      <link>/posts/blocking-harmful-user-agents-with-defender-for-cloud-conditional-access/</link>
      <pubDate>Wed, 08 Apr 2026 17:36:38 -0400</pubDate>
      <guid>/posts/blocking-harmful-user-agents-with-defender-for-cloud-conditional-access/</guid>
      <description>&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;&#xA;&lt;p&gt;An often overlooked control that your organization may already pay for, but underutilize, is Defender for Cloud Apps + Conditional Access policies. These are surprisingly effective, straightforward to set up, and granular once you get a handle on the process. In my cloud apps hardening journey, I found that this specific use case (and many more!) are not well documented or laid out as clear as they could be in Microsoft documentation. Instead of paying a third-party for their bespoke product, you can leverage the capabilities of MDCA and conditional access to act as a reverse proxy for your Entra ID user authentication traffic.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
