Skip to main content

AI-powered penetration testing platform

Evidence, not guesses.

Every finding in your queue was confirmed by AI review of evidence captured from your target. Findings that are not confirmed never reach your engineering queue.

No credit card required A free pentest of your own app

Findings flow into

  • Slack
  • Microsoft Teams
  • Discord
  • Email
  • Custom Webhook
  • GitHub Actions
  • GitLab CI
  • Jenkins
  • CircleCI
  • Azure Pipelines
  • Bitbucket

Platform

Two pentest modes. One verified outcome.

Web App Pentesting and API Pentesting are how you point Pentrova at a target. The capabilities below are built into every engagement of the matching mode, not sold as add-ons.

Inside every pentest

Three capabilities run in every engagement; DOM XSS taint runs in every Web App pentest, where there is a browser DOM.

Attack chains, Sandbox PoC and the Authorization Matrix run in every Pentrova engagement; DOM XSS taint runs in every Web App pentest. See the full pipeline , how AI-powered VAPT works for web apps and APIs, what AI penetration testing means in practice, or jump straight to pricing .

Engagement flow

From surface to signed-off evidence. Three phases.

Every Pentrova engagement runs the same pipeline. You bring the target; we bring the evidence.

  1. Surface · Schema · Session

    01 Ingest

    Point us at the surface.

    Upload an OpenAPI or Postman collection, paste a starting URL, or hand us a session cookie or bearer token. LLM-driven login handles the rest.

  2. Agent library · Chain catalog · Safe defaults

    02 Exploit

    Exploits run against your scope.

    Pentrova chains confirmed findings into business-impact paths. The scan sends real test traffic to your target, with payloads such as DROP TABLE and rm -rf blocked by default, so test a staging copy where you can.

  3. Evidence · cURL export · Masked secrets

    03 Evidence

    You get the captured evidence.

    Each finding carries the evidence captured from your target, with recognised secrets masked. Where it has an HTTP exchange, engineers can copy it as cURL and re-run it.

Beyond the OWASP Top 10

The vulnerabilities scanners were never built to find.

Pentrova goes deeper than injection and XSS. It tests the logic your application was built on — the kind of flaws that only senior pentesters catch.

  • Access control

    Cross-tenant isolation

    Tests whether User A can access User B’s data in multi-tenant SaaS environments — broken access control at the deepest level.

    How Pentrova proves it
  • Business logic

    Workflow bypass & business rules

    Step-skipping on read steps, rate-limit gaps and mass assignment — the flaws that live in your business rules, not your code syntax. Payment, refund and concurrent-write tests are not sent by default.

    How Pentrova proves it
  • AI security

    LLM & prompt injection

    If your application uses AI, Pentrova tests it for prompt injection, jailbreaks, and data exfiltration from language model endpoints.

    How Pentrova proves it
  • API security

    GraphQL & OpenAPI deep scan

    Native GraphQL introspection, mutation testing, and OpenAPI schema parsing to discover shadow endpoints that documentation missed.

    How Pentrova proves it
  • Modern auth

    MFA, SAML & SSO bypass

    Tests OTP brute-forcing, SAML signature wrapping, SSO relay attacks, and WebAuthn implementation flaws in enterprise auth stacks.

    How Pentrova proves it
  • Client-side

    WebSocket & PostMessage

    Modern browser vectors including prototype pollution, DOM clobbering, service worker hijacking, and real-time WebSocket injection.

    How Pentrova proves it

CI/CD Integration

Break the build before it breaks production.

On the Continuous plan, one POST /api/ci/scan call runs a CI check against your staging URL and returns a pass/fail quality gate. Drop it into any pipeline — GitHub Actions, GitLab, Jenkins, CircleCI, Azure, Bitbucket.

  • Per-severity quality gate — set fail_on thresholds for critical, high, medium, and low. The build fails the moment confirmed findings exceed your limits.
  • SARIF 2.1.0 & JUnit exports — findings surface natively in the GitHub Security tab, plus JUnit XML for GitLab and Jenkins test reports.
  • Sync or async — block the pipeline until the check completes (wait: true), or fire-and-forget and receive an HMAC-signed webhook callback.
  • Authenticated & scoped — test behind login, restrict the run to a defined scope, and authorize each check with a tenant-isolated, permission-scoped API key.

Example CI run: Pentrova receives a POST to /api/ci/scan with a quality gate of fail_on critical 0. The security scan runs against staging, AI review of the captured evidence confirms one critical finding, and because that exceeds the threshold the quality gate fails and the deploy to production is blocked. The run exports SARIF 2.1.0 for the GitHub Security tab and JUnit XML for Jenkins and GitLab.

Attack surface

Every layer. Every vector. Every edge case.

From classic injection to modern browser exploits, Pentrova covers the full spectrum of application security — continuously and autonomously.

  • Injection SQL, NoSQL, command & template
  • Cross-site scripting Reflected, stored & DOM-based
  • Authentication Tokens, sessions & federation
  • Server-side SSRF, XXE & out-of-band
  • Access control Authorization & tenant isolation
  • Infrastructure Transport, headers & policy
  • Business logic Workflow, race & abuse
  • Evidence Captured request & response evidence

Method

How Pentrova works.

Six engineering decisions shape every Pentrova engagement — what we confirm, what is blocked by default, what leaves your environment, what your audit team gets. Every one is independently verifiable in your first run.

  • 01 Verification

    Confirmed on evidence from your target

    Every finding in your queue was confirmed by AI review of evidence captured from your target. Where a finding has a captured HTTP exchange, your engineers can copy it as a cURL command and re-run it. Findings that are not confirmed never enter your queue.

    Verify: Copy a finding’s captured request as cURL and re-run it in staging.
  • 02 Safety

    Safe defaults, real traffic

    Payloads such as DROP TABLE, TRUNCATE and rm -rf are blocked by default and request rates are limited. The scan still sends real test traffic to your target and can change data or trigger alerts, so test a staging copy where you can and take backups before testing production.

    Verify: Scope a target and review what the run is allowed to touch.
  • 03 Data

    Scan output is sensitive. We treat it that way.

    Scan output can contain working credentials and personal data captured from your systems. Pentrova masks the secrets it recognises (passwords, tokens, API keys and session values) in exports and the live scan view; it does not remove personal data. Pentest content is never used to train models, never sold, never shared beyond the named subprocessors.

    Verify: Read how scan data is handled in the Trust Center.
  • 04 Evidence

    Portable evidence, not vendor lock-in

    Where a finding has a captured HTTP exchange, you can copy it as a cURL command or raw HTTP, or, on paid plans, download it as Markdown or HAR, and re-send it against the target yourself, without our control plane in the path.

    Verify: Copy a finding’s request as cURL and re-send it in staging.
  • 05 Compliance

    Compliance posture, in writing

    Every pentest on a paid plan ships a compliance-mapped PDF report — every finding tagged to the relevant PCI DSS v4.0.1, ISO 27001:2022, HIPAA Security Rule, and GDPR controls. Pentrova’s own ISO 27001 program is in build; we publish the audit timeline in the Trust Center as soon as the registrar engagement is signed.

    Verify: Check the control tags in the report against your framework.
  • 06 Scope

    Scope is fixed before the pentest runs

    The targets you have verified, the retest window your plan carries, and your integration scopes are all settled before a pentest starts. Retention is stated in the published policies rather than negotiated deal by deal. No surprise data egress, no quota games, no hidden invoices.

    Verify: Open a target and review the scope the run is allowed to touch.

Next step

Ship secure. Stay compliant.

Replace quarterly pentests with continuous, AI-driven security assurance — from business logic to GraphQL, from CI/CD gates to compliance-mapped evidence.

Site search

↑↓ navigateEnter openEsc close