Web Security: Browser to Database
Map browser execution, origins, cookies, API decisions and database interpretation onto one end-to-end path.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
The design treats the browser as trusted, confuses an origin policy with authentication, or lets data change meaning at a downstream interpreter.
The important question is not “what is Web Security: Browser to Database?” but “which assumption let untrusted data or an over-scoped identity cross browser → web application → api → database?” 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: Classify every input and output context 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 |
|---|---|---|
| Classify every input and output context · Authenticate and authorize on the server · Use narrow browser and database privileges | Log denied boundary decisions · Monitor unusual browser and API action sequences | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: User identity, browser state, application data and the integrity of actions.
- Boundary: Browser → web application → API → database
- Primary control: Classify every input and output context
- Detection signal: Log denied boundary decisions
- Always ask what limits damage when the primary control fails.
Boundary control exercise
This lesson uses the shared boundary-control exercise.
Follow the attack
Safe conceptual simulation: capability → missing control → crossed boundary → asset impact.
- 1Attacker starts with: A remote visitor who controls requests, links, form fields and content rendered for other users.
- 2The design treats the browser as trusted, confuses an origin policy with authentication, or lets data change meaning at a downstream interpreter.
- 3The weak or missing boundary control is crossed: Browser → web application → API → database
- 4Impact: Account actions, data disclosure or server-side compromise depending on which boundary is crossed.
- Account actions, data disclosure or server-side compromise depending on which boundary is crossed.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Classify every input and output context
- • Authenticate and authorize on the server
- • Use narrow browser and database privileges
- • Log denied boundary decisions
- • Monitor unusual browser and API action sequences
- • 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.