Zendesk - Create Ticket Per Entity

Zendesk - Create Ticket Per Entity creates a ticket in Zendesk for:

Each asset returned by the selected query or assets selected on the relevant asset page.

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.

These fields must be configured to run the Enforcement Set.

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 Zendesk adapter - Select this option to use the Zendesk connected adapter credentials. By default, the first connection is selected.
- When you select this option, the Select Adapter Connection dropdown is available, and you can choose which adapter connection to use for this Enforcement Action.
Note:
To use this option, you must successfully configure a Zendesk adapter connection.
Requester ID - The ID of the user creating the ticket.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

Ticket Main Settings

These fields are optional.

Ticket subject - Enter a short description of the ticket issue.
Ticket body - Enter a full description of the issue.
Ticket Status - Select the ticket status: new, open, pending, hold, solved, closed.
Assignee ID - Enter the ID of the user assigned to this ticket.
Group ID - Enter the ID of the group to which the user creating the ticket belongs.
Priority (default: Normal) - Select the ticket priority: Low, Normal, High, Urgent.
Create ticket even if no new entities were added - When selected, a ticket is generated even if no new assets were added to the query.
Tags to Add - Select or create new tags to add to the ticket.

Ticket Additional Settings

These fields are optional.

Map Axonius fields to adapter fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.

Note:

For details, see Axonius to External Field Mapping.

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.

Sub Domain - The subdomain used to access Zendesk. For example, Axonius is the subdomain for https://axonius.zendesk.com/.
User Name - The username of an Axonius dedicated user account.
API Key/Token - An API Key/Token associated with a user account that has permissions to perform this action.
Password - The password of the Axonius dedicated user account.
Note:
The ZenDesk API does not support MFA or SAML; an API token is required when using either of the User Name or Password fields.
2FA Secret Key - The secret generated in Zendesk for setting up two-factor authentication for the Zendesk user created to collect SaaS Management data. See Zendesk documentation for instructions on how to set up two-factor authentication (2FA) and generate the 2FA secret.
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.

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.