> For the complete documentation index, see [llms.txt](https://docs.probe.splx.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.probe.splx.ai/ai-red-teaming/probe/probe-run/remediation.md).

# Remediation

In addition to the probe results, each probe includes a tab showing a **Remediation Tasks (General and Dynamic)** to address vulnerabilities identified by the probe, which can be applied to your target application.

The Platform also enables you take actions, by [Hardening your System Prompt](/ai-red-teaming/remediation/prompt-hardening.md), or configuring AI Runtime Protection through [Guardrails Setup](broken://pages/xHcV1spoF4RWrpY8Xg6J).

{% hint style="info" %}
You can manually mark task as applied. Each task includes a **clickable checkmark** next to the "Status" label. It allowing you to track whether the mitigation has been applied to a specific target.
{% endhint %}

Each remediation task card includes:

* **Title** - A short label describing the recommended fix.
* **Status** - Indicates whether the remediation has been applied. By default, it's shown as Not Applied.
* **Applied By / Timestamp** - These fields remain empty until the task is marked as applied, allowing for audit tracking.
* **Details** - A clear and actionable recommendation, tailored to mitigate the specific type of vulnerability observed.

General Remediation Tasks are automatically generated after a Probe Run is completed. Dynamic Remediation Tasks are generated once the [AI Analysis](/ai-red-teaming/probe/probe-run/analyze-with-ai.md) is finished, triggered by clicking the **“Analyze with AI”** button in the top-right corner.

## General Remediation Tasks

These tasks are general and static in nature, serving as the first line of defense against vulnerabilities tested in a specific probe. They are created based on content provided by our red team, who propose best practices identified through research and hands-on experience.

<figure><img src="/files/F9obkYASrgA0f9rsCls3" alt=""><figcaption><p>Figure 1: General Remediation Tasks </p></figcaption></figure>

## Dynamic Remediation Tasks

The **Analyze with AI** feature generates dynamic remediation tasks once the analysis is complete. To access them, go to the **Remediation** tab and then switch to the **Dynamic Remediation Tasks** sub-tab.

This tab presents **AI-generated, context-specific remediation suggestions** based on the results of a specific probe run. Unlike General Remediation Tasks, these tasks are dynamically created to address vulnerabilities identified during that exact probe run.

<figure><img src="/files/w0HWqh1kPLaorI3SrNBy" alt=""><figcaption><p>Figure 2: Dynamic Remediation Tasks</p></figcaption></figure>


---

# 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.probe.splx.ai/ai-red-teaming/probe/probe-run/remediation.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.