BitSight - Assign Role to User
BitSight - Assign Role to User assigns a role to BitSight user for each user returned by the saved query supplied as a trigger (or devices selected in the asset table).
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.
- Use stored credentials from BitSight Security Ratings adapter - Select this option to use BitSight Security Ratings connected adapter credentials.
-
When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
-
Note
To use this option, you must successfully configure an BitSight Security Ratings adapter connection.
- Role - Select the role to assign the user.
-
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.
Additional Fields
These fields are optional.
-
- User guid - The guid of the user to which to assign the role.
Connection and CredentialsWhen Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.
BitSight Domain - The hostname or IP address of the Datadog server.
API Key - API key associated with a user account that has the Required Permissions to perform this action.
Company Name - The name of the company from which to fetch data. Leave empty to fetch data from parent company.
CIDR Data CSV File - Upload the .csv file with your CIDR data. This is a CSV file that allows adding data for a specific IP CIDR range. The CSV file should contain the following columns, "CIDR Block", "Country", "Attributed To", "Source", "AS Number". If an IP address is contained in the CIDR block in the CSV file, the values from the other columns in this file are applied to the device.
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.
Justification reason - Enter the reason the user is being created.
Gateway Name - Select the Gateway through which to connect to perform the action.
Required Permissions
The stored credentials, or those provided in Connection and Credentials, must have permission to perform this Enforcement Action.
For more details about other Enforcement Actions available, see Action Library.
Updated about 14 hours ago
