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

# Vendor Risk History

> Track security findings, severity trends, and remediation progress over time.

The Risk History page shows all security findings DSALTA has identified for a specific vendor, organized by severity and recency.

## Severity levels

| Severity     | Description                                                  |
| ------------ | ------------------------------------------------------------ |
| **Critical** | Requires immediate attention — significant security exposure |
| **High**     | Should be addressed promptly                                 |
| **Medium**   | Address in your normal workflow                              |
| **Low**      | Minor issues to address when convenient                      |

## Findings table

Each finding includes:

| Column              | Description                                                                               |
| ------------------- | ----------------------------------------------------------------------------------------- |
| **Finding Name**    | What was discovered                                                                       |
| **Description**     | Detailed explanation                                                                      |
| **Category**        | One of the 10 security assessment categories                                              |
| **Status**          | **PASS** or **FAIL** — the result the security check returned on the vendor's latest scan |
| **Affected Assets** | Number of domains or IPs impacted                                                         |
| **First Detected**  | When the finding was first identified                                                     |

## Finding detail

Click any finding to see:

* **Severity and category** classification
* **Summary** of the issue and its potential impact
* **Recommended remediation** steps
* **Evidence** showing how the finding was identified
* **Affected assets** — specific domains or IP addresses

## Requesting remediation

From any finding, you can click **Request Remediation** to create a formal remediation request sent to the vendor. You can also use **Manage Risk** to generate a comprehensive remediation plan across multiple findings.

<Note>
  This page is rebuilt from the vendor's most recent scan: every check is re-run and comes back as PASS or FAIL, so an issue the vendor has fixed reappears here as PASS. DSALTA re-queues an automated vendor for a fresh scan once its last scan is more than a month old.
</Note>

## Related pages

* [Vendor Summary](/guides/vendors/vendor-summary)
* [Remediations](/guides/vendors/remediations)