<?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: Defined Developer Application Group - what is it exactly, our developerexp team are seeing high cpu usage and we believe we need to create all these policies manually to meet cyber security workflow? in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418395#M8812</link>
    <description>&lt;P&gt;Glad to help... and yes, you don't want to replicate or disable this group (typically at least).  You also don't want to add all your developer applications to it.  As mentioned, it's designed for those that act in a certain way where normal interaction with CyberArk would otherwise cause performance problems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As mentioned, we have Allow and Elevate if necessary policies for all our developer applications, but this group only contains the default entries that come with CyberArk.  We haven't found that any of our other developer applications work in a way where they need to be added to this group too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-rwm&lt;/P&gt;</description>
    <pubDate>Fri, 22 Nov 2024 14:47:52 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-11-22T14:47:52Z</dc:date>
    <item>
      <title>Defined Developer Application Group - what is it exactly, our developerexp team are seeing high cpu usage and we believe we need to create all these policies manually to meet cyber security workflow?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418392#M8809</link>
      <description>&lt;P&gt;&lt;A alt="https://docs.cyberark.com/epm/latest/en/content/epm/server%20user%20guide/predefinedpolicies-newui.htm#Developerapplicationspolicy" href="https://docs.cyberark.com/epm/latest/en/content/epm/server%20user%20guide/predefinedpolicies-newui.htm#Developerapplicationspolicy" target="_blank"&gt;Predefined policies | CyberArk Docs&lt;/A&gt; |I can see each policy has child processes ticket, we would ideally want at least 3 parameters for each policy to meet our cybers guardrails - Is it an Allow policy as oppose to an Elevate policy? I will create a test policy it's now been discussed with cyber and test them one by one with a friendly developer.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Nov 2024 15:01:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418392#M8809</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-11-20T15:01:58Z</dc:date>
    </item>
    <item>
      <title>Re: Defined Developer Application Group - what is it exactly, our developerexp team are seeing high cpu usage and we believe we need to create all these policies manually to meet cyber security workflow?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418393#M8810</link>
      <description>&lt;P&gt;Hi @Touseef-ur rehman​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The "Developer Applications Application Group" is a special group that doesn't work like the others.  I've requested in the past that CyberArk clarify the documentation (enhance it) so that users can better understand what it does and why.  I actually don't have the level of understanding on it that I would like either.  But I'll attempt to explain to you based on what I do know.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This group itself forms its own "policy" (but again, unlike a true policy as we know it).  It does not "allow" or "elevate".  Instead, what it is doing is looking at what those applications are doing, and essentially ignoring when they create large volumes of child processes (because that's what those apps do).  In short, it's making sure that EPM is not impacting the performance of those applications.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me give you an example... We have an advanced policy to allow Node.js.  But we (like everyone) also have it in the Developer Applications Application Group.  Our developers were happily using Node.js without issue.  But then in the past Node.js changed their publisher signature, so the definition in the Developer Applications Application Group no longer matched (we had already updated it in our advanced policy though).  At that point our developers started having performance issues.  Node.js worked (because it was allowed in our advanced policy), but EPM was now evaluating everything it was doing and causing it to severely slow down... making it unbearably slow for the developers.  So, we simply added the new publisher signature into the Developer Applications Application Group and once again all was well.  By the way, you won't need to do that because in the last release CyberArk included that update to the group as part of the release.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In summary, it's a special group that works unlike the others.  It could be used in an advanced policy, but is really intended to serve a special purpose which is to prevent performance issues with developer applications that produce a lot of files/child processes as part of their functioning.  I personally haven't found the need to add any additional developer applications to the group, but your mileage may vary.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this helps @Touseef-ur rehman​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;CYBERARK FOLKS&lt;/B&gt;, please chime in if I've missed or misstated something here.  Again, I'm not 100% on this either.  And I'd greatly appreciate it if you updated your documentation to better explain this group.  I've seen confusion on this for years.  Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-rwm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 14:12:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418393#M8810</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-11-22T14:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: Defined Developer Application Group - what is it exactly, our developerexp team are seeing high cpu usage and we believe we need to create all these policies manually to meet cyber security workflow?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418394#M8811</link>
      <description>&lt;P&gt;Thanks Rwm, that explains it a lot better, I was going to create a new Policy All-Win-Allow-Developer - and copy and paste each of the 9 Developer policies but now you've made me realised there's some specialness about the Predefined Group so I will ask our cyber team to re-enable it and use it! only as we have this preferred naming convention and they wanted to test it's findings but it's already proven the defined group works and has a certain purpose outside of elevation and child process enablement -   Thank-you for the detailed response! I presume you can't replicate the the group as it's somewhat locked down and so on, so all good!&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 14:26:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418394#M8811</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-11-22T14:26:24Z</dc:date>
    </item>
    <item>
      <title>Re: Defined Developer Application Group - what is it exactly, our developerexp team are seeing high cpu usage and we believe we need to create all these policies manually to meet cyber security workflow?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418395#M8812</link>
      <description>&lt;P&gt;Glad to help... and yes, you don't want to replicate or disable this group (typically at least).  You also don't want to add all your developer applications to it.  As mentioned, it's designed for those that act in a certain way where normal interaction with CyberArk would otherwise cause performance problems.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As mentioned, we have Allow and Elevate if necessary policies for all our developer applications, but this group only contains the default entries that come with CyberArk.  We haven't found that any of our other developer applications work in a way where they need to be added to this group too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-rwm&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 14:47:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418395#M8812</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-11-22T14:47:52Z</dc:date>
    </item>
    <item>
      <title>Re: Defined Developer Application Group - what is it exactly, our developerexp team are seeing high cpu usage and we believe we need to create all these policies manually to meet cyber security workflow?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418396#M8813</link>
      <description>&lt;P&gt;Hello! We use an Advanced Trust Policy specifically for Developer Applications. We are a large Enterprise with thousands of users and aim to make the administration as fluid as possible. The problem I see with using the built-in Developer Group is that it creates extra work - Have to click on App Groups to edit the Developer Policy, then go back to the policy and edit users. This creates extra work as opposed to editing everything within a single policy menu. To my understanding, creating a Trust Source Policy tells EPM to not intercept every subprocess, especially in Visual Studio Compilations.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 18:08:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418396#M8813</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-11-22T18:08:23Z</dc:date>
    </item>
    <item>
      <title>Re: Defined Developer Application Group - what is it exactly, our developerexp team are seeing high cpu usage and we believe we need to create all these policies manually to meet cyber security workflow?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418397#M8814</link>
      <description>&lt;P&gt;our epm users are only developers thankfully so we apply to ALL rather than individual users/devices - Cyber are pretty strict we know from VS you can spawn child processes such as cmd/ notepad potentially as admin even if we have AAD SAML in place to lockdown CMD/PS /notepad++ . and the other worry is what you can run from VS loads of things are out there that are a security risk with this APP&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 18:15:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418397#M8814</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-11-22T18:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: Defined Developer Application Group - what is it exactly, our developerexp team are seeing high cpu usage and we believe we need to create all these policies manually to meet cyber security workflow?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418398#M8815</link>
      <description>&lt;P&gt;Hi @Martin Carlos​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You said "To my understanding, creating a Trust Source Policy tells EPM to not intercept every subprocess, especially in Visual Studio Compilations."   But I don't think that is correct.  I'm pretty sure EPM is going to intercept and evaluate every process for a matching policy/instruction unless it is excluded in the agent configuration or handled via a special group like the 'Developer Application Applications Group'.  Basically, that group is an exclusion for the sub-processes of the listed developer apps (to describe at a high level).  Just because it's in a Trust policy or Advanced policy does not prevent the evaluation of all aspects of the application process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hopefully someone from CyberArk will chime in to confirm.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As for the double-work, I know what you mean.  I dislike the way the Ransomware policy is implemented because it requires double-work (the need to put in the exclusion group, even if already covered by other policies).  In the case of this developer apps group, I can kind of understand it though.  You don't want to "exclude" all your developer apps from being evaluated, just the ones that would cause performance problems.  So it makes more sense to have a separate group here.  I guess what you could do though, is to add that group to your advanced policy so that any apps you put in it are covered by the advanced policy and then you are only creating the definition for the app one time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-rwm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 18:22:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418398#M8815</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-11-22T18:22:40Z</dc:date>
    </item>
    <item>
      <title>Re: Defined Developer Application Group - what is it exactly, our developerexp team are seeing high cpu usage and we believe we need to create all these policies manually to meet cyber security workflow?</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418399#M8816</link>
      <description>&lt;P&gt;Yeah, VS and some of the other development IDEs make this a challenge.  You simply need to weigh the risks and come up with the right balance of policies for all.  To be honest, the way Microsoft built all this in Windows doesn't make it easy for anyone, CyberArk included.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-rwm&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 18:25:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/defined-developer-application-group-what-is-it-exactly-our/m-p/1418399#M8816</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-11-22T18:25:56Z</dc:date>
    </item>
  </channel>
</rss>

