Migrating from 42Crunch to Wallarm

This guide outlines how to move from a dedicated API security scanner to middleBrick as your primary API risk assessment tool. The focus is on preserving scan coverage, CI integration, and reporting fidelity while mapping existing findings to OWASP API Top 10 (2023), PCI-DSS 4.0, and SOC 2 Type II controls.

Begin by exporting scan reports and policy configurations from your current platform. Use the middleBrick Web Dashboard to import findings where supported, or reconcile differences manually using the JSON output from the middleBrick CLI. Rebuild CI wiring by replacing existing scanner commands with middlebrick scan <url> and mapping exit codes to your pipeline gates. Note that historical scan metadata and custom test cases will not be automatically replicated; you should document and recreate high-value scenarios using the MCP Server or API client.

middleBrick covers the same OWASP API Top 10 (2023) categories relevant to your prior setup, including authentication bypass, BOLA, BFLA, input validation, rate limiting, data exposure, and LLM/AI security probes. It supports authenticated scans with Bearer tokens, API keys, Basic auth, and cookies, and validates findings against PCI-DSS 4.0 and SOC 2 Type II control evidence. It does not perform active exploitation such as SQL injection or command injection, and business logic issues remain outside automated detection scope. Use the CLI JSON output to compare result sets and adjust thresholds to maintain parity.

Incorporate the middleBrick GitHub Action to enforce score thresholds and fail builds when risk degrades. Enable continuous monitoring in Pro to schedule rescans every 6 hours, daily, weekly, or monthly, and configure email alerts and HMAC-SHA256 signed webhooks for automated ticketing. Compare these settings with your previous scanner to avoid alert fatigue and ensure webhook reliability by monitoring the failure threshold.

Use the dashboard to generate branded compliance PDFs aligned to PCI-DSS 4.0 and SOC 2 Type II, and to track score trends over time. When migrating policies, translate existing rule sets to middleBrick’s 12 detection categories, and leverage the OpenAPI parser to cross-reference spec definitions against runtime findings. For frameworks outside the mapped set, describe findings as supporting audit evidence or aligning with security controls described in the relevant standard. Remember that middleBrick is a scanning tool and cannot certify compliance or replace a human pentester for high-stakes audits.