Migrating from Noname Security to middleBrick
What middleBrick covers
- Black-box scanning with no agents or SDK dependencies
- Risk score A–F with prioritized findings
- OpenAPI 3.0/3.1 and Swagger 2.0 parsing with recursive $ref
- LLM security probes across Quick, Standard, and Deep tiers
- Proactive monitoring with scheduled rescans and diff detection
- CI/CD integration via GitHub Action and MCP Server
Overview of migration objectives
Migrating from Noname Security to middleBrick centers on moving scan execution into a self-service model while preserving historical context. middleBrick is a black-box scanner that submits a URL and returns a risk score from A to F with prioritized findings. It does not require agents, code access, or SDK integration, and completes a scan in under one minute using read-only methods.
Data export from Noname Security
Export all relevant data from Noname Security before cutover. Use their UI or API to retrieve scan records, findings, and risk assessments in JSON or CSV. Map findings to middleBrick categories such as Authentication, BOLA IDOR, BFLA Privilege Escalation, and Data Exposure. Note that Noname classifications, custom tags, and historical ticket links will not transfer automatically; you will need to reconcile these in your ticketing system or spreadsheet before importing into middleBrick workflows.
Rebuilding scan history and continuous monitoring
To rebuild history, import your exported scan data into a structured log (for example, a CSV or a small database) and use it as a baseline. middleBrick Pro tier supports scheduled rescans every 6 hours, daily, weekly, or monthly, with diff detection that surfaces new findings, resolved findings, and score drift. Configure email alerts limited to 1 per hour per API and HMAC-SHA256 signed webhooks that auto-disable after 5 consecutive failures to maintain signal quality without overwhelming your team.
CI/CD wiring during the cutover
Keep CI pipelines running by maintaining the Noname Security integration until middleBrick is verified in staging. Then switch the CI gate to the middleBrick GitHub Action, setting a minimum score threshold so the build fails on regressions. For initial migration, run middleBrick in parallel in read-only mode against a staging subset to compare results. Expect differences in detection granularity; treat middleBrick as the source of truth for OWASP API Top 2023 mapping, PCI-DSS 4.0, and SOC 2 Type II audit evidence, while using Noname for legacy tracking until the transition is complete.
Capabilities gained and limitations to acknowledge
After migration, your team gains black-box scanning across any language or cloud, OpenAPI 3.0/3.1/Swagger 2.0 parsing with recursive $ref resolution, and an LLM security test tier with 18 adversarial probes across Quick, Standard, and Deep scan levels. You will lose Noname-specific custom rulesets and proprietary detection logic; middleBrick does not fix, patch, block, or remediate, nor does it perform active SQL injection, command injection, or blind SSRF testing. It maps findings to compliance frameworks such as PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10, and it helps you prepare for audits without claiming certification.
Pricing and access planning
Evaluate pricing tiers against your API inventory. The Free tier allows 3 scans per month and CLI access. The Starter tier at 99 dollars per month supports 15 APIs, monthly scans, dashboard reports, email alerts, and the MCP Server for AI coding assistants. The Pro tier at 499 dollars per month covers 100 APIs with continuous monitoring, GitHub Action gates, CI/CD integration, Slack or Teams alerts, compliance reports, and signed webhooks. Enterprise tiers are available for unlimited APIs, custom rules, SSO, audit logs, SLAs, and dedicated support.