Micro Frontends and Security
summary
Explains when micro frontends actually break security and gives concrete fixes: avoid leaking powerful session cookies over bearer tokens by using browser cookies plus a gateway that exchanges them for backend tokens; protect injected assets with subresource integrity (sha384) served from a discovery feed; sandbox server-side modules with Node.js VM sandbox and custom require/timeouts; enforce and report violations with CSP report-only and correct CORS headers; notes Webpack Module Federation needs a discovery + integrity step to be safe.
AI-written summary · about
chapters (15)
- 0:00Micro frontends security intro
- 1:30Speaker intro
- 3:39Why micro frontends need security
- 7:29Distributed code risks
- 9:19OWASP threats for micro frontends
- 11:48Authentication flaws
- 19:22Session cookies mitigation
- 21:52Code integrity checks
- 26:08Injection challenges
- 27:51Server composition risks
- 29:15Sandboxing with Node.js VM
- 32:46CSP for micro frontends
- 36:16CORS and security headers
- 38:01Q&A: Security mistakes
- 41:12Q&A: Social engineering risks
related talks
32mSecurity-First Web Apps
27mMicro-frontends: anti-patterns
52mMicro frontends: prepare for the ride
48mMicrofrontend Architecture – technical implementation.
24mScaling Frontend Development using Micro-frontends
28mHow to Protect Java Microservices and React.js Micro frontends
19mCritical Security Mistakes in Frontend Applications
58mPractical Secure Development and Operations with JavaScript in 2020
