<?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 Cortex xdr agent certificate in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate/m-p/1223740#M8050</link>
    <description>&lt;P data-start="133" data-end="142"&gt;Hi all,&lt;/P&gt;
&lt;P data-start="144" data-end="373"&gt;I have some doubts regarding the Cortex XDR agent certificate. I have gone through multiple blogs, which provided some insights, but I am still unable to see the complete picture. Below are the key facts I have gathered so far:&lt;/P&gt;
&lt;OL data-start="375" data-end="1448"&gt;
&lt;LI data-start="375" data-end="749"&gt;
&lt;P data-start="378" data-end="749"&gt;&lt;STRONG data-start="378" data-end="410"&gt;New Certificate Enforcement:&lt;/STRONG&gt; Cortex XDR enforced a new certificate because the old certificate was vulnerable to MITM (Man-in-the-Middle) attacks. The previous implementation accepted any certificate for communication as long as it was signed. To mitigate this, Palo Alto Networks now enforces a certificate issued exclusively by them, ensuring stricter validation.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="751" data-end="1208"&gt;
&lt;P data-start="754" data-end="1208"&gt;&lt;STRONG data-start="754" data-end="804"&gt;Certificate Enforcement in Different Machines:&lt;/STRONG&gt; In new machines, the agent certificate enforcement is enabled by default in agent settings. However, for older machines, the default setting was &lt;STRONG data-start="950" data-end="971"&gt;Disabled (Notify)&lt;/STRONG&gt;, requiring manual activation. Despite this, I have observed cases where both the &lt;STRONG data-start="1053" data-end="1111"&gt;old certificate (Trusted Root Certification Authority)&lt;/STRONG&gt; and the &lt;STRONG data-start="1120" data-end="1150"&gt;new certificate (root.pem)&lt;/STRONG&gt; are present on the same endpoint. Why does this happen?&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1210" data-end="1448"&gt;
&lt;P data-start="1213" data-end="1448"&gt;&lt;STRONG data-start="1213" data-end="1250"&gt;Certificate Contents and Purpose:&lt;/STRONG&gt; The certificate lists multiple well-known names such as Microsoft, Google, and DigiCert, among others. Does this imply that the certificate is used for communication beyond the Cortex XDR server?&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;H3 data-start="1450" data-end="1487"&gt;&lt;STRONG data-start="1454" data-end="1485"&gt;Questions I Need Clarified:&amp;nbsp;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P data-start="1488" data-end="1767"&gt;&lt;span class="lia-unicode-emoji" title=":small_blue_diamond:"&gt;🔹&lt;/span&gt; &lt;STRONG data-start="1491" data-end="1589"&gt;How does communication with the Cortex XDR server differ between the old and new certificates?&lt;/STRONG&gt;&lt;BR data-start="1589" data-end="1592" /&gt;&lt;span class="lia-unicode-emoji" title=":small_blue_diamond:"&gt;🔹&lt;/span&gt; &lt;STRONG data-start="1595" data-end="1668"&gt;Why are both the old and new certificates available on some machines?&lt;/STRONG&gt;&lt;BR data-start="1668" data-end="1671" /&gt;&lt;span class="lia-unicode-emoji" title=":small_blue_diamond:"&gt;🔹&lt;/span&gt; &lt;STRONG data-start="1674" data-end="1765"&gt;How was the old agent certificate used for communication before the enforcement change?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P data-start="1488" data-end="1767"&gt;&lt;STRONG data-start="1674" data-end="1765"&gt;&lt;span class="lia-unicode-emoji" title=":small_blue_diamond:"&gt;🔹&lt;/span&gt; Do the names listed in the certificate indicate that Cortex XDR communicates with third parties other than the XDR server?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P data-start="1769" data-end="1829"&gt;Any insights on these points would be greatly appreciated.&lt;/P&gt;
&lt;P data-start="1831" data-end="1854"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="1831" data-end="1854"&gt;Thanks,&lt;/P&gt;</description>
    <pubDate>Thu, 13 Mar 2025 10:57:19 GMT</pubDate>
    <dc:creator>Vinothkumar_SBA</dc:creator>
    <dc:date>2025-03-13T10:57:19Z</dc:date>
    <item>
      <title>Cortex xdr agent certificate</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate/m-p/1223740#M8050</link>
      <description>&lt;P data-start="133" data-end="142"&gt;Hi all,&lt;/P&gt;
&lt;P data-start="144" data-end="373"&gt;I have some doubts regarding the Cortex XDR agent certificate. I have gone through multiple blogs, which provided some insights, but I am still unable to see the complete picture. Below are the key facts I have gathered so far:&lt;/P&gt;
&lt;OL data-start="375" data-end="1448"&gt;
&lt;LI data-start="375" data-end="749"&gt;
&lt;P data-start="378" data-end="749"&gt;&lt;STRONG data-start="378" data-end="410"&gt;New Certificate Enforcement:&lt;/STRONG&gt; Cortex XDR enforced a new certificate because the old certificate was vulnerable to MITM (Man-in-the-Middle) attacks. The previous implementation accepted any certificate for communication as long as it was signed. To mitigate this, Palo Alto Networks now enforces a certificate issued exclusively by them, ensuring stricter validation.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="751" data-end="1208"&gt;
&lt;P data-start="754" data-end="1208"&gt;&lt;STRONG data-start="754" data-end="804"&gt;Certificate Enforcement in Different Machines:&lt;/STRONG&gt; In new machines, the agent certificate enforcement is enabled by default in agent settings. However, for older machines, the default setting was &lt;STRONG data-start="950" data-end="971"&gt;Disabled (Notify)&lt;/STRONG&gt;, requiring manual activation. Despite this, I have observed cases where both the &lt;STRONG data-start="1053" data-end="1111"&gt;old certificate (Trusted Root Certification Authority)&lt;/STRONG&gt; and the &lt;STRONG data-start="1120" data-end="1150"&gt;new certificate (root.pem)&lt;/STRONG&gt; are present on the same endpoint. Why does this happen?&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="1210" data-end="1448"&gt;
&lt;P data-start="1213" data-end="1448"&gt;&lt;STRONG data-start="1213" data-end="1250"&gt;Certificate Contents and Purpose:&lt;/STRONG&gt; The certificate lists multiple well-known names such as Microsoft, Google, and DigiCert, among others. Does this imply that the certificate is used for communication beyond the Cortex XDR server?&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;H3 data-start="1450" data-end="1487"&gt;&lt;STRONG data-start="1454" data-end="1485"&gt;Questions I Need Clarified:&amp;nbsp;&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P data-start="1488" data-end="1767"&gt;&lt;span class="lia-unicode-emoji" title=":small_blue_diamond:"&gt;🔹&lt;/span&gt; &lt;STRONG data-start="1491" data-end="1589"&gt;How does communication with the Cortex XDR server differ between the old and new certificates?&lt;/STRONG&gt;&lt;BR data-start="1589" data-end="1592" /&gt;&lt;span class="lia-unicode-emoji" title=":small_blue_diamond:"&gt;🔹&lt;/span&gt; &lt;STRONG data-start="1595" data-end="1668"&gt;Why are both the old and new certificates available on some machines?&lt;/STRONG&gt;&lt;BR data-start="1668" data-end="1671" /&gt;&lt;span class="lia-unicode-emoji" title=":small_blue_diamond:"&gt;🔹&lt;/span&gt; &lt;STRONG data-start="1674" data-end="1765"&gt;How was the old agent certificate used for communication before the enforcement change?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P data-start="1488" data-end="1767"&gt;&lt;STRONG data-start="1674" data-end="1765"&gt;&lt;span class="lia-unicode-emoji" title=":small_blue_diamond:"&gt;🔹&lt;/span&gt; Do the names listed in the certificate indicate that Cortex XDR communicates with third parties other than the XDR server?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P data-start="1769" data-end="1829"&gt;Any insights on these points would be greatly appreciated.&lt;/P&gt;
&lt;P data-start="1831" data-end="1854"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-start="1831" data-end="1854"&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Thu, 13 Mar 2025 10:57:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate/m-p/1223740#M8050</guid>
      <dc:creator>Vinothkumar_SBA</dc:creator>
      <dc:date>2025-03-13T10:57:19Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex xdr agent certificate</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate/m-p/1224000#M8069</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;To answer your questions:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG data-start="1491" data-end="1589"&gt;How does communication with the Cortex XDR server differ between the old and new certificates?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG data-start="1491" data-end="1589"&gt;Old Certificate&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;The agent uses a wildcard certificate (*.traps.paloaltonetworks.com) verified by the GoDaddy Root Certificate Authority G2.&lt;BR /&gt;The root CA is installed under the computer's trusted root certificate authority store.&lt;BR /&gt;The agent checks the roots.pem file for the root certificate and falls back to the local store if not found.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;New Certificate:&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;The agent will solely rely on the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;roots.pem&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;file for certificate validation, eliminating the fallback to the local store.&lt;/LI&gt;
&lt;LI&gt;This change mitigates MITM attacks where an attacker could use a legitimate root certificate installed in the machine's root certificate store to intercept communications.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;STRONG data-start="1595" data-end="1668"&gt;Why are both the old and new certificates available on some machines?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;The agent checks the roots.pem file for the root certificate and falls back to the local store if not found, which makes agent partially protected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG data-start="1674" data-end="1765"&gt;How was the old agent certificate used for communication before the enforcement change?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Explained in first point&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG data-start="1674" data-end="1765"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Do the names listed in the certificate indicate that Cortex XDR communicates with third parties other than the XDR server?&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Please confirm the attribute where it is mentioned? And also is it for Old or New certificate.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 10:47:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/cortex-xdr-agent-certificate/m-p/1224000#M8069</guid>
      <dc:creator>aspatil</dc:creator>
      <dc:date>2025-03-17T10:47:31Z</dc:date>
    </item>
  </channel>
</rss>

