Scope
Reads the request and the signed scope. Marks what is inside and what is outside.
home / products
product
An AI-assisted analysis system that runs tests following a fixed method. It stops whenever a human decision is needed.
the six stages
Reads the request and the signed scope. Marks what is inside and what is outside.
Maps the verified domain: pages, endpoints, visible roles.
Proposes test hypotheses, each with a written reason.
Runs only actions from a closed list. Logs every request and response.
Tries to break conclusions before they reach a person.
Drafts the report with the steps to reproduce each vulnerability.
human control
Scope and hypotheses are approved by a person. A hypothesis outside the scope is not run.
A vulnerability is confirmed only if the finding is reproducible and a person has assigned the severity.
No document reaches the client without review. The reviewer can change the severity or discard the point.
the platform
Every test begins by naming the target, which must fall within an authorised scope. You can set a priority (IDOR/BOLA, SSRF, RCE), add instructions and, if needed, provide authentication.
Screenshot of the ExploitFinder platform.
product status
This is the architecture planned for the services. What is still a prototype or on the roadmap is stated as such.
| Part | Status |
|---|---|
| Action log with chain of custody | prototype |
| Scope control and domain verification | prototype |
| Human review and verdict for each vulnerability | prototype |
| Analysis connected to a language model | in progress |
| Public benchmark on test applications | in progress |
| Emergency stop for the whole scope | to complete before the first service |
| Client portal to follow tests | roadmap |
It starts from a written proposal, with the scope signed before any test.