Not by malice. By accident.
Dangerous actions happen fast. A deploy to the wrong branch. A database drop without a where clause. A privilege left active for ten minutes too long. These aren't hypotheticals. They are in the incident reports you never want to publish.
The problem is not just who has access. The problem is how long they keep it. Permanent standing privileges are an open door in a locked building. They invite mistakes and make them harder to trace. Traditional role-based models grant power 24/7, even when that power is only needed for a single task. That is where Zero Standing Privilege (ZSP) changes the game.
Zero Standing Privilege removes ongoing access. No engineer, admin, or operator holds dangerous rights by default. Access is granted just-in-time, for the shortest useful duration, with full audit. When the work is done, privileges vanish. This cuts the blast radius of any dangerous action to minutes instead of months.
ZSP is not theory. It is a control layer that eliminates the silent risk of dormant power. Combined with strict action approvals, it stops the most damaging errors before they start. Dangerous Action Prevention with ZSP means a developer cannot accidentally trigger a system-wide outage. It means a misclick stays local instead of rippling through production. It means you sleep without waiting for the pager.