> 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-api-security-testing/product-overview/readme/api-security-dashboard.md).

# API Security Dashboard

Review API exposure, open issues, test coverage, threat activity, and traffic in the API Security dashboard of Harness Runtime Protection Agent (RPA).

The API Security Board in Harness Runtime Protection Agent (RPA) provides a consolidated view of your API security posture. It brings together data on API exposure, security issues, test coverage, threat activity, and traffic patterns. Use it to identify risky APIs, track how issues and threats change over time, and decide what to investigate first. You can filter the data by environment and time range, and then navigate to the relevant pages to investigate individual APIs, issues, or security events

## What you will learn from this topic

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

* Navigate to the API Security dashboard and its sections.
* Filter the data by environment and time range.
* Understand the widgets and analyze their metrics.

***

## Before you begin

The dashboard reflects the data that Harness collects, so some widgets show no data until you set up the following:

* **API traffic:** Harness must receive traffic from your applications. Without traffic, the overview shows no APIs, issues, or threat activity.
* **API documentation (optional):** Upload documentation for your APIs so that Harness can identify shadow APIs in the **API Classification** widget. For more information about API conformance, see [Conformance Analysis](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/risk/conformance-analysis.md).
* **API scans (optional):** Run Application Security Testing (AST) scans on your APIs so that the **API Test Coverage** card can count tested APIs. For more information about scan results, see [Scan Details](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/api-security-testing/ast-basics-and-workflow/scan-details.md).

***

## Overview

The API Security dashboard organizes API security data into summary cards and widgets.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-ebc61c65b210fb31a9b0465dc9eed98080603957%2Fdiscovery_api_security_dashboard.png?alt=media" alt="The full API Security dashboard, with four summary cards across the top, the API Classification and APIs with Toxic Combinations widgets, the framework references table, and the Issues Trend, Traffic Distribution, and Threat Actors widgets" width="563"><figcaption><p>API Security dashboard</p></figcaption></figure>

The page has the following sections:

* **Summary cards:** Total APIs, open critical and high-severity issues, API test coverage, and total threat traffic.
* **API Classification:** How your APIs break down by exposure and risk.
* **APIs with Toxic Combinations:** Attribute combinations that indicate greater exposure.
* **Open Issues & Security Events by Framework References:** Open issues mapped to references from security and compliance frameworks, along with related security events and threat activities.
* **Trend widgets:** Charts that plot data over time:
  * **Issues Trend:** Opened and resolved issues.
  * **Traffic Distribution:** Total traffic against monitored and blocked threat traffic.
* **Threat Actors:** The current number of threat actors at each severity level.

***

## Navigate to the API Security dashboard

The API Security dashboard is displayed by default when you log in to Harness RPA. To navigate to it from another page, do one of the following:

* Click the Harness RPA icon.
* Navigate to **Insights →** **API Security.**

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-9e29ebcc42f108c49083a3e42c8c17af44f71404%2Fapi_security_dashboard_navigation.png?alt=media" alt="The Insights menu expanded in the left navigation, with API Security selected above AI Security, Explore Data, Custom Boards, and Reports" width="563"><figcaption><p>API Security dashboard navigation</p></figcaption></figure>

***

## **Environment and time filters**

The environment and time range filters at the top of the API Security dashboard control which data the widgets display.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-0e1bf5398371d612bdd2674fefba9c8b4f3566a4%2Fapi_security_environment_and_time_filters.png?alt=media" alt="The All Environments dropdown, the time range dropdown set to Last 30 days, and the Refresh button, highlighted at the top of the dashboard" width="563"><figcaption><p>Environment and time filters</p></figcaption></figure>

To view data for a specific environment and time period, follow these steps:

1. Select an environment from the **All Environments** dropdown.
2. Select a time range of up to 90 days, such as **Last 30 days**.
3. Click **Refresh** to reload the data.

The page updates to reflect the selected environment and time range. Not every value responds to the time range, so a label below each widget title tells you how the selected range applies. For example, if you select **Last 30 days**:

* A widget labeled **in selected range** includes only data from the last 30 days.
* A widget labeled **as of today** shows the current total, regardless of the range you selected.
* A widget labeled **Time filter is not applied here** applies only to API inventory data. It displays statistics based on the current inventory counts and classifications, regardless of the selected time range.

### Change indicators

A change indicator appears below the headline number on the following cards and widgets. It shows, as a percentage, how much the value changed for the selected time range:

* **Open Critical & High Sev Issues**
* **Total Threat Traffic**
* **Issues Trend**
* **Traffic Distribution**

Two comparison bases are in use. The **Open Critical & High Sev Issues** card compares the number of open issues at each end of the range. The other three sum their values across the range and compare that sum with the preceding period of the same length. Because the bases differ, the same time range can produce very different percentages.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-3dda32da3b00e6c422529367b5930b1ef7ba35b3%2Fapi_security_dashboard_change_Indicator.png?alt=media" alt="The Open Critical &#x26; High Sev Issues and Total Threat Traffic cards with their change indicators highlighted" width="563"><figcaption><p>Change Indicator</p></figcaption></figure>

#### **Open Critical & High Sev Issues**

The headline number is the count of issues open on the last day of the selected time range. The change indicator compares it with the count that was open on the first day of that range.

Harness calculates the change as follows:

`Change = (Open issues on the last day of the range − Open issues on the first day of the range) ÷ Open issues on the first day of the range × 100`

A range such as **Last 30 days** ends today, so the headline number is the current count. A custom range ends on the date you select, so the headline number is the count on that date.

The following example shows the same card with three time ranges selected:

| Time range                | Headline number (open at end of range) | Open at start of range | Change                              |
| ------------------------- | -------------------------------------- | ---------------------- | ----------------------------------- |
| **Last 30 days**          | 142 (today)                            | 152 (30 days ago)      | (142 − 152) ÷ 152 × 100 = **−6.6%** |
| **Last 60 days**          | 142 (today)                            | 130 (60 days ago)      | (142 − 130) ÷ 130 × 100 = **+9.2%** |
| **August 1 to August 31** | 128 (August 31)                        | 140 (August 1)         | (128 − 140) ÷ 140 × 100 = **−8.6%** |

Every last range ends today, so it always shows today's count, even if the range goes far back. In this example, today's count is 142, so both last rows show 142 and differ only in their starting count. The custom range ends on August 31, so its headline number is the count on that day. A negative value means fewer issues were open at the end of the range than at the start.

#### **Total Threat Traffic and the trend widgets**

The **Total Threat Traffic** card, the **Issues Trend** widget, and the **Traffic Distribution** widget share the same comparison. The headline number is the sum of values across every day in the selected time range. The change indicator compares it with the sum for the period of the same length immediately before that range.

Harness calculates the change as follows:

`Change = (Sum of daily values in range − Sum of daily values in preceding period) ÷ Sum of daily values in preceding period × 100`

The following example shows the **Total Threat Traffic** card with three time ranges selected:

| Time range       | Headline number (sum for range) | Preceding period   | Sum for preceding period | Change                                           |
| ---------------- | ------------------------------- | ------------------ | ------------------------ | ------------------------------------------------ |
| **Last 1 week**  | 820,000                         | 8 to 14 days ago   | 640,000                  | (820,000 − 640,000) ÷ 640,000 × 100 = **+28.1%** |
| **Last 30 days** | 3,500,000 (3.5M)                | 31 to 60 days ago  | 3,300,000                | (3.5M − 3.3M) ÷ 3.3M × 100 = **+6.1%**           |
| **Last 60 days** | 6,800,000 (6.8M)                | 61 to 120 days ago | Not available            | Not shown                                        |

Unlike the **Open Critical & High Sev Issues** card, this card sums threat traffic across the selected time range, so its headline value changes with the range. For **Last 60 days**, the preceding 60-day period falls outside Harness’s 90-day data retention window, so the change indicator is not shown.

When you change the time range, both the headline number and the comparison update accordingly.

{% hint style="info" %}
**Change indicator limits**

Harness retains data for 90 days, which limits how far back a change indicator can compare:

* **Total Threat Traffic**, **Issues Trend**, and **Traffic Distribution:** Not shown for time ranges longer than 45 days, because the comparison needs a preceding period of the same length.
* **Open Critical & High Sev Issues:** Available for all time ranges.
  {% endhint %}

***

## Schedule and download reports

You can share the API Security dashboard as a scheduled email report or as a PDF. Both options are in the menu that opens when you click the More icon (<i class="fa-ellipsis-vertical">:ellipsis-vertical:</i>) at the top of the page.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-3ec9ed5c71816be41a25ef2fd7fc47d69a447614%2Fapi_security_dashboard_download_or_schedule_reports.png?alt=media" alt="The More menu open on the API Security dashboard, showing the Schedule Report and Download PDF options" width="563"><figcaption><p>Download or schedule reports</p></figcaption></figure>

When you reviews the numbers regularly, schedule a report so that Harness automatically emails the overview. The following interactive demo shows you how to set one up with an *hourly*, *daily*, or *weekly* frequency:

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

Follow these steps to schedule a report:

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-d0c02972839859138ad9b31278c2adeb7cdabbc0%2Fschedule_api_security_overview_reports.png?alt=media" alt="The Schedule Dashboard Report panel with Name, Format, Environment, Frequency, Time, and Email fields, showing the message that at least one valid email address is required" width="375"><figcaption><p>Schedule Dashboard Report</p></figcaption></figure>

1. Click the **More** (<i class="fa-ellipsis-vertical">:ellipsis-vertical:</i>) icon, then click **Schedule Report**.
2. In the **Schedule Dashboard Report** panel, enter a **Name** for the report. Harness prefills a default name that you can replace.
3. Select the **Format** of the report: **PDF** or **CSV**.
4. Select the **Environment** to include in the report, such as **All Environments**.
5. Select the **Frequency**: **Hourly**, **Daily**, or **Weekly**.
6. Select the **Time** at which Harness sends the report, such as **7:00 PM**.
7. In the **Email(s)** field, enter the recipient email addresses, separated by commas.
8. Click **Save.**

{% hint style="info" %}
**A recipient is required to schedule a report**

Add at least one valid email address to save the schedule. If no recipient is provided, you cannot save the schedule.
{% endhint %}

If you need only a one-time copy, such as one for an audit or a review meeting, click **Download PDF** in the same menu instead.

***

## Widgets and analyze metrics

The following sections describe the widgets in the order in which they appear on the page.

### Summary cards

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-7a3241e41adefe3464c317d7a88974f5b1011990%2Fapi_security_dashboard_summary_cards.png?alt=media" alt="The four summary cards, Total APIs, Open Critical &#x26; High Sev Issues, API Test Coverage, and Total Threat Traffic, each labeled with the time scope it uses" width="563"><figcaption><p>Summary cards</p></figcaption></figure>

The following table describes the summary cards at the top of the page:

| Card                                | Description                                                                                                                                                                                                                                                                                                                                                       | Time scope          |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- |
| **Total APIs**                      | The number of unique APIs that Harness has discovered. For more information about discovered APIs, see [API Endpoints](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/discovery-1/inventory/api-endpoints.md).                                                                           | As of today         |
| **Open Critical & High Sev Issues** | The number of issues with *Critical* or *High* severity that are awaiting remediation, with a trend line. 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-api-security-testing/discovery/risk/issues-overview.md). | Selected time range |
| **API Test Coverage**               | The number of discovered APIs that were tested. For more information about scan results, see [Scan Details](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/api-security-testing/ast-basics-and-workflow/scan-details.md).                                                                          | Selected time range |
| **Total Threat Traffic**            | The number of malicious requests across all traffic, with a trend line. For more information about security events, see [Security Events](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/protection/web-app-api-protection/security-events.md).                                                    | Selected time range |

### API Classification

The **API Classification** widget shows how many APIs belong to each classification category. Each row displays the category, a bar for comparing categories, and the number of APIs.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-632e11303e47668c471fa08bf60d02290d6469fc%2Fapi_security_overview_api_classification.png?alt=media" alt="The API Classification widget listing eight categories, from Internet Facing through Unused in last 60 days, each with a comparison bar and an API count" width="563"><figcaption><p>API Classification</p></figcaption></figure>

The following table describes the categories in the widget:

| Category                     | Description                                                                                                                                                                                                                                                                                                                              |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Internet Facing**          | APIs that are accessible from the public internet. Harness identifies these APIs from labels that you apply or from whether the IP addresses in their traffic are public.                                                                                                                                                                |
| **Unauthenticated**          | APIs that do not enforce authentication. Harness determines authentication from the headers, tokens, and other credentials in API traffic.                                                                                                                                                                                               |
| **Unencrypted APIs**         | APIs that are not encrypted. Lack of encryption contributes to a higher [risk score](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/settings/risk-scoring.md).                                                                                                  |
| **Shadow APIs**              | APIs that Harness observes in traffic but that are not defined in the API documentation that you uploaded. For more information about API conformance, see [Conformance Analysis](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/risk/conformance-analysis.md). |
| **APIs with Sensitive Data** | APIs through which sensitive data flows. Harness identifies sensitive data based on the data types in [Data Classification](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/settings/discovery/data-classification.md).                                                    |
| **High Risk APIs**           | APIs that have a high risk score. For more information about risk scores, see [Risk Scoring](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/settings/risk-scoring.md).                                                                                          |
| **AI APIs**                  | APIs that Harness discovers as AI assets. For more information about AI assets, see [AI Assets](https://developer.harness.io/ai-security/use-ai-security/ai-assets.md).                                                                                                                                                                  |
| **Unused in last 60 days**   | APIs that have not been used in the last 60 days.                                                                                                                                                                                                                                                                                        |

{% hint style="info" %}
**Category counts can exceed the total**

An API can belong to more than one category. For example, an API can be both internet-facing and unauthenticated. As a result, the category counts can add up to more than the **Total APIs** value.
{% endhint %}

### API with Toxic Combinations

The **API with Toxic Combinations** widget lists combinations of attributes from the **API Classification** widget, along with the number of APIs that match each combination. For example, one combination identifies APIs that are internet-facing, unauthenticated, and handle sensitive data. The widget ranks combinations by exposure, not by count.

The widget helps identify groups of APIs with multiple risk factors that might not be apparent from individual category counts.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-37e7eb51edfaca43db93fc70b4b9892fda82d3bd%2Fapi_security_overview_apis_with_toxic_combinations.png?alt=media" alt="The APIs with Toxic Combinations widget listing attribute combinations such as Internet Facing, Unauthenticated, and Sensitive Data, each with the number of matching APIs" width="563"><figcaption><p>API with Toxic Combinations</p></figcaption></figure>

The widget displays the following information for each combination:

| **Column**            | **Description**                                                                                                                                                                      |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Toxic Combination** | The attributes that define the combination, such as **Internet Facing** and **Unused (60d)**. The **Unused (60d)** attribute corresponds to the **Unused in last 60 days** category. |
| **Count**             | The number of APIs that match all attributes in the combination.                                                                                                                     |

{% hint style="info" %}
**Attribute combinations are fixed**

The widget displays predefined attribute combinations. You cannot customize them.
{% endhint %}

### Open Issues & Security Events by Framework References

The **Open Issues & Security Events by Framework References** widget maps open issues to references from security and compliance frameworks, such as *OWASP API 2023:API9*, *CWE-282*, and *DORA-Art.5*. It also shows the security events and threat activities related to each reference. The widget helps you review open issues against the frameworks that your organization follows and see which references also have related security events and threat activities.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-a31358beda1c21a72cb55412957729984fbbd2ff%2Fapi_security_dashboard_open_issues_and_security_events_by_framework_references.png?alt=media" alt="The Open Issues &#x26; Security Events by Framework References table, with columns for the framework reference, framework name, mapped issues, counts by severity, and related security events" width="563"><figcaption><p>Open Issues &#x26; Security Events by Framework References</p></figcaption></figure>

The widget displays the following information for each row:

| Column                   | Description                                                                                                                                                                                                                                                                                                    |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Framework References** | The framework reference to which the issues map, for example, *OWASP API 2023:API9* or *T1190*. For more information about issue policies, see [Policies](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/settings/issue-policies.md). |
| **Framework Name**       | The name of the framework reference. For example, Improper Inventory Management for OWASP API 2023:API9.                                                                                                                                                                                                       |
| **Issue**                | The open issues mapped to the reference, for example, *TA005*. When more than one issue maps to the reference, a `+N` chip shows the number of additional issues.                                                                                                                                              |
| **By Severity**          | The number of open issues for each severity: **C** (Critical), **H** (High), **M** (Medium), and **L** (Low). Severities without open issues do not appear.                                                                                                                                                    |
| **Security Events**      | The number of security events related to the framework reference. A security event is a security-relevant API activity that Harness detects at runtime.                                                                                                                                                        |

### Trend widgets

The **Issues Trend** and **Traffic Distribution** widgets plot data over time. Below each chart, a legend identifies each line by color. To hide a line, select its entry in the legend. The chart then shows only the remaining lines. The following sections describe what each trend widget shows and how to interpret it.

#### **Issues Trend**

The **Issues Trend** widget compares opened and resolved issues over time. Summary values at the top of the widget show the **Total Issues** and the number of issues for each severity level: **Critical**, **High**, **Medium**, and **Low**. The chart plots two lines, **Opened** and **Resolved**.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-f6ae5456fc4106c407c72f5c825e47a2550834f8%2Fapi_security_overview_issue_trends.png?alt=media" alt="The Issues Trend widget, with Total Issues and per-severity values above a chart plotting opened and resolved issues across the selected range" width="563"><figcaption><p>Issues Trend</p></figcaption></figure>

When the **Resolved** line keeps pace with the **Opened** line, your team is resolving issues as fast as new ones appear. If the **Opened** line rises while the **Resolved** line stays flat, unresolved issues are accumulating. For more information about issue management, see [Issue Management](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/risk/issue-management.md).

#### **Traffic Distribution**

The **Traffic Distribution** widget compares total traffic with threat traffic. Summary values at the top of the widget show the totals, and the chart plots each type of traffic over time.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-fbdd23deca7dc383646895be47eb272b331db8ff%2Fapi_security_dashboard_traffic_distribution.png?alt=media" alt="The Traffic Distribution widget, with Total Traffic, Total Threat Traffic, Total Monitored, and Total Blocked values above a chart plotting each traffic type over time" width="563"><figcaption><p>Traffic Distribution</p></figcaption></figure>

The widget displays the following information for each type of traffic:

| Summary value            | Chart line                      | Description                                                                                          |
| ------------------------ | ------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Total Traffic**        | Traffic (Green)                 | The total traffic that Harness processed.                                                            |
| **Total Threat Traffic** | Threat Traffic (Orange)         | Traffic that Harness considers malicious, that is, traffic with the *Monitored* or *Blocked* status. |
| **Total Monitored**      | Monitored Threat Traffic (Blue) | Threat traffic that is logged (monitored) but not blocked.                                           |
| **Total Blocked**        | Blocked Threat Traffic (Red)    | Threat traffic that is actively blocked.                                                             |

Whether threat traffic is monitored or blocked depends on the actions in your protection policies. For example, you can monitor threats first and then move to enforcement. For more information about protection policies, see [Protection Policy Types](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/protection/settings/protection-policy-types.md).

The chart helps identify traffic spikes and correlate them with attack attempts. When total traffic is much larger than threat traffic, the threat traffic lines appear close to the horizontal axis. For more information about the breakdown of threat traffic by threat type, source, and destination, see [Protection dashboards](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/protection/web-app-api-protection/dashboards.md).

### **Threat Actors**

The **Threat Actors** widget shows the threat actors that Harness has observed and their distribution by severity. Summary values at the top of the widget show the **Total Actors** and the number of actors for each severity level: **Critical**, **High**, **Medium**, and **Low**. The chart plots the number of actors for each severity over time.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-21adefae3724bb19ffdf2e03fe71f23c23203f56%2Fdiscovery_threat_actors.png?alt=media" alt="The Threat Actors widget showing the number of threat actors at Critical, High, Medium, and Low severity, each with a comparison bar" width="375"><figcaption><p>Threat Actors</p></figcaption></figure>

Harness labels a traffic source as a threat actor as the number of anomalies from that source increases. It identifies anonymous sources by IP address and authenticated users by user ID. Each threat actor accumulates a threat score, which determines the actor's severity. You can configure the scoring values and thresholds for each severity level. For more information about threat actors and threat scoring, see [Threat Actors](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/protection/web-app-api-protection/threat-actors.md) and [Threat Scoring](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/protection/settings/threat-scoring.md).

***

## Next steps

The following topics cover each area in more detail:

* **Issues:** [Issue types, sources, severity, and the Issues page](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/risk/issues-overview.md).
* **Security events:** [API requests that contain threats or trigger protection rules](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/protection/web-app-api-protection/security-events.md).
* **Threat actors:** [Detection, investigation, and response](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/protection/web-app-api-protection/threat-actors.md).
