Database Privileges and Blast Radius
An application connected as superuser turns every injection or process compromise into total database compromise.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
Convenience wins during setup and the production service retains schema, cross-table or administrative privileges.
The important question is not “what is Database Privileges and Blast Radius?” but “which assumption let untrusted data or an over-scoped identity cross application service identity → database authorization?” 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: Create one restricted role per workload 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 |
|---|---|---|
| Create one restricted role per workload · Separate migrations from runtime identities · Deny public database exposure | Alert on denied privilege attempts and administrative verbs by runtime roles | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: Tables, schemas, backups and administrative functions the application does not need.
- Boundary: Application service identity → database authorization
- Primary control: Create one restricted role per workload
- Detection signal: Alert on denied privilege attempts and administrative verbs by runtime roles
- 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 caller who exploits an application bug or steals its database credential.
- 2Convenience wins during setup and the production service retains schema, cross-table or administrative privileges.
- 3The weak or missing boundary control is crossed: Application service identity → database authorization
- 4Impact: The full database instead of the service’s narrow data slice.
- The full database instead of the service’s narrow data slice.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Create one restricted role per workload
- • Separate migrations from runtime identities
- • Deny public database exposure
- • Alert on denied privilege attempts and administrative verbs by runtime roles
- • 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.