business-logic

Identify and remediate security vulnerabilities in application business logic workflows.

3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/0x1337c0d3/claude-security --skill business-logic-0x1337c0d3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-logic
Source: https://github.com/0x1337c0d3/claude-security/tree/main/skills/sentinel/skills/business-logic
Command: npx skills add https://github.com/0x1337c0d3/claude-security --skill business-logic-0x1337c0d3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Business logic flaws are highly contextual and often invisible to generic scanners. This Skill guides auditors to identify workflow bypasses, negative amount manipulation, coupon abuse, self-referral exploitation, and improper state transitions that enable abuse.

Core Features & Use Cases

  • Identify critical workflow vulnerabilities in checkout, payments, discounts, and referrals.
  • Provide a structured manual analysis checklist for rapid triage and remediation.
  • Integrate with Sentinel findings to augment SAST with business-logic focused insights.

Quick Start

Ask me to audit your checkout and workflow logic for bypasses and manipulation vulnerabilities.

Frequently Asked Questions about business-logic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find business logic vulnerabilities during a code review?

To find business logic vulnerabilities during code review, map critical workflows and validate state transitions to identify workflow bypasses, negative amount manipulation, and coupon abuse. This structured approach enables rapid triage and remediation of contextual security flaws.

Why does my application have checkout and discount workflow bypasses?

Checkout and discount workflow bypasses occur when server-side checks are improperly enforced, allowing negative amount manipulation and coupon abuse. Identifying these business logic flaws requires mapping critical payment workflows and validating state transitions to prevent exploitation.

Can I use SAST findings to detect business logic security flaws?

Generic SAST findings alone cannot detect business logic security flaws because these vulnerabilities are highly contextual. You can augment SAST insights with a structured manual analysis approach that maps critical workflows and enforces server-side checks to prevent abuse.

What is the best way to audit referral programs for self-referral exploitation?

The best way to audit referral programs for self-referral exploitation is to perform a structured manual analysis of the referral workflow. Map critical workflows, validate state transitions, and enforce server-side checks to identify and remediate contextual business logic abuse.

How do I validate state machines to prevent improper state transitions?

To validate state machines and prevent improper state transitions, map critical workflows and enforce strict server-side checks across time-based conditions. This structured review approach identifies and remediates business logic vulnerabilities across various applications and industries.