> 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/findings/viewing-and-acting-on-your-pentest-results.md).

# Viewing and acting on your pentest results

After each penetration test, your results are uploaded into <code class="expression">space.vars.product\_name</code>. You will receive a notification by email (and Slack, if you have the integration) when results are available.

***

### **View your results**

1. In the projects bar, select the project that you would like to view.&#x20;
2. Open  the <mark style="color:orange;">**Vulnerabilities**</mark> tab.
3. In the table view, you can view the status, severity, SLA status, date identified, last updated, affected compliance frameworks, and any labels. If you have any project management integrations enabled they will also be visible.

<figure><img src="/files/FuC79UXPGAwTu7sbIlTJ" alt=""><figcaption><p>The <mark style="color:orange;"><strong>Vulnerabilities</strong></mark> tab includes a table of all vulnerabilities in the project.</p></figcaption></figure>

3. Select any vulnerability in the table to review its details, including the description, impact, mitigation tactics, replication steps, evidence, and comments.&#x20;

***

### Remediation actions

After viewing your results, there are actions your team can take to tackle remediation.&#x20;

In the main menu of your project’s vulnerability dashboard, you can take the following actions:

* Book a retest for selected issues (see [Retesting your vulnerabilities](/after-testing/retesting-your-vulnerabilities.md)).
* Copy vulnerability information to your clipboard.
* Export vulnerability data as a CSV file (see [Viewing and downloading reports and executive summaries](/reports-and-certificates/viewing-and-downloading-reports-and-executive-summaries.md)).&#x20;
* Add labels.
  * Labels make it easier to categorize and sort vulnerabilities. Users can add up to 50 labels per project, including (but not limited to) release versions, assigned teams, or internal priority.&#x20;
* Accept risk for a vulnerability.&#x20;
  * <mark style="color:orange;">Org Admins</mark> and <mark style="color:orange;">Project Admins</mark> can accept risk by selecting the vulnerability and clicking <mark style="color:orange;">**Accept Risk**</mark>.&#x20;
  * When submitting a request to accept the risk of a vulnerability, you must provide a note to explain why the risk is accepted and timestamp for the acceptance.&#x20;
  * After the request is approved, the issue is assigned the <mark style="color:orange;">**Accepted Risk**</mark> state and will be treated as a <mark style="color:orange;">**Closed**</mark> issue. Therefore, SLAs don’t apply to it.
* Reopening vulnerabilities.&#x20;
  * An vulnerability is reope*n*ed by Software Secured if—after it was first detected and then confirmed to be remediated—it is detected again.
  * If your team chooses to mitigate an issue that you <mark style="color:orange;">**Accepted Risk**</mark> on in the past, you will need to reopen it before you can request retesting.
  * To reopen an issue, select an <mark style="color:orange;">**Accepted Risk**</mark> vulnerability and click <mark style="color:orange;">**Reopen Issue**</mark>.  The issue is then marked with the <mark style="color:orange;">**Updated**</mark> status and the original risk score is applied again. For any new report, the issue is moved back into the main report.&#x20;

{% hint style="info" %}
For more information about tracking remediation efforts, see [Remediating vulnerabilities](/after-testing/remediating-vulnerabilities.md).&#x20;
{% endhint %}


---

# 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/findings/viewing-and-acting-on-your-pentest-results.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.