Mapping Business Workflows
You'll learn how to systematically document application processes to uncover hidden security weaknesses in business logic.
Why Map Workflows?
Before you can break business logic, you need to understand it. Mapping business workflows means creating a visual or written blueprint of how your application's features actually work—every step, decision point, and state transition. Think of it like drawing a treasure map where X marks the vulnerabilities.
Unlike technical flaws (like SQL injection), business logic vulnerabilities hide in the design of how things should work. Mapping reveals these hidden attack surfaces.
What to Document
When mapping a workflow, capture:
Step Sequences: Every action a user takes from start to finish (e.g., browse → add to cart → checkout → payment → confirmation)
State Transitions: How the application moves between states (e.g., order status: pending → processing → shipped)
Business Rules: The logic governing what's allowed (e.g., "discount codes apply only once per user" or "refunds only within 30 days")
Decision Points: Where the application checks conditions and branches (e.g., "If account balance > $0, allow withdrawal")
Input Parameters: What data flows through each step and how it's validated
The Mapping Process
Start by using the application normally while taking detailed notes. Document URLs, parameters, state values, and the order of operations. Look for multi-step processes like registration, checkout, password reset, or fund transfers.
Create simple flowcharts or numbered lists showing each state and valid transitions. Note where state is stored (cookies, hidden fields, session server-side) and what values change.
Then ask: What happens if I skip step 3? Repeat step 2? Go backward? Change this parameter? Your map becomes a checklist of attack vectors.
Key Takeaway: Mapping business workflows transforms opaque application logic into a testable attack surface by documenting every step, state, and rule that governs how features should behave.