A Test Run is a group of executed probes performed at a specific point in time against your target. In each test run, you can choose which vulnerabilities to test by selecting one or more pre-configured probes.
To initiate a new test run, click the "New Test Run +" button on the Overview or Test Run page.
A dialog box will appear, prompting you to:
Enter the name of your run.
Select one or multiple probes to be included in the run.
Additionally, you can enable notifications or schedule the test run for later.
Your available probe credits are displayed in the header. Each selected probe deducts from your total.
To receive email notifications for a specific test run, enable the "Receive notifications" checkbox in the new test run modal.
Once the test run is complete, the user who initiated it will receive an email containing the test run details and the generated report as an attachment.
For more information about the report, refer to the Test Run Report page.
The test run can have the following statuses:
Pending: The test run will start when the queue is clear.
Running: The test run is in progress.
Finished: All scheduled probes and their attacks are completed.
Canceled: The test run was canceled by the user before completion.
Error: The test run was aborted due to target misconfiguration.
The test run's progress indicates the percentage of completed attacks out of the total scheduled.
To stop a test run in progress, open the Test Run View and click the "Cancel Test" button. This will abort the test run and stop all probes. All attacks executed up to that point will remain visible and will be included in the results.
You can re-run an existing test run by clicking the "Re-Run Test" button in the top right corner of the Test Run View. A test run cannot be rerun until it is either completed or stopped.
The test run results are displayed in the Test Run View, accessible by selecting the test run from either the Overview or Test Run History page.
The Test Run View displays and visualizes the data from all the probes selected for that test run. It includes an overview of the test run status, a Sankey diagram, and the probes table, which provides an overview of the results for each probe. From this page, you can cancel an ongoing test run or rerun a completed test run.
In the continuation of this page, you will find detailed explanations of the sections within the Test Run View and the data they contain.
At the top of the page, you will find the total number of test cases and the number of failed and error test cases from all included probes. The execution date and time are displayed next to the status and progress bar. A report for the test run can also be generated by clicking on the button in the top right corner.
A Sankey diagram visualizes the flow of data from one node to another, with the width of the flow representing the quantity or magnitude of the data. In this context the data represents executed test cases against your target.
The diagram illustrates the flow from the probe categories to specific probes visualizing the ratio of executed test cases between probes.
From the single probe, the flow connects towards passed, failed and error test case outcome, where the width of each flow indicates the number of test cases. Passed, failed and error nodes show total number of corresponding test cases in the test run.
The gradient from green to red visually represents the ratio of failed to passed test cases for each node. Nodes with fewer failed test cases appear greener, while those with more failed test cases appear redder. This provides a clear visual summary of the test run results.
In the Test Run View, the Probes Table lists all probes executed in that test run. The probes are grouped by category and display the total number of executed test cases, along with the counts of passed, failed and error test cases. A progress bar is also visible.
By clicking the arrowhead on the right, you can navigate to the Probe Run details for the selected probe within the test run.
The Test Run History provides a comprehensive list of all test runs associated with a single target, including those currently in progress. By default, test runs are sorted chronologically, with the most recent run appearing at the top.
The test run history table includes:
Test run's name.
Date and time of the execution.
The current test run status.
Probes included in the test run.
The Result that displays the total number of passed, failed and error test cases across all probes.
You can filter test runs by the following criteria:
Name: Search for a test run with the specific name.
Status: Filter by test run status.
Results: Filter test runs to include those with at least one passed or one failed test case.
Probes: Show test runs with at least one probe from selection.
Clicking on the "Details" button will open the Test Run View of the selected test run.
For each test run, you can download a shareable PDF report. This report provides details about your test target, along with an overview and summary of the test run. It includes general information such as the start time, execution time, total number of test cases, and more. Additionally, it features the combined results and a chart of all probe runs, offering a clear, one-stop insight into the target’s vulnerabilities.
The report also provides specific results for each probe run and their suggested mitigation strategies, helping you understand vulnerabilities and how to fix them.
To download the report, click the Generate Report button on the Test Run View.
The Test Run Scheduler enables you to plan and automate test runs at predefined times and frequencies, helping your team streamline evaluation workflows and reduce operational overhead. Instead of manually setting up tests every time you want to validate model behavior, scheduler allows you to set up recurring or single-run executions that run in the background.
Scheduler supports a wide range of use cases, from scheduled daily Context Leakage probe in production to monthly full security assessments—enabling consistent, repeatable testing practices aligned with your organization's policies and release cycles.
A new Scheduled tab has been added to the Test Runs page for easy management of your upcoming test runs, giving you clear visibility into what test runs are scheduled.
Starting a new test run now includes the option to schedule it for later. The familiar flow for launching a test is unchanged, but a new "Schedule For Later" button has been added to the test run creation modal.
Go to the Test Runs or Overview page.
Click New Test Run.
Configure the test name and select probes.
Click Schedule for Later.
Choose a date, time, and frequency for execution.
Confirm with Schedule Test Run.
All scheduled test runs can be fully managed from the Scheduled tab on the Test Runs page. This page provides a centralized view of upcoming and recurring test runs, allowing you to take direct actions as needed.
Each scheduled test run includes three control icons:
Start Test Run – Manually trigger the test run immediately.
Edit Test Run – Modify the scheduled test run configuration.
Delete Test Run – Permanently remove the scheduled run.
If a test run is not currently needed, you can toggle its status to Inactive without deleting it. This is useful for temporarily pausing automated runs without losing their configuration.
Click the Edit Test Run icon to modify any existing scheduled run. The following parameters can be updated:
Test Run Name
Date and Time of Next Run
Frequency (e.g. Daily, Weekly, Monthly, Single Run)
Selected Probes (custom or predefined probes)
Once changes are made, click Save Changes to update the schedule.