<?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 - Source Code in Enterprise Data Loss Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/enterprise-data-loss-prevention/enterprise-dlp-source-code/m-p/556568#M13</link>
    <description>&lt;P&gt;I'm testing enterprise DLP and I'm wondering how I can test source code?&amp;nbsp; I asked my SE and he gave me the following answer which explains what is done to inspect source code but not how to test source code:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"For document types such as 'source code', 'legal documents', 'financial documents', etc we leverage machine learning models to classify the data.&amp;nbsp; &amp;nbsp;The ML models use a combination of test classification, RegEx, anomaly detection, NLP, token&amp;nbsp;analysis, semantic analysis and others."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When testing data like credit card numbers, SSNs, or sensitivity labels it is simple to create a rule, pass traffic, and know which data should be stopped and which data should be permitted.&amp;nbsp; When testing source code I have no idea what should be permitted and what should be blocked by DLP.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Has anyone tested source code in eDLP?&lt;/P&gt;
&lt;P&gt;If so, how are you testing it?&lt;/P&gt;
&lt;P&gt;Does anyone know what types of data in source code should be blocked?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the help!&lt;/P&gt;
&lt;P&gt;-John&lt;/P&gt;</description>
    <pubDate>Tue, 05 Sep 2023 16:23:50 GMT</pubDate>
    <dc:creator>John_J</dc:creator>
    <dc:date>2023-09-05T16:23:50Z</dc:date>
    <item>
      <title>Enterprise DLP - Source Code</title>
      <link>https://live.paloaltonetworks.com/t5/enterprise-data-loss-prevention/enterprise-dlp-source-code/m-p/556568#M13</link>
      <description>&lt;P&gt;I'm testing enterprise DLP and I'm wondering how I can test source code?&amp;nbsp; I asked my SE and he gave me the following answer which explains what is done to inspect source code but not how to test source code:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"For document types such as 'source code', 'legal documents', 'financial documents', etc we leverage machine learning models to classify the data.&amp;nbsp; &amp;nbsp;The ML models use a combination of test classification, RegEx, anomaly detection, NLP, token&amp;nbsp;analysis, semantic analysis and others."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When testing data like credit card numbers, SSNs, or sensitivity labels it is simple to create a rule, pass traffic, and know which data should be stopped and which data should be permitted.&amp;nbsp; When testing source code I have no idea what should be permitted and what should be blocked by DLP.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Has anyone tested source code in eDLP?&lt;/P&gt;
&lt;P&gt;If so, how are you testing it?&lt;/P&gt;
&lt;P&gt;Does anyone know what types of data in source code should be blocked?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the help!&lt;/P&gt;
&lt;P&gt;-John&lt;/P&gt;</description>
      <pubDate>Tue, 05 Sep 2023 16:23:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/enterprise-data-loss-prevention/enterprise-dlp-source-code/m-p/556568#M13</guid>
      <dc:creator>John_J</dc:creator>
      <dc:date>2023-09-05T16:23:50Z</dc:date>
    </item>
  </channel>
</rss>

