Join our Newsletter — 33% off our NHI Course
Home› Glossary› Architecture & Implementation› Centralised Database
Architecture & Implementation

Centralised Database

← Back to Glossary
By NHI Mgmt Group Updated October 30, 2026 Domain: Architecture & Implementation

A centralised database is a shared back-end store that many users or workflows depend on for access, recovery, or transaction processing. In crypto and identity contexts, it becomes a concentrated trust point. If compromised, it can expose data, alter records, or enable direct theft across an entire platform.

What a centralised database means in security terms

A centralised database is not just a convenient shared store, it is a concentration of trust, state, and operational dependency. When many workflows depend on one back end, the database becomes a high-value target and a single failure domain. That makes integrity, availability, and access control inseparable from the design.

Why centralisation changes the threat model

The main difference from distributed storage is the blast radius. A compromise can affect many applications at once, so attackers who gain access to the database often do not need to pivot far to steal records, alter business-critical state, or extract secrets stored alongside data. In practice, the risk is often amplified by weak segmentation, overbroad service permissions, and unsafe administrative access paths.

Because central databases frequently hold authentication data, tokens, configuration records, or recovery material, a breach can become both a data incident and an access incident. The security question is therefore not only whether the database is encrypted, but who can reach it, what can be changed there, and how quickly abnormal access would be detected.

Where exposure usually comes from

Exposure often begins with inventory gaps, internet-facing management interfaces, misconfiguration, or overly permissive application accounts. A central store is also attractive when backups, replicas, or migration copies are treated as lower risk than production, even though they may contain the same sensitive content.

Centralisation can hide fragile dependencies. If multiple services assume one database will always be available, then an outage, lock contention event, or destructive change can cascade across sign-in, transaction processing, reporting, and recovery workflows. The design becomes especially fragile when teams rely on implicit trust instead of explicit segmentation and ownership boundaries.

For a practical view of how database hardening is handled in the field, the CIS Benchmarks are a useful reference point for secure configuration expectations.

Control priorities for a central trust point

A centralised database needs stronger controls than a peripheral data store because it sits inside the core trust boundary. Access should be tightly scoped, administrative paths should be separate from application paths, and changes should be auditable because record integrity matters as much as confidentiality.

Operationally, teams should assume the database will be probed, misused, and occasionally stressed by failure. That means monitoring for anomalous queries, privilege drift, destructive actions, and backup or restore anomalies. It also means treating schema changes, replication settings, and recovery procedures as security-relevant controls rather than purely operational tasks.

When the platform itself is the subject of review, authoritative control guidance such as the NIST SP 800-53 Rev 5 Security and Privacy Controls is a strong fit for access control, auditability, configuration management, and system integrity.

Risk and Threat Considerations

A centralised database concentrates both trust and failure. If an attacker reaches it, the same compromise can expose data, corrupt records, or abuse the store as a launch point for wider platform theft. Even without a direct intrusion, a misconfiguration or destructive administrative action can create platform-wide loss because so many services depend on the same back end.

Failure mechanism: Weak authentication, overprivileged service access, exposed management surfaces, or insecure replication and backup handling can turn one database into a mass-exposure event. Compromise of the central store can also enable silent record tampering, which is often harder to detect than simple data theft.

Impact: Organisations can lose confidentiality, integrity, and availability at the same time. Recovery may require validating data correctness, rotating dependent credentials or secrets, and checking downstream systems that consumed poisoned or altered records.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-5 — Account ManagementCentral databases depend on tightly governed access and privileged accounts.
Recommendation — Restrict database access to named roles and remove unnecessary accounts and permissions.
NIST SP 800-53 Rev 5AC-6 — Least PrivilegeCentralised stores become high-impact if users or services hold excess permissions.
AU-6 — Audit Record Review, Analysis, and ReportingA shared database needs strong review of access and change activity.
CM-2 — Baseline ConfigurationMisconfiguration is a common failure mode for centralised database exposure.
Recommendation — Enforce least privilege for database users, services, and administrators. Review database logs for anomalous access, destructive changes, and privilege abuse. Maintain a hardened configuration baseline for the database platform and replicas.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org