<?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>Cyren on Ru Campbell MVP</title>
    <link>https://campbell.scot/tags/cyren/</link>
    <description>Recent content in Cyren on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sat, 04 Jul 2020 14:15:32 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/tags/cyren/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Microsoft Defender for Endpoint Web Content Filtering - Migrate Rules from Existing Security Software</title>
      <link>https://campbell.scot/microsoft-defender-atp-web-content-filtering-migrate-rules-from-existing-security-software/</link>
      <pubDate>Sat, 04 Jul 2020 14:15:32 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-atp-web-content-filtering-migrate-rules-from-existing-security-software/</guid>
      <description>&lt;p&gt;In my &lt;a href=&#34;https://campbell.scot/microsoft-defender-atp-web-content-filtering-administration-limitations-and-user-experience/&#34;&gt;last blog&lt;/a&gt;, I wrote about web content filtering in MDATP and how it now allows you to block website categories on the client across all apps.  Category blockers are great because, with one easy checkbox, you ban hundreds of thousands of dangerous on inappropriate websites.  Nothing is perfect, though, and anyone who&amp;rsquo;s ever worked a helpdesk or SOC will attest that false positives and false negatives are common.&lt;/p&gt;
&lt;p&gt;The engine for MDATP web content filtering is &lt;a href=&#34;https://www.cyren.com/&#34;&gt;Cyren&lt;/a&gt;, and you can check if a website is caught by its category rules using their online &lt;a href=&#34;https://www.cyren.com/security-center/url-category-check&#34;&gt;category check tool&lt;/a&gt;.  This takes a bit of time, as each check is subject to a &lt;a href=&#34;https://developers.google.com/recaptcha/docs/v3&#34;&gt;Google reCAPTCHA test&lt;/a&gt;.  If you&amp;rsquo;re migrating anything of scale to MDATP, you don&amp;rsquo;t have the time to do this, and also do not want to risk important websites later being swept up by category rules even if they are fine for now.  When you allowed or blocked websites on your existing solution, it&amp;rsquo;s assumed you&amp;rsquo;ve done the due diligence, and you want to take the remediation you&amp;rsquo;ve applied against those (potential) false positives and false negatives with you.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Defender for Endpoint Web Content Filtering - Administration, Limitations, and User Experience</title>
      <link>https://campbell.scot/microsoft-defender-atp-web-content-filtering-administration-limitations-and-user-experience/</link>
      <pubDate>Sun, 28 Jun 2020 16:37:29 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-defender-atp-web-content-filtering-administration-limitations-and-user-experience/</guid>
      <description>&lt;p&gt;Historically, one of the big features missing &amp;ldquo;out of the box&amp;rdquo; with MDATP was web content filtering.  Customers typically look at MDATP as an option when their existing endpoint security is due for license renewal, and compare their existing solution against it.  They would be moving from one of the big security vendors such as Sophos, Norton, and McAfee, which all supported web content filtering.  Higher lever stakeholders often listed the ability to block websites as essential, and as Microsoft did not maintain such a categorisation database, if you wanted it with Defender ATP, you&amp;rsquo;d be looking at other solutions too.  This took away from Defender ATP&amp;rsquo;s &amp;ldquo;single pane of glass&amp;rdquo; selling point.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
