Cross-Site Request Forgery and Same-Site Cookies

Cross-Site Request Forgery tricks a logged-in user's browser into sending a request the user never intended, and the target site honours it because the browser automatically attaches the user's session cookie. The attacker never sees the response or steals the cookie; they simply borrow the victim's authenticated session to perform a state-changing action such as a transfer or a settings change.

Analogy🏏Cricket

🍳 Think of it like cooking: A recipe can look flawless on paper, but a head chef only truly judges the dish by tasting the finished plate, because heat, timing, and the actual oven reveal problems the written method never shows. Just as tasting the cooked result catches what reading the recipe cannot, DAST probes the running application and catches the misconfigurations and runtime behaviour that reading the source cannot. This reveals DAST's stance: it judges the dish as it is actually served, not the recipe as it was merely written.

The vulnerability exists because cookie-based authentication is ambient: browsers send cookies on every request to a site, regardless of which page triggered it. Understanding that ambient behaviour is the key to every CSRF defence, from anti-forgery tokens to the SameSite cookie attribute. This lesson explains the mechanism and then the layered controls that close it.

Analogy🏏Cricket

💰 Think of it like finance: A real audit that actually attempts a sample transaction proves beyond doubt whether a control can be bypassed, with little room for a false alarm, but it can only test the accounts and processes the auditors actually reach. Just as a hands-on audit yields high-confidence, low-false-positive results yet is bounded by what it examines, DAST yields high-confidence findings about real exploitability yet is bounded by the surface it can reach. This reveals its trade-off: what it confirms is solid, but it only confirms what it manages to touch.