Documentation
Technical reference for AbuseTest operational diagnostics.
Overview
AbuseTest performs deterministic operational diagnostics on web system flows explicitly defined by the user.
What it evaluates
It evaluates structural behavior under:
- Repetition
- Concurrency
- Boundary input stress
- Controlled spike conditions
What it does not perform
- Does not access your repository
- Vulnerability exploitation
- SQL injection attempts
- Authentication bypass
- Code exploitation
- Unauthorized data extraction
Core Concepts
An execution cycle consisting of defined scenarios applied to a target endpoint or flow.
A deterministic behavioral simulation such as:
- Rate Limit Enforcement
- Retry Storm Resilience
- Double Submit Prevention
- Traffic Spike Tolerance
- Race Condition Detection
- Boundary Payload Stress
- Cross-Origin Exposure Check
- Operational Cost Projection
Number of simultaneous requests executed during a scenario.
Controlled increase in request body size to evaluate boundary enforcement.
Analytical estimation based on accepted requests and observed behavior. Does not represent billing from target provider. Represents modeled operational exposure.
Smart Mode
Automatically generates inspection profile based on endpoint type. Recommended for all experience levels.
Supported endpoint types
- Authentication (login, reset, 2FA)
- Payment / Order Processing
- Public API (REST/GraphQL)
- File / Processing (upload, converter, transform)
- Admin / Internal
- Form Submission
- Auto-detect (hybrid profile)
Parameters are controlled and bounded. Smart Mode selects appropriate scenarios based on endpoint type risk patterns.
Advanced Mode
Allows manual adjustment of inspection parameters.
Configurable parameters
- Scenarios
- Concurrency
- Retry depth
- Payload size
- Spike multiplier
- Origin headers
Hard safety limits apply. Advanced Mode cannot exceed system-defined caps.
Safety Controls
All inspections operate within enforced boundaries.
AbuseTest does not execute unbounded stress testing.