- 08 Jul 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
SymphonyAI Summit - Create Ticket per Entity
- Updated on 08 Jul 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
SymphonyAI Summit - Create Ticket per Entity creates a ticket in SymphonyAI Summit for each entity retrieved from the saved query supplied as a trigger (or from the entities selected in the asset table).
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
- Add description - Add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories 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.
- Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
- 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 the SymphonyAI Summit adapter - Select this option to use the the first connected SymphonyAI Summit adapter credentials.
Required Fields
These fields must be configured to run the Enforcement Set.
- Caller Email - Specify the caller's email address.
- Assigned WorkGroup Name - Enter the workgroup name to which the new ticket will be assigned.
- Instance Name (default: IT) - The name of the SymphonyAI Summit instance. The current default is “IT” but can be any word.
- Urgency Name - Set the level of urgency for the ticket from the list: High, Medium, or Low.
- Description - Enter a description.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
Connection Parameters
If Use stored credentials from the SymphonyAI Summit adapter is disabled, these fields are required:
- Host Name or IP Address - The full URL of the SymphonyAI Summit server.
- API Key - If necessary, include how this is generated or obtained.
Verify SSL - 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 - Connect the adapter to a proxy instead of directly connecting it to the domain.
HTTPS Proxy User Name - The user name to use when connecting to the server using the HTTPS Proxy.
HTTPS Proxy Password - The password to use when connecting to the server using the HTTPS Proxy.
- Static Attributes - Define the static SymphonyAI Summit field IDs and their values. Click + to add a static attribute. Multiple static attributes can be added.
- Attach CSV to ticket - Select to attach a CSV to the ticket.
Gateway Name - Select the gateway through which to connect to perform the action.
APIs
Axonius uses the SummitAI API.
For more details about other Enforcement Actions available, see Action Library.