← ClaudeAtlas

detect-business-logic-abuselisted

Detection and hardening methodology for business logic abuse in web and API applications: workflow/state-machine bypass (skipping payment or approval steps) and pricing abuse (client-side price tampering, coupon cracking, discount stacking, refund and inventory-hold abuse). Requests are individually valid, so no payload signature fires; the skill teaches session-journey reconstruction, server-vs-client price reconciliation, and redemption-velocity baselining. Maps to MITRE ATT&CK T1190 and T1499, plus OWASP API Security Top 10 2023 API6 and OWASP Automated Threats (OAT). Log sources: application access logs (nginx/Apache, ALB/CloudFront), API gateway, WAF, and application transaction/audit logs. Use when investigating coupon or promo abuse, checkout or price manipulation, orders that skip payment, bonus or referral farming, inventory hold abuse, or building workflow-bypass and pricing-abuse detections for an e-commerce or SaaS app.
umbrasec-labs/umbra-blue · ★ 0 · AI & Automation · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# Business Logic Abuse - 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 Business logic abuse exploits the gap between how a workflow is *meant* to run and how the server *actually enforces* it. Every request is well formed and often authenticated, so WAF signatures, SQLi/XSS rules, and IDS pattern matching all pass it. You catch it at the application layer, not the packet layer, by asking three questions per session: did the steps happen in the allowed order, does the price the server charged match the price the catalog says, and is any single identity or IP redeeming codes or placing orders faster than a human could. Build detection on your application transaction logs and access logs keyed by session and user, not on generic network telemetry. There is no portable signature; the detection is specific to your app's intended state machine and pricing policy. ## What it looks like, defender view In telemetry, workflow bypass appears as a request to a late-stage endpoint (for example `POST /api/order/confirm` or `/checkout/complet