Join our Newsletter — 33% off our NHI Course
Home› Glossary› Foundations & NHI Taxonomy› Credentials.db
Foundations & NHI Taxonomy

Credentials.db

← Back to Glossary
By NHI Mgmt Group Updated November 18, 2026 Domain: Foundations & NHI Taxonomy

Credentials.db is a local database file used by some software to store saved authentication material. It typically contains usernames, passwords, tokens, or other secrets in a form that applications can read for automatic sign-in or account reuse.

What Credentials.db Is Used For

Credentials.db is typically a local application store for reusable authentication material. The important point is not the file name itself, but that software may rely on it to recover usernames, passwords, session tokens, or similar secrets without prompting the user every time.

That makes the file part of the application’s trust boundary. If an attacker, another local user, or a compromised process can read it, they may inherit the same access the application intended to preserve for convenience.

Why Stored Authentication Material Becomes Sensitive

A file like Credentials.db matters because it can convert a single successful compromise into repeated access. Saved passwords, bearer tokens, API keys, and refresh-like material can be reused to sign in, impersonate the user, or reach connected services long after the original login event.

In practical terms, the risk increases when the database is stored in a predictable location, protected only by file permissions, or protected by the operating system but then copied by malware running as the user. The file is valuable precisely because it lowers friction for legitimate access, which also lowers friction for abuse.

How Exposure Usually Happens

Exposure often comes from endpoint compromise, local privilege abuse, poor file permissions, backup leakage, or application design that stores secrets without strong encryption and key protection. Once the file is reachable, the contents can reveal not just one account, but a path into multiple applications or cloud services.

For that reason, treat a credential store as a high-value secret container rather than a harmless cache. NHIMG’s Ultimate Guide to NHIs — Static vs Dynamic Secrets is useful background on why long-lived secrets and reusable credentials create durable exposure, and the OWASP Non-Human Identity Top 10 frames the same storage-and-reuse problem from a broader secrets and credential risk perspective.

What Good Handling Looks Like

The safer pattern is to minimise what is written to disk, prefer short-lived or narrowly scoped credentials where possible, and avoid making local files the primary source of reusable trust. When software must persist secrets, it should use strong local protection, clear ownership, and a lifecycle that includes rotation and revocation.

Practitioners should also think about what happens when the file is copied, backed up, synchronised, or migrated. A credential database that is secure on the endpoint can still become risky if it is moved into logs, crash dumps, support bundles, or ungoverned storage.

For implementation guidance on lifecycle and storage choices, Secrets Management Guide explains why centralisation, rotation, and secretless patterns reduce dependence on durable local secret stores, while API Key Management Guide is relevant where the stored material includes reusable API credentials.

Risk and Threat Considerations

Credentials.db is risky because a single file can expose multiple authenticators at once, turning local access into account reuse across systems. If malware, an insider, or a local compromise retrieves the file, the attacker may be able to bypass normal login flows and persist through the reused secrets.

Failure mechanism: The file is read, copied, or decrypted by an unauthorised process, and the embedded secrets are then replayed against the original service or adjacent services that trust them.

Impact: Account takeover, session abuse, API access, and lateral movement become possible, and the organisation may need to rotate credentials, invalidate sessions, and review connected services for follow-on compromise.

Standards & Framework Alignment

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

NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementCredentials.db stores authenticators and reusable secrets that need lifecycle control.
IA-9 — Identification and Authentication (Non-Organizational Users)The file may contain credentials used to authenticate to external services and accounts.
AC-6 — Least PrivilegeThe file should only be readable by the minimum processes and users that require it.
Recommendation — Rotate, revoke, and protect stored authenticators under IA-5. Use strong authentication controls for any external-facing credentials stored or derived from the file. Restrict file access to the minimum set of processes and accounts that truly need it.
ISO/IEC 27001:2022A.8.24 — Use of CryptographyStored authentication material in a local database should be protected with appropriate cryptographic controls.
Recommendation — Protect persisted secrets with approved cryptographic safeguards and controlled key handling.
CIS Controls v8CIS-5 — Account ManagementSaved credentials directly affect account lifecycle, access persistence, and revocation.
Recommendation — Inventory, revoke, and regularly review accounts and credentials that can be recovered from the store.

Practitioner Guidance

Why practitioners should care: A local credential database is not just a storage detail, it is an access-control decision with direct blast-radius implications. If the software depends on it, then endpoint hardening, secret lifecycle, and local file protection all become part of the control design.

Practitioner note: Treat every persistent secret store as recoverable by an attacker who reaches the host or the user context. That assumption is often the difference between a minor endpoint event and a broader account compromise.

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 November 18, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org