An AI Full Pentest is an on-demand penetration test of a single web application, run end-to-end by Intruder's autonomous AI pentesting agents. It tests your web apps specifically, not your whole external network, so you can run one with every release instead of waiting for an annual or quarterly engagement.

It regularly surfaces critical issues that scanners and human testers both miss, such as authentication and authorization bypasses. Each finding is verified against the running app with live evidence, and the report points to the source file and line it comes from. When it finishes, you get a downloadable PDF report you can hand to an auditor or customer. Intruder's reports are routinely used as evidence for frameworks like SOC 2, ISO 27001, and PCI DSS.

To start, go to the Pentests tab and click New pentest

You'll then see an overview of the feature: what you get, the price, a link to a sample report, the terms and conditions, a Learn more link back to this article, and an Ask us anything button if you'd rather put a question to the Support team first.

If you already have a setup in progress, the overview is skipped and you go straight back into it.

Once you have selected an AI Pentest, you will be presented with a form taking you through the setup stages: two parts are required (Scope and Source), and two are optional (Accounts and Context). Everything you enter saves automatically.

Scope tells the AI agent what to test.

Test accounts let the agent log in and test the authenticated parts of your app, which is usually where the interesting risk lives. If your app has any kind of login, adding credentials matters: without them, the agent can only test what's reachable when logged out, so most of the application goes untested. Only skip this step if the target is a fully public site with no authenticated area.

We highly recommend adding as many accounts as you can, covering every access level in your app — and, if it's multi-tenant, accounts belonging to different tenants or customers. This lets the agent test for privilege escalation and cross-tenant authorization failures, where a user reaches data or actions they shouldn't, which are among the most common critical issues it finds. As a rule of thumb, more is better — we test our own platform with roughly a dozen accounts covering every access level.

To add an account:

Source code is where you connect the repository that the agent reviews. This is a required part of an AI Full Pentest — the test is code-assisted, so the agent needs to read your code to pinpoint where issues originate.

Repositories are connected read-only, are not accessed by a person, and our engagement data is deleted when the pentest is torn down; we may keep limited source code excerpts for up to 30 days to improve the service. See the Intruder Trust Center for the full picture.

Context is where you point the agent at what matters. Every field is optional, but highly recommended. The more you give, the more targeted the results.

Checkout shows a summary of your configuration to review, then handles payment.

To discard your progress and start fresh, open the ⋯ menu at the top of the setup and select Start again. This menu is available throughout setup. Starting again clears your saved draft completely — there's no undo.

After you submit, you're taken to the pentest's status page, where the AI agent's progress is shown in real time — moving from Pending to Running to Completed. You can leave and return; the pentest keeps running regardless.

Before testing gets fully underway, Intruder runs preflight checks that confirm it can access your repository and log in with any credentials you supplied. If a check fails, you'll see a clear error — "Source code check failed" or "Accounts check failed" — with a Contact us button, so a misconfigured repo or credential doesn't quietly waste a test.

You can cancel at any point up until a report has been generated — while the pentest is still running, a Cancel pentest button is available on the status page. Canceling stops further testing, but can't undo actions the agent has already taken. It does not refund the test, and it won't produce a report for that engagement. If you want to resume a canceled pentest, contact us — but we can't guarantee it can be continued. Once the report exists, the pentest is complete and can't be canceled, but you can still leave feedback or raise questions with support.

The deliverable is a downloadable PDF report, accessed through a secure, time-limited link, and built to be handed to a third party. It follows a consistent structure:

Findings come with built-in recommended remediation SLAs — Critical within 24 hours, High within 7 days, Medium within 30 days, Low by the next release — so you have a timeline you can commit to internally or show an auditor.

You can use the report internally and share it with your own customers, regulators, auditors, and professional advisors to demonstrate your security posture. You can't share it with other third parties — in particular, providers of competing security testing services — without Intruder's written consent.

Retesting is a follow-up test that checks whether the findings from your AI Full Pentest have actually been fixed. Retesting is included with every AI Full Pentest at no extra cost, and there is no limit on how many times you can retest. You choose which findings to send back, the agent rechecks only those, and you get a new report showing which are remediated and which are still present.

Retesting needs the Admin role, the same as setting up a pentest.

While a retest runs, the pentest page shows Retest in progress with an elapsed timer, and each finding being rechecked shows a Retesting badge. You can leave the page and come back; the retest keeps running.

A retest covers only the findings you selected from your most recent report. It does not test the rest of your application again. Changes made elsewhere since the original test are not tested, except where they relate directly to the findings being rechecked. If you want the whole application tested again, that is a new AI Full Pentest.

A retest reuses the setup from the original pentest: the same scope, the same source code repositories, and the same test account credentials. There is nothing to configure. If those credentials have changed since the original test, contact us before starting the retest and we will update them for you.

Each retest produces its own PDF report, separate from your original report. The retest report:

In the portal, each retested finding ends up as either Remediated or Still present. The Executive summary on the pentest page becomes a Retest summary once your first retest completes.