Webcsrfdefense

CSRF Defense

Choose defenses from the authentication style: ambient cookies create CSRF exposure; explicit authorization headers change the browser behavior and threat.

Follow the failure

Frame the problem

Security starts with a concrete asset, attacker capability and trust crossing.

Asset
User intent for state changes.
Attacker & capability
A hostile origin able to induce browser requests but unable to read protected responses.
Trust boundary
Cross-origin request → state-changing handler
Asset→Threat→Attack Surface→Trust Boundary→Vulnerability→Exploit Path→Impact→Mitigation→Defense in Depth→Residual Risk

Why the system fails

The server accepts cookie-authenticated mutations without a same-site signal, token, or origin decision.

The important question is not “what is CSRF Defense?” but “which assumption let untrusted data or an over-scoped identity cross cross-origin request → state-changing handler?” Trace the decision at the boundary, then constrain what can happen after the first control fails.

Design the control in layers

Start with the control closest to the interpretation or privilege boundary: Layer SameSite, CSRF tokens and Origin checks Then add a control that reduces blast radius and telemetry that proves the decision was enforced.

The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.

PreventDetectRecover
Layer SameSite, CSRF tokens and Origin checks · Require re-authentication for critical changesReject and count missing or invalid CSRF tokensContain the affected identity or component, scope impact from audit evidence, and preserve a regression test.

Key points

  • Asset: User intent for state changes.
  • Boundary: Cross-origin request → state-changing handler
  • Primary control: Layer SameSite, CSRF tokens and Origin checks
  • Detection signal: Reject and count missing or invalid CSRF tokens
  • Always ask what limits damage when the primary control fails.

Follow the attack

Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.

  1. 1
    Attacker starts with: A hostile origin able to induce browser requests but unable to read protected responses.
  2. 2
    The server accepts cookie-authenticated mutations without a same-site signal, token, or origin decision.
  3. 3
    The weak or missing boundary control is crossed: Cross-origin request → state-changing handler
  4. 4
    Impact: Authenticated state changes without the user’s informed action.
Blast radius
  • Authenticated state changes without the user’s informed action.

Defend, detect, recover

One prevention is a single point of security failure. Layer it and make failure observable.

Prevent
  • • Layer SameSite, CSRF tokens and Origin checks
  • • Require re-authentication for critical changes
Detect
  • • Reject and count missing or invalid CSRF tokens
Respond & recover
  • • Contain the affected identity or component.
  • • Scope access from audit evidence.
  • • Fix the boundary and add a regression test.
Residual risk
  • • Misconfiguration and new access paths can bypass the intended control.
  • • A privileged insider or compromised control plane may still reach the asset.

Misconceptions

Claim
“A single layer samesite, csrf tokens and origin checks control makes this safe.”
Reality
One control changes risk; it does not erase it. Design prevention, detection, recovery, and blast-radius limits together.
← Cross-Site Request Forgery (CSRF)CORS Without the Myths →