<?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 Venafi Discovery automatically linking created devices/apps to existing managed certs. in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/venafi-discovery-automatically-linking-created-devices-apps-to/m-p/1419500#M527</link>
    <description>If anyone uses tools like Chef for automation, copies of the Chef cert are placed in every DevOps pipeline. These copies are discovered by venafi and devices/apps created and linked to the managed cert. In this case the manage Chef cert is on a load balancer and the management type of the cert is set to provisioning for the Netscaler. But when the cert is renewed, it also attempts to install it to every pipeline object where venafi discovery created a device/app and linked it to the managed cert. This is a big issue because Venafi obviously does not have the credentials and other required data to actually install all these pipeline certs. As a result, the cert hangs in a stage 800 state. If or when the cert needs to be renewed again, it cannot be renewed until an admin resets it, then goes to the associations tab and selects all the venafi created devices/apps and disables them.Since Venafi can never provision to these objects created by discovery, why does it set them to Enabled as the default? This only opens the door to errors and issues that admins will have to fix. Wouldnt it make more sense to create these as Disabled, then if it is chosen to automate provisioning for that cert, the required data can be updated on the object and at that time it can be set to Enabled..</description>
    <pubDate>Fri, 02 Dec 2022 20:23:51 GMT</pubDate>
    <dc:creator>DPrice</dc:creator>
    <dc:date>2022-12-02T20:23:51Z</dc:date>
    <item>
      <title>Venafi Discovery automatically linking created devices/apps to existing managed certs.</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/venafi-discovery-automatically-linking-created-devices-apps-to/m-p/1419500#M527</link>
      <description>If anyone uses tools like Chef for automation, copies of the Chef cert are placed in every DevOps pipeline. These copies are discovered by venafi and devices/apps created and linked to the managed cert. In this case the manage Chef cert is on a load balancer and the management type of the cert is set to provisioning for the Netscaler. But when the cert is renewed, it also attempts to install it to every pipeline object where venafi discovery created a device/app and linked it to the managed cert. This is a big issue because Venafi obviously does not have the credentials and other required data to actually install all these pipeline certs. As a result, the cert hangs in a stage 800 state. If or when the cert needs to be renewed again, it cannot be renewed until an admin resets it, then goes to the associations tab and selects all the venafi created devices/apps and disables them.Since Venafi can never provision to these objects created by discovery, why does it set them to Enabled as the default? This only opens the door to errors and issues that admins will have to fix. Wouldnt it make more sense to create these as Disabled, then if it is chosen to automate provisioning for that cert, the required data can be updated on the object and at that time it can be set to Enabled..</description>
      <pubDate>Fri, 02 Dec 2022 20:23:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/venafi-discovery-automatically-linking-created-devices-apps-to/m-p/1419500#M527</guid>
      <dc:creator>DPrice</dc:creator>
      <dc:date>2022-12-02T20:23:51Z</dc:date>
    </item>
  </channel>
</rss>

