42Crunch for Multi-turn manipulation audit
What middleBrick covers
- Black-box scanning with no agents or SDK dependencies
- 18 LLM adversarial probes across Quick, Standard, and Deep tiers
- Read-only methods only, no destructive payloads
- OpenAPI 3.0/3.1 and Swagger 2.0 parsing with $ref resolution
- Authenticated scanning for Bearer, API key, Basic, and Cookie
- Continuous monitoring with diff detection and alerts
Scope of multi-turn manipulation testing
Multi-turn manipulation refers to attacks that unfold across multiple requests, where earlier interactions influence later behavior. The scanner exercises this surface with 18 adversarial probes across three scan tiers: Quick, Standard, and Deep. These probes target system prompt extraction, instruction override, DAN and roleplay jailbreaks, data exfiltration, cost exploitation, encoding bypasses, translation-embedded injection, few-shot poisoning, markdown injection, multi-turn manipulation, indirect prompt injection, token smuggling, tool-abuse, nested instruction injection, and PII extraction.
How middleBrick handles multi-turn scenarios
Because scanning is black-box, the engine sends read-only methods (GET and HEAD) and text-only POST bodies for LLM probes. No agents, SDKs, or code access are required, so the approach works with any language, framework, or cloud. Scan duration is under a minute. The scanner checks for unsafe consumption surfaces such as excessive third-party URLs and webhook/callback endpoints that could be leveraged in chained interactions.
Integration friction and operational considerations
Authenticated scanning at the Starter tier and above supports Bearer, API key, Basic auth, and cookies, with domain verification via DNS TXT record or an HTTP well-known file. Only a restricted allowlist of headers is forwarded, reducing risk when credentials are supplied. The scanner parses OpenAPI 3.0, 3.1, and Swagger 2.0 with recursive $ref resolution and cross-references spec definitions against runtime findings to highlight undefined security schemes or deprecated operations.
What the scanner does not cover for multi-turn manipulation
The tool does not perform active SQL injection or command injection, as those require intrusive payloads outside its scope. It does not detect business logic vulnerabilities, blind SSRF, or guarantee coverage of all multi-turn chains, because these often require deep domain understanding and out-of-band infrastructure. It is not a replacement for a human pentester in high-stakes audits.
Mapping to compliance and reporting
Findings map directly to OWASP API Top 10 (2023), and the tool aligns with security controls described in SOC 2 Type II and PCI-DSS 4.0. Reports include prioritized findings, remediation guidance, and support for audit evidence collection. Organizations can use the Web Dashboard for scan management and trend tracking, generate branded compliance PDFs, and integrate via CLI, GitHub Action, MCP Server, or a programmable API client.