Overview
Privilege escalation is gaining higher access than intended, and it revolves around privilege boundaries — the lines between levels of access. Understanding these boundaries is the foundation. This lesson covers privilege boundaries.
Learning objectives
- Define privilege boundaries and levels.
- Explain what privilege escalation means relative to them.
- Distinguish vertical from horizontal escalation.
Core concept
Privilege boundaries are the lines separating different levels of access in a system — for example, an unprivileged user versus an administrator/root, or one user's data versus another's. Privilege escalation is crossing such a boundary to gain access you should not have:
- Vertical escalation — gaining a higher privilege level (e.g. user → admin/root).
- Horizontal escalation — accessing another entity's resources at the same level (e.g. one user → another user's data).
Understanding where the boundaries are — and what should enforce them — is prerequisite to both attacking (in authorized testing) and defending them.
How it works
Systems define privilege levels and enforce boundaries through controls (permissions, roles, access checks). Privilege escalation occurs when a weakness lets someone cross a boundary the controls were supposed to enforce — a misconfiguration, a flaw, or a missing check. Vertical escalation raises the attacker's level (the most impactful, e.g. to admin/root); horizontal escalation reaches a peer's resources. Mapping the boundaries in a system — who is supposed to have what access, and what enforces it — reveals where escalation could occur and where defenses must be verified. This framing applies across operating systems, applications, and networks.
Practical example
In a system, a normal user should not reach administrator functions (a vertical boundary) and should not access other users' private data (a horizontal boundary). Privilege escalation would be, for example, a normal user finding a weakness that grants admin capabilities (vertical) or lets them read another user's records (horizontal). Identifying these boundaries first — normal user vs admin, and user-vs-user data — tells a tester (in an authorized lab) exactly which crossings to test and a defender which to protect.
Cybersecurity relevance
Privilege escalation is a critical stage in many attacks: after an initial foothold, attackers seek to escalate (especially vertically, to admin/root) to expand control. Understanding privilege boundaries is thus central to both offense (identifying escalation paths in authorized tests) and defense (enforcing and monitoring boundaries). It connects to the least-privilege and access-control concepts from earlier paths. The subtypes (vertical/horizontal) mirror the authorization module's privilege-escalation lesson, applied broadly. Knowing the boundaries is the first step to finding and closing escalation paths.
Common mistakes
- Confusing vertical and horizontal escalation — one raises level, the other reaches a peer.
- Not mapping privilege boundaries, missing where escalation could occur.
- Assuming boundaries are enforced without verifying the controls behind them.
Key takeaways
- Privilege boundaries separate access levels (e.g. user vs admin/root, or one user's data vs another's).
- Privilege escalation crosses a boundary illegitimately: vertical (higher level) or horizontal (peer's resources).
- Mapping boundaries and their enforcing controls reveals escalation paths to test or defend; escalation is a critical post-foothold stage in attacks.
Check your understanding
- What is the difference between vertical and horizontal privilege escalation?
- Why is mapping a system's privilege boundaries a prerequisite to finding escalation paths?