Jira Assets Platform

Notice:

Jira has deprecated this solution. Consequently, this Enforcement Action is no longer available in Axonius.

Jira Assets Platform - Add Assets creates a new asset or updates an existing asset in Jira Assets Platform for each of the assets that are the results of the saved query supplied as a trigger (or devices that were selected in the asset table).

NOTE

Updating an asset will overwrite its properties with the properties defined in the request object from Axonius.

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.

Note:

To find the correct schema and the Jira Insight Fields IDs:

Go to your Jira instance and then click Assets then Schema.
In Schema, select the object type and then click Attributes. The field IDs are listed here.

Only users with admin privileges can see this menu.

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.

Required Fields

These fields must be configured to run the Enforcement Set.

Jira Domain (required) - The hostname or IP address of the Atlassian Jira Assets Platform server.
User Name and API key (required) - The credentials for a user account that has the Required Permissions to read, add and to update assets.
Asset type appKey and Asset type originId (required, default: AxoniusEC | axonius-enforcement) - Specify the appKey and the originId of an Asset Type you have created on your JIRA Assets Platform project.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
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.
Assignee account ID (optional, default: empty) - Specify the Atlassian account id for the assignee.
- If supplied, the new/updated asset will be assigned to the specified account.
- If not supplied and Assignee email is not supplied, the new/updated asset will not be assigned.
Assignee email (optional, default: empty) - Specify the email address for the assignee. The email must be associated with a valid Atlassian account id.
- If supplied and there is an account id associated with this email address, the new/updated asset will be assigned to the specified account.
- If not supplied, or if supplied and there is no account id associated with this email address, the new/updated asset will not be assigned.
NOTE

If both Assignee account ID and Assignee email are supplied, the action will fail.

APIs

Axonius uses the Atlassian Jira Asset Platform - Create or Update Asset API.

Required Permissions

The value supplied in User Name and in API Key must have read, add and update access to devices.

To integrate Axonius with Jira, you need to do the following :

Create a user in Atlassian with access to Jira. The user should be part of the most basic group which is jira-software-users.
Log in to Jira using the created user and generate an API token.
For cloud based Atlassian sites, use the following URL to generate an API token: https://id.atlassian.com/manage/api-tokens#

For more details about other Enforcement Actions available, see Action Library.