> 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/getting-started.md).

# Getting Started

## Hierarchy Of Concepts

To fully understand all the features available on the Platform, keep in mind the **hierarchy of concepts** from higher to lower level:

* [**Target**](/ai-red-teaming/probe/target.md) - your **generative AI application being** tested by executing Test Runs.
  * [**Test Run**](/ai-red-teaming/probe/test-run.md) **-** consist of one or more [**Probes**](/ai-red-teaming/probe.md). When a Test Run is started, the associated Probe Runs are executed sequentially.
    * [**Probe Run**](/ai-red-teaming/probe/probe-run.md) (e.g. Context Leakage, Jailbreak etc.) - all Test Cases **associated with the specific vulnerability** that the Probe is designed to detect. It cannot be triggered independently, it can only be triggered through a Test Run.
      * [**Test Case**](/ai-red-teaming/probe/probe-run/test-case-details.md) **-** an adversarial attempt defined by a strategy, a red-teamer, and a variation. It is executed against the target and validated to determine whether the attack attempt succeeded. Based on the outcome the Test Case status is marked Passed (attack did not succeed) or Failed (attack succeeded, vulnerability found).

## Start Testing

1.  [**Add a Target**](/ai-red-teaming/probe/target/add-target.md) \
   **-** Connect your AI system and configure it within the Platform. \
   \- Save your target for testing.
2. [**Configure Probes**](/ai-red-teaming/probe/probe-configuration.md) \
   **-** Choose and configure the scanners you wish to test your target with (called probes).\
   \- Optionally, add custom probes.
3.  [**Run a Test**](/ai-red-teaming/probe/test-run.md)\
   **-** Execute the selected probes against your target in a test run.\
   \- Monitor probe execution, attack attempts, and system responses.
4. [**Review Results**](/ai-red-teaming/probe/test-run.md#test-run-results)\
   **-** Inspect vulnerability findings.\
   \- Drill down into specific [**Probe Runs**](/ai-red-teaming/probe/probe-run.md) and test cases with input/output details.\
   \- The Platform displays results on the [**Test Run Results**](/ai-red-teaming/probe/test-run.md#test-run-results)**,** [**Probe Run Results**](/ai-red-teaming/probe/probe-run/probe-run-view.md#probe-result-table) and [**Probe Overview**](/ai-red-teaming/probe/overview-page.md) page. 
5. [**Generate Reports**](/ai-red-teaming/probe/test-run/test-run-report.md) **&** [**Check Compliance**](/ai-red-teaming/probe/compliance.md)\
   **-** Export results for auditors or internal governance.\
   \- Validate test results against different compliance frameworks and policies.

### **Review & Iterate**

Probe is designed for continuous security and safety validation. After each run that uncovers vulnerabilities:

* [Adjust the system prompt](/ai-red-teaming/remediation/prompt-hardening.md)
* Re-run probes to validate improvements.


---

# 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/getting-started.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.