<?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: Best Practices for Maintaining CyberArk Project Documentation in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417153#M6926</link>
    <description>&lt;P&gt;Done !&lt;/P&gt;</description>
    <pubDate>Thu, 03 Apr 2025 11:42:49 GMT</pubDate>
    <dc:creator>TKHAN</dc:creator>
    <dc:date>2025-04-03T11:42:49Z</dc:date>
    <item>
      <title>Best Practices for Maintaining CyberArk Project Documentation</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417148#M6921</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am currently working on a CyberArk project, and as part of the implementation, I need to prepare and maintain a variety of documents, such as step-by-step guides, configurations, troubleshooting steps, and best practices.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Right now, I am documenting everything in simple MS Word files and storing them in a folder structure. While this works fine for now, I am concerned that as the project grows, managing these documents may become cumbersome. Searching for specific information, version control, and collaboration with team members might become challenging.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to know if there are any best practices or recommended tools to efficiently document and manage a CyberArk project. Some aspects I am considering:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Easy searchability and organization&lt;/P&gt;&lt;P&gt;Version control and change tracking&lt;/P&gt;&lt;P&gt;Collaboration features for multiple team members&lt;/P&gt;&lt;P&gt;Secure storage and controlled access&lt;/P&gt;&lt;P&gt;If anyone has experience with this or can suggest an efficient approach, your insights would be highly appreciated. Looking forward to learning from the community!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Tue, 04 Mar 2025 19:34:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417148#M6921</guid>
      <dc:creator>TKHAN</dc:creator>
      <dc:date>2025-03-04T19:34:34Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices for Maintaining CyberArk Project Documentation</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417149#M6922</link>
      <description>&lt;P&gt;Hi @TAIFUL KHAN​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can leverage Confluence or SharePoint or GitBook (version control) to structure and manage the documentations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some of the folders structure you can have included are,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Project Overview&lt;/P&gt;&lt;P&gt;Implementation Guides&lt;/P&gt;&lt;P&gt;Configuration Steps&lt;/P&gt;&lt;P&gt;Troubleshooting &amp;amp; Known Issues&lt;/P&gt;&lt;P&gt;Best Practices &amp;amp; Recommendations&lt;/P&gt;&lt;P&gt;Change Logs &amp;amp; Updates&lt;/P&gt;&lt;P&gt; Vendor documents and KB links &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope it helps !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Mar 2025 22:21:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417149#M6922</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-03-04T22:21:36Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices for Maintaining CyberArk Project Documentation</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417150#M6923</link>
      <description>&lt;P&gt;Thanks for your suggestion! &lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2025 12:44:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417150#M6923</guid>
      <dc:creator>TKHAN</dc:creator>
      <dc:date>2025-03-05T12:44:10Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices for Maintaining CyberArk Project Documentation</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417151#M6924</link>
      <description>&lt;P&gt;One suggestion I have: Don't put information such as current software versions (as in - which CyberArk verison is the Vault running, which Chrome version is installed on PSM, etc...) into the documentation, because it will be outdated very quickly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Instead, check if you can configure your monitoring solution or SIEM solution (Zabbix, Splunk, Nagios, ...) to retrieve it and give you that information in a dashboard. That way, you always have the correct information about what is *actually* running on your CyberArk PAS components.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2025 14:07:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417151#M6924</guid>
      <dc:creator>B.Brckler554136</dc:creator>
      <dc:date>2025-03-05T14:07:27Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices for Maintaining CyberArk Project Documentation</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417152#M6925</link>
      <description>&lt;P&gt;Hi @TAIFUL KHAN​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since several community members answered your question, please let us know if these solutions addressed your query.&lt;/P&gt;&lt;P&gt;If so, it would be great if you could mark the most helpful response as 'Select as Best' to assist other community members with similar questions.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you, Liad.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 08:14:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417152#M6925</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-04-03T08:14:36Z</dc:date>
    </item>
    <item>
      <title>Re: Best Practices for Maintaining CyberArk Project Documentation</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417153#M6926</link>
      <description>&lt;P&gt;Done !&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 11:42:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/best-practices-for-maintaining-cyberark-project-documentation/m-p/1417153#M6926</guid>
      <dc:creator>TKHAN</dc:creator>
      <dc:date>2025-04-03T11:42:49Z</dc:date>
    </item>
  </channel>
</rss>

