<?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 Re: Cortex XDR Agent certificate enforcement in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate-enforcement/m-p/599124#M7252</link>
    <description>&lt;P&gt;Hi, same problem here and yes, we're doing deep packet inspection, as many others do. Strangely, not all the endpoints are in partially protected state while they all have their traffic scanned with DPI. What toubleshooting is required in this case, as we can confirm that we have DPI in place? Would they add our private CA to the root ca pem file?&lt;/P&gt;</description>
    <pubDate>Mon, 30 Sep 2024 19:44:13 GMT</pubDate>
    <dc:creator>Dario_Palermo</dc:creator>
    <dc:date>2024-09-30T19:44:13Z</dc:date>
    <item>
      <title>Cortex XDR Agent certificate enforcement</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate-enforcement/m-p/589358#M6823</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;I have &lt;STRONG&gt;enabled the Cortex XDR agent settings for certificate enforcement&lt;/STRONG&gt;. However, endpoints are showing as only &lt;STRONG&gt;partially protected&lt;/STRONG&gt;, and the Operational Status Details &lt;STRONG&gt;indicate that certificate enforcement is disabled against policy&lt;/STRONG&gt; (Failed to enable certificate enforcement due to local store fallback). Could you please help with this issue?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 07:38:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate-enforcement/m-p/589358#M6823</guid>
      <dc:creator>Vinothkumar_SBA</dc:creator>
      <dc:date>2024-06-12T07:38:13Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XDR Agent certificate enforcement</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate-enforcement/m-p/589359#M6824</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/243138"&gt;@Vinothkumar_SBA&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;As you have mentioned the error is&amp;nbsp;"Failed to enable certificate enforcement due to local-store fallback". That means Certificate enforcement is not enabled and instead of root.pem , the agent is using Local store certificate which is not recommended. Hence, partially protected.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The solution is not disabling the policy, it is finding out why it is falling back. The reason may be that, you are decrypting the agent traffic or SSL inspection is enabled in your proxy or VPN.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hence, please open a TAC support case to troubleshoot further.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If you feel this has answered your query, please let us know by clicking on "mark this as a Solution".&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 07:41:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate-enforcement/m-p/589359#M6824</guid>
      <dc:creator>aspatil</dc:creator>
      <dc:date>2024-06-12T07:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XDR Agent certificate enforcement</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate-enforcement/m-p/594841#M7068</link>
      <description>&lt;P&gt;Dear&amp;nbsp;&lt;A id="link_17" class="lia-link-navigation lia-page-link lia-user-name-link" href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/308232" target="_self" aria-label="View Profile of aspatil"&gt;&lt;SPAN class=""&gt;Aspatil&lt;/SPAN&gt;&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;I have the same problem, does this error affect the protection ability or even the functionality of the Agent?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What adjustments would you recommend? Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2024 03:00:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate-enforcement/m-p/594841#M7068</guid>
      <dc:creator>S.Lin576639</dc:creator>
      <dc:date>2024-08-14T03:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XDR Agent certificate enforcement</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate-enforcement/m-p/599124#M7252</link>
      <description>&lt;P&gt;Hi, same problem here and yes, we're doing deep packet inspection, as many others do. Strangely, not all the endpoints are in partially protected state while they all have their traffic scanned with DPI. What toubleshooting is required in this case, as we can confirm that we have DPI in place? Would they add our private CA to the root ca pem file?&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2024 19:44:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate-enforcement/m-p/599124#M7252</guid>
      <dc:creator>Dario_Palermo</dc:creator>
      <dc:date>2024-09-30T19:44:13Z</dc:date>
    </item>
  </channel>
</rss>

