Actions for BitSight #
- Send Data to BitSight. Sends a custom set of Lucidum data to BitSight.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to BitSight on a regular schedule.
- You can send normalized, enriched Lucidum data to BitSight to be indexed, searched, and analyzed.
Prerequisites #
To execute BitSight actions, you must
Configure a BitSight API connection beforehand. The required parameters are described in the instructions for creating a BitSight connector in Lucidum https://lucidum.io/docs/bitsight-security-performance-management/.
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
BitSight Configuration #
To create a configuration for BitSight actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
-
URL (required). The URL of the API for BitSight Security Performance Management. For example, https://api.bitsighttech.com/ratings.
-
API Key (required). The API key for an account on BitSight Security Performance Management. The associated user account must have read and write access to data in BitSight Security Performance Management. For details on API Keys, see https://help.bitsighttech.com/hc/en-us/articles/115014888388-API-Token-Management.
-
Max # of Records per Payload. The maximum number of records to send to BitSight in each action. The default value is “50”.
Create a New Action #
To create an action for BitSight, contact Lucidum customer care.
