#oauth2.0#xss#backend-for-frontend
230K subscribers • 110 videos on Hallway • Conference channel
Intermediate. Assumes working knowledge.
20K views3 years ago2 recommendations
SecurityWeb developmentWeb and application securityCryptographyHTTP, REST and GraphQL
Philippe de Ryck explains the security risks of storing OAuth tokens in browser-based frontends and advocates for the Backend-for-Frontend pattern.
Everyone agrees that Cross-Site Scripting (XSS) is a real threat to browser-based applications, but many underestimate the true power of XSS. In fact, various OAuth 2.0 security mechanisms for frontends, such as refresh token rotation or token isolation in workers, fail to look beyond script kiddie XSS attacks. In this talk, we take an in-depth look at the consequences of XSS in frontend OAuth 2.0 clients. We explore real-world attacker capabilities and map them against a concrete threat model. We also explore how structural solutions like the Backend-for-Frontend pattern effectively increase the security of frontend applications. By the end of this session, you will have the necessary knowledge to assess the security of your frontends and choose the appropriate defense strategy. Check out our new channel: NDC Clips: @ndcclips Check out more of our featured speakers and talks at ndcconferences.com/ ndc-security.com/What people say. Recommended as an excellent explanation of why storing JWTs in single-page applications is insecure and how BFF solves it.
u/Shaddarin r/dotnet • Recommends
On “Are Cookies getting ditched in favor of JWT?”
u/Meradin r/dotnet • Recommends
On “how do you handle auth between an API and an SPA?”
u/Shaddarin r/dotnet • Recommends
On “How Can I Deal With Refresh Tokens In Blazor Webassembly?”
u/tragicsharkin r/dotnet • Mentions
On “Why does it seem that most .NET roles require web development skills (HTML/CSS/JS)?”