Migrating from 42Crunch to middleBrick for Customer chatbot security review

What middleBrick covers

  • Black-box API scanning with risk score A–F in under a minute
  • Detection of 12 categories aligned to OWASP API Top 10
  • OpenAPI 3.0/3.1/Swagger 2.0 parsing with $ref resolution
  • Authenticated scanning with strict header allowlist
  • Continuous monitoring with diff detection and alerts
  • Programmatic access via CLI, API client, and MCP Server

Overview of migration from 42Crunch to middleBrick

Migrating from 42Crunch to middleBrick for customer chatbot security review workflows replaces an integrated scanner with a black-box service that emphasizes read-only detection and minimal integration overhead. middleBrick requires no agents, SDKs, or code access; you submit a URL and receive a risk score from A to F with prioritized findings within under a minute. The scanner exercises endpoints using only GET and HEAD methods, with text-only POST reserved for LLM probes, avoiding destructive payloads. This approach suits environments where installing agents or altering deployment pipelines is undesirable.

Detection coverage aligned to standards for chatbot APIs

For customer chatbot security review, middleBrick maps findings to three frameworks: PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). The tool detects issues across 12 categories aligned to OWASP API Top 10, including Authentication bypass, BOLA and BFLA, Property Authorization over-exposure, Input Validation anomalies such as CORS wildcard usage, Rate Limiting behavior, Data Exposure patterns like emails, card Luhn validity, API key formats, and error leakage. LLM-specific probes cover 18 adversarial tests across Quick, Standard, and Deep scan tiers, targeting system prompt extraction, jailbreak techniques, data exfiltration, token smuggling, and related AI security risks. OpenAPI 3.0, 3.1, and Swagger 2.0 files are parsed with recursive $ref resolution, enabling cross-reference between spec definitions and runtime behavior to identify undefined security schemes or deprecated operations.

Authenticated scanning and domain verification for chatback endpoints

Authenticated scanning is available from Starter tier onward, supporting Bearer, API key, Basic auth, and Cookie credentials. Before running authenticated scans, domain verification is enforced via DNS TXT record or HTTP well-known file, ensuring only the domain owner can submit credentials. When credentials are provided, header forwarding is limited to Authorization, X-API-Key, Cookie, and X-Custom-* headers. This control helps keep customer chatbot review workflows scoped to intended endpoints while preventing unauthorized scan traffic.

Operational differences in reporting and monitoring

The Web Dashboard centralizes scan records, score trends, and allows export of branded compliance PDFs. CLI access through the middlebrick npm package supports commands such as middlebrick scan <url> with JSON or text output. The GitHub Action can enforce CI/CD gates by failing builds when scores drop below configured thresholds. For ongoing review, Pro tier provides scheduled rescans (every 6 hours, daily, weekly, or monthly), diff detection across scans to surface new or resolved findings, and email alerts rate-limited to 1 per hour per API. Webhooks are HMAC-SHA256 signed and auto-disabled after 5 consecutive failures. Enterprise tier adds unlimited APIs, custom rules, SSO, audit logs, SLA, and dedicated support.

Limitations and complementary testing practices

middleBrick is a scanner that detects and reports with remediation guidance; it does not fix, patch, block, or remediate findings. It does not perform active SQL injection or command injection tests, which require intrusive payloads outside its scope. Business logic vulnerabilities are not detected, as they demand domain understanding that a tool cannot replicate. Blind SSRF and other out-of-band infrastructure checks are out of scope, and the tool does not replace a human pentester for high-stakes audits. Use middleBrick to surface issues efficiently within defined constraints and plan complementary manual reviews where necessary.

Frequently Asked Questions

Does middleBrick require installing an agent in my environment?
No. middleBrick performs black-box scanning without agents, SDKs, or code access, making it suitable for environments where deployment changes must be avoided.
How are chatbot API keys handled during authenticated scans?
Authenticated scans support Bearer, API key, Basic auth, and Cookie credentials. Domain verification via DNS TXT or HTTP well-known file is required, and only specific headers are forwarded to limit exposure.
Can middleBrick map findings to compliance frameworks?
Yes. Findings map directly to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other frameworks, it supports audit evidence and aligns with described security controls.
What happens to scan data after account cancellation?
Customer scan data is deletable on demand and purged within 30 days of cancellation. Data is never sold and is not used for model training.