Aurva

Jira Integration

Auto-create Jira tickets for Aurva findings with priority mapping, custom fields, and bidirectional state sync.

The Jira integration creates tickets automatically when Aurva detects policy violations or risk findings, keeping your security backlog in sync without manual effort.

Setup

  1. 1

    Generate a Jira API token

    In Atlassian, go to Account Settings -> Security -> API tokens and create a token.

  2. 2

    Configure in Aurva

    Navigate to Settings -> Integrations -> Jira and provide:

    • Jira base URL (e.g. https://yourcompany.atlassian.net)
    • Email address associated with the API token
    • API token
    • Default project key (e.g. SEC)
    • Default issue type (e.g. Bug or Task)
  3. 3

    Assign to an Alert Route

    Go to Alert Routes and add Jira as a destination on one or more routes.

Priority Mapping

Aurva severity levels map to Jira priority fields:

Aurva SeverityJira Priority
CriticalP1 - Highest
HighP2 - High
MediumP3 - Medium
LowP4 - Low

You can customise this mapping in Settings -> Integrations -> Jira -> Priority Mapping.

Custom Fields

Map Aurva event attributes to Jira custom fields to enrich tickets:

Aurva AttributeExample Jira Field
Policy nameSecurity Policy (text)
Data assetAffected System (text)
ClassifiersData Types (multi-select)
EnvironmentEnvironment (dropdown)

Configure field mappings in the Jira integration settings.

Bidirectional Sync

When bidirectional sync is enabled:

  • Aurva -> Jira: New findings create tickets; updated findings add comments.
  • Jira -> Aurva: Closing or resolving a Jira ticket marks the corresponding finding as resolved in Aurva.

Sync runs on a configurable interval (default: every 5 minutes).

Deduplication

Aurva prevents duplicate tickets by tracking a unique finding ID per Jira issue. If the same finding triggers again while an open ticket exists, Aurva adds a comment to the existing ticket instead of creating a new one.