Topic starter
07/06/2026 8:02 pm
TL;DR: Database environments now span more than 400 SQL and NoSQL systems, and 57% of organisations say databases are among the hardest technologies to manage for access, according to StrongDM. Manual provisioning, default admin access, and forgotten decommissioning turn database access into an NHI governance problem, not just an operations problem.
Editorial analysis by NHI Mgmt Group, based on content published by StrongDM: “Are Your Databases a Pain in the Access?”.
By the numbers:
- Today there are more than 400 SQL and NoSQL databases alone.
Key questions
Q: What breaks when database access is still provisioned manually at scale?
A: Manual provisioning breaks when every request must be approved and applied database by database.
Q: Why do default database admin rights increase governance risk?
A: Default administrator rights increase risk because they collapse role design into blanket privilege.
Q: How do you know if database access controls are actually working?
A: They are working when access can be granted and removed quickly, role scope stays narrow, and audit logs show a clean match between approval, usage, and removal.
Practitioner guidance
- Implement database access lifecycle controls Map request, approval, provisioning, and decommissioning into a single lifecycle workflow so access removal is not left to memory or manual follow-up.
- Replace default administrator access Create task-based database roles that separate routine access from elevated administration so users receive only the authority they need for the work at hand.
- Automate deprovisioning for leavers and project exits Trigger access removal from role change and offboarding events so database entitlements do not persist after the business need ends.
Bottom line: Database sprawl turns access management into a lifecycle governance problem because manual grant and removal processes do not scale cleanly.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
07/06/2026 9:48 pm
Database access sprawl is an NHI governance problem, not an admin inconvenience. Once database estates grow into the hundreds, access lifecycle decisions stop being isolated requests and become a control plane problem. The article shows that manual provisioning and decommissioning cannot keep pace with scale, which means governance has to move from ticket handling to entitlement orchestration. Practitioners should treat database access as a governed non-human identity surface, not a queue of one-off exceptions.
A question worth separating out:
Q: Should database access be treated differently from general IAM governance?
A: Yes. Database access has its own lifecycle pressure because access often spans many systems, versions, and elevated roles, so ad hoc handling breaks down quickly. The governing principle is the same as IAM, but the operational risk is sharper: unmanaged database entitlements can persist quietly and create broad exposure without obvious user friction.
👉 Read our full editorial: Database access sprawl is exposing NHI governance gaps
This post was modified 4 days ago by NHI Mgmt Group