Akto for Series B/C companies

What middleBrick covers

  • Black-box scanning with under one minute scan time
  • Covers OWASP API Top 10, PCI-DSS 4.0, SOC 2 Type II
  • Supports authenticated scans with header allowlist
  • Provides diff detection and score trend tracking
  • Delivers CLI, GitHub Action, and MCP Server integrations
  • Offers continuous monitoring with HMAC-SHA256 signed webhooks

Overview for Series B and C API security evaluation

At Series B and C, API risk directly impacts valuation, investor diligence, and incident response budgets. This scanner is a self-service black-box tool that submits a URL and returns a letter-grade risk score with prioritized findings. It operates without agents, SDKs, or code access, supporting any language, framework, or cloud in under a minute. The approach is read-only, using GET and HEAD methods plus text-only POST for LLM probes, avoiding intrusive payloads that disrupt production services.

Detection scope aligned to major frameworks

The scanner maps findings to OWASP API Top 10 (2023), covering common misconfigurations and attack patterns. It also aligns with requirements of PCI-DSS 4.0 and SOC 2 Type II by surfacing controls relevant to authentication, authorization, input validation, and data exposure. Detection categories include authentication bypass and JWT misconfigurations, BOLA and BFLA, property over-exposure, CORS misconfigurations, rate limiting issues, PII and API key leakage, HTTPS and cookie security, SSRF indicators, inventory shortcomings, unsafe consumption surfaces, and LLM/AI security probes across tiered scan depths.

Authenticated scanning and scope controls

With Starter tier and above, you can add Bearer tokens, API keys, Basic auth, and cookies to authenticated scans. A domain verification gate using DNS TXT records or an HTTP well-known file ensures only the domain owner can scan with credentials. The scanner forwards a restricted allowlist of headers, including Authorization, X-API-Key, Cookie, and X-Custom-* headers, minimizing exposure during testing.

Integration into development and compliance workflows

The tool supports multiple consumption models for engineering and security workflows. Use the CLI with middlebrick scan <url> for local or scripted runs, outputting JSON or text. The GitHub Action can gate CI/CD, failing the build when the score drops below a defined threshold. The MCP Server enables scanning from AI coding assistants, and the Web Dashboard centralizes reports and score trends. Continuous monitoring in Pro tiers provides scheduled rescans, diff detection, and email or webhook alerts for score changes.

Limitations and responsible usage

The scanner does not fix, patch, or block findings; it reports with remediation guidance. It does not perform active SQL injection or command injection testing, which requires intrusive payloads outside scope. Business logic vulnerabilities, blind SSRF, and high-stakes audit requirements are outside its scope and should be handled by human experts. This tool is an aid in assessment and evidence gathering, not a replacement for specialized analysis or formal audits.

Frequently Asked Questions

What does the risk score mean and how are findings prioritized?
The score ranges from A to F and reflects the combined severity and exploitability of findings. Prioritized findings highlight the most immediate risks, enabling teams to address high-impact issues first based on evidence from the scan.
Can authenticated scans validate domain ownership?
Yes, authenticated scans require domain verification via DNS TXT record or an HTTP well-known file. Only the entity that controls the domain can provide the credentials, preventing unauthorized scans.
How does the scanner support compliance evidence?