Actions for Fortra VM #
- Send Data to Fortra VM. Sends a custom set of Lucidum data to Fortra VM.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to Fortra VM on a regular schedule.
- You can send normalized, enriched Lucidum data to Fortra VM to be indexed, searched, and analyzed.
Prerequisites #
To execute Fortra VM actions, you must configure an API connection beforehand.
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
Fortra VM Configuration #
To create a configuration for Fortra VM actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
- URL. The URL for your regional instances of Fortra VM API. For example, https://api.frontline.cloud/.
-
API Token. API token associated with a Fortra VM account with read and write access to the API. For details on generating the API Token, see https://hstechdocs.helpsystems.com/manuals/digitaldefense/frontline/content/vm/integrations/quickconnectapi.htm.
-
Max # of Records per Payload. The maximum number of records to send to Fortra VM in each action. The default value is “50”.
Create a New Action #
To create an action for Fortra VM, contact Lucidum customer care.
