Bright Security for Mid-market companies

What middleBrick covers

  • Black-box scanning with no agents or code access
  • Risk scoring from A to F with prioritized findings
  • Detection aligned to OWASP API Top 10 (2023)
  • OpenAPI 3.x and Swagger 2.0 parsing with $ref resolution
  • Authenticated scans with header allowlisting
  • CI/CD integration via GitHub Action and MCP server

API Security Visibility For Mid-market Teams

Mid-market organizations face pressure to move quickly while maintaining a defensible security posture. This scanner provides a read-only assessment of public and authenticated API surfaces without requiring code access or agents. Within under a minute, you receive a risk score and prioritized findings that map to common security frameworks, helping you understand exposure without disrupting production systems.

Detection Scope And Method

The scanner operates as a black-box solution, validating behaviors rather than relying on source code. It supports GET and HEAD methods by default, with limited text-only POST capabilities for LLM probes. Detection coverage spans 12 categories aligned to the OWASP API Top 10 (2023), including authentication bypass, excessive data exposure, injection surfaces, and LLM-specific adversarial probes across Quick, Standard, and Deep scan tiers. OpenAPI 3.0, 3.1, and Swagger 2.0 specs are parsed with recursive $ref resolution, and findings are cross-referenced against the spec to highlight undefined security schemes or deprecated operations.

Authenticated Scanning And Controls

For Starter tier and above, authenticated scans are supported via Bearer tokens, API keys, Basic auth, and cookies. Domain verification requires control of a DNS TXT record or an HTTP well-known file, ensuring only domain owners can scan with credentials. The scanner forwards a restricted allowlist of headers, including Authorization, X-API-Key, Cookie, and X-Custom-*, and does not attempt to remediate or block endpoints. This approach surfaces misconfigurations such as weak JWT settings, misconfigured security headers, and IDOR indicators while preserving environment integrity.

Integration And Ongoing Monitoring

The platform integrates into existing workflows through a web dashboard, CLI, GitHub Action, and an MCP server for AI-assisted development. The dashboard centralizes scans, tracks score trends, and enables export of branded compliance PDFs. With Pro tier, scheduled rescans run every 6 hours to monthly, and diff detection highlights new findings, resolved items, and score drift. Alerting includes rate-limited email notifications and HMAC-SHA256 signed webhooks that auto-disable after repeated failures, ensuring signals remain actionable without overwhelming teams.

Limitations And Responsible Use

This tool is a scanner and does not fix, patch, or block issues. It does not execute active SQL injection or command injection payloads, and business logic vulnerabilities require domain expertise to evaluate. Blind SSRF and certain advanced infrastructure weaknesses are out of scope because they rely on out-of-band channels. The scanner supports audit evidence collection and aligns with security controls described in frameworks such as PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023), but it does not certify compliance or replace a human pentester for high-stakes assessments.

Frequently Asked Questions

How are scan results scored?
Each API receives a letter-grade risk score from A to F based on the severity and quantity of findings. Higher-risk issues such as authentication bypass or data exposure carry more weight than low-severity misconfigurations.
Can I scan internal APIs behind authentication?
Yes, authenticated scanning is available in Starter and higher tiers. You provide credentials and the domain must be verified through DNS or file-based validation before the scan proceeds.
What frameworks do findings map to?
Findings directly map to PCI-DSS 4.0, SOC 2 Type II, and OWASP API Top 10 (2023). For other standards, the output can help you prepare evidence and align with described security controls.
How are LLM-specific probes handled?
The scanner runs 18 adversarial probes in three tiers, testing for system prompt extraction, instruction override, jailbreak techniques, data exfiltration paths, and token manipulation without executing destructive actions.
Is historical data retained after cancellation?
Customer scan data is deletable on demand and purged within 30 days of cancellation. It is not sold and is not used for model training.