Database Security Properties
Database security is authentication, network reachability, least privilege, encryption, audit, tenant enforcement and secure copies—not one checkbox.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
A broadly reachable database accepts a shared high-privilege identity and records too little evidence to scope misuse.
The important question is not “what is Database Security Properties?” but “which assumption let untrusted data or an over-scoped identity cross application or operator identity → database capability?” 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 per-service restricted database roles 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 per-service restricted database roles · Restrict network paths and enforce tenant access · Encrypt transport and protected storage | Database audit events and unusual tables, verbs or result volumes | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: Primary data and every replica, export, log and backup containing it.
- Boundary: Application or operator identity → database capability
- Primary control: Use per-service restricted database roles
- Detection signal: Database audit events and unusual tables, verbs or result volumes
- 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 compromised application, stolen database credential or over-privileged operator.
- 2A broadly reachable database accepts a shared high-privilege identity and records too little evidence to scope misuse.
- 3The weak or missing boundary control is crossed: Application or operator identity → database capability
- 4Impact: Bulk confidentiality and integrity loss across all data the role can reach.
- Bulk confidentiality and integrity loss across all data the role can reach.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Use per-service restricted database roles
- • Restrict network paths and enforce tenant access
- • Encrypt transport and protected storage
- • Database audit events and unusual tables, verbs or result volumes
- • 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.