Migrating from APIsec to Escape

This guide outlines how to move from APIsec to middleBrick when changing tools. It focuses on data export, rebuilding scan workflows, and aligning existing CI wiring with middleBrick capabilities. middleBrick is a scanner that reports findings and does not fix, patch, or certify compliance.

Extract findings from APIsec and map them to middleBrick categories aligned to OWASP API Top 10 (2023). Prioritize items by severity and exploitability. Common mappings include authentication bypass and JWT misconfigurations to middleBrick Authentication findings, and ID enumeration to BOLA. Export in JSON or CSV, then use a small transformation script to match middleBrick output fields such as category, location, and confidence.

Example transformation in Python:

import json
with open('apisec_export.json') as f:
    data = json.load(f)
for item in data.get('findings', []):
    mapped = {
        'id': item.get('id'),
        'title': item.get('title'),
        'category': map_category(item.get('severity')),
        'location': item.get('endpoint')
    }
    # send mapped to middleBrick import if supported

Recreate your scanning cadence using middleBrick scan modes. For external endpoints, use the CLI with middlebrick scan <url> and schedule via your existing orchestration. For authenticated coverage, provide Bearer, API key, Basic auth, or cookies and ensure domain verification via DNS TXT or HTTP well-known file. Replicate previous frequency by configuring Continuous Monitoring in Pro for daily or weekly rescans and diff detection to surface new findings or score drift.

Example CLI usage:

middlebrick scan https://api.example.com --auth-type bearer --auth-token <token>

Wire middleBrick into your pipelines using the GitHub Action to gate builds on score thresholds, or use the CLI in pre-commit and CI steps. Configure email alerts limited to 1 per hour per API, or set up HMAC-SHA256 signed webhooks with auto-disable after 5 consecutive failures. If you previously used APIsec CI hooks, replace them with these integration points and test failure behavior in a non-production environment.

Example GitHub Action snippet:

- name: MiddleBrick Scan
  uses: middlebrick/github-action@v1
  with:
    url: ${{ secrets.TARGET_URL }}
    threshold: C

middleBrick does not perform active SQL injection or command injection, does not detect business logic vulnerabilities, and does not replace a human pentester for high-stakes audits. If APIsec provided coverage for these areas, plan manual validation or complementary tooling. Use middleBrick for continuous OWASP API Top 10 monitoring and to surface findings relevant to SOC 2 Type II and PCI-DSS 4.0 controls, but do not rely on it to certify or ensure compliance with any regulatory framework.

Maintain a separate process for logic flaws and blind SSRF where out-of-band infrastructure is required. Track migrated scan history by correlating external identifiers such as endpoint paths and severity to preserve trend analysis across tools.