Unverified50% confidenceOpinionExact time
Permission creep is usually caused by the fact that granting permissions is easy while revoking them is difficult: new projects, temporary tasks, and position changes all bring new grants, yet corresponding revocation actions are rare.
1
Sources
50%
Confidence
Long-term
Relevance
10/20/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe principle of least privilege has an often-overlooked precondition: the permissions granted must be sufficient to complete the task; when permissions are drawn too narrowly, the subject cannot perform its duties, and in practice people look for workarounds, which instead creates more covert and harder-to-audit temporary channels.67% similarUnverifiedThe difficulty of workforce identity management lies not in technical deployment but in the supporting organizational processes; even if the system supports automatic permission revocation, if HR's offboarding process does not trigger data changes in time, permissions will still remain.66% similarUnverifiedHaving the on-call engineer who made the emergency change complete the PR best preserves the original intent of the change, but may disrupt their rest schedule and is not conducive to a sustainable on-call culture.65% similarUnverifiedIn AI agent scenarios, the correct engineering response to the principle of least privilege is to request permissions on demand at runtime and reclaim them after use, rather than granting all permissions across the board.65% similarUnverifiedThe inherent conflict between flexible prompt ownership and rigorous version promotion discipline is an open problem yet to be resolved in the current field of prompt engineering.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1077557API
curl https://kongchang.com/api/v1/knowledge/claims/1077557MCP
get_claim(id=1077557)