---
title: "Scan Details"
slug: "ast-scan-details"
description: "Explore how to interpret Traceable’s scan results, including identified vulnerabilities, API coverage, scan runs, executed tests, and reachability tests. Learn how to use these insights to fine-tune your API security posture and troubleshoot scan behavior."
status: "update"
updated: 2026-06-08T05:33:29Z
published: 2026-06-08T05:33:29Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://traceabledocs.document360.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Scan Details

##### Updates (April 2026 to June 2026)

- *June 2026* —
  - Updated the page to add information about assigning labels to a scan. For more information, see [Assign labels to a scan](/v1/docs/ast-scan-details#assign-labels-to-a-scan).
  - Updated the page to add information about details displayed on the Scans page. For more information, see [Understand Scans view](/v1/docs/ast-scan-details#understand-scans-view).
- *April 2026* —
  - Updated the page to add information about the details displayed for each scan run.
  - Updated the page to add information about re-running a scan. For more information, see [Understand and leverage scan details](/v1/docs/ast-scan-details#understand-and-leverage-scan-details), **Scan Runs** tab.
- *April 2026* — Updated the page to add information about the Reachability Tests tab. For more information, see [Understand and leverage scan details](/v1/docs/ast-scan-details#understand-and-leverage-scan-details), **Reachability Tests** tab.

After a scan execution is complete, the Scan Details page highlights key information about the scan. It provides comprehensive information on the identified issues, the APIs covered (tested), the list of scan runs performed, and the specific tests executed during each scan run.

## What will you learn in this topic?

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

- The details displayed on the Scans page.
- The details displayed for each scan.
- The way you can leverage the details in each tab to analyze the test results and customize security testing.
- The steps to assign labels to each scan.

---

## Understand Scans view

The **Scans** page provides a centralized list of all the configured and executed scans in your environment. You can use this view to monitor scan execution status, review coverage, and identify scans that detected issues and require your attention.

![Scans View](https://cdn.document360.io/24f14f07-13d1-4684-8fae-6d8f811768ee/Images/Documentation/traceable_ast_scans_view.png)

Scans View

### Widget on the Scans page

At the top of the page, Traceable displays the **Open Issues** trend chart, which shows the number of unresolved vulnerabilities over the past 7 days. This helps you:

- Understand whether risk exposure is increasing or decreasing.
- Measure remediation progress over the week.
- Identify sudden spikes after new scan executions.

A steady increase may indicate newly discovered issues or delayed remediation. A downward trend usually reflects effective issue resolution.

### Table on the Scans page

Below the chart, Traceable also displays a **Scans** table that lists execution details and results. Each row highlights a scan configuration and its most recent execution status. The table includes the following columns:

| Column | Description |
| --- | --- |
| **Last Run Status** | Displays the most recent scan execution. This status can be from *Completed*, *Queued*, or *Aborted*. This helps you identify whether the scan executed successfully or requires your attention. |
| **Scan Name** | Displays the name of the scan. You can click the scan to view detailed execution insights and findings. For more information, see the section below. |
| **Policy Name** | Displays the policy selected during scan creation. This defines the attack depth and test depth applied to APIs. |
| **Environment** | Displays the environment associated with the scan. |
| **Scanned APIs** | Displays the number of APIs tested during scan execution. A higher number indicates improved coverage. |
| **Vulnerabilities** | Displays the number of issues identified in the scan. You can click the value to view the detected vulnerabilities for the respective scan on the **Issues** page. |
| **Last Run** | Displays when the scan was most recently executed. This helps you determine if the scan coverage is up to date. |
| **Total Run** | Displays the total number of scan executions. Higher scan runs may indicate scheduled scans. |

### Actions on the Scans page

The Scans page provides the following actions to organize and manage scans:

| Action | Description |
| --- | --- |
| **Filter** | The **Filter** (![](https://cdn.document360.io/24f14f07-13d1-4684-8fae-6d8f811768ee/Images/Documentation/traceable_filter_icon.png)) icon in the page’s top left corner helps you refine the list of displayed scans based on attributes, such as *Status*. |
| **Group By** | The **Group By** drop-down in the page’s top right corner helps you organize scans based on the following attributes: - **Policy** — Updates the table displayed on the page based on the policies for which you have configured scans. - **Environment** — Updates the table displayed on the page based on the environments for which you have configured scans. - **Label** — Updates the table displayed on the page based on the labels you have assigned to the scans. For more information, see [Assign labels to a scan](/v1/docs/ast-scan-details#assign-labels-to-a-scan). |
| **Search** | The **Search** bar in the page’s top left corner helps you locate a specific scan by typing its name. |
| **Delete** a scan | The **Ellipse** (![](https://cdn.document360.io/24f14f07-13d1-4684-8fae-6d8f811768ee/Images/Documentation/traceable_catalog_posture_events_ellipse_icon.png)) icon corresponding to a scan in the table helps you delete scans that are no longer required. > [!NOTE] > Note > > Deleted scans cannot be restored. |

---

## Understand and leverage scan details

The following tabs outline the key details displayed in each scan tab and explain how to use the data to tailor and analyze tests according to your requirements.

**Reachability Tests**

The **Reachability Tests** tab provides visibility into whether Traceable can successfully reach API endpoints before generating and executing security tests during a *Replay* or *DAST* scan.

> [!NOTE]
> Note
> 
> - This tab is available for *XAST Replay* and *DAST* scans only.
> - This tab displays data when you use CLI version *2.5.0*and above.

Traceable executes reachability tests differently depending on the scan type:

- **XAST Replay** scans — Traceable replays previously captured traces for each endpoint.
- **DAST** scans — Traceable uses request samples from the specification file that you uploaded during scan creation.

These reachability tests are executed without applying mutations or assertions. Based on the response received, Traceable determines whether the endpoint is reachable and eligible for security testing.

Traceable generates security tests only for endpoints that are successfully reachable. If an endpoint is unreachable, no security tests are generated for that endpoint in the **Tests** tab.

### Understand the Reachability Tests tab

![](https://cdn.document360.io/24f14f07-13d1-4684-8fae-6d8f811768ee/Images/Documentation/traceable_ast_scan_details_replay_reachability_test.png)

Reachability Tests

The tab displays a table with the following details:

| Column | Description |
| --- | --- |
| **Endpoint** | The API endpoint for which Traceable executed the reachability test. |
| **Service** | The service associated with the endpoint. |
| **Status** | Indicates whether the endpoint is Reachable, Unreachable, Authentication Failed, or Error. |
| **Response Code** | The HTTP or gRPC response code returned by the endpoint during the reachability test. |

Traceable determines reachability status based on the response received from the endpoint:

| Status | Description |
| --- | --- |
| **Reachable** | The endpoint returned a successful response, for example, an *HTTP 2xx* or *3xx* status code. |
| **Unreachable** | The endpoint returned an unsuccessful response, for example, *HTTP 4xx*or *5xx*, excluding authentication failures. |
| **Authentication Failed** | The endpoint returned an authentication-related failure, for example, *HTTP 401*, *403*, or *407*. |
| **Error** | Traceable could not send the request to the endpoint. |

If an endpoint is temporarily unreachable, Traceable retries the reachability test multiple times before determining the final status.

Traceable also provides the following features in the tab:

| Feature | Description |
| --- | --- |
| **Search** bar | Type and locate any of the above details. |
| **Filter**icon | Refine the data displayed in the tab using various metrics. After you apply, you can also save the filter for later use. The saved filters are visible under **Filter** → **Saved** tab. |
| **Download** icon | Download the list of reachability tests associated with a scan for offline analysis. |

---

### Leverage the data shown in the tab

You can use the **Reachability Tests** tab to understand endpoint availability and interpret scan behavior more effectively.

For example, if security tests are not generated for certain endpoints in the **Tests** tab, you can review their reachability status to determine whether the endpoints were unreachable or blocked due to authentication failures during the scan.

Similarly, if multiple endpoints show an *Authentication Failed* status, you can verify whether the configured authentication settings allow Traceable to access the endpoints correctly.

Consistent *Reachable* statuses across endpoints indicate that Traceable can successfully replay traffic and proceed with generating security tests. Unexpected spikes in *Unreachable* or *Error* statuses may indicate configuration issues, environment instability, or changes in endpoint availability.

The **Reachability Tests** tab helps you:

- Identify endpoints that are not eligible for security testing.
- Troubleshoot authentication and connectivity issues.
- Validate endpoint availability before generating security tests.
- Analyze changes in endpoint reachability across scan executions.

---

## Assign labels to a scan

Labels enable you to categorize scans according to your conventions, such as *critical APIs*, *regression*, *production*, and *testing*. Once assigned, you can use these labels to group and organize scans on the **Scans** page. For more information, see [Actions on the Scans page](/v1/docs/ast-scan-details#actions-on-the-scans-page). These labels help you group and organize a large number of scans and improve visibility when using the **Group By** option. For example, assigning a label named *production* may help you group and review all production-related scans.

To assign a label to a scan, complete the following steps:

![Assign a Scan Label](https://cdn.document360.io/24f14f07-13d1-4684-8fae-6d8f811768ee/Images/Documentation/traceable_ast_scans_labels.png)

Assign a Scan Label

1. Click a scan in the table on the **Scans** page.
2. In the **Scan Details** page’s top right corner, click **Manage Labels**.
3. Select one or more labels from the list of pre-existing labels and/or type to create a new one.
4. Click **Apply**.

Once assigned, the label is available for filtering and grouping on the **Scans** page.