PSM 15.2 - increased hardening causing issues with mapped drives and error when attempting to download

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PSM 15.2 - increased hardening causing issues with mapped drives and error when attempting to download

L4 Transporter

Just in case other folks are seeing this, with PSM 15.2, Idira increased the hardening. Although this does indeed increase security it causes issues with the mapped drives being seen for PSM sessions.

 

When the PSM session is established the capsm application adds two registry values to the shadow users profile:

NoViewOnDrive

  • Hides the drive letters/icons in File Explorer
  • causes issues with not being able to reach the default save location when explorer window opens

NoDrives

  • Blocks user access to the contents of the specified drives.

 

As seen below these are added to the shadow users profile at the start of the session:

 

Field_Content_versions_oct20__068Vy00001q3Ok7IAE.png 

This error is seen when trying to save/download files within a PSM Web app session, although pressing ok gets past it. It is because the default folder that would be open can not be reached due to the NoDrives being set to 0xffffffff (all drives blocked to user)

 

Field_Content_versions_oct20__068Vy00001q2N6xIAE.png 

WINSCP and other apps will struggle to fine the mapped drives with this setting in place

 

Workaround 1

To see all the drives, in the 'file name' section in the explorer window, type in '\\tsclient\, this will review all the drives that were mapped

 

This will not prevent the error above from showing though

 

Workaround 2 (preferred but reduces hardening but no different from v14.6)

This affects all PSM users and also direct logons to the PSM servers. Add the same registry items to the local machine hive

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer

NoViewOnDrives = 12

NoDrives = 0

 

The above will mean that the users can not see the c (4) and d (8) drives, although they can see navigate them (same as with PSM 14.6 and lower) if they type in 'c:\' in the 'file explorer' bit

 

Due to the way that the hardening has been implemented, it is not something we can modify with a parameter as it seems to be hard coded in the PSM application. In order to change the registry on the shadow user on the fly, this can cause other security issues and may not affect the active session anyway.

 

UPDATE

Looks like this has been updated from 15.2.0 to 15.2.1 (released 10th Oct)

 

Instead of blocking all drives (which also affects tsclient/mapped drives), it now is set to bvlock c, d and z drives.

 

Although this will still cause the error window to appear when trying to open he save/open explorer window within a web app and other apps

 

15.2.0

Field_Content_versions_oct20__068Vy00001q3Ok7IAE.png 

15.2.1

Field_Content_versions_oct20__068Vy00001q2IYiIAM.png

4 REPLIES 4

L5 Sessionator

Hey @Nathan Southgate​ Users are not allowed to browse to UNC paths if the "run" command is not available, this is restricted via HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer

 

The security enhancement for NoViewOnDrive was introduced in PSM version 15.2 where the PSMShadowUsers are created (via NTUSER.DAT) with NoViewOnDrive applied against them by default. If the administrator's profile was created after hardening on the PSM OS, the same hardened NTUSER.DAT is used, but you already have access to remove this hardening if desired via HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer.

 

(It's not recommended to modify the hardening, and the risk introduced by doing so should be accepted prior to making the changes)

For PSM-### shadow users, you can use this article (which is a similar process), as a guideline for loading NTUSER.DAT, editing, and then removing current shadow users so they get recreated with new level of hardening:

https://community.cyberark.com/s/article/How-to-customize-the-font-and-font-size-for-the-default-PSM-SSH-connection-component-via-registry

 

 

Hey @Patrick Booth​ ,

 

Thanks for the reply. What are you referencing when you say 'administrators profile', do you mean the hidden default profile?

 

We did try to change the ntuser.dat profile previuslly (as per your link) as we have had to make a few changes in the past (changed font size for psm-ssh putty sessions for example), however this was superceeded as shown in my screenshots, the capsm app adds these on runtime.

 

For example, no changes were done to the default profile a psm session through 15.2.0 uses different registry entries as 15.2.1 (as per screenshot).

 

Thanks.

Hey @Nathan Southgate​ Any new user that logs in has a local profile created upon logon, that local profile is created using the NTUSER.DAT. If that user is an Administrator, they will have access to run regedit and change their own registry via HKEY_CURRENT_USER.

 

PSM Shadow users are a different process because those profiles get recreated frequently, so changes must be made to the NTUSER.dat.

 

If this isn't working as expected, it may be best to open a support case for review.

Hey @Patrick Booth​ ,

 

Thanks for the info, I know that the shadow users profiles are constantly deleted and created based on the default user profile ntuser.dat.

 

Why on earth would you make the default profile user an administrator?

 

Your correct that the profiles are based on this default user profile but in this case, from looking at procmon, the capsm app add these extra registry values at runtime, after the profile is created.

 

Seems like Idira relised this issue and thus updated this in 15.2.1 to mostly fix the issue.

 

I do have a case over with support, we have been looking in to the issue for some time.

  • 134 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!