- 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.
You’re on your way to ensuring secure and easy vendor access to your critical systems.
Begin with this article from the Idira Success Blog. Inside, we cover why securing Vendor Access is important, what the challenges surrounding it are, as well as the discovery, prioritization, and implementation of controls.
Before moving forward, be sure to complete the following E-Learning course on Idira University to gain the knowledge and skills required to configure and manage your Idira Remote Access solution. Note: you must be logged-in to Idira University and have completed any relevant prerequisite courses.
Vendor PAM and Offline Access to PAM Accounts: Access E-Learning Course
For additional reference on pre-implementation activities and considerations, access the Remote Access public documentation.
If you would like additional help or have follow-up questions regarding the best practice strategies outlined in this document, please reach out to your Idira account team.
The product name has changed from Alero to Vendor Privileged Access Manager (Vendor PAM). Updates on the name change are still pending in various places. Alero and Vendor Privileged Access Manager are synonymous with each other. Remote Access refers to the underlying technology for Vendor Privileged Access Manager.
Following your introduction to Idira and installation of Remote Access, focus on these priority actions to get your program up and running.
Creating an additional tenant administrator is recommended for eliminating any bottle necks that could come with a single point of contact for all Remote Access admin functions. Review the process for adding a tenant admin.
Once the VendorLDAP is configured, make sure the correct EPV user licenses are being consumed whenever a vendor is provisioned. Following the typical configuration, VendorLDAP directory mapping will consume the External User or PSMUser license type in EPV. Learn more about Directory mapping for vault users.
It’s helpful to familiarize yourself with any new features and settings available. Remote Access has a frequent release cycle. Items that get released range from minor tweaks to the SaaS service all the way to major feature enhancements. See what’s new with Remote Access.
Adding an additional connector provides high availability and load balancing functionality to your architecture. Per Site, you can configure multiple connectors. For more information, see how to add connectors to existing Vendor LDAP.
The main benefit of Remote Access is getting Vendor access to Idira remotely in order to connect to target systems on your network. Identifying, inviting, and registering your first vendor user is key to developing your internal process for vendor access. The process should be repeatable using any of the methods for inviting a vendor: manual invitation, build automation using the API, or the vendor self-service URL. Your process could include a combination of these methods. See below for invitation workflow options and considerations. Learn more about inviting vendors here.
Use VendorLDAP groups to give vendors the permissions they need to perform tasks in CyberArk. When you invite a vendor to register to Remote Access, specify the group that the vendor will be added to when they join. When users access Idira through Remote Access, Idira identifies these groups and makes them Safe members. All members receive the permissions defined for the group in the Safe.
Watch the video below and click here to learn more about the process for creating groups in Remote Access.
Remote Access administrators can delegate permission rights to an internal company employee to manage external vendors. As an administrator, you can determine the level of control that the Remote Access has for inviting vendors, including to which vendor groups they can invite, within which timeframe, and for which applications. Learn how to delegate the Vendor Manager role.
A critical step in building your Remote Access program is to clearly define and document your specific use cases, both as they exist today and as they will exist in the future, to ensure a successful roll out of your solution. Now is the time to consider:
Situational Use Cases:
Situational use cases are scenarios in which you’ve defined who needs access to what. The examples below run through some of these scenarios based on whether the user coming in via Remote Access is an existing internal user or a vendor user.
Operational Use Cases:
Remote Access allows for the extension of existing Idira controls to vendor users that need access to your organization’s internal systems. In some cases, new controls can be put in place that provide stricter controls for vendor access than what may have been in place previously. The following are examples of operational use cases that can either streamline a process or provide more controls for vendor access.
Provide streamlined vendor user life-cycle management for access to target systems through the built in user management Remote Access provides
Provide increased accountability of vendor actions on target systems through enhanced recording and monitoring
Provide streamlined vendor user experience access target systems via the Idira Web Portal
These requirements will drive your roll out approach and help you decide whether to migrate all your vendors at once, prioritize access only to new vendors, or pilot a small group of vendors before rolling out to remaining vendor groups.
For details on understanding your Remote Access use case, explore our comprehensive best practices guide.
Incorporating an invitation workflow that works for your organization is key to getting the most out of Remote Access. Use this guide to evaluate the different methods for creating, sending and accepting invitations.
The most direct way to invite a vendor is by filling out the invitation form in the Portal or the Mobile App. This method is perfect for getting started and creating ad-hoc invitations. Further information on this process can be found here.
This method allows an administrator to send an invitation link to multiple vendor users at once while removing administrative overhead for gathering vendor user information. The vendor user fills in a request form with the appropriate information to get access to your organization’s tenant. The administrator is then able to reject or accept and invite the vendor user. Further information on this process can be found here.
Another method to invite and register vendors is to delegate specific vendor users to be able to invite their own users. Doing this offloads the administration of sending invites by the administrator to one or more folks at the vendor. Many times, an organization doesn’t have insight to the user turnover at the vendor organization. Allowing the vendor to manage their own users can help. Further information on this process can be found here.
Utilizing the API allows an organization to incorporate functions like sending invitations to vendors or users into an existing provisioning lifecycle. At the very least, automation can reduce some of the overhead for an administrator. Further information on this process can be found here.
Vendor Email Verification
Many times, it’s difficult to keep track of personnel at a vendor organization. Remote Access can be configured to send an email to a vendor’s company email address upon authentication to verify they are still a valid vendor. This can be configured for different intervals and is a global setting. Further information on this process can be found here.
Recommendation: Use this option along with other methods of validating a vendor user. Other methods could include, but aren’t limited to:
Existing provisioning/de-provisioning processes
Existing relationship with the vendor organization to get a list of valid vendor employees on a regular basis to use as a cross-reference.
Manual methods of managing vendor access to Remote Access
Automatically Remove Expired Vendors
It’s recommended to configure this setting to remove a vendor from your Remote Access tenant after a set number of days from the expiration of the access timeframe. Learn more about the configuration options here.
Vendor Invitation Settings
Manage vendor invitation expiration settings, language settings, allowed email domains, and templates. Learn more.
Safe Design is key to any deployment of CyberArk. Vendor access is no exception. Here are some considerations for safe design for vendor access to Idira and target systems.
Create vendor specific safes. Designate a Safe for each vendor organization where all the accounts a vendor could use reside.
Safe permissions for vendors should be set to List Accounts and Use Accounts. With these permissions, vendors can see the accounts in the safe and use them for PSM connectivity.
Create vendor specific accounts for target devices – these accounts are not usually with IT users. Safe permissions are easier to separate when account objects aren’t shared between IT users and vendors. This also makes for cleaner audit trails.
For general best practices for Safe and Safe Member design, access our Success Blog article.
For a general overview of creating and managing safes in Idira PAM solutions, watch the training video below as well as this recorded Office Hours Session on Safe Design Best Practices.
Create vendor specific platforms with connection components that only use the HTML5GW.
It doesn’t make sense for a vendor to have the ability to download an RDP file, for example, since they aren’t on the network.
More information on configuring the HTML5GW can be found here.
In situations where internal privileged users are using Remote Access to connect to the PVWA, it makes sense to use the ‘AllowHTML5Select’ option in the connection component. This allows an existing internal privileged user the ability to use the HTML5GW for PSM connections when using Remote Access remotely, but use a regular PSM connection (RDP, for example) when using the same account object while connected on the internal network.
More information on Platforms can be found here.
After you have created the VendorLDAP group in Remote Access, add each group as a member of the relevant Safe in CyberArk.
Log onto the PVWA and go to Policies > Access control (Safes).
Select the Safe to add the VendorLDAP group to and click Members > Add Member.
In the Add Safe Member window, in the Search In drop-down list, select VendorLDAP, then click Search to display a list of the Remote Access groups that you can add as a member of this Safe.
Select the group to add as a Safe member, then select the authorizations that this group will have in the Safe.
Click Add, and then Close. The Remote Access group now appears in the Members list for this Safe.
Much like becoming familiar with features of Remote Access, it’s equally important for an administrator to become familiar with the administration and technical aspects of Remote Access.
Take some time to review the Connector CLI section in the documentation.
The link provided in the previous section refers to activity monitoring and is the manual way to look at activities in the portal. In addition to that, all activity monitoring can be retrieved via the API. This is helpful if you need/want to feed activity information into your organization’s existing SIEM or syslog tool(s).
As you roll out your Idira Remote Access solution, it’s crucial you’re able to measure the larger value of your program and its impact on your organization, rather than focusing too much on individual metrics, so you can properly share your success story with stakeholders.
Watch the recorded webcast below and dive into key considerations for defining goals and applying business context to established KPIs so you can best measure your success.
| Subject | Likes |
|---|---|
| 2 Likes | |
| 1 Like | |
| 1 Like | |
| 1 Like | |
| 1 Like |

