Manage Integrations

After configuring your issue integrations, you can view their status, edit connection details, review created issues, or delete integrations that are no longer needed.

INFO

Requires Admin role or higher.

Viewing Integrations

Navigate to Integrations > Issue Integrations to see all configured integrations.

The integrations list displays:

Column	Description
Name	The integration name (auto-generated or custom).
Type	Jira, ServiceNow, or GitHub Issues.
Status	Connected or Error.
Target	The project key (Jira), instance (ServiceNow), or repository (GitHub).
Issues Created	Total number of issues created through this integration.
Last Used	Timestamp of the most recent issue creation.

Editing an Integration

To modify an existing integration:

1. Click on the integration in the list to open its detail view.
2. Click Edit.
3. Update the desired fields (URL, credentials, project, mapping, etc.).
4. Click Test Connection to verify the updated configuration.
5. Click Save.

INFO

When editing credentials (API tokens, passwords), the current value is not displayed for security reasons. You must enter the new value in full. If you do not change the credential field, the existing stored credential remains in use.

Common Edits

• Rotating credentials: When an API token is about to expire or has been compromised, update the credential field with the new value.
• Changing the target project: If your team moves to a new Jira project or GitHub repository, update the project key or repository field.
• Adjusting severity mapping: Fine-tune how AttackLens severities map to external priorities as your organization's processes evolve.

Viewing Created Issues

Each integration maintains a log of all issues created through it. To view the log:

1. Click on the integration in the list.
2. Navigate to the Issues Log tab.

The issues log shows:

Column	Description
Finding	The AttackLens finding that triggered the issue.
External Issue	The issue identifier in the external system (e.g., SEC-42, INC0012345, #87).
URL	A direct link to the issue in the external system. Click to open it.
Created At	When the issue was created.
Created By	The AttackLens user who triggered the issue creation.
Status	Success or Failed.

Failed Issues

If an issue creation failed (e.g., due to a temporary network error or permission issue), it appears in the log with a Failed status and an error message. You can:

• Review the error message for details.
• Fix the underlying issue (network, permissions, configuration).
• Retry by going back to the finding and creating the issue again.

Deleting an Integration

To permanently remove an integration:

1. Click on the integration in the list.
2. Click Delete.
3. Confirm the deletion in the dialog.

WARNING

Deleting an integration is permanent and cannot be undone. The integration's configuration, credentials, and issue creation log will be removed. Issues that were already created in the external system (Jira, ServiceNow, GitHub) are not affected -- they remain in the external system.

Troubleshooting

Integration shows Error status

The Error status indicates that AttackLens cannot connect to the external system. Common causes:

• Expired credentials: API tokens or passwords have expired. Edit the integration and provide new credentials.
• Network issues: The AttackLens backend cannot reach the external system. Check firewall rules for outbound HTTPS.
• Permission changes: The service account's permissions in the external system have been modified. Verify the account still has the required roles.
• URL changes: The external system's URL has changed (e.g., after a migration). Update the instance URL in the integration configuration.

Issues are created with wrong priority/labels

Review the severity mapping in the integration configuration. The mapping may not match your organization's current priority scheme. Edit the integration and adjust the mapping.

Duplicate issues

AttackLens does not currently prevent duplicate issue creation. If you create an issue for the same finding multiple times, multiple issues will be created in the external system. Check the issues log before creating a new issue to avoid duplicates.