Privilege escalation
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Privilege escalation is gaining more access than was granted, usually by using one permission to obtain another, such as assuming a more powerful role or editing a policy. It is why a modest-looking permission can be dangerous: the real risk is what it can be turned into.
An example, sourced
A Wiz engineering post on protecting a security baseline says the baseline commonly contains IAM roles from vendors, from your own tooling, or for different teams to gain access to the accounts. The aim is to prevent modification or deletion of these roles, and privilege escalation, where even someone with admin privileges in an account could assume the role in order to take actions that a special role is meant to perform.
Why it matters here
Escalation paths are why unused-access counts understate risk. Ask whether a tool follows role assumption and policy-edit permissions, or only lists the permissions as written. Escalation routes are also why wide boundaries around roles, and not only clean-up of single permissions, are part of a serious program. Ask which routes a tool follows.
Related pages
Sources
- https://www.wiz.io/blog/using-service-control-policies-to-protect-security-baselines, read 10 Nov 2026
Last reviewed 16 Nov 2026.