Privilege Creep
A security term referring to the gradual accumulation of access permissions beyond what is actually needed by a system or user over time, typically in the absence of regular review and revocation mechanisms. In AI agent scenarios, the autonomous nature of agents can significantly accelerate this accumulation.
Timeline (last 90 days)
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.
Permission creep refers to the phenomenon in which the access permissions a user accumulates grow continuously over time and exceed what their current responsibilities actually require.
Permission creep expands the attack surface, increases the difficulty of compliance audits, and makes it hard to trace 'who should have what access.'
Privilege creep refers to the phenomenon in which a user account continuously accumulates access permissions beyond what its initial responsibilities require over long-term use, while the original permissions are rarely actively reclaimed.
Due to privilege creep, a contractor's actual access scope often exceeds the initially approved scope, so the checklist should include a step to regularly compare request forms with the actual permissions in the IAM system.
A common mistake is directly copying the permission configuration of an existing employee, which leads to privilege creep or omissions.
In a SaaS environment, permission deviations from the least privilege principle typically manifest as privilege creep, such as old roles not being reclaimed after an employee changes positions, temporary authorizations not being revoked after a project ends, or administrator roles being granted directly for convenience.
All Facts (7)
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.
50%UnverifiedPermission creep refers to the phenomenon in which the access permissions a user accumulates grow continuously over time and exceed what their current responsibilities actually require.
50%UnverifiedPermission creep expands the attack surface, increases the difficulty of compliance audits, and makes it hard to trace 'who should have what access.'
50%UnverifiedPrivilege creep refers to the phenomenon in which a user account continuously accumulates access permissions beyond what its initial responsibilities require over long-term use, while the original permissions are rarely actively reclaimed.
50%UnverifiedDue to privilege creep, a contractor's actual access scope often exceeds the initially approved scope, so the checklist should include a step to regularly compare request forms with the actual permissions in the IAM system.
50%UnverifiedA common mistake is directly copying the permission configuration of an existing employee, which leads to privilege creep or omissions.
50%UnverifiedIn a SaaS environment, permission deviations from the least privilege principle typically manifest as privilege creep, such as old roles not being reclaimed after an employee changes positions, temporary authorizations not being revoked after a project ends, or administrator roles being granted directly for convenience.
50%