Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01List every state-changing endpoint
- 02Check CSRF tokens, Origin checks and SameSite behavior
- 03Review GET requests that change data
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Require non-idempotent methods for changes
- 02Validate a token or trusted request origin
- 03Reauthenticate for especially sensitive actions
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Attempt cross-origin form and fetch submissions
- 02Test expired and reused tokens
- 03Confirm rejected requests do not change state
Common pitfall
A shortcut to avoid
Relying on a frontend framework or SameSite cookie alone can leave alternate endpoints unprotected.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.