CSRF is dead (or is it?)

Many developers have never heard of SameSite cookies before, or how they can protect their apps from CSRF attacks. In this session we will learn about the three different options: “None”, “Lax”, and “Strict” and discuss the benefits of each value.

“CSRF is dead (or is it?)” looks at SameSite cookies and whether they mean the end of CSRF (Cross Site Request Forgery) attacks or not. We discuss the different options and when you should use them, plus why Lax is the sane default.

Presented At

Browser Tests

The browser tests discussed in the talk can be found at https://samesitetest.com/.

Manual SameSite Cookie Test
Manually test the behaviour of SameSite cookies in your browser across the different cross-site request types: GETPOST, and embedded content.

Automatic SameSite Browser Test
Automated test suite that audits the behaviour of your browser with the different SameSite options, across https and http, same-site and cross-site requests. Note, it will take a while as there is a delay of 2 minutes to properly account for SameSite=Lax+POST in Chrome.

The source code for the browser tests is on GitHub at valorin/samesite. If you have any ideas or suggestions, please feel free to submit an issue or PR.

About Cross Site Request Forgery (CSRF)

About SameSite Cookies

Leave a Reply

Your email address will not be published. Required fields are marked *