> For the complete documentation index, see [llms.txt](https://docs.softwaresecured.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.softwaresecured.com/after-testing/retesting-your-vulnerabilities.md).

# Retesting your vulnerabilities

The goal for many clients is to remediate reported vulnerabilities, have the remediation validated, and obtain evidence that they have done so for any stakeholders, auditors, or customers. 

Depending on the size of the report and availability, <code class="expression">space.vars.company\_name</code> can typically support retesting within two weeks of the request being submitted. For maximum flexibility—and if you have a tight timetable—let us know as soon as you have an estimated time for remediation completion, and we can then schedule a retest date.

***

### Retest overview

A retest involves testing the previously reported vulnerabilities to verify that they have been remediated properly. Retests do not identify new vulnerabilities unless new vulnerabilities arise as a direct result of remediation.&#x20;

Depending on your internal SLAs and timelines, you can either retest all vulnerabilities or only a subset, such as high or critical severity vulnerabilities only. You can choose which vulnerabilities to include when you submit the retesting request.&#x20;

{% hint style="warning" %}
Confirm whether the retesting is occurring within the same environment and the same accounts as the initial test, or if it is being completed in a new environment or with new accounts.
{% endhint %}

When the retest is complete, <code class="expression">space.vars.company\_name</code> will provide a new report with the updated status of the vulnerabilities. If any vulnerabilities were not be effectively fixed, this will be indicated in the updated report with supporting comments or evidence.&#x20;

{% hint style="info" %} <code class="expression">space.vars.company\_name</code> can support a maximum of 1 round of retesting for Pentest Standard, 3 rounds of retesting for Pentest Standard Plus, and unlimited retesting for <code class="expression">space.vars.ptass</code> and Premium clients to validate revised remediation, subject to schedule availability. Further retesting might be possible for an additional fee. For more information, see [Software Secured - Pricing and Service Packages](https://www.softwaresecured.com/pricing).&#x20;
{% endhint %}

***

### **Requesting a retest**

1. In the projects bar, select the project that you would like to view.&#x20;
2. Go to the <mark style="color:orange;">**Vulnerabilities**</mark> tab.
3. Using the table multiselect, select the vulnerabilities that you would like to request a retest on, and then click <mark style="color:orange;">**Add to Retest**</mark> from the bulk actions dropdown.
4. Alternatively, you can right click any item from the table and use the <mark style="color:orange;">**Add to Retest**</mark> option from the context menu.

<figure><img src="/files/92yPucHHkYjOSe0aQlOl" alt=""><figcaption></figcaption></figure>

4. To view your retest request, click <mark style="color:orange;">**Submit Retest**</mark>.&#x20;
5. The <mark style="color:orange;">**Retesting Round**</mark> modal displays the details of the items in your retest batch.&#x20;
   * You can go back to the vulnerabilities table and add more items to the retest round with the <mark style="color:orange;">**Add to Retest**</mark> button.&#x20;
   * If you have any notes about the issues to retest or the retest environment, you can include them in the note field.&#x20;
6. Once all issues are in the retesting round, click <mark style="color:orange;">**Submit Request**</mark>.

<figure><img src="/files/i8b1ZiUEgFpLkxEHYDPx" alt=""><figcaption></figcaption></figure>

***

### Retest results

After a retest, the status of your vulnerabilities can change. You will receive a notification by email, Slack, or both every time new results are available for your project (or projects, if applicable) in <code class="expression">space.vars.product\_name</code>.&#x20;

Any vulnerabilities that were marked with a <mark style="color:orange;">**New**</mark> status will be changed to the <mark style="color:orange;">**Updated**</mark> status, and the <mark style="color:orange;">**Last updated**</mark> date will change to the date of the most recent retest.&#x20;

If a known vulnerability was remediated successfully, its status will change to <mark style="color:orange;">**Closed**</mark> and the SLA status will change to <mark style="color:green;">**Compliant**</mark>. If the issue remains unresolved, its SLA status does not change because the SLA policy begins on the date that the vulnerability was first found.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.softwaresecured.com/after-testing/retesting-your-vulnerabilities.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.