CyberArk Alero - Delete User
- 06 Feb 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
CyberArk Alero - Delete User
- Updated on 06 Feb 2025
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
CyberArk Alero - Delete User deletes a user for:
- Assets returned by the selected query or assets selected on the relevant asset page.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
Note:
- Not all asset types are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
Required Fields
These fields must be configured to run the Enforcement Set.
- Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
- Host Name or IP Address - The hostname or IP address of the CyberArk Alero server.
- Tenant ID - Specify the Tenant ID value.
- Service Account JSON - Upload the JSON file required to make the API calls. For information on how to create a service account and the JSON file, see Service accounts.
- Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
- HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
- HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.
- HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.
- Gateway Name - Select the Gateway through which to connect to perform the action.
APIs
Axonius uses the Remote Access API.
Required Permissions
The stored credentials must have permission to perform this Enforcement Action.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?