> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/discovery/risk/issue-management.md).

# Issue Management

Investigate, update, and remediate the security issues that Harness detects across your APIs and AI assets.

<details>

<summary><strong>Updates (October 2026 to December 2026)</strong></summary>

*October 2026* — Updated the topic to cover issues on AI assets, such as AI APIs, MCP servers, tools, prompts, and resources, and to reflect the redesigned **Issues** page.

</details>

The **Issues** page lists the security issues that Harness detects across your application programming interfaces (APIs) and AI assets. [AI assets](https://developer.harness.io/ai-security/use-ai-security/ai-assets.md) include [AI APIs](https://developer.harness.io/ai-security/use-ai-security/ai-asset-details.md#ai-apis-and-their-details1) and Model Context Protocol (MCP) assets, such as [MCP servers](https://developer.harness.io/ai-security/use-ai-security/ai-asset-details.md#mcp-servers-details), [MCP tools](https://developer.harness.io/ai-security/use-ai-security/ai-asset-details.md#mcp-tools-details), [MCP prompts](https://developer.harness.io/ai-security/use-ai-security/ai-asset-details.md#mcp-prompts-details), and [MCP resources](https://developer.harness.io/ai-security/use-ai-security/ai-asset-details.md#mcp-resources-details).<br>

This topic shows how you investigate an issue, review its evidence, and track it to resolution through status changes and project management tickets. For more information about issue types, sources, severity, and the Issues page, see [Issues Overview](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/discovery/risk/issues-overview.md).

### What you will learn from this topic

By the end of this topic, you will be able to:

* Navigate the issues flow and open an issue to review its details, evidence, and status history.
* Update issue statuses and create project management tickets, one issue at a time or in bulk.
* Understand how Harness auto-resolves and deletes issues based on their detection source.

***

### Before you begin

Before you investigate and remediate issues, review the following terms and requirements:

* **Security issue**: A security gap in an asset that threat actors may exploit. Each issue has a type, a source indicating how Harness found it, and a severity ranging that shows how Harness found it, and a severity from *Informational* to *Critical*. For more information about issue types, sources, and severity, see [Issues Overview](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/discovery/risk/issues-overview.md).
* **Issue evidence**: The data that led Harness to report the issue, such as a request URL, a response status code, or asset attributes. For more information about evidence, see [Evidence](#evidence).
* **Issue status**: The state of an issue in your workflow, such as *Open*, *Under review*, or *Fixed*. For more information about each status, see [Supported statuses](#supported-statuses).
* **Issue resolution**: How an issue closes. You set a status such as *Fixed*, or Harness resolves the issue automatically once it no longer detects it. For more information about automatic resolution, see [Auto-resolve issues](#auto-resolve-issues).
* **Project management integration**: Creating tickets requires a configured integration with Jira, ServiceNow ITSM, or Azure DevOps. For more information about configuring integrations, see [Project Management](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/integrations/project-management.md).

***

### Navigate issues

When you open the **Issues** page, you first see two charts that summarize your issues by severity and status. Below the charts, a list shows your issues in groups, and a search field, filters, and a **Group by** dropdown help you narrow that list.

The page shows the same issues at three levels of detail. Click a row to move from one level to the next. The following table describes each level:

| Level                   | What it shows                                 | Question it answers                              | What you do                          |
| ----------------------- | --------------------------------------------- | ------------------------------------------------ | ------------------------------------ |
| **Issue groups**        | One issue type, such as an exposed MCP prompt | Which kinds of problems do I have, and how many? | Narrow the list and decide priority  |
| **Issues**              | One issue type found on one specific asset    | Where exactly does the problem occur?            | Change the status or create a ticket |
| **Issue details panel** | Everything that Harness knows about one issue | Is the problem real, and how do I fix it?        | Investigate, then act                |

#### Level 1: Issue groups

The **Issues** page is under **Discovery** → **Risk** → **Issues**. The page opens at the first level, where each row is an issue group. By default, Harness groups issues by **Issue Name**, so each group collects all issues of that issue type.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-924f487774b0cb1af1abb68f684ae7aac56e368d%2Fdiscovery_issue_groups.png?alt=media" alt="Issue groups showing issues grouped by issue name, along with severity, issue count, framework references, and last seen time." width="563"><figcaption><p>Issue groups</p></figcaption></figure>

In the example, the *Externally Exposed MCP Prompt Containing Sensitive Data* group shows *76* in the **Issues** column. This means that Harness found this issue type 76 times across your assets. Each row in a group also shows the **Severity**, **Framework References**, and **Last Seen** time for the issue type. For more information about issue listings and their columns, see [Issue listings](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/discovery/risk/issues-overview.md#issue-listings).

#### Level 2: Individual issues

An issue group tells you how widespread an issue type is, but not where it occurs. To find out, click the **Expand** (<i class="fa-angle-right">:angle-right:</i>) icon next to the group. The group opens into a list of its issues, and each issue is the issue type found on one specific asset.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-6d4421fa96f578b40f71ff2299fad4f404e19330%2Fdiscovery_issues_in_a_group.png?alt=media" alt="Issues in a group showing individual issues and their affected assets." width="563"><figcaption><p>Issues in a group</p></figcaption></figure>

In the example, when you expand the *Unauthenticated External MCP Tool* group, the page lists its 39 issues, one for each affected asset.

The list shows the following columns for each issue:

| Column                   | Description                                                                                                                                                                                                                                                                                                                                   |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Issue Name**           | The issue type, which is the same for every issue in the group. When you click the name, the issue details panel opens.                                                                                                                                                                                                                       |
| **Asset**                | The asset where Harness found the issue, such as an API endpoint, an MCP tool, an MCP prompt, or an MCP resource.                                                                                                                                                                                                                             |
| **Severity**             | The severity of the issue, such as *Informational*, *Low*, *Medium*, *High*, or *Critical.*                                                                                                                                                                                                                                                   |
| **Source**               | How Harness found the issue. For more information about each issue source, see [Issue sources](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/discovery/risk/issues-overview.md#issue-sources).                                                                                 |
| **Framework References** | The security framework references that the issue maps to, such as *OWASP MCP 2025:MCP1* or *CWE-200*.                                                                                                                                                                                                                                         |
| **Last Seen**            | The most recent time that Harness detected the issue on this asset.                                                                                                                                                                                                                                                                           |
| **Status**               | The status of the issue. Select the status dropdown to change it. For more information about each status, see [Supported statuses](#supported-statuses).                                                                                                                                                                                      |
| **Jira**                 | Click the **Jira** (<i class="fa-jira">:jira:</i>) icon to create a Jira ticket for the issue.                                                                                                                                                                                                                                                |
| **Azure DevOps**         | Click the **Azure DevOps** (<img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-be024b156f0d7d9057cf3f0c7b061f8aed58a872%2Fimage.png?alt=media" alt="" data-size="line">) icon to create an Azure DevOps work item for the issue.                      |
| **Servicenow Itsm**      | Click the **ServiceNow ITSM** (<img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-5985b39a347158d4be72e842281f33437fbc385f%2FServiceNow%20ITSM%20icon.png?alt=media" alt="" data-size="line">) icon to create a ServiceNow ITSM ticket for the issue. |
| **Actions**              | The **More** ( <i class="fa-ellipsis-vertical">:ellipsis-vertical:</i> ) icon opens the **Edit Issue policy** option. This option is available only for issues created by custom policies and opens the corresponding policy for editing.                                                                                                     |

Because each issue belongs to a single asset, this is the level at which you act. A status or ticket applies to a single issue on a single asset, not to the whole group. For more information about changing statuses and creating tickets, see [Remediate issues](#remediate-issues).

#### Level 3: Issue details panel

The list of issues in a group is enough for a quick status change or ticket. When you need to understand an issue before you act on it, click its name to open the issue details panel.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-eeb43341b963a1cd87cb53cc5115da4c321ca3f9%2Fdiscovery_issue_details%20_panel.png?alt=media" alt="Issue details panel showing the affected asset, environment, severity, CVSS score, and other issue details." width="563"><figcaption><p>Issue details panel</p></figcaption></figure>

The panel contains the following sections:

* **Issue details**: The top of the panel displays the issue type and its attributes. The first set of attributes identifies the affected asset. For API issues, this includes the **API Endpoint** and its **Service**. For MCP asset issues, this includes the affected asset (such as MCP Prompt) and the **MCP Server Hostname**.

  Every issue also displays the **Environment**, **Last Seen**, **Source**, **Severity**, **CVSS Score** (Common Vulnerability Scoring System), **OWASP Rank**, and **CWE** (Common Weakness Enumeration). The asset name is a link that opens the corresponding asset.
* **Overview**: The **Overview** tab explains the issue type and why Harness reported it. It includes a **Description**, the **Evidence** that Harness collected, the **Impact** of the issue, the **Attack Methodology**, and **Mitigation** guidance. You can start with the **Evidence** to confirm the issue is real before changing its status.
* **References**: The **References** tab lists trusted external sources that explain the nature, impact, and remediation of the issue type. They help you understand how the attack works and what it affects.
* **Status Log**: The **Status Log** tab shows a timeline of all status changes for this issue, including timestamps and comments. It shows when and how the issue was opened, reopened, or fixed.
* **Remediation actions**: The top-right corner of the panel contains the **Jira**, **ServiceNow ITSM**, and **Azure DevOps** icons, along with the status dropdown. These are the same actions that the issue row offers at the second level.

#### **Evidence**

The **Evidence** section in the **Overview** tab shows the data that led Harness to report the issue. Its content depends on the asset type:

* **API issues**: Harness shows the *5* most recent pieces of evidence from the past 24 hours, including the request URL and response status code. You can open the span of each piece to view the full request and response.
* **MCP asset issues**: Harness shows the asset attributes that led to the issue, such as **Is Internet Facing** for an MCP prompt.

{% hint style="info" %}
**Evidence for dormant APIs and API Security Testing issues**

* For dormant APIs, which are APIs that have not received traffic recently, Harness shows the *5* most recent pieces of evidence from the last *90* days instead of the last *24* hours.
* For issues with *API Security Testing* as the source, you can customize the detection conditions. For more information about customizing detection conditions, see [Mutation and Assertion Overrides](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/api-security-testing/advanced-usage/mutation-and-assertion-overrides.md).
  {% endhint %}

If you enable AI Features in your account, the **Overview** tab also shows **AI Generated Insights** along with the evidence. These context-sensitive insights help you analyze and prioritize the issue and plan its remediation.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-a9ef5cf2a752e4e32d84e8adc451bd7fca427ddb%2Fdiscovery_issues_ai_remediation.png?alt=media" alt="" width="563"><figcaption><p><strong>AI Generated Insights</strong></p></figcaption></figure>

***

### Manage status

After you investigate an issue, the next step is to act on it. You record your decision as a status, and you hand off the fix by creating a ticket in your project management tool. Every status change appears in the **Status Log** tab of the issue, so the history stays with the issue.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-4e72ea3a7a27fdeec21e280f46cc95c6b89dbc37%2Fdiscovery_issues_status_log.png?alt=media" alt="Issue details panel showing the Status Log, where status changes are recorded for the issue." width="563"><figcaption><p>Status Log</p></figcaption></figure>

#### Supported statuses

The status tells Harness and your team where the issue stands. You can set an issue to any of the following statuses:

| Status            | Use it when                                                                                                                        | What happens next                                                                                      |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Open**          | Harness sets this status when it first detects the issue.                                                                          | The issue stays open until you change the status or Harness auto-resolves it.                          |
| **Under review**  | You have triaged the issue and someone is working on a fix.                                                                        | Your team can see that the issue has an owner.                                                         |
| **Fixed**         | You have shipped a fix and want to close the issue now, instead of waiting for auto-resolution.                                    | Harness keeps monitoring the asset. If it detects the issue again, it moves the issue to **Reopened**. |
| **Not an issue**  | The issue is a false positive, because the finding does not apply to your asset.                                                   | Harness stops reporting the issue. It does not reopen the issue, even if it detects the issue again.   |
| **Accepted risk** | The issue is real, but you have decided not to fix it. For example, the asset is an internal test service with no production data. | The issue stays on record as a known risk that your team has accepted.                                 |
| **Reopened**      | Harness sets this status when it detects a closed issue again. You can also set it yourself to reopen an issue.                    | Treat the issue as newly open. Check the **Status Log** tab to see why it was closed before.           |

***

### Remediate issues

Status changes and tickets work the same way whether you act on one issue or many. The difference is where you start:

* **Individual update**: Update one issue at a time, from its row in an expanded group or from its issue details panel. You can use this when you need to investigate each issue before you decide.
* **Bulk update**: Select several issues in expanded groups and update them together. You can use this when the same decision applies to many issues, for example, when you mark all issues on an internal test service as *Accepted risk*.

The following tabs outline the steps for the methods above:

{% tabs %}
{% tab title="Individual update" %}
The following steps update one issue:

1. Navigate to **Discovery** → **Risk** → **Issues**.
2. Click the **Expand** icon next to the issue group that contains the issue.
3. Locate the issue in the expanded group.
4. In the row of the issue, take one of the following actions:

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-a20cd107ba95c1db81916d51a4c9f31292dab171%2Fdiscovery_issue_remediation_individual_update.png?alt=media" alt="Individual remediation showing the available actions for a single issue." width="563"><figcaption><p>Individual remediation</p></figcaption></figure>

* **Create a Jira ticket**: Click the **Jira** (<i class="fa-jira">:jira:</i>) icon, then enter the ticket details. The **Link Existing Jira** option links existing related Jira tickets instead. For more information about configuring issue linking in Jira, see [Configure issue linking in Jira](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-linking/).
* **Create a ServiceNow ITSM ticket**: Click the **ServiceNow ITSM** (<img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-5985b39a347158d4be72e842281f33437fbc385f%2FServiceNow%20ITSM%20icon.png?alt=media" alt="" data-size="line">) icon, then enter the ticket details. For more information about ServiceNow ITSM ticket fields, see [ServiceNow ITSM Integration](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/integrations/project-management/servicenow-itsm-integration.md).
* **Create an Azure DevOps work item**: Click the **Azure DevOps** (<img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-be024b156f0d7d9057cf3f0c7b061f8aed58a872%2Fimage.png?alt=media" alt="" data-size="line">) icon, then enter the work item details. For more information about Azure DevOps work item fields, see [Azure DevOps Integration](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/integrations/project-management/azure-devops-integration.md).
* **Change the status**: Select the status dropdown. In the panel that appears, select the new status and, optionally, enter a comment that describes the change. A comment helps your team understand the decision later, especially for *"Not an issue" and "Accepted risk"*.

The issue details panel offers the same actions. When you review an issue in the panel, the icons and the status dropdown are in its top-right corner.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-078851f461e683a9759c97619e12ff5ececd26ca%2Fdiscovery_issues_issue_remediation_details_panel.png?alt=media" alt=""><figcaption><p>Issue remediation from details panel</p></figcaption></figure>

{% hint style="info" %}
**Configure an integration from the issue**

If you have not configured an integration, click its icon to configure it. For more information about configuring project management integrations, see [Project Management](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/integrations/project-management.md).
{% endhint %}

Any comment that you enter with a status change appears in the **Status Log** tab of the issue details panel.
{% endtab %}

{% tab title="Bulk update" %}
The following steps update several issues at once:

1. Navigate to **Discovery** → **Risk** → **Issues**.
2. Narrow the list with filters or the **Group by** dropdown.
3. Click the **Expand** icon next to each group containing issues you want to update.
4. Select the checkbox next to each issue that you want to update.
5. In the action bar, click one of the following options:

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-202427d112987d485811e54f8a425758ec03a9b6%2Fdiscovery_issue_remediation_bulk_update.png?alt=media" alt="Bulk remediation showing multiple issues selected for a status update."><figcaption><p>Bulk remediation</p></figcaption></figure>

* **Update Status**: In the panel that appears, select the new status for the selected issues and, optionally, enter a comment that describes the change. The comment appears in the **Status Log** tab of each issue. The following interactive demo walks you through updating the status of several issues at once:

{% @arcade/embed url="<https://app.arcade.software/share/LCOpMNRdeMgqruwgNaTC>" flowId="LCOpMNRdeMgqruwgNaTC" %}

* **Jira**: Click the **Jira** (<i class="fa-jira">:jira:</i>) icon to create Jira tickets for the selected issues.
* **ServiceNow ITSM**: Click the **ServiceNow ITSM** (<img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-5985b39a347158d4be72e842281f33437fbc385f%2FServiceNow%20ITSM%20icon.png?alt=media" alt="" data-size="line">) icon to create ServiceNow ITSM tickets for the selected issues.

If any of the selected issues are already linked to Jira tickets, Harness asks you to select one of the following options:

* **View linked issues**: Creates tickets only for the unlinked issues and lets you view the existing Jira links.
* **Unlink and create new**: Removes the existing Jira links and creates new tickets for all selected issues.

{% hint style="info" %}
**Integration requirements for bulk ticket creation**

* You need a configured Jira or ServiceNow ITSM integration to create tickets in bulk. If you have not configured one, click its icon to complete the setup. For more information about configuring Jira or ServiceNow ITSM integrations, see [Jira Integration](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/integrations/project-management/jira-integration.md) or [ServiceNow ITSM Integration](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/integrations/project-management/servicenow-itsm-integration.md).
* When you create Jira tickets in bulk, you can also update the status of the selected issues from the same panel. Harness records each status change in the **Status Log** tab. Harness also keeps the status in sync with the linked Jira tickets in both directions. A status change in Harness updates the Jira ticket, and a status change in Jira updates the issue in Harness.
  {% endhint %}
  {% endtab %}
  {% endtabs %}

***

### Auto-resolve issues

Besides the statuses you set, Harness automatically resolves an issue once it no longer detects it. The following table lists the applicability and scenario of auto-resolution for each source:

| <p>Applicability and Scenario →<br>Source ↓</p> | Auto-Resolution | Scenario 1                                                                     | Scenario 2                                                                          |
| ----------------------------------------------- | --------------- | ------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------- |
| Live Traffic                                    | Yes             | Harness has not detected the issue in the *14* days since its last occurrence. | Not Applicable.                                                                     |
| API Security Testing                            | Yes             | Harness has not detected the issue in the *60* days since its last occurrence. | Harness does not detect the issue in the *15* scans following its last observation. |
| Compliance                                      | Yes             | Harness has not detected the issue in the *14* days since its last occurrence. | Not Applicable.                                                                     |

{% hint style="info" %}
**Timing and customization of auto-resolution**

* The status of an auto-resolved issue can take up to *24* hours to appear in Harness.
* While Harness sets the above auto-resolution timelines for *Live Traffic* and *Compliance* by default, you can contact your Account Executive to customize them according to your requirements.<br>
  {% endhint %}

***

### Delete an issue

You can delete an issue from the issue details panel when you change its status to *Fixed* or *Not an issue*. Harness also deletes an issue once it has been removed from all its sources. For example, an issue might have both *Live Traffic* and *API Security Testing* as sources. Harness deletes that issue only after it has been removed from both sources.

***

### Next steps

The following topics help you extend this workflow:

* For more information about the issue types Harness detects for APIs and AI assets, see [Issues Overview](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/discovery/risk/issues-overview.md).
* For more information about configuring Jira, ServiceNow ITSM, or Azure DevOps for ticket creation, see [Project Management](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/integrations/project-management.md).
* For more information about how Harness detects conformance issues for MCP assets, see [Conformance Analysis](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/discovery/risk/conformance-analysis.md).

{% @harness-feedback/feedback %}
