> 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/risk/conformance-analysis.md).

# Conformance Analysis

Use Conformance Analysis in Traceable to compare observed API behavior with specifications and detect drift, including for MCP Servers

<details>

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

* *November 2026*: Updated the topic to reflect the redesigned Conformance Analysis interface.

Older Updates

* *September 2026:* Updated Conformance Analysis to support drift analysis for MCP Servers.

</details>

Your API specifications and Model Context Protocol (MCP) Server manifests describe what you expect to run. Live traffic shows what actually runs. Conformance Analysis compares the two and sorts every endpoint and MCP asset based on its findings. You learn which assets run without documentation, which documentation matches nothing in traffic, and where behavior has drifted from the definition.

Each kind of gap calls for a different fix. Undocumented assets need a security review, stale documentation needs updating, and drift requires updating the service or the specification so the two match again.

## What you will learn from this topic

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

* Explain how Harness classifies endpoints and MCP assets during an analysis.
* Decide when to run a one-time, scheduled, or system-generated analysis.
* Start, schedule, and manage analysis jobs.
* Read analysis results and download them as CSV.
* Create tickets for findings and track them on the Issues page.

***

## Before you begin

Make sure you have the following before you start an analysis:

* **Traffic in the environment:** Harness compares your documentation with the traffic it has observed in the environment you analyze. If the environment sends no traffic to Harness, every documented asset appears as an orphan.
* **API specification or MCP Server manifest:** Upload documentation when you start an analysis, or add it in advance from **Discovery** → **Settings** → **Documentation**. Go to [Sample MCP server manifest format](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/discovery-1/documentation-and-inspector.md#sample-mcp-server-manifest-format) to learn about the MCP Server manifest format.
* **Familiarity with drift**: Drift occurs when an endpoint or MCP asset behaves differently in live traffic than its documentation specifies. For example, an API parameter might be documented as an integer but sent as a string in live traffic. Harness checks for drift only on assets that appear in both the documentation and live traffic.
* **Ticketing integration (optional):** Creating tickets from **Conformance Analysis** results requires a connected Jira, ServiceNow ITSM, or Azure DevOps integration. Go to [Jira integration](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/integrations/project-management/jira-integration.md), [ServiceNow ITSM integration](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/integrations/project-management/servicenow-itsm-integration.md), or [Azure DevOps integration](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/integrations/project-management/azure-devops-integration.md) to connect each tool.

***

## Asset categories

Every Conformance Analysis job places each endpoint or MCP asset into one of the following categories:

* [Shadow assets](#shadow-assets)
* [Orphan assets](#orphan-assets)
* [Matched assets with drift](#matched-assets-with-drift)
* [Matched assets without drift](#matched-assets-without-drift)

The category depends on whether the asset appears in your documentation, in live traffic, or in both, and whether a matched asset shows drift.

On the **Conformance Analysis** results page, an API endpoint analysis labels these categories as endpoints, such as **Shadow Endpoints**. An MCP server analysis labels them as assets, such as **Shadow Assets**.

### Shadow assets

A shadow asset appears in live traffic but is not defined in your documentation.

For example, your specification defines only `GET /cart` and `GET /checkout`, but live traffic contains `GET /cart`, `GET /checkout`, and `GET /admin`. Because `GET /admin` is not documented, Harness identifies it as a shadow endpoint. The same applies to MCP assets. If your manifest defines only the `fetchUserDetails` tool, but live traffic also shows calls to `fund-distributions`, Harness identifies `fund-distributions` as a shadow asset.

Shadow assets usually deserve attention first. These undocumented assets may not have undergone design or security reviews, which could expose data or functionality that is not being monitored.

{% hint style="info" %}
**Each method is a separate endpoint**

Harness treats `GET /cart` and `POST /cart` as two different endpoints, so each one is classified on its own.
{% endhint %}

### Orphan assets

An orphan asset is defined in your documentation but was not observed by Harness during the analysis.

For example, if your specification defines `GET /cart` and `GET /checkout`, but live traffic contains only `GET /cart`, Harness identifies `GET /checkout` as an orphan endpoint. Similarly, a prompt defined in your manifest but not called by any client is an orphan MCP asset.

Orphan assets usually have one of three causes, each requiring a different response:

* **Retired asset:** The service no longer exposes the asset. In this case, the documentation is outdated, and the entry can be removed.
* **No traffic in this environment:** The asset still exists, but no requests to it were observed in the analyzed environment. An analysis of an environment where the asset is used can provide a clearer picture.
* **Still being learned:** Harness has not yet observed enough traffic to identify the asset. A later analysis may move it into a matched category.

### Matched assets with drift

A matched asset with drift appears in both your documentation and live traffic, but its observed behavior differs from its documented definition.

For API endpoints, drift includes type mismatches, missing parameters, and authentication differences. For MCP assets, drift includes changes to tool input or output schemas, prompt arguments, and resource content types.

Drift matters because clients built using your documentation expect the documented behavior. Any difference in the actual service behavior can cause those clients to send requests that the service rejects or receive responses they cannot handle.

### Matched assets without drift

A matched asset without drift appears in both your documentation and live traffic, with no differences identified by Harness. This match covers only the elements included in the analysis drift scope. Other elements outside that scope may still differ.

***

## Analysis types

Conformance Analysis jobs are available in three types, which appear in the **Schedule** column of the job list. You can create one-time and scheduled jobs, while Harness automatically creates system-generated jobs.

| Type                 | Created by                                | Runs                                    | Best for                                                                                      | Results retention period |
| -------------------- | ----------------------------------------- | --------------------------------------- | --------------------------------------------------------------------------------------------- | ------------------------ |
| **One Time**         | Manual creation, with Schedule turned off | Once, after submission                  | Checking a newly uploaded or updated specification, or verifying conformance before a release | 10 days                  |
| **Scheduled**        | Manual creation, with Schedule turned on  | Daily or weekly, at the configured time | Tracking drift in a single environment over time                                              | 10 days for each run     |
| **System Generated** | Harness, automatically                    | Every 12 hours                          | Regular, automatic checks of OpenAPI specifications in every environment                      | 3 days                   |

### System-generated analysis

System-generated analysis runs automatically every *12* hours, based on the completion time of the previous automated run. It covers the API specifications that have **Enabled for Naming** turned on. For example, if *12* API specifications are available and eight have **Enabled for Naming** turned on, Harness runs the system-generated analysis for those eight specifications.

Unlike one-time and scheduled analyses, which require selecting an environment for each job, system-generated analyses run across all environments automatically.

{% hint style="info" %}
**System-generated analysis has a fixed scope**

* System-generated analysis is available only for Open API Spec documentation.
* Harness runs it on the **Path**, **Query**, **Request Cookie**, and **Request Header** parameters, and this scope cannot be changed.
  {% endhint %}

You can include an API specification in system-generated analysis by turning on **Enabled for Naming** in its settings:

1. Navigate to **Discovery** → **Settings** → **Documentation**.
2. Locate the documentation you want to include, and confirm that its **Type** is **Open API Spec**. System-generated analysis supports only this documentation type.
3. In the **Actions** column for that specification, click the **More** (<i class="fa-ellipsis-vertical">:ellipsis-vertical:</i>) icon, then click **Edit**. The **Edit Documentation** panel opens.
4. Turn on **Enabled for Naming**, then click **Save**.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-4353cf1ab48fc88e4f890906e12a4c954c1ce9f6%2Fdiscovery_enabling_naming_for_api_specification.png?alt=media" alt="Enabled for Naming toggle in the Edit Documentation panel" width="563"><figcaption><p>Enabled for Naming</p></figcaption></figure>

Harness includes the specification from the next automated run. The **Documentation** tab also lets you upload API specifications and delete existing ones. Specifications uploaded there appear in the **Documentation ID** dropdown when you create a one-time or scheduled analysis. Go to [Documentation and Inspector](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/discovery-1/documentation-and-inspector.md) to manage documentation.

***

## Start an analysis

Every one-time and scheduled job starts from the **Start Analysis** panel. In the panel, you tell Harness which documentation to compare, which environment's traffic to compare it with, and what to check. The **Schedule** toggle decides whether the job runs once or repeats.

The following interactive walkthrough shows how to run a one-time analysis with **Open API Spec** documentation:

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

{% stepper %}
{% step %}

### Open the Start Analysis panel

On the **Discovery** → **Conformance Analysis** page, click **Start Analysis** to open the **Start Analysis** panel.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-7c155cc0d22efbbcba1554e82e39d5d466db7a79%2Fdiscovery_start_conformance_analysis.png?alt=media" alt="Start Analysis panel for an Open API Spec conformance analysis" width="563"><figcaption><p>Start Analysis</p></figcaption></figure>
{% endstep %}

{% step %}

### Select the documentation type

The documentation type decides which assets Harness analyzes and which options appear in the rest of the panel. Select one from **Documentation Type**.

| Documentation Type | Select it for                              | Supported file types     |
| ------------------ | ------------------------------------------ | ------------------------ |
| **Open API Spec**  | REST API endpoints                         | `.yaml`, `.yml`, `.json` |
| **WSDL**           | SOAP API endpoints                         | `.wsdl`                  |
| **MCP Server**     | MCP servers, tools, resources, and prompts | `.yaml`, `.yml`          |
| {% endstep %}      |                                            |                          |

{% step %}

### Select or upload the documentation to compare

Harness compares live traffic with the specifications or manifests you add to the analysis. You can reuse documentation already in Harness, upload new files, or combine both in one analysis:

* **Documentation ID:** Select one or more entries from the dropdown. The list shows all specifications and manifests already in Harness, including files uploaded in previous analyses and those added via **Discovery** → **Settings** → **Documentation**.
* **Click to upload:** Add new files from your computer. You can upload up to 10 files, with a combined size of up to 20 MB. Harness saves uploaded files to the **Documentation ID** list, so later analyses can reuse them.
  {% endstep %}

{% step %}

### Set the name and environment

The job name identifies the analysis in the job list, and the environment decides which traffic Harness compares with your documentation. Enter both:

* **Job Name:** Identifies the job in the job list. A name that reflects the documentation and environment, such as `payments-api-staging`, makes the job easy to find later.
* **Environment:** Decides which traffic Harness compares with your documentation. A documented asset with no traffic in the selected environment appears as an orphan, even if it receives traffic in another environment.
  {% endstep %}

{% step %}

### Select the assets to analyze

Under **Select API Endpoints** or **Select MCP Servers**, depending on the documentation type, select one of the following options:

| API option                       | MCP option                         | Includes                                                                                                                                                                                 | Best for                                                    |
| -------------------------------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| **All Endpoints**                | **All MCP Servers**                | Every asset in the environment, including assets Harness discovers later                                                                                                                 | Full coverage, especially for scheduled jobs                |
| **Specific Endpoints**           | **Specific MCP Servers**           | Only the assets you pick from a list                                                                                                                                                     | Checking a few assets you recently changed                  |
| **Endpoint Selection Condition** | **MCP Server Selection Condition** | Assets that match the conditions you define, such as an **Endpoint Type** of REST and an **HTTP Method** of GET for APIs, or a **Discovered Source** of **Live Traffic** for MCP servers | Limiting the job to a group of assets that share attributes |

{% hint style="info" %}
**Condition preview**

For an API condition, **View Endpoints** lists the matching endpoints before you submit. Check the list to ensure required endpoints are present.
{% endhint %}
{% endstep %}

{% step %}

### Set a schedule (optional)

For a one-time analysis, make sure **Schedule** is turned off, then continue to the next step.

For a scheduled analysis, turn on **Schedule**, then set when it runs:

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-0acd27f4795311db93ec6db1eeb4771243b54dc6%2Fdiscovery_schedule_conformance_analysis.png?alt=media" alt="Schedule settings for a weekly analysis"><figcaption><p>Schedule Conformance Analysis</p></figcaption></figure>

* **Frequency:** **Daily** or **Weekly**.
* **Days:** The day a weekly analysis runs, such as **Monday**.
* **Time:** The time each run starts, such as **8:30 AM**.
  {% endstep %}

{% step %}

### Set the drift scope

The drift scope lists the elements Harness compares when it checks for drift. Harness does not report drift in elements outside the scope.

{% hint style="info" %}
**Drift Scope is not available for WSDL documentation**

Drift analysis supports REST APIs and MCP servers only. WSDL analyses report shadow and orphan endpoints.
{% endhint %}

#### **Open API Spec documentation**

By default, the **Drift Scope** dropdown includes **Path**, **Query**, **Request Cookie**, and **Request Header**, which cover how a client calls each endpoint. Three more elements can be added:

* **Request Body**
* **Response Body**
* **Response Header**

Without the response elements, a change in what the service returns, such as a renamed field, is not reported as drift.

#### **MCP Server documentation**

Each row pairs an asset **Type** with the element to check under **Detect Drift On**. Add one row for each asset type you want to check. Each type can appear in only one row, so an **MCP Tool** row checks either the input schema or the output schema.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-ff0ee297e64c285e68f4945442fd1df8d5d0a8f9%2Fdiscovery_mcp_drift_scope.png?alt=media" alt="Drift scope rows for an MCP Server analysis" width="563"><figcaption><p>MCP drift scope</p></figcaption></figure>

| Type             | Detect Drift On                                 |
| ---------------- | ----------------------------------------------- |
| **MCP Tool**     | **Tool Input Schema** or **Tool Output Schema** |
| **MCP Prompt**   | **Prompt Arguments**                            |
| **MCP Resource** | **Content type**                                |
| {% endstep %}    |                                                 |

{% step %}

### Submit the analysis

Click **Submit**. The job appears in the job list on the **Conformance Analysis** page.

A one-time job runs once. A scheduled job runs at each scheduled time, and each run produces its own results. When a job's **Status** shows **Success**, its results are ready and available for 10 days.
{% endstep %}
{% endstepper %}

***

## Review analysis results

After an analysis completes, select the job in the job list on the **Conformance Analysis** page to view results. The **Configuration** summary gives the overall comparison between your documentation and live traffic. The four category tabs then list each endpoint or asset within their respective categories.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-dd9a6b7dd470a4802c27bf17981c358b176c89c8%2Fdiscovery_conformance_analysis_results_page.png?alt=media" alt="Results page of an API analysis" width="563"><figcaption><p>Conformance Analysis result page</p></figcaption></figure>

### Configuration summary

The **Configuration** summary names the environment and documentation the job used, and counts the assets on each side:

* **Live Traffic:** The assets Harness observed in the environment.
* **Documentation:** The assets your specifications or manifests define.

For an MCP analysis, each side shows a separate count for every asset type: **MCP Server**, **MCP Tools**, **MCP Resources**, and **MCP Prompts**.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-dfcb90adcfd5ddb9f1f8080476cad16c66787edb%2Fdiscovery_mcp_configuration_summary.png?alt=media" alt="Configuration summary of an MCP Server analysis" width="563"><figcaption><p>MCP configuration summary</p></figcaption></figure>

If live traffic shows more assets than the documentation, expect shadow assets. If the documentation lists more than that, expect orphan assets. For example, an API endpoint analysis comparing *226* endpoints in live traffic with *1,200* in the documentation finds that most are orphan endpoints.

The summary shows only the key details of the job. For an overview of the whole job, click the **Settings** ( <i class="fa-gear">:gear:</i> ) icon on the **Conformance Analysis** results page.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-b04646fbb7602643a18b0a9a46a53b875aad57b3%2Fdiscovery_job_summary_settings_icon.png?alt=media" alt="Settings icon on the results page" width="563"><figcaption><p>Settings icon</p></figcaption></figure>

### Category tabs

Each asset category has its own tab, with the number of assets shown on the tab. The drift and shadow tabs usually need action first, because they show behavior that no one has documented or reviewed.

{% hint style="info" %}
**Each asset is compared with one documentation file**

An endpoint or MCP asset can appear in more than one documentation file in the same analysis. In that case, Harness checks it against only the most recently uploaded file, and the **Documentation** column shows only that file. Drift is also determined against this file, so any updates to resolve it should be made there.
{% endhint %}

The tab names and filters differ between an API analysis and an MCP Server analysis:

{% tabs %}
{% tab title="API Endpoint analysis" %}
Review the tabs to identify endpoints that need attention and determine the appropriate action for each category:

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-7cb172a8e21d5cc53a331fb4d0524135e10f77d3%2Fdiscovery_conformance_analysis_api_category_tabs.png?alt=media" alt="Category tabs of an API analysis" width="563"><figcaption><p>API endpoints category tabs</p></figcaption></figure>

| Tab                                 | What to do next                                                                              | Filter by              | Tickets |
| ----------------------------------- | -------------------------------------------------------------------------------------------- | ---------------------- | ------- |
| **Matched Endpoints with Drift**    | Update the specification or the service so they agree.                                       | Service, Documentation | Yes     |
| **Shadow Endpoints**                | Document the endpoint, or retire it if it should not exist.                                  | Service, Sensitivity   | Yes     |
| **Orphan Endpoints**                | Confirm whether the endpoint is retired, unused in this environment, or still being learned. | Documentation          | No      |
| **Matched Endpoints without Drift** | No action needed. These endpoints conform within the drift scope.                            | Service, Sensitivity   | No      |
| {% endtab %}                        |                                                                                              |                        |         |

{% tab title="MCP Server analysis" %}
Review the tabs to identify MCP assets that need attention and determine the appropriate action for each category:

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-c2911c1c7883044ddba102483e71cd307355af95%2Fdiscovery_conformance_analysis_mcp_category_tabs.png?alt=media" alt="Category tabs of an MCP Server analysis" width="563"><figcaption><p>MCP category tabs</p></figcaption></figure>

| Tab                              | What to do next                                                                           | Filter by                              | Tickets |
| -------------------------------- | ----------------------------------------------------------------------------------------- | -------------------------------------- | ------- |
| **Matched Assets with Drift**    | Update the manifest or the MCP server so they agree.                                      | Asset Type, Server Name, Documentation | Yes     |
| **Shadow Assets**                | Add the asset to the manifest, or remove it from the server if it should not exist.       | Asset Type, Server Name                | Yes     |
| **Orphan Assets**                | Confirm whether the asset is retired, unused in this environment, or still being learned. | Asset Type, Server Name, Documentation | No      |
| **Matched Assets without Drift** | No action needed. These assets conform within the drift scope.                            | Asset Type, Server Name                | No      |
| {% endtab %}                     |                                                                                           |                                        |         |
| {% endtabs %}                    |                                                                                           |                                        |         |

### Search, filter, and download results

Each tab has its own tools for working through a long list:

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-06b32bf35fcdbe4e74af710f24fc7d5d842d7d55%2Fdiscovery_search_filter_and_download_conformance_analysis_results.png?alt=media" alt="Search, filter, Group by, and download controls on a results tab" width="563"><figcaption><p>Search, filter, and download results</p></figcaption></figure>

* **Search by Name:** Finds an endpoint or asset by name.
* **Filter:** Narrows the tab by the attributes listed for it in the earlier table, such as **Service** or **Asset Type**.
* **Group by**: Groups the rows by an attribute, such as *Server* or *Service*.
* **Download:** The Download (<i class="fa-arrow-down-to-line">:arrow-down-to-line:</i>) icon saves the current tab as a comma-separated values (CSV) file, with the number of rows you select.

***

## Act on findings

After you review the results, drift and shadow findings can go to the owning team as tickets. Conformance findings also appear on the **Issues** page alongside issues from other sources.

### Create tickets

A ticket sends one finding to the team that owns the endpoint or MCP asset, in the tool that team already uses. Ticket columns for **Jira**, **ServiceNow ITSM**, and **Azure DevOps** appear on the drift and shadow tabs only.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-cfb741add17dc6522a2dfb3229b7281eb9d657c7%2Fdiscovery_conformance_analysis_create_tickets.png?alt=media" alt="Ticket columns on a results tab" width="563"><figcaption><p>Create tickets</p></figcaption></figure>

Tickets are created from the results page:

1. On the **Conformance Analysis** page, select the job to open its results.
2. Select **Matched Endpoints with Drift** or **Shadow Endpoints** for an API analysis, or **Matched Assets with Drift** or **Shadow Assets** for an MCP Server analysis.
3. In the row for the endpoint or asset, click the icon in the **Jira**, **ServiceNow ITSM**, or **Azure DevOps** column.

Harness prompts you for the ticket details in the selected tool, then creates the ticket. Each ticket includes a **Link to job**, so whoever picks up the ticket can open the **Conformance Analysis** and see the finding in context.

{% hint style="info" %}
**The job link expires after 10 days**

The **Link to job** is valid for 10 days after Harness generates the results. After that, the results are deleted, and the link no longer opens them.
{% endhint %}

### Track findings on the Issues page

The **Issues** page lists conformance findings together with issues from every other source.

A filter on the **Issues** page narrows it to issues from **Conformance Analysis**:

1. Navigate to **Discovery** → **Risk** → **Issues**.
2. Click the **Filter** icon, then select either of the following:
   * **Source:** **Conformance Analysis**
   * **Category:** **API Governance** for API endpoint issues, or **MCP Tools**, **MCP Resources**, or **MCP Prompts** for MCP asset issues.

Go to [Issues Overview](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/risk/issues-overview.md) and [Issue Management](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/risk/issue-management.md) to learn about issue types, severity, and issue workflows.

***

## Manage analysis jobs

The job list on the **Conformance Analysis** page includes all one-time, scheduled, and system-generated jobs. It is where you check a job's progress, view past results, and rerun, edit, clone, or delete jobs.

The **Conformance Analysis** job list shows each job's environment, documentation, finding counts, schedule type, start time, and status.

### Read and filter the job list

Each row summarizes one job. The **Schedule** column shows the job type, and the **Info** (<i class="fa-circle-info">:circle-info:</i>) icon next to **Scheduled** or **System Generated** shows when the job runs. The **Shadow**, **Orphan**, and **With Drift** columns show the job's totals, so jobs that need attention stand out without opening them.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-8c8336f1fd4dfd6b7a8c3f4c909530bd83b56e2d%2Fdiscovery_read_and_filter_the_job_list.png?alt=media" alt="Controls for narrowing the job list" width="563"><figcaption><p>Manage analysis jobs</p></figcaption></figure>

The following filters narrow the list:

* **All Environments:** Limits the list to one environment.
* **Time range:** Limits the list to a period, from **Last 15 minutes** to **Last 1 week**, or to a **Custom** range.
* **Search by Name:** Finds a job by its name.
* **Filter:** Narrows the list by **Status**, **Schedule**, **Documentation Type**, or **Documentation**.
* **Refresh:** Loads the latest jobs and status changes.

### Show or hide job details

The job list displays different details about each job in separate columns, including its environment and status. The **Columns** dropdown lets you customize which of the 10 available details appear in the list. The count (for example, **Columns 10/10**) indicates how many columns are currently displayed.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-459b4ad2efa86c3f440f47f050b612c8720b56dd%2Fdiscovery_conformance_analysis_column_selector_for_conformance_analysis_jobs.png?alt=media" alt="" width="563"><figcaption><p>Column selector</p></figcaption></figure>

The checkboxes in the dropdown control the visibility of each detail. Checking or unchecking an option shows or hides the corresponding column, while **Reset** restores the default column selection. For a quick overview of jobs with findings, keep **Shadow**, **Orphan**, and **With Drift** visible. This makes it easier to spot relevant jobs directly from the list without opening each one.

### Job actions

The actions for a job appear when you click the **More** ( <i class="fa-ellipsis-vertical">:ellipsis-vertical:</i> ) icon in its **Actions** column. Which actions appear depends on whether the job is one-time, scheduled, or system-generated.

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-f70baaf3f68f9b1b43ad60ccd85b89efbca8e9d0%2Fdiscovery_conformance_analysis_job_actions.png?alt=media" alt="Actions menu for a system-generated job" width="563"><figcaption><p>Actions</p></figcaption></figure>

The following table shows what each action does and when it is useful:

| Action     | Job types         | What happens                                                                                                                     | Purpose                                                                                      |
| ---------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| **Re-run** | **One Time**      | Harness creates a new job with the same configuration and runs it.                                                               | Check again after a deployment or a specification update.                                    |
| **Edit**   | **Scheduled**     | The **Edit Analysis** panel opens, with only the schedule editable.                                                              | Move a scheduled job to a different day or time, or switch it between daily and weekly runs. |
| **Clone**  | **Scheduled**     | The **Start Analysis** panel opens with this job's configuration filled in. You change what you need and submit it as a new job. | Run a similar analysis with different documentation, environment, assets, or drift scope.    |
| **Delete** | **All job types** | The job is removed from the list.                                                                                                | Remove jobs you no longer need.                                                              |

### Change when a scheduled job runs

{% hint style="info" %}
**Editing an existing scheduled job**

After you submit a scheduled job, you can change when it runs but not what it analyzes. The documentation, environment, assets, and drift scope stay the same.
{% endhint %}

You can edit the schedule from the job list or from the job's results page. Both methods update the same schedule.\
\
To edit a schedule from the job list:

<figure><img src="https://1414883571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdr7UJpJrdGkkSGT6AFTu%2Fuploads%2Fgit-blob-b3ce7efad19682072a01a897a28b706050786849%2Fdiscovery_edit_scheduled_conformance_analysis_jobs.png?alt=media" alt="Edit option for a scheduled job"><figcaption><p>Edit Conformance Analysis</p></figcaption></figure>

1. In the **Actions** column of the scheduled job, click the **More** ( <i class="fa-ellipsis-vertical">:ellipsis-vertical:</i> ) icon, then click **Edit**.
2. In the **Edit Analysis** panel, update **Frequency**, **Days**, or **Time**.
3. Click **Submit.**

To edit a schedule from the results page:

1. On the **Conformance Analysis** page, select the scheduled job to open its results.
2. Click the Settings ( <i class="fa-gear">:gear:</i>) icon.
3. Update **Frequency**, **Days**, or **Time**.
4. Click **Submit**.

The job follows the new schedule from its next run.

***

## Next steps

After your first analysis, the following pages help you act on what it found:

* **Track and resolve findings:** Go to [Issue Management](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/risk/issue-management.md) to assign and resolve issues.
* **Keep documentation current:** Go to [Documentation and Inspector](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-api-security-testing/discovery/discovery-1/documentation-and-inspector.md) to upload documentation and enable it for naming.

{% @harness-feedback/feedback %}
