Add Business Logic Security Cheat Sheet#2117
Open
0xBassia wants to merge 1 commit intoOWASP:masterfrom
Open
Conversation
Adds a new cheat sheet covering prevention patterns for business logic vulnerabilities, which are typically missed by scanners because they require understanding of the intended application behavior. Covers server-side value re-derivation, workflow state machine enforcement, race condition prevention, feature-level abuse controls (referrals, coupons, promos), contextual authorization, invariant-based testing, and threat modeling from the business process perspective. Addresses issue OWASP#2064.
9b5ef04 to
b46b1f2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2064
Adds a new cheat sheet on preventing business logic vulnerabilities. This is the class of flaws that scanners don't find, because the bug isn't in any individual piece of code, it's in the gap between what the developer assumed and what the user can actually do.
The cheat sheet covers:
The scope is intentionally preventive, aimed at developers. Testing-focused content stays in the OWASP WSTG BUSL section, which is linked. Where topics overlap with existing cheat sheets (Access Control, Authorization, Transaction Authorization, Input Validation, Abuse Case), those are linked inline rather than duplicated.
Notes on approach
markdown-link-check.npm run lint-markdownandnpm run lint-terminologyboth pass cleanly.Index.mdunder B and bumped the count.Checklist
templates/New_CheatSheet.md