Migrating from APIsec to GitGuardian
What middleBrick covers
- Black-box scanning with no agents or SDK dependencies
- URL submission returns A–F risk score with prioritized findings
- Detects OWASP API Top 10 (2023) and related mapping
- OpenAPI 3.0/3.1 and Swagger 2.0 parsing with ref resolution
- Authenticated scans with header allowlist and domain verification
- Pro continuous monitoring and diff detection across scans
Overview of migration goals
This guide describes practical steps when moving API security scanning from APIsec to middleBrick. The focus is on data export, rebuilding scan history, preserving CI wiring, and understanding current gaps. middleBrick operates as a distinct tool with its own data model, so direct feature parity is not expected.
Exporting findings and historical data
Begin by extracting findings and metadata from APIsec. Most platforms provide an export of findings in JSON or CSV, including severity, location, and status (open/remediated). If timestamps are available, include them to preserve chronological context when importing into middleBrick. Note that middleBrick does not ingest external scan formats; you will re-scan assets to generate native findings and rely on continuous monitoring for change tracking across scans.
Rebuilding scan history and CI integration
To rebuild scan history in middleBrick, re-scan each API endpoint using the CLI or dashboard. Use the same URL list and authentication context (Bearer, API key, Basic, or Cookie) that was used previously. For CI, integrate the middleBrick CLI into your pipeline with a command such as:
middlebrick scan https://api.example.com --format json --out results.jsonCompare results over time using the dashboard’s trend view. The diff detection in Pro tracks new findings, resolved findings, and score drift, which you can use to approximate historical progression. Note that detailed line-by-line history from APIsec will not carry over; only recurring scan snapshots will be preserved.
Authentication and scope alignment
Ensure that authentication configurations in middleBrick match the original coverage. Authenticated scanning in middleBrick supports Bearer, API key, Basic auth, and Cookie, with domain verification required to confirm ownership. The scanner only forwards a strict allowlist of headers: Authorization, X-API-Key, Cookie, and X-Custom-*. If APIsec used custom headers for authorization, replicate them using the X-Custom-* allowlist to maintain similar test conditions.
Known gaps and limitations
middleBrick does not ingest or replay APIsec’s raw test cases or exploit payloads. Business logic vulnerabilities that were previously identified will need manual re-evaluation in the context of your domain. The tool does not perform active SQL injection or command injection testing, nor does it detect blind SSRF without out-of-band infrastructure. It also does not replace a human pentester for high-stakes audits. Continuous monitoring can reduce drift, but historical scan detail from APIsec cannot be fully reconstructed within middleBrick.