Actions for CyberArk #
- Send Data to CyberArk. Sends a custom set of Lucidum data to CyberArk.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to CyberArk on a regular schedule.
- You can send normalized, enriched Lucidum data to CyberArk to be indexed, searched, and analyzed.
Prerequisites #
To execute CyberArk actions, you must
Configure a CyberArk API connection beforehand. The required parameters are described in the instructions for creating a CyberArk connector in Lucidum https://lucidum.io/docs/cyberark-endpoint-privilege-manager-epm/.
NOTE. The specified account should have read and write permissions.
Workflows #
- Creating a new Configuration and a new Action
- Cloning an Existing Action
- Creating a new Action from the Location Results page
- Editing a Configuration
- Editing an Action
- Viewing Information about an Action
CyberArk Configuration #
To create a configuration for CyberArk actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
- URL. The URL for the CyberArk API. For example, http://178.218.57.190/EPM/API/11.5.0.1.
- Login URL. The URL of the CyberArk dispatcher server for the CyberArk services. For example, https://login.epm.cyberark.com
- Application ID. Source application ID that distinguishes between REST API calls from CyberArk and REST API calls from another application. This name must be unique in CyberArk. We recommend that you specify a name, like “Lucidum”.
- Username. User name for an account be that is an Account Administrator and has view and write scope for all sets managed by CyberArk.
- Password. The password for the CyberArk EPM account.
- Max # of Records per Payload. The maximum number of records to send to CyberArk in each action. The default value is “50”.
Create a New Action #
To create an action for CyberArk, contact Lucidum customer care.
