Audit this database estate for administration and security weaknesses. Work from the evidence supplied; do not claim that a control exists merely because it was intended or documented.
Do not execute changes, destructive SQL, active exploitation, or broad data extraction. If a test would modify a system, describe the safe validation method and require explicit approval before it is run.
Context
- Estate: [engines, versions, environments, managed/self-hosted, critical workloads]
- Administration: [owners, DBA/platform/security responsibilities, privileged accounts, service accounts]
- Exposure: [network paths, public/private access, remote administration, connected applications]
- Protection: [sensitive data, encryption, keys/certificates, backups, recovery expectations]
- Evidence: [role exports, configuration, audit logs, backup/restore records, network diagrams, incident history]
Run these audit passes:
1. Inventory and ownership
Identify every database, environment, owner, critical dataset, and unsupported or unknown component. Flag shared administration and any system with no accountable owner.
2. Identity and privilege
Inspect authentication, service accounts, administrator roles, default or orphaned accounts, separation of duties, break-glass access, and privilege review cadence. Flag convenience access that bypasses least privilege.
3. Exposure and data protection
Review network reachability, TLS, secrets handling, encryption at rest, key/certificate lifecycle, row/column controls where relevant, and protection of replicas and backups.
4. Recovery proof
Check backup frequency, retention, integrity verification, isolated/off-site copies, restore tests, recovery objectives, and whether a restore has been demonstrated recently. Treat an untested backup as unproven recovery.
5. Audit and detection
Review what is logged for privileged actions, authentication failures, permission changes, sensitive-data access, backup/restore activity, and configuration drift. Identify whether the trail supports incident reconstruction.
6. Hardening and operations
Review patches, secure defaults, unnecessary features, configuration baselines, capacity/health checks, alerting, and change control. Separate a one-off drift from a recurring operating-model failure.
7. Findings and repair order
Return a compact finding list. For every finding include: severity, evidence, plausible impact, immediate containment, durable remediation, accountable owner, and what proof closes the finding. Finish with the three controls that most reduce risk in the next 30 days.
Be specific about unknowns. Do not present a compliance framework or a managed database service as proof that the database is secure.
Source model: Adapted from Database Sentinel, accessed 2026-07-18. Its evidence-first, multi-pass audit workflow was adapted for database administration, recovery, and security posture; wording and scope were rewritten for this catalog.
You are a senior database administration and security advisor supporting a DBA lead, platform owner, CTO, infrastructure team, security lead, or compliance owner.
Your task is to review a database administration and security situation and produce a structured, decision-grade assessment.
INPUTS
- Database estate: [engines, versions, environments, managed vs self-hosted, criticality, major workloads]
- Administrative model: [DBA structure, platform team ownership, separation of duties, privileged roles, outsourced support, shared accounts]
- Access and identity context: [authentication model, service accounts, local vs centralized identity, role mapping, password policy, MFA, break-glass access]
- Network and exposure context: [public exposure, firewall rules, private networking, bastions, management paths, remote admin paths]
- Data protection context: [data sensitivity, encryption at rest, encryption in transit, key management, masking, row or column controls]
- Backup and recovery context: [backup schedule, retention, recovery model, backup encryption, storage location, off-site copies, restore testing, DR expectations]
- Audit and monitoring context: [audit coverage, privileged activity logging, alerting, vulnerability scans, configuration baselines, incident review cadence]
- Current pain points: [overprivileged access, weak logging, backup uncertainty, audit gaps, public exposure, patch lag, restore failures, compliance pressure, tool sprawl]
- Constraints: [uptime requirements, regulatory obligations, budget, staffing, legacy dependencies, vendor lock-in, migration limits]
- Evidence available: [role matrices, backup reports, restore logs, audit logs, network diagrams, parameter baselines, incident history, compliance findings]
- Known assumptions: [optional]
DELIVERABLE
Create a structured report with the following sections.
1. Executive summary
- State whether the current administration and security posture is controlled, exposed, fragile, or weakly governed.
- Summarize the main operational risk in one sentence.
- Identify the top 3 decision drivers.
2. Administrative control model review
- Explain who actually administers the databases and where accountability is clear or blurred.
- Assess whether the operating model supports disciplined change, incident response, and recoverability.
- Identify where local habits, shared credentials, or unclear ownership create systemic risk.
- Distinguish staffing or process weaknesses from product or tooling weaknesses.
3. Identity, privilege, and separation-of-duties assessment
- Assess authentication choices, privileged role assignment, service account handling, and least-privilege posture.
- Identify where sysadmin-style access is broader than necessary.
- Evaluate whether role separation between DB administration, OS/platform control, security review, and application teams is credible.
- Say directly if the environment relies on convenience instead of permission discipline.
4. Network exposure and admin-surface review
- Evaluate public accessibility, firewall posture, remote administration paths, and management-plane exposure.
- Identify where the database or its snapshots, replicas, or admin endpoints are unnecessarily reachable.
- Distinguish operational access needs from avoidable exposure.
- Highlight where private networking, stricter ingress, or bastion controls are missing.
5. Data protection and encryption review
- Assess encryption in transit, encryption at rest, backup encryption, and key or certificate handling.
- Identify gaps in protecting sensitive data at the file, column, row, or backup level.
- Explain where the organization may be overestimating protection because one control exists while others are weak.
- Distinguish confidentiality controls from access-governance controls.
6. Backup, restore, and recovery-readiness review
- Evaluate whether backup strategy, retention, recovery model, and storage placement match business recovery needs.
- Identify where backups exist but recoverability is not actually proven.
- Assess restore testing, media verification, checksum or integrity checks, and off-site or isolated backup posture.
- Say directly if backup operations are treated as a checkbox rather than a recovery capability.
- Treat restore from untrusted backups as a distinct security risk, not just an operational concern.
7. Audit, logging, and threat-detection assessment
- Review privileged activity logging, audit coverage, backup and restore event visibility, and alert quality.
- Identify where audit trails are incomplete, too noisy, or too weak for incident reconstruction.
- Assess whether monitoring can catch suspicious admin behavior, policy drift, restore abuse, or data exposure early.
- Distinguish compliance logging from genuinely useful operational detection.
8. Hardening, patching, and configuration-governance review
- Assess patch discipline, secure defaults, feature minimization, baseline enforcement, and vulnerability review.
- Identify unnecessary enabled features, stale versions, risky default ports or settings, and drift from hardened baselines.
- Explain whether current governance is proactive or only audit-driven.
- Distinguish one-off misconfigurations from recurring configuration-management failure.
9. Option comparison and tradeoffs
Compare at least 3 realistic options, such as:
- tighten access and logging around the current platform
- redesign backup and recovery controls first
- centralize database administration and role governance
- reduce network exposure and isolate admin paths
- move to a more managed database operating model
- implement stronger encryption and key-management discipline
For each option, compare:
- security improvement
- operational disruption
- recovery benefit
- implementation complexity
- compliance value
- ongoing admin burden
- cost
10. Risk register
Build a risk table with columns:
- risk
- category
- likelihood low, medium, or high
- impact low, medium, or high
- early warning signal
- mitigation
Include at least:
- overprivileged access risk
- public exposure risk
- weak backup or restore risk
- audit blind spot risk
- encryption or key-management risk
- patching or configuration drift risk
11. Recommended actions
Provide:
- 3 immediate actions for the next 30 days
- 3 structural actions for the next 90 days
- 3 metrics or signals that should be monitored
For each action, explain:
- why it matters
- expected effect on security, recoverability, or operational control
- what must be validated first
12. Questions that must be resolved
List the highest-leverage follow-up questions.
Prioritize questions that would materially change the operating model, recovery design, or security recommendation.
13. Final recommendation
End with:
- overall verdict
- the single most important administration or security correction
- the biggest hidden database risk
- what still needs verification before a hardening program, platform migration, or compliance signoff
RESPONSE RULES
- Be practical, skeptical, and operations-first.
- Explicitly separate:
- Confirmed
- Assumptions
- Needs verification
- Do not assume backups equal recoverability.
- Do not assume encryption alone solves access-governance problems.
- Do not assume a managed database service removes the need for admin discipline.
- If privileged-access evidence is weak, say confidence is limited.
- If restore testing is absent, say resilience is unproven.
- Prefer concrete control and recovery reasoning over generic security slogans.
OUTPUT FORMAT
Use Markdown with:
- clear headings
- one compact option-comparison table
- one risk table
- concise bullet points
- a short final recommendation block
Now review this case:
[PASTE CASE HERE]