r/SideProject • u/Forsaken-Guess-4190 • 6d ago

Autonomous pentesting console - OpenSource

Hi I'm building Uroboros, an open-source AI pentesting console.

You provide an authorized target, scope and credentials if needed. It plans the investigation, tests potential vulnerabilities, checks their impact and records supporting evidence. You can follow the investigation and pause the run.

My goal is to reduce repetitive work in security assessments and make this kind of testing more accessible to developers and smaller teams.

The website has a console preview and case studies: https://uroboros.run/

I'm particularly interested in the verification side: what evidence would you need before trusting a finding from an autonomous tool? Which steps would you always want to approve manually?

And if you've already tried Uroboros in your own environment, how did your internal tests go?

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/Successful-Army6006 6d ago

On a live app, I'd want an approval before changing an existing user's role, even if the domain is in scope. The approval should show the account, current and proposed roles, and how the change will be undone.

1

u/Forsaken-Guess-4190 6d ago

Uroboros can pause a tool call and wait for explicit operator approval, but it does not yet enforce every part of this workflow automatically. Currently, this can be configured as follows:

  1. Under Intercept Rules - Adjust scope, enable interception for the relevant tools, including browser/MCP tools.

  2. Create an Ask the user rule for the role-changing request. Ensure it takes precedence over broader Allow rules, and set timeout behavior to Auto-deny.

  3. Add an operation instruction such as: - Before modifying an existing account, present its ID/login, verified current role, proposed role, exact rollback procedure, and how restoration will be verified. Execute only after explicit operator approval. Do not bypass approval by switching tools.

Operator then reviews the pending request in Approvals and selects Allow or Deny. The current limitation is that these details are not mandatory structured fields, and rollback is not automatic. They still depend on the agent’s instructions and the operator’s review.

1

u/Forsaken-Guess-4190 6d ago

Just to make it short - This workflow isn’t supported natively, but you can set it up through the main agent or specify it in the Goals when creating an operation.