EPM - Trusted Network Location does not elevate Child Process

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Endpoint Privilege Manager (EPM) Articles
3 min read
L3 Networker
No ratings

Question

Trusted network location policy will not work for child process. 

Answer

Trust action elevates ONLY IF the application REQUESTS ELEVATION. If the parent application did not require elevation than the child application will not be elevated. This is also true for Trusted network location policy application that creates a new file locally by the installation and the new file will not elevate as it will not inherit the elevation flag due to security reasons.

There are two workarounds for the issue:

1. Create a Trusted Source by Publisher or Installation Package (instead of the Network Location Trusted Source)
 OR
2. Create an additional Advanced policy for the relevant exe files as follows

- Go to Advanced Policies->Create Application Policy->Elevate
- In 'Application Type', select "Permit Application Installation"
- In 'Installation', select "EXE Installation"
- in 'Parameters' set only File Name to *.exe
(in warning message box click on yes; this is security warning and later we will add a source to avoid the security risk)
- 'Protect Installed Files' and 'Parent Process' settings can be left unchanged
- In Source select "From Network Location:" and set the field value according to the network location in Trusted Source policy
- Click on Finish and then complete creating the policy

This Advanced policy, in addition to the existing Network Location Trusted Source, should solve the issue.

Issue

Hello, Running the following application from Trusted Network Location "http://vsphereclient.vmware.com/vsphereclient/1/2/3/0/3/8/6/9/VMware-ClientIntegrationPlugin-6.0.0-12303869.exe" doesn't work. After analysis in my testing enviroment (reprodice the behaviour is really easy) I found that this executable is a self-extracting 7zip package, which run the setup after unzipping it (all file, the package and zipped file are signed as “VMware, Inc.”. Basically the Trusted Network Location doesn't apply by default on child process. Quick solution is to create Trusted Signature for “VMware, Inc.” or a specific advanced policy. Customer report this "feature" as a limitation to use "Trusted Network Location", do you have any advice about the problem identifed or this is a "limitation" known? Thank you, Giulio

Environment

Component: Viewfinity Server Functional Area: Privilege Elevation

Resolution

Trust action elevates ONLY IF the application REQUESTS ELEVATION. If the parent application did not require elevation than the child application will not be elevated. This is also true for trusted application that create a new file locally by the installation and the new file will not elevate as it will not inherit the elevation flag due to security reasons.
Rate this article: