Issues Overview

The Issues page in Traceable is your central command center for monitoring API risks. If you are responsible for the organization’s API security, you log into Traceable and head over to the Issues page. This page is a hub where all potential vulnerabilities, risky patterns, and compliance gaps are surfaced via discovery using various sources.

What will you Learn from this Topic?

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

Understand what Issues are and how Traceable detects and displays them.
Understand the Issue life-cycle, from discovery to remediation and monitoring
Understand the key components such as:
- Visual charts for severity and status trends
- Issue listings with column-level information
- Grouping and Filtering options to organize and prioritize issues effectively

If you already have an understanding of these components and want to learn how you can drill down and manage an issue, see Issue Management.

What are Issues and How does Traceable Identify Them?

Issues are security gaps in your API definition that threat actors may exploit to attack your API infrastructure. Traceable identifies assets or API endpoints and services in your environment through the discovery process. After Traceable discovers the API endpoints, it scans APIs and the associated services for issues and shows them on the Issues page.

Note
Traceable does not scan APIs for issues while they are in the learning phase.

How is the Issues Page Helpful?

The Issues page gives you a streamlined, intuitive experience to help you detect issues, understand them deeply, conduct a risk assessment, and resolve them quickly. Even when you have resolved an issue, Traceable continuously monitors the API endpoints that you have remediated and secured. It reports an issue if it finds any in the future; hence, continuous monitoring. For more information, see Journey of an Issue.

Whether you are a security engineer, developer, or DevOps lead, Traceable gives you the visibility and control to secure your APIs effectively.

Journey of an Issue

Every security story in Traceable begins with an API, and that story is mapped through an issue lifecycle. The issue-management life cycle process helps identify and remediate security risks before threat actors can exploit them.

Following is the life-cycle and how issues flow within it:

Stage	Description
Discovery (Identify API Endpoints)	API Identification via live traffic or integrations.
Scan (Issue Scan)	Scans on your identified APIs to detect potential vulnerabilities.
Analysis (Risk Assessment)	You analyze the issue: What it is, where it occurred, and the risk associated with it.
Remediation	You act on the issue: fix it, mark it under review, accept the risk, or dismiss it.
Monitoring (Verification and Monitoring)	Traceable verifies the remediation on the APIs, tracks its reoccurrence and reopens it, if necessary.

This feedback loop ensures that you are always working with relevant, current, and actionable security information and issues.

Understanding Issues

The Issues page is a centralized hub for visualizing all vulnerabilities detected in both External and Internal APIs. It provides a comprehensive overview of open issues, their severity, and key details like the time it was last seen. This dashboard offers a clear snapshot of your system’s security risks and helps you investigate and prioritize their resolution efficiently. To view the Issues page, navigate to Catalog → API Risk → Issues.

For information on how to drill down into an issue, manage its status and remediate it, and the rules around resolution and deletion, see Issue Management.

Issue Types

Traceable, based on its continuous learning, detects the following types of issues:

Category	Issue Type
Insecure Design	Query params contain sensitive data Lack of encryption API params contain URL HTTP redirect Insecure HTTP method Username and password enumeration Regex DOS
Remote Code Execution	Java Log4Shell Buffer overflow Integer overflow error
Security Headers	HSTS header misconfiguration Missing nosniff in content type options header CSP header misconfiguration
Authentication	Basic authentication method Unauthenticated access Weak password
SQL Injection	Blind SQL injection Error-based SQL injection
Data Exposure	Excessive data exposure
JSON Web Token (JWT)	JWT token expiry JWT weak algorithm JWT algorithm confusion JWT invalid signature JWT JKU misuse JWT missing audience claim
Improper asset management	Multiple versions of API
Business logic	Parameter pollution Mass assignment
Security misconfiguration	HTTP only site Server version disclosure .env information leak HTTPS not accessible Directory listing leak
Access control	Rate limiting
TLS	TLS not implemented TLS/DTLS CBC attack (Lucky13)(CVE-2013-0169) Self-signed certificate
Authorization	Broken object-level authorization Broken function level authorization
Cross-site scripting	Reflected cross-site scripting
Server-side request forgery	Server-side request forgery blind

Issue Sources

The Issues page displays issues discovered during run time protection, API security testing (AST), or detected by an Issue policy. These three different categories of issues are based on different sources:

Live Traffic
AST
Compliance

Issue Severity

Traceable categorizes detected issues based on their criticality and impact on your application ecosystem. Following are the categories in the descending order of severity:

Critical
High
Medium
Low

Key Components

The page contains key components that help you quickly assess and understand issues. Below are the main elements of the page and their significance:

Visual Insights

At the top of the page, Traceable shows the following charts:

Chart	Description
Issues by Severity	Shows the count of issues by severity (Severity Breakdown). You can click on the severity to filter the results based on your selection.
Issues by Status	Shows a trend of the open and resolved issues over the past 30 days.

Collectively, the above charts provide an overview of your application’s security health and trends, based on which you can take the necessary actions.

Issue Listings

Each entry on the page represents a unique issue, when grouped by Issue Name (default), with each column providing the following details. If you wish to drill down into an issue and manage it individually according to your requirements, see Navigating the Issues Flow.

Column	Description
Issue Name	Specifies the name of the issue (e.g. Broken Object Level Authorization). This name is used across the Traceable platform for identification purposes.
Endpoint	Specifies the API or system endpoint (e.g. `PUT /identity/api/v2/user/videos/{video_id}`) where Traceable observed the issue. This helps you focus on which parts of the infrastructure are targeted and may require additional security.
Severity	Each issue is categorized by color-coded labels (e.g., Low, Medium, High, Critical), allowing you to gauge its impact and urgency quickly. This is helpful as it gives you a way to prioritize issue resolution based on risk, focusing on high-severity issues that may require immediate action, while lower-severity issues can be addressed as part of routine maintenance.
Source	Displays information about the origin of the issue (e.g. AST). This helps identify whether the issue got detected as part of the API scan, Issue policy, or testing.
OWASP API Top 10	Specifies the mapping to the OWASP API Top 10 security risks. This helps you understand and prioritize issues based on their global recognition.
Last Seen	Specifies the most recent occurrence of the issue. This helps you determine whether the issue is still active, has reappeared, or is no longer a threat.
Status	Displays the current status of the issue. This serves as a communication medium to indicate whether or not an issue requires prioritization. For more information on the available statuses, see Issue Management.
Integrations	Displays the Jira icon. This helps you track an issue by creating a Jira ticket directly from the Traceable platform. Note This icon is enabled only when you configure the Jira integration. For more information, see Jira integration.
Actions	Enables you to edit the policy through which Traceable detected the issue. Note This option is available only for Issues having Compliance as the Source.

Grouping and Filtering Options

While Traceable groups the issues on the page based on their name, you can filter and group issues based on several criteria:

Group By

Category	Description
Issue Name	Groups issues based on the specific issue. This helps you understand how widespread an issue is across environments and focus on resolving the most recurring issues.
Endpoint	Groups issues based on the endpoints in which they were detected. This helps you analyze the risk exposure for endpoints and prioritize resolution based on them.
Category	Groups issues based on broader classifications such as Authentication, Authorization, or JSON Web Token. This helps you analyze the issues from a broader level, as to which issues are most common across the system.
OWASP API Top 10	Groups issues based on their mapping in OWASP API Top 10 categories. This helps you align your analysis based on the recognized industry standards.

To group the issues using either of the above criteria, use the Group by drop-down, as shown in the image above.

Filters

Narrow the issues based on options, such as status, severity, source, timestamp, or sensitivity ensuring that you can analyze them accordingly. To filter the issues based on your requirements, use the Filter () icon, as shown in the image above.

For information on managing issues based on the above groups and filters, see Issue Management.