State alignment

Keeping UI, database records, and session checkpoints coherent across multi-step flows.

1 min di letturaaggiornato il 2 ott 2026florianamette1 contributore
Chiedi al tuo assistente (MCP)Modifica su GitHub

State alignment asks whether the surface (what the user sees), the record (authoritative row in the database), and the session (ephemeral checkpoint) all describe the same step of a workflow. Drift enables skipping, duplicate submission, or wrong-branch transitions.

Pages#

PageFocus
Surface vs versionClient step counter vs server workflow version
Record statusRow status fields vs side effects already executed
Session checkpointSession keys that gate steps without DB corroboration

Tools#

  • Burp Suite (Repeater): replay steps while mutating the backing record to surface surface, record, and session drift.
  • Manual testing with Burp Repeater and crafted payloads.

References#

  • PortSwigger Web Security Academy: Business logic vulnerabilities
  • OWASP WSTG: Testing for Business Logic