What are PSM Shadow Users and how do they work?

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

PAM Self-Hosted Articles
11 min read
L1 Bithead
No ratings

Question


Q1:
What are PSM Shadow User accounts and how do they work?

Q2:
What is their purpose? 
 
Q3:
When do these accounts get deleted?
 
Q4:
What is the recommended method for cleaning up unused accounts/profiles?
 
Q5:
Why do RDP sessions not require or use a PSM Shadow User account to connect through PSM?
 
Q6:
How does password rotation on PSM Shadow User accounts work?
 
Q7:
Can I remove specific folder from Shadowuser profile?

 

Answer

A1:

A PSM Shadow user is automatically created during a PSM Connection. The PSM Shadow users sandbox the client session. The point of the Shadow users is process isolation, so the programs launched on the same server by different vault users run under different identities, and cannot leak information between the sessions. These identities are created by the SYSTEM user and do not have any privileges. 

The credentials of the shadow users are managed and changed internally by the PSM server. The PSM will change (reset) the shadow user password every time a new connection is made. Also, the hardening of the PSM Server restricts the use of these Shadow users. PIM Suite Installation Guide describes hardening procedure for PSM server that includes steps to limit permissions of the Shadow users on the PSM server 


A2:
In v6.0 we added the ability to use a variety of clients on the PSM server (i.e. Toad, SQL+, etc...). To help increase the security and the expand-ability of the PSM in version 7.0 we took some steps towards sandboxing the client sessions. 

This is achieved via the new PSM Shadow users with a unique account being created for each Vault user - their shadow user. These shadow users are local users on the PSM machine. 

This user is created dynamically and managed by the PSM (the default is for no password to be used, unless GPO requires one) 

When a user is connecting using the PSM, we still connect to the PSM machine using the PSMConnect user, but we now use the shadow-user to run the client (similar to a "run-as" approach). This creates full separation with each user having its own permissions, files, registry - making it very difficult to harm other users sessions. 

As these Shadow users are local users they should have the log on locally right. 

 

A3:
This is a configurable parameter (ClearUserProfilesInterval). It can be found in PVWA in: 
1) Administration Tab 
2) (System Configuration - Component Settings - Options) 
3) (PIM Suite Configuration - Privileged Session Management - General Settings - Server Settings) 

This parameter defines the interval in which the Shadow User cleanup process will be initiated. The default is every 30 days. The Shadow User account and profile will be removed by this process if the associated Vault User no longer exists in the vault. 


A4:
It would be recommended to keep the shadow user account as long as the associated vault user still exists. Once the vault user is removed, the shadow user will be cleaned up in the next cycle of the ClearUserProfilesInterval. 

If you need to keep the vault user and are not concerned about losing the associated shadow user and profile, it is ok to manually clean these up on the PSM server by completing both steps below: 

1) Control Panel -> System -> Advanced system settings -> On Advanced tab, in the User Profiles section - Click on the Settings button -> Select the required user name and click on the Delete button 

A5:
Because PSMRdpClient is the only connection client that runs with PSMConnect and not a shadow user. 
If we were using a shadow user, some functionality won't work – like copy-paste from client to target machine. 
And shadow user is not needed here for the purpose of security that we need it for the other connection clients. 

 

A6:
There is no mechanism in place to allow automatic rotation of PSM Shadow Users password. 

Please note that we don't consider Shadow Users to be a risk, because a Shadow User is a weak user, who cannot log in remotely to the PSM server. 
Additionally, every session a new password is being generated for the Shadow User. 


A7:

It's not possible to delete folder paths, if e.g Appdata/Local/Temp. 

This type of notation is not supported. the parameter CleanupFolder will only delete folder names that are under the Shadowuser profile but not with the subfolder structure using character  "\". 

For the example AppData\Local\Temp, you could only specify AppData in the parameter and it will erase its hole content and the content of the sub folders.

Multiple questions and answers on PSM Shadow User accounts are listed below:
 
Q1:
What are PSM Shadow User accounts and how do they work?
 
A1:
A PSM Shadow user is automatically created during a PSM Connection. The PSM Shadow users sandbox the client session. The point of the Shadow users is process isolation, so the programs launched on the same server by different vault users run under different identities, and cannot leak information between the sessions. 

The credentials of the shadow users are managed and changed internally by the PSM server. The PSM will change (reset) the shadow user password every time a new connection is made. Also, the hardening of the PSM Server restricts the use of these Shadow users. PIM Suite Installation Guide describes hardening procedure for PSM server that includes steps to limit permissions of the Shadow users on the PSM server 


Q2:
What is their purpose? 

A2:
In v6.0 we added the ability to use a variety of clients on the PSM server (i.e. Toad, SQL+, etc...). To help increase the security and the expand-ability of the PSM in version 7.0 we took some steps towards sandboxing the client sessions. 

This is achieved via the new PSM Shadow users with a unique account being created for each Vault user - their shadow user. These shadow users are local users on the PSM machine. 

This user is created dynamically and managed by the PSM (the default is for no password to be used, unless GPO requires one) 

When a user is connecting using the PSM, we still connect to the PSM machine using the PSMConnect user, but we now use the shadow-user to run the client (similar to a "run-as" approach). This creates full separation with each user having its own permissions, files, registry - making it very difficult to harm other users sessions. 

As these Shadow users are local users they should have the log on locally right. 


Q3:
When do these accounts get deleted?
 
A3:
This is a configurable parameter (ClearUserProfilesInterval). It can be found in PVWA in: 
1) Administration Tab 
2) (System Configuration - Component Settings - Options) 
3) (PIM Suite Configuration - Privileged Session Management - General Settings - Server Settings) 

This parameter defines the interval in which the Shadow User cleanup process will be initiated. The default is every 30 days. The Shadow User account and profile will be removed by this process if the associated Vault User no longer exists in the vault. 


Q4:
What is the recommended method for cleaning up unused accounts/profiles?
 
A4:
It would be recommended to keep the shadow user account as long as the associated vault user still exists. Once the vault user is removed, the shadow user will be cleaned up in the next cycle of the ClearUserProfilesInterval. 

If you need to keep the vault user and are not concerned about losing the associated shadow user and profile, it is ok to manually clean these up on the PSM server by completing both steps below: 

1) Control Panel -> System -> Advanced system settings -> On Advanced tab, in the User Profiles section - Click on the Settings button -> Select the required user name and click on the Delete button 

 
 
Q5:
Why do RDP sessions not require or use a PSM Shadow User account to connect through PSM?
 
A5:
Because PSMRdpClient is the only connection client that runs with PSMConnect and not a shadow user. 
If we were using a shadow user, some functionality won't work – like copy-paste from client to target machine. 
And shadow user is not needed here for the purpose of security that we need it for the other connection clients. 
Multiple questions and answers on PSM Shadow User accounts are listed below:
 
Q1:
What are PSM Shadow User accounts and how do they work?
 
A1:
A PSM Shadow user is automatically created during a PSM Connection. The PSM Shadow users sandbox the client session. The point of the Shadow users is process isolation, so the programs launched on the same server by different vault users run under different identities, and cannot leak information between the sessions. 

The credentials of the shadow users are managed and changed internally by the PSM server. The PSM will change (reset) the shadow user password every time a new connection is made. Also, the hardening of the PSM Server restricts the use of these Shadow users. PIM Suite Installation Guide describes hardening procedure for PSM server that includes steps to limit permissions of the Shadow users on the PSM server 


Q2:
What is their purpose? 

A2:
In v6.0 we added the ability to use a variety of clients on the PSM server (i.e. Toad, SQL+, etc...). To help increase the security and the expand-ability of the PSM in version 7.0 we took some steps towards sandboxing the client sessions. 

This is achieved via the new PSM Shadow users with a unique account being created for each Vault user - their shadow user. These shadow users are local users on the PSM machine. 

This user is created dynamically and managed by the PSM (the default is for no password to be used, unless GPO requires one) 

When a user is connecting using the PSM, we still connect to the PSM machine using the PSMConnect user, but we now use the shadow-user to run the client (similar to a "run-as" approach). This creates full separation with each user having its own permissions, files, registry - making it very difficult to harm other users sessions. 

As these Shadow users are local users they should have the log on locally right. 


Q3:
When do these accounts get deleted?
 
A3:
This is a configurable parameter (ClearUserProfilesInterval). It can be found in PVWA in: 
1) Administration Tab 
2) (System Configuration - Component Settings - Options) 
3) (PIM Suite Configuration - Privileged Session Management - General Settings - Server Settings) 

This parameter defines the interval in which the Shadow User cleanup process will be initiated. The default is every 30 days. The Shadow User account and profile will be removed by this process if the associated Vault User no longer exists in the vault. 


Q4:
What is the recommended method for cleaning up unused accounts/profiles?
 
A4:
It would be recommended to keep the shadow user account as long as the associated vault user still exists. Once the vault user is removed, the shadow user will be cleaned up in the next cycle of the ClearUserProfilesInterval. 

If you need to keep the vault user and are not concerned about losing the associated shadow user and profile, it is ok to manually clean these up on the PSM server by completing both steps below: 

1) Control Panel -> System -> Advanced system settings -> On Advanced tab, in the User Profiles section - Click on the Settings button -> Select the required user name and click on the Delete button 

 
 
Q5:
Why do RDP sessions not require or use a PSM Shadow User account to connect through PSM?
 
A5:
Because PSMRdpClient is the only connection client that runs with PSMConnect and not a shadow user. 
If we were using a shadow user, some functionality won't work – like copy-paste from client to target machine. 
And shadow user is not needed here for the purpose of security that we need it for the other connection clients. 

 
Q6:
How does password rotation on PSM Shadow User accounts work on accounts are not used for long time?
A6:
We don't consider Shadow Users to be a risk, because a Shadow User is a weak user, who cannot log in remotely to the PSM server.
Therefore, there is no mechanism in place to allow automatic rotation of PSM Shadow Users password.
However, every time a session is established, a new password is being generated for the Shadow User. 
Rate this article:
  • 43132 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-19-2025 09:00 PM
Updated by: