Astra for Fintech

What middleBrick covers

  • Black-box scanning with read-only methods under one minute
  • 12 OWASP API Top 10 aligned risk categories
  • Authentication support for Bearer, API key, Basic, and Cookie
  • OpenAPI 3.0/3.1 and Swagger 2.0 parsing with ref resolution
  • CI/CD integration via GitHub Action and MCP Server
  • Continuous monitoring with diff detection and email alerts

API Security Posture for Financial Services

Financial APIs move sensitive payment and identity data, so security must be precise and verifiable. middleBrick maps findings to OWASP API Top 10, covers requirements of PCI-DSS 4.0, and supports audit evidence for SOC 2 Type II. The scanner operates as a black-box tool, submitting only read-only methods to observe runtime behavior without altering systems.

Scan Methodology and Limitations

middleBrick is a self-service API security scanner that submits a URL and returns a risk score from A to F with prioritized findings. Scan time is under a minute using GET and HEAD methods, with text-only POST for LLM probes. It does not fix, patch, block, or remediate, and it does not perform active SQL injection or command injection, as those require intrusive payloads outside scope. It also does not detect business logic vulnerabilities, blind SSRF, or replace a human pentester for high-stakes audits.

Detection Coverage for Common API Risks

The scanner evaluates 12 categories aligned to OWASP API Top 10. These include authentication bypass and JWT misconfigurations such as alg=none and expired claims, BOLA and IDOR via sequential ID enumeration, BFLA and privilege escalation through admin endpoint probing, and property authorization issues like over-exposed internal fields. Input validation checks for CORS wildcard usage and dangerous HTTP methods, while rate limiting detection reviews headers and oversized responses. Data exposure identifies PII patterns, API key formats, and error leakage, and encryption checks enforce HTTPS, HSTS, and cookie flags. SSRF detection targets URL-accepting parameters and internal IP probing, and inventory management flags missing versioning and legacy paths.

Authenticated Scanning and Compliance Alignment

Authenticated scanning (Starter tier and above) supports Bearer, API key, Basic auth, and Cookie methods, gated by domain verification to ensure only domain owners can scan with credentials. Header allowlist is limited to Authorization, X-API-Key, Cookie, and X-Custom-* headers. middleBrick helps you prepare for regulatory alignment with security controls described in PCI-DSS 4.0 and SOC 2 Type II, and surfaces findings relevant to OWASP API Top 10 (2023).

Product Integration and Deployment Options

The Web Dashboard provides a centralized view for scanning, reporting, and tracking score trends, with branded compliance PDFs available for sharing. The CLI via the middlebrick npm package supports command-line scans with JSON or text output. A GitHub Action can enforce CI/CD gates by failing builds when scores drop below a set threshold. An MCP Server enables scanning from AI coding assistants, and an API client allows custom integrations for continuous monitoring workflows.

Frequently Asked Questions

Does middleBrick perform active exploitation during scans?
No. The scanner only uses read-only methods and does not send destructive payloads, active SQL injection, or command injection.
Can authenticated scans be run in CI/CD pipelines?
Yes, authenticated scanning is supported from Starter tier onward, with domain verification required for credentialed scans.
How are compliance requirements addressed?
Findings map to OWASP API Top 10, and the tool helps prepare for security controls described in PCI-DSS 4.0 and SOC 2 Type II.
Is customer scan data retained or used for model training?
No. Data is deletable on demand, purged within 30 days of cancellation, and is never sold or used for model training.