Freshservice - Create Problem per Asset

Freshservice - Create Problem per Asset creates a Freshservice Problem for each asset that matches a selected query or is selected on an asset page. Axonius links each created Problem to the source asset and adds it to the Axonius Tickets module.

Use this action for:

• Assets 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.

When accessing an enforcement action using the API, you must use the backend form of field names.

Use the Syntax Helper to find the correct name. In the enforcement action, enable Configure Dynamic Values and select Syntax Helper.

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 Aggregated Security Findings.
• See Actions supported for Software.

Required Fields

These fields must be configured to run the Enforcement Action.

• Use stored credentials from the Freshservice adapter - Select this option to use credentials from an existing Freshservice adapter connection. By default, the first connection is selected.

• When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

• Problem name - Enter the Problem subject. The default is Axonius-created problem.
• Problem description - Enter the description for each created Problem. The default is Problem created by Axonius.
• Requester ID - Enter the unique identifier of the Problem requester. Freshservice requires this value for the Problems API.
• Due by - Enter the date and time by which the Problem is due. Freshservice requires this value for the Problems API.
• Priority - Select low, medium, or high. The default is low.
• Impact - Select low, medium, or high. The default is low.

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

• Custom fields (JSON format) - Enter a JSON object with additional Freshservice Problem fields, such as group_id, category, custom_fields, or analysis_fields. Values in the configured required fields take precedence over matching JSON keys.
• Field Mapping - Map Axonius asset fields to Freshservice Problem fields. Mapped dotted field names, such as custom_fields.computer_name, are added as nested Freshservice fields.

• Verify SSL (Optional) (default: enabled) - Selects whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings. This setting is enabled by default on all new adapter settings. If you need to disable SSL verification, make sure you disable this setting.)

APIs

Axonius uses the Freshservice Problems API - POST /api/v2/problems.

Required Ports

Axonius must be able to communicate via the following ports:

• TCP port 443 (HTTPS) — confirm the exact port with your Freshservice administrator.

Required Permissions

The action uses a Freshservice API key with Basic authentication to create Problems. The code change does not define the exact Freshservice role or permission names; confirm that the API key can create Problems with your Freshservice administrator.

To learn more about Enforcement Actions, see Enforcement Actions.