Ivanti Endpoint Security Actions

Actions for Ivanti Endpoint Security #

• Send Data to Ivanti Endpoint Security. Sends a custom set of Lucidum data to Ivanti Endpoint Security.

Use Cases #

Below are the possible use cases for these actions:

• If you want to run Lucidum “headless”, you can send relevant data to Ivanti Endpoint Security on a regular schedule.

• You can send normalized, enriched Lucidum data to Ivanti Endpoint Security to be indexed, searched, and analyzed.

Prerequisites #

To execute Ivanti Endpoint Security actions, you must:

• Configure an Ivanti Endpoint Security API connection beforehand. The required parameters are described in the instructions for creating an  Ivanti Endpoint Security connector in Lucidum https://lucidum.io/docs/ivanti-endpoint-security/.

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

Ivanti Endpoint Security Configuration #

To create a configuration for Ivanti Endpoint Security actions:

• Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.

• Host. The hostname of the server for Ivanti Endpoint Security API.

• Port. The port on the Ivanti Endpoint Security server. Default port is 389

• API Token. API token for a Ivanti Endpoint Security account with read access.

• Max # of Records per Payload. The maximum number of records to send to Ivanti Endpoint Security in each action. The default value is “50”.

Create a New Action #

To create an action for Ivanti Endpoint Security, contact Lucidum customer care.