Migrating from Nuclei to middleBrick

Begin by cataloging the templates and workflows you run today. List the custom templates, the feed versions, and the execution patterns you rely on for rate handling and payload encoding. Export the scan reports you want to preserve; Nuclei JSON and CSV exports contain the fields you will need to map to middleBrick findings. Note which scans are tied to authentication flows or headers, because those will need reimplementation using Bearer, API key, Basic auth, or cookies in the new environment.

Use the exported JSON to reconstruct a timeline of findings outside of Nuclei. Parse timestamps, severity labels, and affected endpoints to create a canonical inventory in a spreadsheet or a lightweight database. In middleBrick, each scan produces a risk score and a prioritized finding list; map Nuclei issue IDs and template names to these findings to preserve traceability. Retain the original exports as audit evidence, and link them to the corresponding middleBrick scan IDs in your records.

During the transition, keep your Nuclei-based gates in place while you stand up middleBrick. Use the middleBrick CLI (middlebrick scan <url>) in parallel pipelines to compare outputs. Define a header allowlist that includes only Authorization, X-API-Key, Cookie, and X-Custom-*; this mirrors Nuclei’s header injection patterns while fitting middleBrick’s authenticated scanning rules. For authenticated scans, verify domain ownership via DNS TXT or an HTTP well-known file before enabling credentials in any pipeline.

You will lose some Nuclei template coverage, especially highly specialized or frequently updated community templates that probe protocols or proprietary payloads. middleBrick focuses on OWASP API Top 10 (2023) aligned detection, OpenAPI schema validation, and LLM/AI security probes across tiered scan depths. You gain structured risk scoring, continuous monitoring with diff detection, automated email alerts limited to one per hour per API, signed webhooks, and integrated compliance mappings to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10. Use the dashboard to track score trends and export branded compliance PDFs as evidence.

Define a runbook for how scans are triggered, who owns remediation, and how findings are triaged. In the Pro tier, schedule rescans at six-hour, daily, weekly, or monthly cadences and use diff detection to identify new findings or regressions. If you rely on webhook integrations, configure HMAC-SHA256 signed endpoints and monitor the auto-disable threshold of five consecutive failures. Keep the CLI in local development workflows with middlebrick scan <url> --output json to preserve output consistency across teams.