- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
Idira Workforce Password Management (WPM) is a cloud-based solution that enables users to securely store and access their professional passwords for web applications. WPM also integrates with Privileged Account Management (PAM) to provide seamless access to shared and privileged accounts. WPM helps users to create strong and unique passwords, avoid password reuse, and reduce the risk of credential theft and compromise.
In this blog post, we will cover the best practices for using WPM effectively. We will discuss how to optimize the architecture, configuration, security, and monitoring of WPM, and provide some tips and tricks to enhance the user experience and productivity. By following these best practices, you can ensure that WPM meets your organization's needs and standards, and that your users can enjoy the benefits of WPM without compromising security.
Introduction
Audience
Architecture
Configuration
Security
Monitoring and Operations
Conclusion
Additional Reading
This technical article is designed for those serving the function of CyberArk Administrator/Security Engineer role. The article can be used by those deploying and operating WPM in their environment and those responsible for the solution's design and rollout.
The architecture of WPM consists of four main components: the user and administration portals, the Idira Identity Browser Extension and Secure Web Access (SWS). The user portal is the web interface where users can manage their personal and shared passwords, and the administration portal is where administrators can configure policies and settings. Idira Identity Browser Extension is a browser add-on that enables users to access their passwords and web applications from any web browser, it is required to autofill password when connecting to different web applications. SWS is a browser add-on that records and protect sessions started from a WPM application.
The following diagram shows how users connect to applications by logging in to Identity portal and then launching the application:
To make the sessions more secure a user might want to use SWS. Here it can be seen that a user can launch a protect application and have SWS protection applied to it:
Ensure that the user's devices meet the system requirements for WPM, as specified in the Idira Docs.
Enable WPM and SWS extension for the different browsers using group policy. This will ensure that users can access their passwords and web applications from any browser, and that they do not miss any updates or patches. You can use the following guides to mass deploy the Idira Identity Browser Extension for Chrome, Microsoft Edge, and Firefox and deploy SWS extension using this guide.
The configuration of WPM involves setting up the policies, settings, and web applications that govern how users can store and access their passwords. The configuration of WPM can be done by administrators or delegated to users, depending on the level of control and flexibility required.
Enable users to add personal applications, unless you want to restrict them to a predefined list of approved applications. Allowing users to add personal applications gives them the convenience and autonomy to manage their own passwords, and reduces the administrative burden of creating and maintaining applications for every user. You can override the permission for specific domains later in the settings, if you want to block certain sites from being managed by the users themselves.
Allow users to customize user-added applications, such as changing descriptions and names, unless you want to maintain a consistent representation of the applications. Allowing users to customize user-added applications does not pose significant security concerns, and can help users to personalize their experience and identify their applications easily. However, you might want to restrict certain aspects like URL or logo customization, to avoid confusion or misuse.
Allow users to view and copy personal passwords, unless you want to enforce a strict policy of never revealing passwords. Generally, allowing users to view or copy their own personal passwords is acceptable, considering these are their personal accounts. The rationale is that users should have the autonomy to manage their personal account credentials, and that they might need to use them outside of WPM, such as on mobile devices or other platforms.
Setup the clipboard to be cleared after the configured time, to reduce the risk of exposing passwords to unauthorized parties. The default time is 60 seconds, which is reasonable for most scenarios. However, you can adjust the time according to your preferences and needs.
Enable Browser Extension Land & Catch, to allow users to capture and save passwords from web forms, and to autofill and submit passwords to web applications. This feature enhances the user experience and productivity, and encourages users to adopt WPM as their primary password manager. However, you can disable this feature if you want to prevent users from capturing or auto filling certain passwords, such as for privileged or sensitive applications.
Disable one-time password for two-factor authentication to applications, unless you want to use WPM as your authenticator app. This feature allows users to generate and use one-time passwords for web applications that support two-factor authentication, such as Google or Facebook. However, this feature might not be compatible with some applications, or might conflict with other authenticator apps that users might prefer to use. Therefore, it is recommended to disable this feature by default, and enable it only for specific applications that require it.
Disable WS-Trust protocol, unless you want to use WPM for federated authentication. This feature allows users to use their WPM credentials to access other web applications that support the WS-Trust protocol, such as Microsoft Office 365 or SharePoint. However, this feature might not be widely used or supported by most applications, or might introduce security risks or complexities. Therefore, it is recommended to disable this feature by default, and enable it only for specific applications that require it.
Restrict access to specific URLs, to prevent users from adding or accessing certain applications, especially those with administrative privileges or sensitive data. This feature allows you to add specific URLs to a restricted list, to ensure that only approved applications are used within the WPM environment.
Configure username restrictions, to block specific usernames from being added to the WPM system. This feature is useful for preventing users from adding personal or sensitive accounts, such as admin or service accounts, to ensure these are managed securely and in line with organizational policies. For example, you can block usernames like "admin" or "root" to ensure that critical system accounts are not added inappropriately.
Configure password requirements, to enforce a strong and consistent password policy for WPM users. These settings depend on your organization's policies, and can include the minimum and maximum length, complexity, expiration, and history of passwords. You can also enable the compromised passwords feature, which checks the user's passwords against a database of known breached passwords, and alerts the user if their password is compromised. However, you might want to disable the option to block users from using compromised passwords, as they might have already set up the password in the application, and blocking them might cause inconvenience or confusion.
Enable email notification, to inform users about important events or actions related to their WPM accounts, such as password changes, login attempts, or security alerts. You can also customize the email template for customer branding or marketing purposes.
Enable password insights, to provide users with feedback and recommendations on how to improve their password security and hygiene. This feature analyzes the user's passwords and generates a score based on various criteria, such as strength, uniqueness, and compromise. It also provides tips and suggestions on how to create and maintain strong and secure passwords. However, this feature does not work for vaulted credentials, which are managed by PAM.
Enable secure web sessions (SWS) on specific admin created applications, to provide an additional layer of security for the web applications that store or process sensitive data. SWS allows users to launch a web application in a secure and isolated session. SWS also uses the policy settings and other settings to secure the application session, such as limiting the session duration, or blocking downloads or uploads. You can enable SWS on any web application that is created by an administrator and published to users.
Once you have reviewed all the above configuration settings. It is important to understand that there are two types of WPM applications: Administrator added applications, and personal applications
Administrator added applications are applications that are created by the ISP administrator and can be automatically published to end users. These applications support SWS for recording and can be provided to users per their applicable role.
Personal Applications are applications that an end user adds themselves using the add application functionality. They can use Land & Catch functionality from the browser extension to save passwords they enter while logging into the web app they are using. It is recommended to let end users know to use these only for business purposes rather than their personal accounts like bank accounts.
The security of WPM involves protecting the passwords and web sessions from unauthorized access, disclosure, or manipulation. The security of WPM depends on the security features and settings of WPM, as well as the security practices and awareness of the users.
To mitigate the risk of clipboard scraping attacks, it is advisable to disable the clipboard history feature within your organization. This functionality permits users to retrieve and paste previously copied content, including passwords, across devices. Nonetheless, it could potentially expose sensitive information to malevolent entities or lead to inadvertent disclosure or improper handling of passwords. Consequently, organizations are encouraged to disable clipboard history and employ a secure password manager extension or browser for copying and pasting passwords.
Harden WPM deployment, to ensure that WPM is configured and maintained according to the security standards and best practices of CyberArk. This includes applying the latest updates and patches to the browser extension and endpoints, enabling encryption and SSL, enforcing strong authentication and authorization, and monitoring and auditing WPM activities. You can use the following guide to harden your WPM deployment.
Activate SWS to implement enhanced security layers, including step recording, continuous authentication, session protection, and session control. These features bolster web session security by logging user actions, confirming identities, preventing data leaks, and ending sessions when necessary. Utilizing these features also requires EPM on user devices.
To block the saving of cookie data on local disks and prevent users from accessing web applications or data across different devices or browsers, use this feature. It enables the removal of cookie data from the user's device post-session and retains it solely in the WPM portal. This ensures that web sessions remain isolated and secure, and that web applications or data are inaccessible from other devices or browsers without WPM.
Instruct users to retrieve their credentials from the vault when available. This practice allows for the secure use of shared and privileged accounts managed by PAM for web application access. It safeguards the proper use of these accounts, ensuring they remain secure and unexposed. Users are advised against using personal credentials or storing them in WPM when vaulted credentials are intended for use.
Monitoring and operating WPM involves overseeing its availability and utilization. The effectiveness of WPM's monitoring and operations hinges on its reporting and auditing features, as well as the operational protocols and practices implemented by administrators and users.
Designate SWS auditors to secure access to session recordings. By assigning specific users or roles as SWS auditors, they are empowered to access and download web session recordings captured by SWS. This measure ensures that web sessions undergo scrutiny for compliance, security, and quality assurance, facilitating the timely detection and resolution of any issues or incidents.
Leverage Identity reports for enhanced understanding and oversight of WPM usage and activities. These reports allow for the production and examination of detailed data and metrics concerning WPM users, applications, passwords, and events, aiding in the verification of WPM's operational integrity and the prompt identification and remediation of any irregularities or issues.
Utilize WPM reports to assess and enhance user password security and hygiene. These reports allow the generation and review of detailed information and feedback regarding password strength, uniqueness, and potential compromises. They are instrumental in verifying adherence to password policies and best practices, as well as in addressing and rectifying any risks or vulnerabilities.
This blog post outlines several best practices for WPM architecture, configuration, security, and monitoring operations. Drawing from our expertise as cybersecurity professionals in the SaaS identity and privileged access management domain, we aim to assist you in enhancing your WPM deployment and strengthening your security stance. Additionally, these practices are designed to foster an improved user experience, thereby boosting user adoption and satisfaction.
Securing Workforce Web Application Credentials with Idira Workforce Password Management is another success blog that discusses implementation strategies.
| Subject | Likes |
|---|---|
| 2 Likes | |
| 1 Like | |
| 1 Like | |
| 1 Like | |
| 1 Like |

