Manage Issues
Drill down into APIST issues to review their evidence and logs, update their status, and understand auto-resolution
Harness Runtime Protection Agent (RPA) Issues page provides a view of detected API security issues, enabling you to monitor, analyze, and remediate them effectively. It provides important information, such as severity, endpoint count, and OWASP category.
What you will learn from this topic
By the end of this topic, you will be able to understand:
How to drill down into each issue to access its evidence, context, and logs.
Which statuses an issue can have, and how to change them.
How Harness RPA auto-resolves and deletes issues.
Go to APIST Issues for more details on issues, their lifecycle, and their key components. To learn how to fix an issue, including creating tickets and virtual patches, go to Remediate Issues.
Before you begin
Make a note of the following before working with issues:
Make sure that you understand scans and traffic types, because the evidence available for an issue depends on the traffic type the scan used. Go to Understanding Scans and Traffic Types for more details.
Ensure you are assigned the Security admin or Account Owner role, or the equivalent permissions. Go to Role-Based Access Control (RBAC) for more details.
Issue details panel
The issue details panel displays the evidence, context, and status history of a single issue occurrence. Click an issue name from the issue occurrence list to open it. The panel contains certain fields in the header and three tabs:
Overview: Displays AI-generated insights and evidence for the selected issue occurrence. Go to Issue details panel tabs for more details.
References: Displays external resources related to the issue, including OWASP, CWE, and CAPEC references. Go to Issue details panel tabs for more details.
Status Log: Displays the history of status changes, including who made each change and any associated comments. Go to Issue details panel tabs for more details.
The controls on the left edge of the panel let you close the panel, copy a link to the issue, and move to the previous or next occurrence without returning to the issues table.
Issue details panel header
The table below describes the fields in the panel header:
API Endpoint
Displays the endpoint where Harness RPA detected the issue. Click the endpoint to redirect to the details page. Go to Endpoint Details for more details.
Service
Displays the service that the endpoint belongs to. Click the service name to open its details page. Go to Domains, Services, and Backends for more details.
Environment
Displays the environment in which Harness RPA detected the issue.
Last Seen
Displays the date and time when Harness RPA last detected the issue.
Source
Displays the origin of the issue. For issues detected by a scan, the value is AST.
Severity
Displays the severity of the issue.
CVSS Score
Displays the Common Vulnerability Scoring System (CVSS) score of the issue, for example, 8.1.
OWASP Rank
Displays the OWASP Top 10 category the issue maps to, for example, OWASP 2021:A3.
CWE
Displays the Common Weakness Enumeration (CWE) identifier for the issue, for example, CWE-79.
The panel header also provides the following remediation actions:
Create Jira ticket (
): Go to Create a ticket for more details.Configure ServiceNow for current environment (
): Go to Configure an integration for more details.Configure Azure DevOps for current environment (
): Go to Configure an integration for more details.Create Virtual Patch: Go to Virtual Patching for more details.
Status drop-down: Go to Change the status of an issue for more details.
You can use them to remediate an issue. Go to Remediate Issues for more details.
Issue details panel tabs
The following tabs provide in-depth information on the selected issue:
The Overview tab contains the AI Generated Insight and the Evidence for the selected issue occurrence.
AI Generated Insight
The AI Generated Insight widget explains the specific occurrence in natural language, so that you can understand and prioritize it without first reading the raw request and response. Harness RPA generates it from the evidence of the occurrence, which means the content refers to the actual endpoint, parameter, and payload involved. It contains the following sections:
Quick Summary: Describes what issue Harness RPA found and where, including the affected endpoint, the parameter Harness RPA mutated, the payload it injected, and the response behavior that confirmed the issue.
Impact: Describes what an attacker can achieve by exploiting the issue and the level of risk it poses to user data and system integrity.
Remediation Steps: Describes the actions that resolve the issue, split into the following:
Immediate Fix: Actionable steps you can take right away to address the issue.
Long-term Fix: Changes that prevent the class of issue from recurring.

Evidence
The Evidence section displays the test that detected the issue and the exact request and response involved. Click Evidence to expand it. The section contains the following elements:
Test ID drop-down: Selects the test whose evidence Harness RPA displays, when more than one test detected the issue.
Test summary: Displays the name of the test and the parameter it targeted, followed by these details:
Detected by: Displays the scan and scan run that detected the issue, and the date and time of detection, for example. Clicking the scan run redirects you to that run. Go to Scan Runs for more details.
Status Code: Displays the response code the endpoint returned for the test.
URI: Displays the URL that Harness RPA tested. Click the copy icon to copy it.
Duration: Displays how long the endpoint took to respond to the test.
Original Trace Id: Displays the ID of the original trace on which Harness RPA based the test.
View Traces: Redirects you to the Explorer page, with filters for the endpoint and the test already applied, so that you can analyze the traces Harness RPA captured for the test. Go to Explorer for more details.
Copy as cURL: Opens the Copy cURL command for reverification dialog with the test request as a cURL command. Click Copy to copy it, and run the command against the endpoint to confirm whether the issue still exists.
Assertions tab: Lists the validations Harness RPA ran on the response to decide that the endpoint is vulnerable. Each row displays the Result, Initiator, Parameter, Actual Value, Operator, and Reference Value. Expand a row to view a summary of why the assertion marked the endpoint as vulnerable. Click Add Assertion to add your own validation. Go to Mutation and Assertion Overrides for more details.
Mutations tab: Lists the changes Harness RPA made to the original request to attack the endpoint. Each row displays the Parameter, Initiator, Original Value, Operator, and Mutated Value. Expand a row to view a summary of the change. Click Add Mutation to add your own change. Go to Mutation and Assertion Overrides for more details.
Request tab: Displays the Headers, Cookies, and Body of the request Harness RPA sent. You can view the body as Parsed or Raw.
Response tab: Displays the Headers, Cookies, and Body of the response the endpoint returned.
For each issue detected using APIST, Harness RPA displays the following evidence:
Assertions and Mutations applied by Harness RPA as part of the scan. You can also customize these according to your requirements. Go to Mutation and Assertion Overrides for more details.
The Headers, Cookies, and Body in the Request and Response of the API endpoint.
For issues detected by AI scan policies, Harness RPA displays the evidence as a conversation that triggered the vulnerability. For information on setting up an AI scan, see AI Security Testing.

The References tab lists curated links to external sources, such as the OWASP Top 10, the OWASP cheat sheets, CWE, and CAPEC entries that apply to the issue. You can use these links to understand the attack mechanism and the recommended remediation in more depth.

The Status Log tab displays a timeline of every status change for the issue. Each entry displays when the change happened, the status the issue moved to, and who made the change, for example, Status updated to Open by System. Comments added during a status change also appear here.

Change the status of an issue
Change the status of an issue to tell your team whether it needs attention and to control whether Harness RPA continues to report it. The table below lists the statuses an issue can have:
Open
Harness RPA has detected the issue.
Under Review
The issue has been acknowledged, and you are taking steps to remediate it.
Fixed
The issue has been closed. Harness RPA continues to monitor the asset (API endpoint or service) even after you mark it as fixed. If Harness RPA detects the issue again, it automatically moves the issue to the Reopened state for you to review and resolve.
Not An Issue
You do not want Harness RPA to report the issue. If Harness RPA continues to detect this issue category, it does not move the issue to the Open state.
Accepted Risk
You understand and accept the impact of the issue.
Reopened
Harness RPA has rediscovered the issue. This typically occurs when an issue previously marked as Fixed or Not An Issue is detected again during subsequent scans. Harness RPA sets this status automatically, so it does not appear in the status drop-down.
Follow the given steps to change the status of an issue:
Select Status dropdown in the issue details panel header.
Select the new status for the selected issue.
(Optional) Add a comment describing the change.
After you change the status, the following happens:
Harness RPA records the change, along with your comment, in the Status Log tab of the issue.
If the issue is linked to a Jira ticket, Harness RPA synchronizes the status update with Jira through its bidirectional sync feature.
If you move the issue to Fixed, Not An Issue, or Accepted Risk, the issue no longer appears in the default view of the Issues page, which lists issues in the Open, Reopened, and Under Review states.
In subsequent scans, Harness RPA moves a Fixed issue to Reopened if it detects the issue again, while it does not move a Not An Issue issue to Open.
Go to Update issues for more details on changing the status of issues individually or in bulk.
Auto resolve issues
While you can resolve an issue by changing its status to Fixed, Harness RPA also auto-resolves issues by default in the following scenarios:
Time-based scenario
An issue has not been detected in any of the scans for 60 days since its last occurrence.
Scan-based scenario
An issue has not been detected in 15 consecutive scans since its last observation.
While these are the default thresholds, you can contact Harness RPA Support at support@traceable.ai to modify them according to your requirements.
Example: How auto-resolution works
Consider an API endpoint that is being scanned for the Weak JWT Algorithm attack:
The endpoint has been scanned five times, and the most recent scan detected the issue (vulnerability).
Time-based scenario: This condition is not satisfied, as the issue was just detected, which resets the 60-day timer. The countdown starts only after the most recent detection date.
Scan-based scenario: This condition is not satisfied, as it requires 15 consecutive scans without detection of the issue (vulnerability). As the most recent scan detected the issue, the scan-based counter resets to zero.
Harness RPA resolves the issue automatically if:
15 consecutive scans do not detect the issue.
60 days pass without the issue being detected.
Delete issues
You can delete detected issues from the issue details panel by changing their status to Fixed or Not An Issue. Harness RPA also deletes issues if they are deleted from all sources. For example, if an issue has APIST and Live Traffic as the source, Harness RPA deletes the issue when it is deleted from both sources.
Next steps
APIST Issues: Review, filter, and group the issues that Harness RPA detects.
Remediate Issues: Create tickets and update issues individually or in bulk.
Virtual Patching: Protect an endpoint while your team works on the code-level fix.
Issues: Review the issues detected by a single scan.
Last updated
Was this helpful?