> 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/discovery/settings/issue-policies.md).

# Policies

Reference for the Policies page, which lists the API, MCP, and custom policies that Harness uses to detect and categorize issues

<details>

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

* *November 2026:* Mapped system policies to more frameworks and added framework quick filters to the **API** and **MCP** tabs. Go to [Supported frameworks](#policy-view) for details.

Older Updates

* *September 2026*: Updated the page to reflect the updated **Policies** page, including the API, MCP, and custom tabs. Go to [Policy Categorization](#policy-categorization1) for details.

</details>

The **Policies** page helps you identify API and MCP assets that violate security or compliance requirements. Harness provides predefined policies mapped to security, compliance, and threat frameworks, such as OWASP API Top 10, PCI DSS, and MITRE-ATTACK. You can also define your own policies to detect violations based on attributes, such as vulnerability type, data sensitivity, and endpoint behavior, and enable or disable any policy according to your requirements.

## **What you will learn from this topic** <a href="#what-you-will-learn-from-this-topic1" id="what-you-will-learn-from-this-topic1"></a>

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

* Understand how Harness uses policies to identify security and compliance violations across API and MCP assets.
* Understand how policies are organized across the API, MCP, and Custom tabs.
* Identify the frameworks that system policies map to.
* Review policy details, including framework references, severity, environments, and status.
* Configure predefined policies by defining their scope, detection conditions, and severity.
* Create and manage custom policies.
* Review policy violations and identify the corresponding issues on the Issues page.

***

## Before you begin

Make sure the following are in place before you review or configure policies:

* **Discovered API and MCP assets:** Harness evaluates policies only against assets it has discovered from your traffic. Without traffic data, policies stay enabled, but no issues appear on the Issues page.
* **Data types and datasets (custom policies only):** A custom policy can detect only the data types and datasets already defined in Harness. Go to [Data Classification](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/settings/discovery/data-classification.md) to review or add them.

***

## Understand policies <a href="#understand-policies1" id="understand-policies1"></a>

Harness evaluates every policy against your API and MCP traffic and lists the resulting violations as issues. The following table provides an overview of policies, including their purpose, how they work, and how you can use them in Harness:

| **When to use?**                                                                                                                                                                   | **Why use it?**                                                                                                                                                 | **How can you leverage it?**                                                                                                                                                                                |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| It can be used when you want to know whether your APIs and MCP assets are covered against a given framework, for example, before an audit, or when you want to detect a violation. | It helps you identify security and compliance violations across your API and MCP assets without manually reviewing traffic against every framework requirement. | You can use the policies page to review predefined coverage by framework, tune a policy's scope and severity to your traffic, or create a custom policy for detection logic according to your requirements. |

***

## Policy categorization <a href="#policy-categorization1" id="policy-categorization1"></a>

Harness groups policies by the type of asset they protect, rather than by the framework they belong to. This allows a single policy to map to multiple frameworks, for example, *PCI DSS* and *OWASP API Top 10*, without being duplicated or hidden under the wrong tab. The following table discusses the tabs and how they differ:

| **Comparison Metric**  | **API**                                                                                                            | **MCP**                                                                                       | **Custom**                                                              |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| **Purpose**            | Detects predefined violations across API endpoints, including AI APIs.                                             | Detects predefined violations across MCP Tools, MCP Resources, and MCP Prompts.               | Detects violations you define using your own attributes and conditions. |
| **Frameworks covered** | OWASP API Top 10, OWASP LLM Top 10, and compliance and threat frameworks, such as PCI DSS, NIST, and MITRE-ATTACK. | OWASP MCP Top 10, and compliance and threat frameworks, such as NIST, DORA, and MITRE-ATTACK. | Not applicable; you define the detection logic directly.                |
| **Lifecycle**          | Provided out of the box by Harness, you can edit the scope, conditions, and severity.                              | Provided out of the box by Harness, you can edit the scope, conditions, and severity.         | Created, edited, and deleted by you.                                    |

Go to [Policy view](#policy-view) and [Configure policies](#configure-policies1) for details.

***

## Supported frameworks <a href="#policy-view" id="policy-view"></a>

System policies are mapped to security, compliance, and threat frameworks. This mapping helps you identify which framework requirements each policy addresses and assess your API and MCP security coverage.

Each framework assigns reference codes to its requirements. For example, `2023-API08` identifies a requirement in the OWASP API Top 10. The **Framework References** column displays these codes for each policy, showing which requirements it covers.

The Framework filter on the API and MCP tabs lists the frameworks supported on each tab, allowing you to narrow down policies by framework. Some frameworks also have dedicated quick filters. Go to [Filters](#filter-policies1) for more details.

### **OWASP frameworks**

The Open Worldwide Application Security Project (OWASP) publishes lists of the most critical security risks for specific application types. Security teams use these lists as a baseline to decide which risks to test for and fix first.

When a system policy maps to an OWASP framework, each violation it detects points to a specific risk in that list. This helps you find and prioritize the risks that attackers most often exploit in your API and MCP assets.

The following table discusses the OWASP frameworks that system policies map to:

| **Framework**                                                                                | **Description**                                                                                                                             | **Asset type** |
| -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------- |
| [OWASP](https://owasp.org/www-project-top-ten/)                                              | The OWASP Top 10, the ten most critical security risks for web applications, such as broken access control and injection.                   | API            |
| [OWASP API Top 10](https://owasp.org/API-Security/editions/2023/en/0x11-t10/)                | The ten most critical security risks for APIs, such as broken object level authorization and broken authentication.                         | API            |
| [OWASP LLM Top 10](https://genai.owasp.org/resource/owasp-top-10-for-llm-applications-2025/) | The ten most critical risks for applications built on large language models, such as prompt injection and sensitive information disclosure. | API            |
| [OWASP MCP Top 10](https://owasp.org/www-project-mcp-top-10/)                                | The ten most critical security risks for systems built on the Model Context Protocol (MCP).                                                 | MCP            |

### **Compliance frameworks**

Compliance frameworks are standards and regulations that define the security and privacy controls an organization must have in place. Regulators and auditors use them to check how well an organization protects sensitive data, such as payment card details or personal information.

When a system policy maps to a compliance framework, each violation it detects points to a specific requirement in that framework. This helps you find and fix gaps before an audit and track your coverage against each framework.

The following table discusses the compliance frameworks that system policies map to:

| **Framework**                                                                  | **Description**                                                                                                                                                          | **Asset type** |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------- |
| [PCI DSS](https://www.pcisecuritystandards.org/document_library/)              | The Payment Card Industry Data Security Standard (PCI DSS) sets security requirements for organizations that store, process, or transmit payment card data.              | API            |
| [NIST](https://csrc.nist.gov/pubs/sp/800/53/r5/final)                          | The National Institute of Standards and Technology (NIST) Special Publication 800-53 is a US catalog of security and privacy controls for information systems.           | API and MCP    |
| [CIS](https://www.cisecurity.org/controls)                                     | The Center for Internet Security (CIS) Controls are a prioritized set of safeguards against common cyberattacks.                                                         | API and MCP    |
| [GDPR](https://gdpr.eu/)                                                       | The EU General Data Protection Regulation (GDPR) governs how organizations collect, process, and protect personal data.                                                  | API and MCP    |
| [DORA](https://www.eiopa.europa.eu/digital-operational-resilience-act-dora_en) | The EU Digital Operational Resilience Act (DORA) sets information and communication technology (ICT) risk management and resilience requirements for financial entities. | API and MCP    |
| [OpenBanking](https://openid.net/specs/fapi-security-profile-2_0-final.html)   | The OpenID Foundation’s FAPI 2.0 Security Profile, which sets security requirements for APIs that handle high-value data, such as open banking and payment APIs.         | API and MCP    |

### **Threat taxonomy frameworks**

Threat taxonomy frameworks classify how attackers operate, the patterns they follow, and the weaknesses they exploit. Security teams use them as a shared language to consistently describe attacks and weaknesses.

When a system policy maps to a threat taxonomy framework, each violation it detects points to a specific attack technique, pattern, or weakness. This helps you understand how an attacker could exploit the violation and plan your defenses.

The following table discusses the threat taxonomy frameworks that system policies map to:

| **Framework**                                                                                                            | **Description**                                                                                                                             | **Asset type** |
| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------- |
| [MITRE-ATTACK](https://attack.mitre.org/)                                                                                | MITRE ATT\&CK, a knowledge base of the tactics and techniques that attackers use, based on real-world observations.                         | API and MCP    |
| [MITRE-Tactic](https://attack.mitre.org/tactics/enterprise/)                                                             | The MITRE ATT\&CK tactics, which are the goals an attacker pursues at each stage of an attack, such as initial access and exfiltration.     | API and MCP    |
| [CAPEC](https://capec.mitre.org/)                                                                                        | MITRE's Common Attack Pattern Enumeration and Classification (CAPEC), a catalog of common patterns that attackers use against software.     | API and MCP    |
| [CWE](https://cwe.mitre.org/)                                                                                            | MITRE's Common Weakness Enumeration CWE), a list of common software and hardware weaknesses that attackers exploit.                         | API and MCP    |
| [WASC](https://web.archive.org/web/20241206233551/http://projects.webappsec.org/w/page/13246978/Threat%20Classification) | The Web Application Security Consortium Threat Classification (WASC), which classifies attacks and weaknesses that affect web applications. | API and MCP    |

***

## Policy view <a href="#policy-view" id="policy-view"></a>

The Policy view provides a centralized overview of all policies, including their framework mappings, severity, applicable environments, status, and available actions, helping you understand and manage each policy’s configuration and application.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-04b696bf911d7584849afa5aac405e860be25c39%2Fdiscovery_issue_policies.png?alt=media" alt=""><figcaption><p>Issue Policies</p></figcaption></figure>

Harness shows the following information for each tab mentioned above:

| **Column**                     | **Description**                                                                                                                                                                                                                                                                                                                                                     |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Policy Name**                | The policy name, for example, *Missing Gateway Policies*. Harness uses this policy name as the **Issue Name** on the **Issues** page.                                                                                                                                                                                                                               |
| **Framework References**       | The specific framework codes the policy maps to, for example, `2023-API08` the OWASP API Top 10 or `PCI-DSS-4.2` for PCI DSS. A policy can map to more than one code across multiple frameworks. If a policy maps to more than a few codes, Harness groups the remaining codes under a `+N` chip; hover over a code to see the full control name it corresponds to. |
| **Category** (Custom tab only) | The category you assigned to the policy at the time of creation.                                                                                                                                                                                                                                                                                                    |
| **Severity**                   | The severity of the issue detected as part of this policy, for example, *High* or *Medium*.                                                                                                                                                                                                                                                                         |
| **Environments**               | The environment(s) in which the policy is applicable. By default, a policy applies to *All Environments*; however, you can edit this according to your requirements.                                                                                                                                                                                                |
| **Status**                     | The policy's status: **enabled** or **disabled**. While the policies are enabled (Harness recommended) by default, you can click the toggle for a row to disable them, according to your requirements.                                                                                                                                                              |
| **Actions**                    | The functions you can perform on the policy. You can *edit, clone*, and *delete* the policy configuration according to your requirements.                                                                                                                                                                                                                           |

### Filters <a href="#filter-policies1" id="filter-policies1"></a>

Use multi-select filters on each tab to narrow the policy list based on your requirements. Harness applies AND logic across filter categories and OR logic within a category. This lets you combine multiple criteria to answer specific coverage questions, such as identifying disabled, high-severity policies that protect MCP Tools.

Each tab provides the following filters:

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-d374009991b8e0c2dc122858f38fde65459bcefc%2Fdiscovery_policies_filter.png?alt=media" alt=""><figcaption><p>Policies Filter</p></figcaption></figure>

| Tab    | Available filters                                             |
| ------ | ------------------------------------------------------------- |
| API    | Is AI API, Framework, Framework References, Severity, Status  |
| MCP    | Asset Type, Framework, Framework References, Severity, Status |
| Custom | Severity, Status                                              |

Each tab also includes framework chips relevant to that asset type. Select a framework chip to immediately filter the policy list to policies mapped to that framework.

* **API:** OWASP API Top 10, OWASP LLM Top 10, MITRE, NIST, DORA, Open Banking
* **MCP:** OWASP MCP Top 10, MITRE, NIST, DORA, Open Banking

For a framework without a quick filter, such as PCI DSS, use the **Framework** filter. Go to [Supported frameworks](#policy-view) for the full list.

***

## Configure policies <a href="#configure-policies1" id="configure-policies1"></a>

Harness provides you with the flexibility to rely on predefined policies, customize them, or define your own, according to your requirements. This section highlights the recommendations on when to use these options, along with the corresponding steps.

{% hint style="info" %}
Harness recommends using:

* Predefined policies under the **API** and **MCP** tabs when you want to get started quickly with Harness-recommended coverage for the [supported frameworks](#policy-view).
* Custom policies under the **Custom** tab when you want to detect a violation based on attributes or conditions according to your requirements.
  {% endhint %}

{% tabs %}
{% tab title="System Policies" %}
Harness, by default, provides you with policies under the **API** and **MCP** tabs. Harness recommends enabling these policies to help identify the most common violations of PCI DSS, OWASP API Top 10, OWASP LLM Top 10, and OWASP MCP Top 10 across your API and MCP assets.

Harness also allows you to edit a policy configuration according to your requirements. To edit a configuration, click the **Ellipsis** (⋯) icon corresponding to a policy.

### Edit a policy <a href="#edit-a-policy3" id="edit-a-policy3"></a>

To edit a policy configuration, click the **Ellipsis** (⋯) icon → **Edit** corresponding to a policy, and complete the following steps:

<figure><img src="https://cdn.document360.io/24f14f07-13d1-4684-8fae-6d8f811768ee/Images/Documentation/Traceable_policies_edit_policies.png" alt="" width="360"><figcaption><p>Edit System Policy</p></figcaption></figure>

**Step 1: Scope**

1. Select the **Environment(s)** where you wish to apply the policy, for example, *All Environments*.
2. (Optional) Enable the **Advanced Settings** toggle if you wish to use *SPAN* attributes for configuring the conditions below.
3. Define the policy scope by configuring the condition groups. You can add one or more condition groups according to your requirements:
   1. Select how Harness should match the condition groups:
      * **Match All**: Harness performs an AND operation between the condition groups, if selected.
      * **Match Any**: Harness performs an OR operation between the condition groups, if selected.
   2. Click **+ Condition Group** and complete the following steps:
      1. Select how Harness should match the conditions: *Match All* or *Match Any*.
      2. Click **+ Add condition**.
      3. Select or specify the **Attribute** for which you wish to apply the condition.
      4. Select the **Operator** corresponding to the attribute.
      5. Select or specify the **Value(s)** corresponding to the attribute and operator.
      6. (Optional) Click **+** corresponding to a condition to add more according to your requirements.
   3. (Optional) Repeat the above step to add more condition groups.
4. Click **Next**.

**Step 2: Parameters**

Select the **Attribute**, and its corresponding **Operator**, and specify the **Value** based on which Harness should detect issues for the policy. Further, click **Next**.

{% hint style="info" %}
The availability of the configurations in this step depends on the policy you are editing.
{% endhint %}

**Step 3: Severity Conditions**

Select the **Severity** that Harness should assign to the issues detected using the policy, and click **Save**.
{% endtab %}

{% tab title="Custom policies" %}
You can create custom policies by selecting the attributes according to your requirements. Harness uses these policies, identifies their corresponding violations, and lists them on the **Issues** page for you to take action.

### Create a custom policy <a href="#create-a-custom-policy3" id="create-a-custom-policy3"></a>

To create a custom policy, navigate to the **Custom** tab, click **+ Custom Policy**, and complete the following steps:

<figure><img src="https://cdn.document360.io/24f14f07-13d1-4684-8fae-6d8f811768ee/Images/Documentation/Traceable_policies_create_custom_policy.png" alt="" width="360"><figcaption><p>Scope of Custom Policy</p></figcaption></figure>

**Step 1: Scope**

1. Specify the policy **Name**. Harness uses this policy name as the **Issue Name** on the **Issues** page.
2. Specify a **Description** for the policy.
3. From the **Environment** drop-down list, select the environment(s) in which the policy should apply. By default, Harness selects *All Environments*.
4. Define the policy **Scope** by configuring the condition groups. You can add one or more condition groups according to your requirements:
   1. Select how Harness should match the condition groups:
      * **Match All**: Harness performs an AND operation between the condition groups, if selected.
      * **Match Any**: Harness performs an OR operation between the condition groups, if selected.
   2. Click **+ Condition Group** and complete the following steps:
      1. Select how Harness should match the conditions: *Match All* or *Match Any*.
      2. Click **+ Add condition**.
      3. Select the **Attribute** for which you wish to apply the condition.
      4. Select the **Operator** corresponding to the attribute.
      5. Select the **Value(s)** corresponding to the attribute and operator.
      6. (Optional) Click **+** corresponding to a condition to add more according to your requirements.
   3. (Optional) Repeat the above step to add more condition groups.
5. Click **Next**.

**Step 2: Detection Conditions**

<figure><img src="https://cdn.document360.io/24f14f07-13d1-4684-8fae-6d8f811768ee/Images/Documentation/Traceable_Discovery_policies_create_custom_policies_detection_conditions.png" alt="" width="360"><figcaption><p>Detection Condition</p></figcaption></figure>

1. In the **API Attribute** section, click **+ Add condition**, then select the attribute based on your requirements. For example, *Endpoint Name* is equal to (*=*) *GET /userinfo/json*.
2. In the **Vulnerability Attribute** section, click **+ Add condition** and select the attribute according to your requirements. For example, Vulnerability *Status* is (*IN*) either *Open* or *Under review*.
3. In the **Datatypes** section, click **+ Add condition** and select the attributes according to your requirements. For example, *Request & Response* of the API endpoint contains either (*Contains any of*) the *Credit Card PIN*, *username*, and *password* data types.
4. In the **Datasets** section, click **+ Add condition** and select the attributes according to your requirements. For example, the *Response* of the API endpoint does not contain either (*Contains any of*) the *Generic Personal Info* or *PII UK* data sets.
5. In the **Data Sensitivity** section, click **+ Add condition** and select the attributes according to your requirements. For example, the *Request* data for an API endpoint is highly sensitive (*High*).
6. Click **Next**.

{% hint style="info" %}
Harness carries out an AND operation between the conditions defined above.
{% endhint %}

**Step 3: Severity Conditions**

Select the **Severity** that Harness should assign to the issues detected using the policy, and click **Submit**.
{% endtab %}
{% endtabs %}

***

## List identified issues <a href="#list-identified-issues" id="list-identified-issues"></a>

While the **Policies** page lists the policies themselves, the violations they detect appear on the **Issues** page under **Discovery** → **Issues**. From there, you can review each violation and the API or MCP asset where Harness identified it. Go to [Issues Overview](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/risk/issues-overview.md) for details.

{% hint style="info" %}
The policies on this page only identify violations across discovered assets. To actively protect your APIs based on these findings, you can create policies under API Protection. Go to [Custom Policy](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/protection/settings/custom-policies.md) for details.
{% endhint %}

***

## Manage custom policies <a href="#manage-custom-policies3" id="manage-custom-policies3"></a>

To manage a custom policy, click the **Ellipsis** (⋯) icon corresponding to a row. The following table explains the actions available for managing a custom policy:

| **Action** | **Description**                                                                                                                                                                                                                                                          |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Edit**   | Modify the policy to add or remove any attributes according to your requirements.                                                                                                                                                                                        |
| **Clone**  | Duplicate the policy to add or remove any attributes according to your requirements. While cloning a policy, you can also select if you wish to edit the cloned policy directly. Upon selection, Harness automatically opens the policy configuration for modifications. |
| **Delete** | <p>Delete the policy from the Harness platform.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>A deleted policy cannot be restored.</p></div>                                                                                  |

{% @harness-feedback/feedback %}
