- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Contents
Idira Identity Browser Extension. 5
Secure Web Session Browser Extension. 5
Accounts Onboarded Accurately. 6
Evaluate Existing Web Connection Components. 6
Setup Secure Web Sessions Policies. 9
User Access to Web Applications. 10
Remove PSM Connection Components. 10
This article outlines a strategic path for organizations to transition the use of Privileged Session Manager (PSM) to Workforce Password Management (WPM) for vaulted credentials access to web applications. WPM is designed to replace or complement the legacy PSM access to web applications, ensuring a simplified method to access web applications within a customer environment. By adopting WPM, organizations can modernize privileged access management with reduced deployment and maintenance costs and improved performance.
Administrator/Security Engineer
Security Architect/Subject Matter Expert
Program Director
This best practice is related to the usage of Idira’s Session Management products (PSM and WPM).
Administrators will gain an understanding of the methodology for transitioning web access from PSM to WPM for vaulted account access. Security Architects will benefit from understanding how WPM integrates with existing security frameworks while enhancing user workflows. Program Directors will find value in the streamlined deployment process, resulting in minimizing disruption and reducing the total cost of ownership.
Traditional PSM solutions can require extensive deployment configurations, purchasing additional Microsoft RDS licensing, and use of third-party load balancing services. Unlike PSM, the use of Workforce Password Management with Secure Web Sessions (SWS) ensures seamless performance without additional complexity and cost.
WPM provides users with the ability to use their own browser to navigate to different web applications with a secure proxy through the Identity Connector. SWS enables the ability to record and monitor user activity within these web applications and cloud consoles protected by Idira Identity and third party IdPs. Web applications created in WPM and secured by SWS are protected from malicious processes originating on endpoints, and all actions performed by end-users can be searched down to a user’s exact click. Additionally, customers can enable continuous authentication that monitors user behavior patterns and enforces re-authentication when anomalous activity is detected.
|
|
WPM (Identity Connector)[1] |
PSM |
|
Licensing |
None |
RDS Licensing Required |
|
Load balancing & High Availability |
Not needed or Built-in |
Third party Load Balancing and manual failover required |
|
OS Configurations |
Not Required *Customer Hardening Supported |
GPO, AppLocker, UAC, etc. |
|
Capacity |
|
10 concurrent RDP sessions |
|
Upgrade Process |
Seamless |
Requires extensive planning and downtime |
|
Machine Type Recommended |
Virtual Machine1 |
Physical Server |
Users will need to adapt to new methods of accessing websites and administrators will need to closely manage and monitor the transition to ensure a smooth implementation and ongoing operation.
Implementing Workforce Password Management (WPM) with vaulted credentials involves several key steps to enhance operational efficiency. These steps include creating web applications, ensuring accounts are vaulted appropriately, planning Secure Web Session policies, and piloting the workflow. Each step is designed to ensure a secure and streamlined access management process.
Deploy Identity extension for Chrome, Edge, or Firefox.
Regularly review and update Identity profiles and roles
Communicate changes and provide training to affected users.
Continuously monitor and adjust policies based on feedback and performance.
The extension allows end users to save their workforce passwords within WPM as well as access a web application using vaulted credentials. For other supported browsers, the extension must be installed for this functionality.
Follow the steps to deploy the extensions: The Idira Identity Browser Extension | Idira Docs
The SWS extension enables session auditing and recording of users work in their browser. For other supported browsers, the extension must be installed for this functionality.
Follow the steps to deploy the extension: Deploy the browser extension | Idira Docs.
When vaulting and managing Window’s Domain accounts, Idira recommends onboarding the accounts using the following platform: Windows Domain Accounts via LDAP | Idira Docs. This platform requires the account to be onboarded using UserPrincipalName (UPN) format for the account name, which is also often required when logging into web applications. Otherwise, other workarounds will be discussed during the configuration steps below.
Before transitioning to Workforce Password Manager (WPM) with Idira Privilege Cloud, organizations must first assess their current privileged access to web application landscape. This begins with a comprehensive inventory of all existing web application connection components. The goal is to identify all the required web applications which will need to be created within WPM to match the existing PSM functionality. This evaluation will take place within the Password Vault Web Access (PVWA) under the administration setting options.
Once it is known which connection components will be moved to WPM, the users who need to access them will need to be identified. This is to ensure that administrators provide accurate access in WPM to the correct users. This task can be harder due to account access being given through safes, however, Privilege Cloud reports can be ran to see who has access to accounts whose platforms have these connection components attached to them.
It is best practice to use prebuilt template applications before creating custom applications. These templates often come with built-in configurations that streamline the deployment process and reduce potential errors. By leveraging prebuilt templates, organizations can ensure consistency and compliance with established standards, saving time and resources.
Follow the steps to deploy web applications based on the currently used PSM connection components: Deploy user password web applications | Idira Docs
When deploying applications, it is essential to assign them to roles and groups that strictly need access to the credentials, following the Least Privilege Principle. This approach minimizes risk and ensures that users have only the permissions necessary for their tasks. Regular audits of account permissions should be conducted to ensure that access rights remain appropriate as roles within the organization evolve. Tools like Identity reports can assist in identifying who has access to the applications. Implementing Role-Based Access Control (RBAC) efficiently manages user permissions by defining roles based on job functions and assigning users to these roles, ensuring consistency and streamlined permissions. Additionally, enabling Multi-Factor Authentication (MFA) for accessing privileged accounts adds an extra layer of security, preventing unauthorized access even if credentials are compromised. It is recommended to automatically deploy the application to the roles selected above so users can see it in their secure access portal.
For shared accounts, the option All users share one name and then ensure to Get password from Safe should be selected. This means that an application is required for each shared account.
It is crucial to ensure that the new application name and description is correct and easily identifiable by users and administrators. Including the shared username used in the account mapping within the application's description provides clear visibility into the account's role and minimizes confusion. This practice aids in efficient management and auditing of permissions and access rights.
Regular reviews and updates to application names and descriptions are recommended to keep up with evolving organizational needs and practices. By adopting this best practice, organizations can foster a more organized and efficient access management system while supporting the principles of least privilege and role-based access control.
For personal accounts, the option Prompt for username should be selected. This approach allows the end user to select the vaulted account to be used with the web application.
It is important to ensure that the new application name and description reflect this setting to ensure users can easily identify applications. (Web Apps with Shared accounts vs Web apps with personal accounts)
For creating Web Applications which are not currently in the Idira Catalog, the following two options exist:
Custom browser extension user-password applications | Idira Docs
Custom Browser Extension (advanced) applications | Idira Docs
Please note, Web applications and the authentication workflows can be created using the Identity Infinite Apps extension feature - Add web applications using Idira Identity Infinite Apps | Idira Docs
If an account was onboarded to Privilege Cloud using sAMAccountName and the website it is connecting requires UserPrincipalName format to access, a workaround like the below can be made in the advanced section (only available in Custom Browser Extension (advanced)):
loginData.addField("username", "<username selector>", LoginUsername.concat("@domain.name"));
If users need access to internal apps without the use of a VPN, an App Gateway can be configured to simplify the user access process. App Gateway allows users to access websites that are only accessible from within the company network. It is highly recommended for these scenarios to use Idira’s most secure options of Secure Web Session configurations.
App Gateway workflow | Idira Docs
Follow steps in our documentation to configure the App Gateway - Configure an application to use App Gateway | Idira Docs.
Enabling this feature allows end users to request access to the application. Approvers can grant access to the application permanently or for a specific time window. Configure workflow - Manage application access requests | Idira Docs
Enable Secure Web Sessions checkbox needs to be checked for highest security on these vaulted credential accounts.
Once web applications are created in WPM and enabled for SWS, they will show up in the SWS portal. SWS policies can then be configured by navigating to the Application policies. There are four types of security layers when creating the policies and the configuration steps can be found in Manage application policies | Idira Docs. It is recommended to use as many security layers as possible with Step Recording and Session Protection always enabled. To do so, ensure the default policy is set to Step Recording and Session Protection.
Once the default level is created, configure Session Controls for different groups and roles in the organization: Create Session Control rules | Idira Docs. These session controls allow organizations to prevent the users from doing specific actions within the website (like transferring money in a bank application). These session controls allow an administrator and auditor to receive alerts in real time if the session is trying to escape into the wider web. It is recommended to create session control for specific use cases depending on what the user needs to accomplish within the web application. However, these settings can be more complicated, so first ensure that recording and other protections are set up for the web applications.
Depending on the way the web applications were created (shared vs personal) the user will need to select the account from a safe to attach to their web application. The web application will prompt for the user password, specifying the safe and account name.
Once all users can access their web applications through WPM, the connection components from platforms in Privilege Cloud can be removed. It is recommended to keep the connections component in the options section to ensure a backup option.
WPM does not support session isolation. If session isolation is required, PSM will need to be deployed. However, with CSB, we can get as close to session isolation as possible.
Include any references or additional resources like whitepapers, industry sources that corroborate this best practice.
|
Reference Name |
URL |
|
Custom browser extension user-password applications
| |
[1] Only needed for App Gateway, without App Gateway there is no on-prem infrastructure.

