← ClaudeAtlas

detect-api-business-logic-abuselisted

Detection and response methodology for API business logic abuse - BOLA / IDOR (OWASP API1:2023), request-rate abuse (API4:2023), and out-of-order workflow attacks against REST and GraphQL APIs (MITRE ATT&CK T1190, with high-volume enumeration resembling T1595). Works off API gateway and reverse-proxy access logs (nginx, Apache, AWS ALB / API Gateway, Azure APIM and Front Door, Cloudflare) plus WAF and application audit logs. Gives the method for spotting one principal touching object IDs across many owners, per-principal velocity spikes, and workflow step-skipping, plus public rule sources and object-level-authorization hardening. Use when investigating suspicious API access, hunting for IDOR or BOLA enumeration, triaging a spike of 403 or 404 responses from one token, building rate or sequence anomaly detection, or hardening an API against BOLA.
umbrasec-labs/umbra-blue · ★ 0 · API & Backend · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# API Business Logic Abuse (BOLA / IDOR, Rate and Sequence) - Defensive Methodology > **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's method, the log sources and signals, and the hardening, and points to public rule sources. Promotion to Tier 1 (a sourced, tuned UMBRASEC rule) is tracked in [COVERAGE.md](https://github.com/umbrasec-labs/umbra-blue/blob/main/COVERAGE.md). Do not treat the content below as citing a UMBRASEC rule; there is none for this threat yet. ## TL;DR for defenders API business logic abuse does not look like an exploit. Every request is well formed, authenticated, and returns a normal status code. The abuse is in the aggregate: one principal reads invoice `1001`, then `1002`, then `1003` (Broken Object Level Authorization, OWASP API1:2023); one token makes ten thousand requests a minute (unrestricted resource consumption, API4:2023); or a client calls `POST /checkout` without ever calling `POST /cart` (a skipped workflow step). You catch it by baselining per-principal behaviour at the API gateway: the set of distinct object IDs a principal touches, its request velocity, and the order of its calls. Enforce object-level authorization in the application so BOLA cannot succeed, and log enough at the gateway that you can see enumeration when it does. There is no single event ID here; the signal lives in access-log aggregation. ## What it looks like, defender view In telemetry, BOLA enume