SQL Injection and Parameterization
SQL injection is a boundary failure: user data is concatenated into query syntax and the database interprets it as instructions.
Frame the problem
Security starts with a concrete asset, attacker capability and trust crossing.
Why the system fails
The application builds SQL by string concatenation, allowing one value to alter the grammar of the query.
The important question is not “what is SQL Injection and Parameterization?” but “which assumption let untrusted data or an over-scoped identity cross application data → sql parser?” 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 parameterized queries and bound values 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 parameterized queries and bound values · Avoid unnecessary dynamic SQL · Run with a restricted database role | Query syntax errors and abnormal result volumes · Database audit events outside the service baseline | Contain the affected identity or component, scope impact from audit evidence, and preserve a regression test. |
Key points
- Asset: Database confidentiality and integrity.
- Boundary: Application data → SQL parser
- Primary control: Use parameterized queries and bound values
- Detection signal: Query syntax errors and abnormal 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 caller who controls a field used to construct a query.
- 2The application builds SQL by string concatenation, allowing one value to alter the grammar of the query.
- 3The weak or missing boundary control is crossed: Application data → SQL parser
- 4Impact: Reads or writes available to the application database role.
- Reads or writes available to the application database role.
Defend, detect, recover
One prevention is a single point of security failure. Layer it and make failure observable.
- • Use parameterized queries and bound values
- • Avoid unnecessary dynamic SQL
- • Run with a restricted database role
- • Query syntax errors and abnormal result volumes
- • Database audit events outside the service baseline
- • 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.