Integrating with CyberArk Enterprise Password Vault
Before you begin
We recommend that you do not use DNS names in credential broker fields, as it requires a performant and reliable DNS server. Slow DNS queries significantly increase scan times; even with a fast DNS server scan times are impacted. Where multiple names are defined for an IP address, BMC Discovery uses the first name or FQDN returned by the DNS server, which may not be consistent, depending on the DNS server configuration.
Process overview
Task | Task description | Reference |
|---|---|---|
1. | Create the provider user in the CyberArk Enterprise Password Vault. The user that you create for the first time is used to give access to the CyberArk Vault (Safe). You define additional users for access from specific BMC Discovery appliances BMC Discovery Outposts as they are required. | |
2. | Either: | |
Or: Integrating using the CyberArk Enterprise Platform Vault using the AIM Provider requires further steps. The integration uses a locally installed agent (the AIM provider) to interact with CyberArk Enterprise Platform Vault, offering benefits over the REST integration. For more information, contact your CyberArk administrator. | ||
Note: The choice of an integration method is mutually exclusive. If you integrate BMC Discovery with CyberArk Enterprise Platform Vault using the REST API, you cannot access it using the AIM Provider. | ||
3. | After the connection is successful, you configure BMC Discovery credentials that fetch credentials from CyberArk. Instead of using a username and password, you use a query to perform the task. | |
See this video (4:40) for a demonstration of the integration between BMC Discovery and the CyberArk Vault.