<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Enterprise DLP, Microsoft Teams, and Non-File Inspection/Blocking in Enterprise Data Loss Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/enterprise-data-loss-prevention/enterprise-dlp-microsoft-teams-and-non-file-inspection-blocking/m-p/1224448#M33</link>
    <description>&lt;P&gt;I'm working on testing an Enterprise DLP data profile that includes blocking traffic for non-file-based detections (e.g., PCI data in a Teams message).&amp;nbsp; For file-based detections, the behavior is fairly straight-forward: the upload fails, Teams throws an error, user weeps.&amp;nbsp; For non-file-based detections... Teams behaves strangely.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Teams will, seemingly indefinitely, continue to try and try to post the message that the firewall will block.&amp;nbsp; It doesn't appear to have a sane retry or failure state like it does with file-based detections.&amp;nbsp; It will also spam the firewall and E-DLP portal with events and evidence.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm curious if anyone has observed this behavior, or might have an idea of how to get Teams... if possible... to fail a bit more gracefully in cases like this.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Mar 2025 14:21:55 GMT</pubDate>
    <dc:creator>rickyboone</dc:creator>
    <dc:date>2025-03-21T14:21:55Z</dc:date>
    <item>
      <title>Enterprise DLP, Microsoft Teams, and Non-File Inspection/Blocking</title>
      <link>https://live.paloaltonetworks.com/t5/enterprise-data-loss-prevention/enterprise-dlp-microsoft-teams-and-non-file-inspection-blocking/m-p/1224448#M33</link>
      <description>&lt;P&gt;I'm working on testing an Enterprise DLP data profile that includes blocking traffic for non-file-based detections (e.g., PCI data in a Teams message).&amp;nbsp; For file-based detections, the behavior is fairly straight-forward: the upload fails, Teams throws an error, user weeps.&amp;nbsp; For non-file-based detections... Teams behaves strangely.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Teams will, seemingly indefinitely, continue to try and try to post the message that the firewall will block.&amp;nbsp; It doesn't appear to have a sane retry or failure state like it does with file-based detections.&amp;nbsp; It will also spam the firewall and E-DLP portal with events and evidence.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm curious if anyone has observed this behavior, or might have an idea of how to get Teams... if possible... to fail a bit more gracefully in cases like this.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2025 14:21:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/enterprise-data-loss-prevention/enterprise-dlp-microsoft-teams-and-non-file-inspection-blocking/m-p/1224448#M33</guid>
      <dc:creator>rickyboone</dc:creator>
      <dc:date>2025-03-21T14:21:55Z</dc:date>
    </item>
  </channel>
</rss>

