Agentic Pentester

Note:

• This capability is currently in Early Access (EA) and is not generally available. To request access, please contact OX technical support.

About Agentic Pentester

Agentic Pentester enables you to perform automated penetration testing against web applications using AI-driven agents.

Unlike traditional security scanners that rely on predefined checks, Agentic Pentester performs real attacks against live targets. The agent explores the application, discovers reachable endpoints, identifies attack paths, executes attack techniques, and validates findings with evidence.

Agentic Pentester combines runtime discovery with source code intelligence. By correlating discovered endpoints with connected repositories, OX can better understand application behavior, improve attack accuracy, and provide richer investigation context.

Use Agentic Pentester to:

• Configure applications for assessment.

• Verify that OX can access and authenticate to targets.

• Discover exposed URLs, APIs, and attack surfaces.

• Identify vulnerabilities across the application.

• Correlate runtime findings with source code repositories.

• Visualize relationships between targets, endpoints, and findings.

• Review attack evidence and understand how vulnerabilities were discovered.

Item	Description
Target Name	Name assigned to the target.
Asset Summary	Displays the number of Web and API assets discovered for the target.
Deployment Environment	Development, Staging, or Production environment.
Connectivity Status	Current connectivity verification status.
Findings	Number of findings grouped by severity.
Last Scan	Indicates when the target was last assessed.

How Agentic Pentester Works

Agentic Pentester analyzes applications from two directions:

• Runtime discovery of the running application.

• Source code intelligence from connected repositories.

The agent discovers exposed endpoints, explores application behavior, identifies attack paths, executes security tests, and validates findings using evidence collected during the assessment.

By combining runtime discovery with repository intelligence, OX creates a unified view of the application and its attack surface.

The typical Agentic Pentester workflow is:

1. Create a target and connect repositories

2. Verify connectivity

3. Ensure target access

4. Run an assessment

5. Review discovered endpoints and findings

6. Review target details

7. Export a penetration testing report

Ensure target access

Before assessing protected applications, ensure that OX can access the target.

Some applications are protected by Web Application Firewalls (WAFs), network firewalls, IP allowlists, or other security controls that can block assessment traffic.

To allow Agentic Pentester to access the application, allow traffic from the following OX static IP addresses:

• 18.202.47.201

• 63.33.147.64

If the application uses CAPTCHA or a custom access mechanism, configure a custom header when creating the target.

Run assessments

Agentic Pentester scans run independently from the main OX scan.

Currently, Agentic Pentester scans can be triggered manually only.

The following scan options are available:

Option	Description
Scan All Targets	Scans all configured targets.
Scan n Targets	Scans only the selected targets.

When a scan starts, OX displays scan progress and the number of targets currently being assessed.

Agentic Pentester findings are validated through successful attacks against live targets, providing a higher level of confidence than findings based solely on static analysis or configuration inspection.

To start a Pentester scan:

1. From the upper right corner, select Scan All Targets or Scan <number> Targets. The progress bar appears, with the details that include how many targets are being scanned.

1. To view the Agentic Pentester issues on the Active Issues page, go to Agentic Pentester > Issues.

Review Agentic Pentester findings

Agentic Pentester findings are displayed on the Active Issues page and include an additional Attack Overview tab that provides a step-by-step record of how the vulnerability was identified and validated.

The Attack Overview tab includes:

Section	Description
Attack Recap	High-level summary of the attack and validation process.
Attack Timeline	Chronological view of the actions performed by the agent.
Request Details	Request parameters, headers, payloads, and target information used during the attack.
Evidence	Artifacts collected from the target and used to validate the finding.

Use the Attack Overview tab to understand how the vulnerability was discovered, what evidence was collected, and why the finding was generated.