<?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 RuntimeBroker.exe as Parent Process in Endpoint Privilege Manager (EPM) Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/runtimebroker-exe-as-parent-process/m-p/1416351#M7695</link>
    <description>&lt;P&gt;I'm submitting a case on this, but I wanted to see if anyone in the community has had an issue with RuntimeBroker.exe being the parent process for application launches?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you launch a UWP/Windows Store/Metro app by most methods, the parent process is an on-the-fly instance of RuntimeBroker.exe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can see this by launching something like SystemPropertiesAdvanced.exe&lt;/P&gt;&lt;CODE&gt;2023.10.17 10:06:39 PID:6448 TID:13588 CvfProcessStartRights::PROCSTART: pid=27088, parent=24028, exe=[C:\Windows\System32\SystemPropertiesAdvanced.exe], cmdLine=["C:\Windows\System32\SystemPropertiesAdvanced.exe" ], policyId=64646, action=3 (ELEVATE), policyName=[App - AppDev Baseline - Elevate]&lt;/CODE&gt;&lt;P&gt;The parent, 27088, is not Explorer as you'd expect, but a transitory instance of RuntimeBroker.exe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why is this an issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In my case, I'm moving "admins" to role based rights.  I've got a group with a "backstop" allowing all apps and their children (an improvement from their un-logged, no-justification free-for-all) while we build them an actual role-based group and filter their wheat from their chaff.&lt;/P&gt;&lt;CODE&gt;2023.10.16 15:10:40 PID:6448 TID:14032 CvfProcessStartRights::PROCSTART: pid=22968, parent=17464, exe=[C:\Windows\System32\SystemPropertiesAdvanced.exe], cmdLine=["C:\Windows\System32\SystemPropertiesAdvanced.exe" ], policyId=45306, action=4 (ELEVATE_ON_DEMAND) inherited from parent action 1 (NORMAL_RUN), policyName=[Backstop - Admin - delg-epm-wkst-admin]&lt;/CODE&gt;&lt;P&gt;When the user launches SystemPropertiesAdvanced.exe, Windows passes "SPA" to RuntimeBroker.exe - but "RB" is already a running process, so instead of EPM evaluating the merits of SPA based on any rule that might match it, it evaluates it as a child of RB.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So my higher-priority team-based rule to allow "SPA" to elevate automatically for teams and correctly categorizing their activity instead of hitting their backstop never triggers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Should EPM "ignore" RuntimeBroker as a parent?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To work around this, I'm currently testing an "Allow" rule for RuntimeBroker.exe with a priority just ahead of my backstop rules with children disabled.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Simplified, I now have:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;330: Elevate SystemPropertiesAdanced.exe for De-Admin group.&lt;/LI&gt;&lt;LI&gt;620: Allow RuntimeBroker.exe as "Allow" - no children.&lt;/LI&gt;&lt;LI&gt;640: Elevate as Necessary for All Applications for Former-Admins group.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I'm fearful about the consequences of "Allow"-ing RuntimeBroker.exe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'll update this if I hear anything from my incident that isn't echoed here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;If anyone's encountered this, please share &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;I&gt;[As a small note, if you launch SystemPropertiesAdvanced.exe from the start/search menu, it uses RuntimeBroker as the parent.  If you launch SystemPropertiesAdvanced.exe from Explorer, it uses Explorer.exe as the parent.]&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Oct 2023 17:33:36 GMT</pubDate>
    <dc:creator>mstenger</dc:creator>
    <dc:date>2023-10-17T17:33:36Z</dc:date>
    <item>
      <title>RuntimeBroker.exe as Parent Process</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/runtimebroker-exe-as-parent-process/m-p/1416351#M7695</link>
      <description>&lt;P&gt;I'm submitting a case on this, but I wanted to see if anyone in the community has had an issue with RuntimeBroker.exe being the parent process for application launches?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you launch a UWP/Windows Store/Metro app by most methods, the parent process is an on-the-fly instance of RuntimeBroker.exe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can see this by launching something like SystemPropertiesAdvanced.exe&lt;/P&gt;&lt;CODE&gt;2023.10.17 10:06:39 PID:6448 TID:13588 CvfProcessStartRights::PROCSTART: pid=27088, parent=24028, exe=[C:\Windows\System32\SystemPropertiesAdvanced.exe], cmdLine=["C:\Windows\System32\SystemPropertiesAdvanced.exe" ], policyId=64646, action=3 (ELEVATE), policyName=[App - AppDev Baseline - Elevate]&lt;/CODE&gt;&lt;P&gt;The parent, 27088, is not Explorer as you'd expect, but a transitory instance of RuntimeBroker.exe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why is this an issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In my case, I'm moving "admins" to role based rights.  I've got a group with a "backstop" allowing all apps and their children (an improvement from their un-logged, no-justification free-for-all) while we build them an actual role-based group and filter their wheat from their chaff.&lt;/P&gt;&lt;CODE&gt;2023.10.16 15:10:40 PID:6448 TID:14032 CvfProcessStartRights::PROCSTART: pid=22968, parent=17464, exe=[C:\Windows\System32\SystemPropertiesAdvanced.exe], cmdLine=["C:\Windows\System32\SystemPropertiesAdvanced.exe" ], policyId=45306, action=4 (ELEVATE_ON_DEMAND) inherited from parent action 1 (NORMAL_RUN), policyName=[Backstop - Admin - delg-epm-wkst-admin]&lt;/CODE&gt;&lt;P&gt;When the user launches SystemPropertiesAdvanced.exe, Windows passes "SPA" to RuntimeBroker.exe - but "RB" is already a running process, so instead of EPM evaluating the merits of SPA based on any rule that might match it, it evaluates it as a child of RB.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So my higher-priority team-based rule to allow "SPA" to elevate automatically for teams and correctly categorizing their activity instead of hitting their backstop never triggers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Should EPM "ignore" RuntimeBroker as a parent?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To work around this, I'm currently testing an "Allow" rule for RuntimeBroker.exe with a priority just ahead of my backstop rules with children disabled.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Simplified, I now have:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;330: Elevate SystemPropertiesAdanced.exe for De-Admin group.&lt;/LI&gt;&lt;LI&gt;620: Allow RuntimeBroker.exe as "Allow" - no children.&lt;/LI&gt;&lt;LI&gt;640: Elevate as Necessary for All Applications for Former-Admins group.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I'm fearful about the consequences of "Allow"-ing RuntimeBroker.exe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'll update this if I hear anything from my incident that isn't echoed here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;If anyone's encountered this, please share &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;I&gt;[As a small note, if you launch SystemPropertiesAdvanced.exe from the start/search menu, it uses RuntimeBroker as the parent.  If you launch SystemPropertiesAdvanced.exe from Explorer, it uses Explorer.exe as the parent.]&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Oct 2023 17:33:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/runtimebroker-exe-as-parent-process/m-p/1416351#M7695</guid>
      <dc:creator>mstenger</dc:creator>
      <dc:date>2023-10-17T17:33:36Z</dc:date>
    </item>
    <item>
      <title>Re: RuntimeBroker.exe as Parent Process</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/runtimebroker-exe-as-parent-process/m-p/1416352#M7696</link>
      <description>&lt;P&gt;Hi @Matthew Stenger​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any progress with the issue? &lt;/P&gt;&lt;P&gt;In case you got a resolution for support, could you kindly share how to resolve this issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Niv&lt;/P&gt;</description>
      <pubDate>Mon, 13 Nov 2023 11:01:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/runtimebroker-exe-as-parent-process/m-p/1416352#M7696</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-11-13T11:01:14Z</dc:date>
    </item>
    <item>
      <title>Re: RuntimeBroker.exe as Parent Process</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/runtimebroker-exe-as-parent-process/m-p/1416353#M7697</link>
      <description>&lt;P&gt;Thanks for asking.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, and also no.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm still using this ruleset.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;330: Elevate SystemPropertiesAdanced.exe for De-Admin group.&lt;/LI&gt;&lt;LI&gt;620: Allow RuntimeBroker.exe as "Allow" - no children.&lt;/LI&gt;&lt;LI&gt;640: Elevate as Necessary for All Applications for Former-Admins group.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our 640 rule is granting "admin" to people in an AD group after all team rules.&lt;/P&gt;&lt;P&gt;The 330 will not trigger without the 620 rule.&lt;/P&gt;&lt;P&gt;The 620 rule which specifically enumerates RuntimeBroker.exe causes it to NOT be seen as a child of the 640 rule.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The 620 and 640 groups are targeted to my "admis."&lt;/P&gt;&lt;P&gt;The 330 rule is targeted to the people I'm transitioning out of admin - but who are still members as we organize them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;RuntimeBroker.exe doesn't seem to mind, and about 300 people have this rule.&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I &lt;I&gt;believe&lt;/I&gt; I can promote this rule to a higher level and to all users, but it's only required to be before any "all" rule that allows children. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm still &lt;B&gt;VERY MUCH under the opinion that EPM itself should ignore RuntimeBroker.exe as a parent process&lt;/B&gt; - like Eplorer - and I've been promised a meeting on the subject, but it hasn't yet materialized.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here's my very simple rule and application group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope this helps, but support has been almost entirely hands-off.  &lt;span class="lia-unicode-emoji" title=":unamused_face:"&gt;😒&lt;/span&gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Ht00000T66cvIAB.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/86910iC62CB50BAD9A7722/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Ht00000T66cvIAB.png" alt="Field_Content_versions_oct20__068Ht00000T66cvIAB.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Field_Content_versions_oct20__068Ht00000T66emIAB.png"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/86912i8AB0E88AEB06E233/image-size/large?v=v2&amp;amp;px=999" role="button" title="Field_Content_versions_oct20__068Ht00000T66emIAB.png" alt="Field_Content_versions_oct20__068Ht00000T66emIAB.png" /&gt;&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 18:47:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/runtimebroker-exe-as-parent-process/m-p/1416353#M7697</guid>
      <dc:creator>mstenger</dc:creator>
      <dc:date>2023-11-15T18:47:29Z</dc:date>
    </item>
    <item>
      <title>Re: RuntimeBroker.exe as Parent Process</title>
      <link>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/runtimebroker-exe-as-parent-process/m-p/1416354#M7698</link>
      <description>&lt;P&gt;Hi @Matthew Stenger​,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our support team met with you to explain the appropriate policy configurations better, and the support case is closed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Runtimebroker.exe is a unique system process. The user does not create it. If you tell Windows to launch a specific type of program, Windows instead uses an intermediate program – Runtimebroker.exe – to launch your requested application.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please reopen the support ticket if there are more questions or issues with the suggested solution given by our support team. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Tamir&lt;/P&gt;</description>
      <pubDate>Thu, 23 Nov 2023 14:10:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/endpoint-privilege-manager-epm/runtimebroker-exe-as-parent-process/m-p/1416354#M7698</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-11-23T14:10:09Z</dc:date>
    </item>
  </channel>
</rss>

