Migrating from StackHawk to middleBrick

Begin by extracting your existing findings from StackHawk using its native export capabilities. Use the UI or API to pull scan reports, focusing on severity, endpoint path, and the underlying cause. Save these artifacts in a versioned location so you can cross-reference them during initial validation in middleBrick. This inventory helps you understand coverage gaps before you start the new scan cycle.

middleBrick does not ingest prior scan data automatically. To rebuild history, import your StackHawk exports into a tracking system (spreadsheet or issue tracker) and map each finding to a stable API identifier such as path plus HTTP method. Then run scheduled scans in middleBrick at the same cadence and store results alongside your old records. Over time, you will reconstruct trend lines for severity, detection frequency, and score drift using middleBrick’s dashboard diffing features.

During the transition, maintain CI integrity by running both tools in parallel for one or two cycles. In your CI pipeline, keep the existing StackHawk step but add a new middleBrick CLI step that runs after it. Use the middleBrick CLI to produce JSON output, then compare the new results against the baseline you created from historical exports. If the build fails criteria, route alerts to a temporary channel for review while you tune thresholds. This approach minimizes false positives and prevents deployment blockers due to unfamiliar severity mappings.

middlebrick scan https://api.example.com --output json --out results.json

You will lose StackHawk’s agent-based instrumentation, which can surface runtime behavior tied to specific libraries and frameworks. middleBrick is black-box and does not execute business logic, so subtle authorization flaws that depend on code paths may require manual exploration. In return, you gain broad compatibility across languages and clouds, read-only safety, and under-one-minute scan times. middleBrick’s standardized mappings to OWASP API Top 10 and structured scoring simplify prioritization and reporting, especially when tracking improvements over time.

Once the parallel phase completes, switch CI to use only the middleBrick CLI step and retire the StackHawk integration. Configure continuous monitoring in middleBrick Pro to run scheduled rescans and receive diff-based email alerts. Export periodic compliance PDFs for audits and use signed webhooks to feed security dashboards. Maintain an exception register for findings you cannot remediate immediately, and revisit it in each scan cycle to ensure risk does not accumulate.