Repository navigation
Architecture
Isaac Thor edited this page Mar 8, 2026
·
1 revision
RMLW has two main layers: the Web Attack Workbench (static foundation) and the Recursive Meta-Learning Layer (self-improving orchestration).
The workbench runs vulnerability tests against HTTP endpoints.
| Test | Signal | Heuristic |
|---|---|---|
| XSS | Payload reflection | Payload appears in response body |
| SQLi | Boolean logic | True/false conditions produce different responses |
| LFI | File content | /etc/passwd markers in response |
| CMDi | Timing | sleep N causes measurable delay |
| SSRF | Internal access | Non-error response to internal IP probes |
- Endpoint: (method, url, params, headers, body)
- Parameter: (name, location, baseline_value) – query, path, header, or body
- Finding: (ftype, url, param, payload, detail)
Parameters are extracted from the query string. For URLs without query params, a default "q" is used.
Captures target characteristics:
- waf_detected: WAF presence from headers
- input_filtering: Per-parameter filter behaviour
- successful_payloads: Payloads that triggered findings
- failed_payloads: Payloads that did not
- State: Coarse encoding from EnvironmentModel
- Actions: Test families (xss, sqli, lfi, cmdi, ssrf)
- Algorithm: Tabular Q-learning
- Population: Payload strings
- Fitness: Based on findings
- Operators: Mutation (encoding, case, quotes), crossover
- Stores successful payloads with context
- Supports recent(n) and diversity retrieval
- Feeds recombination and novelty search
- UCB Bandit: Chooses which mechanism to apply
- Strategies: RL-driven, evolution, archive, baseline
- Reward: New findings, novelty
- MetaController selects mechanism (UCB)
- Mechanism influences Workbench (payloads, test order)
- Workbench runs tests against target
- Findings update EnvironmentModel and Archive
- RL/Evolution update based on reward
- Repeat
Target URLs are validated and scoped:
- validate_target_url: Rejects disallowed schemes (file, javascript, data, etc.)
- normalize_url: Structural normalization
- url_in_scope: Ensures endpoints match the configured host
All scans are restricted to the host of the configured base URL.