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.
- 01Inventory every Set-Cookie response
- 02Classify session, authentication and preference cookies
- 03Check Domain, Path, expiry and SameSite scope
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.
- 01Apply Secure on HTTPS-only delivery
- 02Use HttpOnly for values JavaScript does not need
- 03Choose SameSite deliberately and minimize Domain scope
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.
- 01Inspect cookies after login, logout and renewal
- 02Test intended cross-site flows in modern browsers
- 03Verify revoked sessions stop working
Common pitfall
A shortcut to avoid
Applying SameSite=Strict everywhere can break legitimate sign-in, checkout or embedded workflows.
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.