Map AccuKnox Issues to Custom Jira Fields with Simplified Ticketing Templates

The Problem

A prospect asked a sharp question: “Can AccuKnox map finding attributes — like asset type — into our Jira custom fields?”

The answer wasn’t “yes, with a custom integration build.” It was just yes. Out of the box. No code. This post walks through exactly how.

How Custom Ticket Mapping to Jira Works

End-to-end architecture — AccuKnox Scanner → Ticket Template with AssetType → Jira New Ticket → Jira Automation populates the custom field.

The flow has two halves:

1. AccuKnox side: The scanner finds a vulnerability. A ticket template embeds the asset’s metadata (e.g., Container) into the ticket description using a template variable. AccuKnox creates the Jira ticket.
2. Jira side: A Jira Automation rule fires on ticket creation. It reads the embedded value from the description using a regex, then writes it into a custom field called Asset Type.

Step 1 — Set Up the Custom Field in Jira

Jira Space Settings → Fields. The “Asset Type” custom field (short text) added to the acme-project space.

In Jira, go to Space Settings → Fields and add a global custom field:

• Name: Asset Type
• Type: Short text (plain text only)
• Description: AccuKnox Asset type

Add this field to the relevant ticket screen. That’s the only Jira field config needed.

A Jira ticket with the Asset Type custom field populated — value “cloud-account” mapped directly from AccuKnox.

Step 2 — Build the Jira Automation Rule

Jira Automation rule “AccuKnox Auto assign Asset type” — trigger on work item created, create variable via regex, then edit the Asset Type field.

Three components:

Trigger: When a work item is created.

Condition: Issue type equals Feature.

Action 1 — Create Variable: Variable name assetType, smart value:

{{issue.description.text.match(“\[AssetType=([^\]]+)\]”)}}

Action 2 — Edit Field: Set Asset Type = {{assetType}}.

AccuKnox embeds [AssetType=Container] in the description. The regex pulls out Container. Jira writes it to the field. Done — within milliseconds of ticket creation.

Step 3 — Configure the AccuKnox Ticket Template

AccuKnox Ticket Template “Findings with AssetType” — dynamic template body includes [AssetType={{asset.type.category}}] which resolves at ticket creation time.

In AccuKnox, create a Ticket Template with this in the dynamic body:

[AssetType={{asset.type.category}}] {{asset}} | {{location}} | {{vulnerability.name}} | …

{{asset.type.category}} resolves to the real value from the finding’s raw JSON — e.g., Container or Cluster.

Raw JSON of an AccuKnox finding — asset.type.category reads “Container”, the value injected into the Jira description.

Step 4 — Wire the Integration

AccuKnox Ticket Configuration — “Findings with AssetType” template mapped to acme-project, Issue type: Feature, auto-maintain + keep-syncing enabled.

Configure the Jira integration in AccuKnox:

• Default template: Findings with AssetType
• Project: your Jira project
• Issue type: Feature (must match the Jira automation condition)
• Enable: Auto Maintain Tickets + Keep Syncing Closed Tickets

Two Ways to Create Tickets

Manual

Create Ticket modal — select “Vulnerability” ticket configuration, hit Create.

Generated ticket description showing [AssetType=Container] embedded in the Asset column, ready to be parsed by Jira automation.

Select a finding in AccuKnox → choose the Vulnerability config → click Create. The description auto-populates with the [AssetType=…] value.

Automated (Rules Engine)

AccuKnox Rules Engine — auto-create tickets for Risk Factor = Critical or High. Condition types: Last Seen, Date Discovered, Location, Status, Vulnerability Name, and more.

The Rules Engine triggers on Risk Factor = Critical or High + is new = true. Every qualifying finding automatically becomes a Jira ticket with the correct Asset Type populated. Set expiration to never.

Native Jira Filtering by Asset Type

Jira ticket KAN-10 — Asset Type field set to “Container” by the automation rule.

Jira filter by Asset Type = “Container” — only possible because the value is in a structured custom field, not buried in description text.

Because the value lives in a proper custom field, your team can:

• Filter boards by Container vs Cluster vs Cloud Account
• Build separate security workstreams per asset type
• Use JQL for advanced queries
• Trigger further Jira automations based on asset type

FAQs