Experienced an incident?
Dasenda

Platform

The complete platform

Every module working on the same cases, the same assets and the same response policies.

Modules available on their own

Request a demo
ToolsCareersPress kit
Part ofDordio & Associates

© 2026 Dasenda

Offensive testing
that doesn't wait for the annual audit

Offensive agents map your applications and perimeter, test authentication, permissions and business logic, and only report what they managed to exploit.

Included in the complete platform and available on its own

Carpent/AI pentesting/tienda.acme.example
LIVE

Validated findings

Round of 14 Oct · after deployment 2026.10.14-2

Run a round

Routes tested

214

Hypotheses dismissed

1.106

Exploited

2

Fixed this month

6

IDFindingRouteStatus
PT-412
IDOR on other customers' orders
/api/orders/:id
Exploited
PT-409
Email change without re-authentication
/account/email
Exploited
PT-405
Coupon applies more than once
/checkout/coupon
Retesting
PT-401
User enumeration on sign-in
/auth/login
Fixed
PT-398
Incomplete security headers
tienda.acme.example
Fixed

Offensive agents test your applications the way an attacker would, every time they change. You only get what they managed to exploit, with the proof to reproduce it. No lists of possible vulnerabilities.

What it does

GET /api/orders/88412 · session B

HTTP/2 200

{ "id": 88412,

  "customer": "A",

  "address": "Zaragoza" }

IDOR exploitedRetested after the fix
  • Continuous testing

    Every deployment or perimeter change can trigger a new round of tests, without waiting for the next window.

  • Validated findings

    Each finding comes with the request, the response and the steps to reproduce it. No lists of possible vulnerabilities.

  • Business logic

    The agents test permissions between users, payment flows and object access, not just known signatures.

  • Controlled scope

    You set domains, time windows and allowed techniques. The agents check scope before every request.

In the console

Platform screens with data from Acme, the fictional company in the live demo.

Carpent/AI pentesting/PT-412
LIVE

IDOR on other customers' orders

GET /api/orders/:id · CVSS 8.1 · CWE-639

Exploited

Request · test customer B session

GET /api/orders/88412 HTTP/2
Host: tienda.acme.example
Cookie: session=<customer B>
Accept: application/json

Response · customer A's order

HTTP/2 200
{ "id": 88412,
  "customer": "A",
  "address": "C/ Example 12, Zaragoza",
  "items": 7, "total": 64.20 }

Agent-offensive

The ID is sequential and the API does not check the order belongs to the session. Tested with two test accounts, without touching real customer data.

Fix

Filter by the session's customer_id in OrdersController.show

Open in JiraRetest

How it works

  1. 01Set the scope

    You list applications, environments, test credentials and the windows when testing is allowed.

    • ✓Routes and forms mapped
    • ✓Attack hypotheses
    • ✓Exploitation within scope

    02The agents test

    They map the surface, form attack hypotheses and try to exploit them within scope.

    • PT-412 · IDORExploited
    • PT-405 · CouponRetesting
    • PT-401 · Sign-inFixed

    03You fix, it retests

    The finding becomes a case for your team and is retested automatically after the fix.

Connected to the rest of the platform

Exposure management tells it which assets to test first, and every exploited finding raises the priority of alerts on that asset in the Agentic SOC.

See the complete platform

Other modules

Watch it work with data like yours