Security and Hardening (DBA)
Overview
Enforce data integrity and reduce security/operational risk in database changes.
When to Use
- New tables/columns/constraints/indexes
- Changes that affect sensitive data
- Migrations with potentially destructive impact
When NOT to Use
- Pure planning tasks with no database changes
Inputs
- Proposed schema/migration diff
- Data integrity requirements
- Access/sensitivity constraints
Process
- Verify integrity constraints (PK/FK/unique/check) are explicit.
- Identify sensitive data handling implications.
- Confirm migrations avoid unintended destructive behavior.
- Call out risky operations and required approvals.
Verification Checklist
- Integrity protections are explicit
- Sensitive data considerations are addressed
- Risky/destructive operations are flagged
- Migration safety is documented
Failure Modes to Avoid
- Under-constrained schema changes
- Hidden destructive behavior
- Missing risk callouts for production-impacting changes
Output Requirements
- Use
summarizefor final output. - Include security/integrity checks performed and residual risk.