Cross-Site Scripting (XSS)
XSS exists when attacker-controlled data crosses into an HTML, attribute, URL or JavaScript context and the browser interprets it as behavior.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
Untrusted input is stored or reflected and inserted into a document with an API or template that treats it as markup or script.
The important question is not “what is Cross-Site Scripting (XSS)?” but “which assumption let untrusted data or an over-scoped identity cross untrusted data → browser execution context?” Trace the decision at the boundary, then constrain what can happen after the first control fails.
Design the control in layers
Start with the control closest to the interpretation or privilege boundary: Use context-aware output encoding and safe templating Then add a control that reduces blast radius and telemetry that proves the decision was enforced.
The resulting design is not labelled secure. Record the identified controls, the known failure paths, the remaining exposure, and the evidence you would need during an incident.
| Prevent | Detect | Recover |
|---|---|---|
| Use context-aware output encoding and safe templating · Avoid dangerous DOM sinks · Apply a restrictive Content Security Policy as depth | CSP violation reports · Unexpected script sources or DOM mutations | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: The origin authority of the application in each user browser.
- Boundary: Untrusted data → browser execution context
- Primary control: Use context-aware output encoding and safe templating
- Detection signal: CSP violation reports
- Always ask what limits damage when the primary control fails.
XSS Context Visualizer
Change the system and observe which assumption moves.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: A user who can supply content that another user will render.
- 2Untrusted input is stored or reflected and inserted into a document with an API or template that treats it as markup or script.
- 3The weak or missing boundary control is crossed: Untrusted data → browser execution context
- 4Impact: Actions as the victim, page modification, sensitive DOM reads and abuse of any browser-accessible capability.
- Actions as the victim, page modification, sensitive DOM reads and abuse of any browser-accessible capability.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Use context-aware output encoding and safe templating
- • Avoid dangerous DOM sinks
- • Apply a restrictive Content Security Policy as depth
- • CSP violation reports
- • Unexpected script sources or DOM mutations
- • Contain the affected identity or component.
- • Scope access from audit evidence.
- • Fix the boundary and add a regression test.
- • Misconfiguration and new access paths can bypass the intended control.
- • A privileged insider or compromised control plane may still reach the asset.