> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/vulnerabilities/dashboard-actions/mark-vulnerabilities-as-special-cases.md).

# Mark Vulnerabilities as Special Cases

In some situations, a detected vulnerability may not be relevant to your product, infrastructure, or compliance framework. Sprinto allows you to mark such vulnerabilities as *Special Cases*, helping you avoid unnecessary check failures while maintaining a compliant audit trail.

Special case vulnerabilities remain visible in audit logs but are excluded from failing system-status or workflow checks.

***

### When to Use This

You should mark a vulnerability as a special case if:

* It is not exploitable within the context of your product.
* It is irrelevant to the compliance framework in scope.
* Additional time is required to resolve the issue, and a formal extension is justified.
* The vulnerability exists in a deprecated or non-production system.

***

### Before You Begin

Make sure:

* You are logged in as an administrator.
* The vulnerability is visible under the **Vulnerabilities** or **Pentest** tab.
* You have a valid reason for dismissing the issue and, if possible, supporting documentation.

***

### Procedure

To mark a vulnerability as a special case:

1. Go to **Data Library > Vulnerabilities**.
2. From the left-hand navigation, select the relevant monitoring source or click **Pentest** for uploaded issues.
3. Locate the vulnerability you want to mark and click **Dismiss Vulnerabilities**.
4. In the dialogue, choose one of the following options:
   * **Additional time is needed to fix this check**
   * **Other**
5. Enter a justification in the comments field (this is mandatory).
6. (Optional) Click **Upload Document** to attach supporting evidence.
7. Define the expiry of the special case:
   * **Valid forever**
   * **Let me select an expiry date**
     * If an expiry is set, the vulnerability reverts to *Due* status after the date passes.
8. Click **Mark as Special Case**.

***

### Result

The vulnerability is now marked as a special case. Its corresponding check status is updated to **Passing**, and it no longer contributes to SLA failure reports.

You can review the updated status by navigating to the source tab or the Pentest section.


---

# 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:

```
GET https://docs.sprinto.com/data-library/vulnerabilities/dashboard-actions/mark-vulnerabilities-as-special-cases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.