SymphonyAI Summit - Create Ticket per Entity
  • 22 Sep 2024
  • 2 Minutes to read
  • Dark
    Light
  • PDF

SymphonyAI Summit - Create Ticket per Entity

  • Dark
    Light
  • PDF

Article summary

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.

Note:

General Settings

  • 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 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 and Credentials

When 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.

  • Host Name or IP Address - The full URL of the SymphonyAI Summit server.
  • API Key -An API key.
  • 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.
  • HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the  HTTPS Proxy.
  • HTTPS Proxy Password (optional) - 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.


Was this article helpful?