Configure Jira Integration

Connect AttackLens to your Jira instance to create issues directly from security findings. When a finding requires remediation, you can push it to Jira with a single click, complete with severity mapping, affected asset details, and remediation guidance.

INFO

Requires Admin role or higher.

Prerequisites

Before configuring the Jira integration, ensure you have:

• Jira instance URL: The base URL of your Jira instance (e.g., https://yourcompany.atlassian.net for Jira Cloud, or https://jira.internal.company.com for Jira Server/Data Center).
• API token or credentials: A Jira API token (Cloud) or a username/password (Server/Data Center). See Creating a Jira API Token below.
• Target project: The Jira project key where issues will be created (e.g., SEC, VULN).
• Network access: Your AttackLens backend must be able to reach the Jira instance over HTTPS.

Step 1: Navigate to Issue Integrations

Go to Integrations > Issue Integrations in the left sidebar and click Create Integration.

Step 2: Select Jira

Select Jira from the integration type list.

Step 3: Configure Connection

Fill in the connection details:

Instance URL (Required)

The base URL of your Jira instance.

• Jira Cloud: https://yourcompany.atlassian.net
• Jira Server/Data Center: https://jira.internal.company.com

Email (Required for Jira Cloud)

The email address associated with the Jira account that owns the API token.

API Token (Required)

The API token used to authenticate with Jira. This is sent as a Basic Auth header alongside the email.

Project Key (Required)

The key of the Jira project where issues will be created. This is the short prefix that appears before issue numbers (e.g., SEC in SEC-123).

TIP

You can find the project key by navigating to your Jira project and looking at the URL or the issue prefix. The project must already exist in Jira -- AttackLens does not create projects.

Issue Type

Select the Jira issue type to use when creating issues. Common choices:

• Bug: For vulnerability findings.
• Task: For compliance/posture findings.
• Story: For remediation work items.

The available issue types are fetched from your Jira project after you provide the connection details. Click Fetch Issue Types to load the list.

Step 4: Configure Field Mapping

Map AttackLens finding fields to Jira issue fields.

Severity to Priority Mapping

Define how AttackLens finding severities map to Jira priorities:

AttackLens Severity	Jira Priority (Default)
Critical	Highest
High	High
Medium	Medium
Low	Low
Informational	Lowest

You can customize this mapping to match your organization's priority scheme.

Field Mapping

Configure which finding data populates which Jira fields:

AttackLens Field	Jira Field	Notes
Finding title	Summary	Always mapped.
Finding description + remediation	Description	Formatted as Jira markup with sections for description, affected asset, and remediation steps.
Severity	Priority	Based on the severity-to-priority mapping above.
Affected asset name	Custom field (optional)	Map to a custom field if you want the asset name in a structured field.
Policy/Ruleset name	Labels (optional)	Attach the policy or ruleset name as a Jira label.

Step 5: Test the Connection

Click Test Connection to verify that AttackLens can reach your Jira instance and authenticate successfully. The test will:

1. Authenticate with the provided credentials.
2. Verify the project exists and is accessible.
3. Verify the issue type is valid for the project.
4. Confirm that the authenticated user has permission to create issues.

WARNING

If the test fails, check the following:

• The instance URL is correct and reachable from the AttackLens backend.
• The API token has not expired.
• The email address matches the account that owns the token.
• The project key is correct.
• The user has the "Create Issues" permission in the target project.

Step 6: Save

Click Save to create the integration. AttackLens will store the connection details (credentials are encrypted at rest) and the integration will appear in your integrations list.

Creating a Jira API Token

If you do not already have an API token:

1. Log in to https://id.atlassian.com/manage-profile/security/api-tokens.
2. Click Create API token.
3. Enter a label (e.g., "AttackLens Integration").
4. Click Create.
5. Copy the token immediately -- it is only shown once.

TIP

Use a dedicated Jira service account for the integration rather than a personal account. This ensures the integration continues to work when individual employees leave the organization.

Using the Integration

After configuration, you can create Jira issues from findings:

1. Navigate to Findings.
2. Select one or more findings.
3. Click Create Issue.
4. Select the Jira integration.
5. Review the mapped fields and click Create.

The created issue URL is logged in the integration's issue history. See Manage Integrations for details.