<?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: Understanding Network Discovery Jobs and Device-Certificate Association in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/understanding-network-discovery-jobs-and-device-certificate/m-p/1336637#M151</link>
    <description>@dghort - the answer for how we do reconciliation for certificates is very different in how we do reconciliation for devices. Lets start with the certificate first.  You are saying that network discovery finds a certificate, and the same exact certificate (with the same exact thumbprint) already exists in the TPP Policy tree, but doesnt get associated with the results? Or are you saying a similar certificate already exists, and TPP isnt recognizing the certificate you found as a new version of the existing certificate you had in the policy tree?</description>
    <pubDate>Wed, 18 Dec 2024 09:37:48 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-12-18T09:37:48Z</dc:date>
    <item>
      <title>Understanding Network Discovery Jobs and Device-Certificate Association</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/understanding-network-discovery-jobs-and-device-certificate/m-p/1336636#M150</link>
      <description>I am in a scenario where we are really trying to get automation implemented. I have created a few new network discovery jobs to find more certificates that would need to be managed by TPP. In some cases, the device already exists and the certificate already exists, but they do not associate. After manually associating the certificate with the device and validating, it saysmismatch with known on the device. Is this the reason that the association wouldnt occur, or is it because the certificate and device already existed before hand? Just trying to understand how this works..</description>
      <pubDate>Thu, 12 Dec 2024 15:59:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/understanding-network-discovery-jobs-and-device-certificate/m-p/1336636#M150</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2024-12-12T15:59:50Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding Network Discovery Jobs and Device-Certificate Association</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/understanding-network-discovery-jobs-and-device-certificate/m-p/1336637#M151</link>
      <description>@dghort - the answer for how we do reconciliation for certificates is very different in how we do reconciliation for devices. Lets start with the certificate first.  You are saying that network discovery finds a certificate, and the same exact certificate (with the same exact thumbprint) already exists in the TPP Policy tree, but doesnt get associated with the results? Or are you saying a similar certificate already exists, and TPP isnt recognizing the certificate you found as a new version of the existing certificate you had in the policy tree?</description>
      <pubDate>Wed, 18 Dec 2024 09:37:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/understanding-network-discovery-jobs-and-device-certificate/m-p/1336637#M151</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-12-18T09:37:48Z</dc:date>
    </item>
  </channel>
</rss>

