> Markdown version of [/videos/100648-drawing-your-way-into-your-security](https://www.wearedevelopers.com/videos/100648-drawing-your-way-into-your-security). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Drawing Your Way Into Your Security Relying solely on React or Vue for security is a dangerous anti-pattern. Through live sketchnoting, learn how to defend your front-end fortress against supply chain attacks, XSS, and clickjacking. - **Speakers:** [Ramona Schwering](https://www.wearedevelopers.com/@ramona-schwering) - **Event:** HalfStack Vienna 2026 - **Published:** November 19, 2026 - **Duration:** 33:23 - **URL:** https://www.wearedevelopers.com/videos/100648-drawing-your-way-into-your-security - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/21a5f0a682fbf537e24ac185948b80de/thumbnails/thumbnail.jpg?time=1804900ms ## Summary Front-end developers often assume security is strictly a back-end concern or that modern frameworks automatically handle every vulnerability. While frameworks like Vue, React, and Angular provide a sturdy foundation through native browser APIs—such as automatic string escaping in templates and attribute bindings to prevent basic cross-site scripting (XSS)—relying solely on them is a dangerous anti-pattern. Using live sketchnoting and the analogy of defending a medieval fortress, this session explores how front-end and design engineers serve as "the last line of defense" in protecting user identities and application integrity. A fortress is easily compromised if attackers poison its water supply, which in modern web development translates to software supply chain attacks. Ranked high on both the standard and LLM OWASP Top 10 lists, dependency vulnerabilities can infiltrate projects via prototype pollution in popular packages like `vue-i18n`, typosquatting (such as mimicking `cross-env`), or regular expression denial of service (ReDoS) introduced by unvetted, AI-generated code. Even internal tools like Model Context Protocol (MCP) servers must be treated as untrusted dependencies capable of leaking tokens. Closing this "well" requires active hygiene: heeding Dependabot alerts, visualizing dependency trees with Dependency Cruiser, scanning for known CVEs with Retire.js, and pruning dead code using Knip. Beyond dependencies, developers must station guards at the castle gates to prevent Broken Access Control—the number one OWASP threat. While client-side routing checks using JWTs and route metadata help restrict admin views, true security requires pairing front-end navigation guards with fine-grained back-end authorization layers like OpenFGA. Furthermore, attackers still attempt to sneak "Trojan horses" past the gates via advanced XSS and UI redressing. Bypassing framework safeguards with raw HTML directives (`v-html` or `dangerouslySetInnerHTML`), unvalidated URLs, or LLM prompt injections requires explicit sanitization using tools like DOMPurify and `sanitize-url`. Finally, to prevent attackers from cloaking malicious actions over legitimate interfaces via clickjacking or hidden password-manager inputs, engineers must enforce strict Content Security Policy (CSP) headers—configured via hosting providers, Nuxt security modules, or Nitro route rules—to dictate exactly which allied domains can frame or load application resources. **Keywords:** front-end web security, cross-site scripting prevention, software supply chain attacks, owasp top 10 vulnerabilities, content security policy headers, broken access control, html sanitization with dompurify, prototype pollution vulnerabilities, npm typosquatting, regular expression denial of service, client-side route guards, fine-grained authorization with openfga, clickjacking and ui redressing, dependency vulnerability scanning, vue security best practices, llm prompt injection risks, mcp server token security, unused code removal with knip ## Chapters 1. **Conceptualizing web application security using a fortress analogy** (00:01) — Front-end developers often assume security is strictly a back-end concern, so framing applications as fortresses helps visualize how to protect digital identities and business logic. 1. **Preventing cross-site scripting with built-in framework escaping** (03:44) — User-provided strings can introduce cross-site scripting vulnerabilities, which modern frameworks like Vue and React mitigate by automatically escaping interpolated content and attribute bindings. 1. **Understanding supply chain attacks and package vulnerabilities** (07:36) — Attackers frequently compromise applications through third-party dependencies using techniques like prototype pollution, typosquatting, and regular expression denial of service. 1. **Securing project dependencies and leveraging OWASP resources** (13:24) — Managing vulnerabilities manually is unsustainable, so developers should use automated dependency checkers and follow OWASP rankings to stay ahead of security threats. 1. **Mitigating broken access control with authorization and route guards** (18:14) — Relying solely on client-side checks leads to broken access control, requiring teams to combine front-end route metadata guards with fine-grained back-end authorization. 1. **Sanitizing raw HTML and URLs to prevent injection attacks** (22:13) — Rendering raw HTML or dynamic links bypasses default framework protections, making it necessary to sanitize content and protocols using tools like DOMPurify and sanitize-url. 1. **Defending against clickjacking with content security policy headers** (26:41) — Attackers can trick users into unintended actions via UI redressing and hidden inputs, which can be blocked by configuring strict content security policy headers. 1. **Reviewing key front-end security practices and vulnerability reporting** (31:08) — Because framework defaults cannot catch every vulnerability, developers must actively sanitize inputs, audit dependencies, and report discovered security flaws to maintainers. ## Related Moments - [Evaluating framework architectures against cross-site scripting attack vectors](https://www.wearedevelopers.com/videos/361-securing-frontend-applications-with-trusted-types) (from "Securing Frontend Applications with Trusted Types") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/5f0065b19deb52797f722ea9b45f6b00/thumbnails/thumbnail.jpg?time=229355ms - [Handling modern injection flaws and cross-site scripting](https://www.wearedevelopers.com/videos/100072-bulletproof-web-applications-the-2025-owasp-top-ten) (from "Bulletproof Web Applications: The 2025 OWASP Top Ten") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/54978e2ef06cf9b6a7aa19ba30344dea/thumbnails/thumbnail.jpg?time=11910ms - [Uncovering hidden vulnerabilities and bloat in web ecosystems](https://www.wearedevelopers.com/videos/2166-wearedevelopers-live-is-css-catching-up-to-flash) (from "WeAreDevelopers LIVE - Is CSS Catching Up to Flash?") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/fed3981e541dac022f599b412606c66a/thumbnails/thumbnail.jpg?time=30000ms - [Securing frontend applications against untrusted user inputs](https://www.wearedevelopers.com/videos/100115-dangerous-reactivity-why-ai-output-is-the-new-xss) (from "Dangerous Reactivity: Why AI Output Is the New XSS") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/851b8b46bb54af39a7a9ab941616e15b/thumbnails/thumbnail.jpg?time=123590ms - [Navigating web element APIs and emerging software vulnerabilities](https://www.wearedevelopers.com/videos/1362-wearedevelopers-live-our-world-congress-2025-code100-highlights-with-jack-barber-and-marco-podien) (from "WeAreDevelopers LIVE - Our World Congress 2025 & CODE100 Highlights with Jack Barber and Marco Podien") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/4e0df3eefd2971b21ee5f66258732abb/thumbnails/thumbnail.jpg?time=141105ms - [Overview of five common software security pitfalls](https://www.wearedevelopers.com/videos/414-101-typical-security-pitfalls) (from "101 Typical Security Pitfalls") - **Thumbnail URL:** https://customer-goifxnzhrq3d0d54.cloudflarestream.com/9adae9dd5426eab893af9b7422185b4e/thumbnails/thumbnail.jpg?time=93500ms ## Related Articles - [Understanding and Mitigating Common Web Vulnerabilities](https://www.wearedevelopers.com/magazine/565-understanding-and-mitigating-common-web-vulnerabilities) - [Walking Into The Era of Supply Chain Risks](https://www.wearedevelopers.com/magazine/106-walking-into-the-era-of-supply-chain-risks) - [Dev Digest 138 - Are you secure about this?](https://www.wearedevelopers.com/magazine/486-dev-digest-138-are-you-secure-about-this) - [Security Basics for Vibe Coders](https://www.wearedevelopers.com/magazine/598-security-basics-for-vibe-coders) ## Related Jobs - [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/3929243-staff-developer-advocate-github-security-lab) at **GitHub** - [Product Security Incident Response Analyst](https://www.wearedevelopers.com/jobs/ext/4158569-product-security-incident-response-analyst) at **GitHub** - [Senior Product Security Architect](https://www.wearedevelopers.com/jobs/48532-senior-product-security-architect) at **Expedia** - [Principal Cybersecurity Engineer](https://www.wearedevelopers.com/jobs/48534-principal-cybersecurity-engineer) at **Expedia** - [Cyber Defense Specialist](https://www.wearedevelopers.com/jobs/ext/3976960-cyber-defense-specialist) at **Raiffeisen Bank International AG** - [Cyber Defense & Incident Response](https://www.wearedevelopers.com/jobs/ext/4725342-cyber-defense-incident-response) at **Delivery Hero SE**