The database didn’t fail because of bad code. It failed because a bot had more access than any person on the team.
NIST 800-53 calls them Non-Human Identities. They are service accounts, machine users, workloads, scripts, and integrations. They do not log in like humans. They do not take vacations. They run 24/7, touching systems, pulling data, and making changes. When their permissions are wrong, the blast radius is massive.
The NIST 800-53 framework is clear about how to handle them. Identify every non-human identity. Map its privileges. Enforce least privilege. Monitor activity in real time. Revoke unused access. Rotate credentials before they expire—or before they’re stolen. Log everything. Review the logs without fail.
Non-human identity management is now as critical as human identity management. Many breaches come not from brute force but from stolen machine credentials left in code repos, forgotten cron jobs, or old OAuth tokens. Attackers know these accounts often bypass multi-factor rules. NIST 800-53’s Access Control (AC) and Identification and Authentication (IA) families outline controls that stop this path cold if actually enforced.