<?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 Certificate Cleanup in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-cleanup/m-p/1419391#M494</link>
    <description>We recently completed CA imports as well as all devices exported from our SCCM database to Venafi. Before Venafi, we allow users to request multiple certifcates of the same common name if they had to add/modify certificate attributes, e.g. add/remove SAN. Due to this, we have multiple certifcates in Venafi with - #. To clean this up, Im thinking we shouldremove all imported certificates and devices, schedule onboard discovery on the network and place the certs and devices from the discovery jobin a disovered folder. We can then import from CA and SCCM and place certficates and devices that are not discovered in a imported" folder. Does this make sense?.</description>
    <pubDate>Thu, 14 Dec 2023 16:29:30 GMT</pubDate>
    <dc:creator>Dyl8n</dc:creator>
    <dc:date>2023-12-14T16:29:30Z</dc:date>
    <item>
      <title>Certificate Cleanup</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-cleanup/m-p/1419391#M494</link>
      <description>We recently completed CA imports as well as all devices exported from our SCCM database to Venafi. Before Venafi, we allow users to request multiple certifcates of the same common name if they had to add/modify certificate attributes, e.g. add/remove SAN. Due to this, we have multiple certifcates in Venafi with - #. To clean this up, Im thinking we shouldremove all imported certificates and devices, schedule onboard discovery on the network and place the certs and devices from the discovery jobin a disovered folder. We can then import from CA and SCCM and place certficates and devices that are not discovered in a imported" folder. Does this make sense?.</description>
      <pubDate>Thu, 14 Dec 2023 16:29:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-cleanup/m-p/1419391#M494</guid>
      <dc:creator>Dyl8n</dc:creator>
      <dc:date>2023-12-14T16:29:30Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Cleanup</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-cleanup/m-p/1419392#M495</link>
      <description>@Dylan Wu Welcome to the Venafi Community! Were excited to have you here. I wanted to share thisGetting Startedarticle with you to help familiarize you with the community,  Ive reached out to a couple of team members at Venafi so they can chime in with their thoughts. Im also curious to see if @Jeff W , @DomD , or @Daniel Schiada have some thoughts on what you presented.</description>
      <pubDate>Thu, 14 Dec 2023 16:29:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-cleanup/m-p/1419392#M495</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-12-14T16:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate Cleanup</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-cleanup/m-p/1419393#M496</link>
      <description>@Dylan Wu I am going to keep this conversation open so anyone in the community can jump in and reply. From the Venafi side, it does seem that the best path forward is connecting with your Solution Architect, @Jeremy Meldrum . Theyll be able to guide you through your concerns. Thanks Dylan and hope you have a great start to your week!</description>
      <pubDate>Mon, 08 Jan 2024 09:29:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/certificate-cleanup/m-p/1419393#M496</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-01-08T09:29:18Z</dc:date>
    </item>
  </channel>
</rss>

