Alternatives to 42Crunch for Jailbreak resistance probe battery
What middleBrick covers
- Runs 18 adversarial jailbreak probes across three scan tiers
- Black-box scanning with read-only methods only
- OpenAPI 3.0/3.1/Swagger 2.0 parsing with spec/runtime correlation
- Authenticated scans with header allowlist and domain verification
- Continuous monitoring with diff detection and HMAC-SHA256 webhooks
- Maps findings to PCI-DSS 4.0, SOC 2 Type II, OWASP API Top 10
Jailbreak resistance probe battery overview
This page focuses on API scanning tools that exercise jailbreak resistance through adversarial probe batteries. The tool submits a URL and returns a risk grade with prioritized findings. Black-box methodology is used, requiring no agents, SDKs, or code access. Read-only interactions and text-only POST for LLM probes keep the scan non-intrusive and completed in under a minute.
Detection coverage for adversarial probes and OWASP API Top 10
The scanner evaluates 12 categories aligned to OWASP API Top 10 (2023). For jailbreak resistance, it runs 18 adversarial probes across three scan tiers: Quick, Standard, and Deep. These probes test system prompt extraction, instruction override, DAN and roleplay jailbreaks, data exfiltration, cost exploitation, base64 and ROT13 encoding bypass, translation-embedded injection, few-shot poisoning, markdown injection, multi-turn manipulation, indirect prompt injection, token smuggling, tool-abuse, nested instruction injection, and PII extraction.
For broader API risk, detection includes authentication bypass, JWT misconfigurations such as alg=none and expired tokens, BOLA and IDOR via sequential ID enumeration, BFLA and privilege escalation attempts, over-exposed properties, input validation issues like CORS wildcard and dangerous methods, rate limiting and oversized responses, data exposure including PII patterns and API key formats, encryption and header misconfigurations, SSRF via URL-accepting parameters, and inventory issues like missing versioning. The tool also flags unsafe consumption surfaces such as excessive third-party URLs and webhook endpoints.
OpenAPI and authenticated scan considerations
The scanner parses OpenAPI 3.0, 3.1, and Swagger 2.0 with recursive $ref resolution. It cross-references the spec against runtime behavior to highlight undefined security schemes, sensitive field exposure, deprecated operations, and missing pagination. When authenticated scanning is enabled on Starter tier and above, it supports Bearer, API key, Basic auth, and Cookie methods. Domain verification is enforced through DNS TXT records or an HTTP well-known file so that only the domain owner can submit credentials. A strict header allowlist is applied, forwarding only Authorization, X-API-Key, Cookie, and X-Custom-* headers.
Continuous monitoring and compliance mapping
Pro tier adds scheduled rescans at intervals of 6 hours, daily, weekly, or monthly. Diff detection highlights new findings, resolved findings, and score drift between scans. Alerts are delivered via email at a rate-limited pace of 1 per hour per API and through HMAC-SHA256 signed webhooks that auto-disable after 5 consecutive failures. The tool maps findings directly to three frameworks: PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other regulations, it helps you prepare for and supports audit evidence relevant to the controls described.
Operational safety and data handling
The scanner uses read-only methods only and never sends destructive payloads. Private IPs, localhost, and cloud metadata endpoints are blocked at multiple layers. Customer data can be deleted on demand and is purged within 30 days of cancellation. It is not used for model training and is never sold. Note that the tool detects issues and provides remediation guidance but does not fix, patch, block, or remediate. It does not perform active SQL injection or command injection testing, and it does not detect business logic vulnerabilities, blind SSRF, or replace a human pentester for high-stakes audits.