<?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 Best practices for transitioning from Quick Start. in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/best-practices-for-transitioning-from-quick-start/m-p/1416990#M8061</link>
    <description>&lt;P&gt;Desktops are locked down via GPO. Users do not have admin rights. Local admin account used to be managed by EPM LCD but was moved to LAPS. On the Policy side we have been in Quick Start for months and spend very little time with EPM due to other products and priorities (as well as this not being our area of expertise - it's ours because it's CyberArk). Only a small % of our population have  EPM  agents - primarily Developers who need to self-elevate to install/update/etc. Any good advice or best practices how to take the next step? The first swing management would like to take is analyzing what is being self-installed and turn that info over to our software packaging teams. As a company we don't have the concept of an application inventory, off which to base EPM policy decisions. TIA.&lt;/P&gt;</description>
    <pubDate>Tue, 19 Mar 2024 20:31:05 GMT</pubDate>
    <dc:creator>T.Sherwin281643</dc:creator>
    <dc:date>2024-03-19T20:31:05Z</dc:date>
    <item>
      <title>Best practices for transitioning from Quick Start.</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/best-practices-for-transitioning-from-quick-start/m-p/1416990#M8061</link>
      <description>&lt;P&gt;Desktops are locked down via GPO. Users do not have admin rights. Local admin account used to be managed by EPM LCD but was moved to LAPS. On the Policy side we have been in Quick Start for months and spend very little time with EPM due to other products and priorities (as well as this not being our area of expertise - it's ours because it's CyberArk). Only a small % of our population have  EPM  agents - primarily Developers who need to self-elevate to install/update/etc. Any good advice or best practices how to take the next step? The first swing management would like to take is analyzing what is being self-installed and turn that info over to our software packaging teams. As a company we don't have the concept of an application inventory, off which to base EPM policy decisions. TIA.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2024 20:31:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/best-practices-for-transitioning-from-quick-start/m-p/1416990#M8061</guid>
      <dc:creator>T.Sherwin281643</dc:creator>
      <dc:date>2024-03-19T20:31:05Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for transitioning from Quick Start.</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/best-practices-for-transitioning-from-quick-start/m-p/1416991#M8062</link>
      <description>&lt;P&gt;Hey Todd,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you gone through the video nuggets that we've put together yet? There should be some of this information at a high level in there. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://www.youtube.com/playlist?list=PLWktfa5Y09kjILaaGyAH5W7RaGNiCHWBF&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Quickstart concepts are the framework for mature policy creation while allowing users to operate without interruption while we discover what their needs are (IE policy 4 in quickstart elevates apps while auditing them). I'd like to understand a bit more about what you are doing with Quickstart. Is it simply enabled with no additional applications added to the policies? EPM can help understand what applications are being used and the approved ones can be added to the relevant policy (IE quickstart policy 3 for the applicable role). Once we stop seeing a significant amount of new privilege events populating in the inbox, we can be more confident that most of the day-to-day applications are being handled by policy. At this point we would want to get rid of Quickstart Policy 4 so that applications aren't being automatically elevated. Any unknown applications will need review &amp;amp; approval before being allowed to run with admin privileges. Once there is success with one role or BU in the organization, it's just a matter of rinsing and repeating with the rest. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Happy to continue this conversation offline if you want to coordinate with your account team.  &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Steffan&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2024 13:57:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/best-practices-for-transitioning-from-quick-start/m-p/1416991#M8062</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-03-25T13:57:26Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for transitioning from Quick Start.</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/best-practices-for-transitioning-from-quick-start/m-p/1416992#M8063</link>
      <description>&lt;P&gt;Thanks Steffan.  &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2024 19:09:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/best-practices-for-transitioning-from-quick-start/m-p/1416992#M8063</guid>
      <dc:creator>T.Sherwin281643</dc:creator>
      <dc:date>2024-03-28T19:09:58Z</dc:date>
    </item>
  </channel>
</rss>

