Actions for Heimdal Security #
- Send Data to Heimdal Security. Sends a custom set of Lucidum data to Heimdal 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 Heimdal Security on a regular schedule.
- You can send normalized, enriched Lucidum data to Heimdal Security to be indexed, searched, and analyzed.
Prerequisites #
To execute Heimdal Security actions, you must configure a Heimdal Security 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
Heimdal Security Configuration #
To create a configuration for Heimdal Security actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
-
Host. The hostname or IP address of the Heimdal Security server, for example, rc-dashboard.heimdalsecurity.com
-
Port. The port of the Heimdal Security server. The default value is 443
-
Customer ID. The customer ID of an account with access to the Heimdal Security API. For details, see https://support.heimdalsecurity.com/hc/en-us/articles/360001462138-HEIMDAL-Security-APIs.
-
API Key. Personal API key for an account with access to the Heimdal Security API.For details, see https://support.heimdalsecurity.com/hc/en-us/articles/360001462138-HEIMDAL-Security-APIs.
-
Max # of Records per Payload. The maximum number of records to send to Heimdal Security in each action. The default value is “50”.
Create a New Action #
To create an action for Heimdal Security, contact Lucidum customer care.
