Skip to main content

What is privilege escalation?

Privilege escalation is how an attacker gains higher permissions than they started with, such as admin or root, by exploiting flaws, misconfigurations, or credentials.

Glossary
Updated 2 min read

Definition

Privilege escalation

Also called Privesc, Elevation of privilege, TA0004

Privilege escalation is the set of techniques attackers use to gain higher-level permissions on a system or network than they initially had, such as moving from a standard user to administrator, root, or a privileged cloud role.

How it works

MITRE ATT&CK describes privilege escalation (tactic TA0004) as techniques adversaries use to gain higher-level permissions on a system or network. Attackers can often get in and explore with unprivileged access but need elevated permissions to finish the job. Common approaches take advantage of system weaknesses, misconfigurations, and vulnerabilities, and many overlap with persistence, since features that let an attacker persist can also run in an elevated context.

Three routes cover most cases. Exploitation (T1068) abuses a software bug, usually in an operating system component or a service running with high permissions, to go from user level to SYSTEM or root, or to escape a virtual machine or container onto the host. Abuse of elevation controls (T1548) targets mechanisms like sudo, setuid binaries, or Windows UAC. Valid accounts (T1078) skips exploitation entirely: stolen or misused credentials for a more privileged account, and overlapping permissions across local, domain, and cloud accounts, can let an attacker pivot up to domain or enterprise administrator.

In the cloud, escalation usually means identity: a role that can attach a more powerful policy to itself, create access keys for another user, or pass a privileged role to a compute resource.

Example

An attacker gains a shell as a web service account on a Linux server. Enumerating the system, they find a scheduled job that runs as root and executes a script the web account can write to. They append a command, wait for the job to run, and now have root. On the defensive side, file-integrity or EDR telemetry shows the script being changed by a non-root user shortly before a root process spawned a shell.

Why it matters for a SOC

Escalation usually comes right before the most damaging steps: disabling security tools, dumping credentials across the domain, or touching sensitive data. Detecting it early limits blast radius. Useful signals include new members of admin groups, sensitive role or policy changes in cloud audit logs, unexpected processes running as SYSTEM or root, and accounts using permissions they have never used before, which CIEM and ITDR tools focus on.

FAQ

What is the difference between vertical and horizontal privilege escalation?
Vertical escalation gains a higher level of permission, such as a standard user becoming an administrator. Horizontal escalation takes over another account at a similar level, often to reach that account's data or access. Both show up in incidents, and horizontal moves often set up vertical ones.

Sources

  1. Privilege Escalation, Tactic TA0004 - Enterprise | MITRE ATT&CK · accessed November 16, 2026
  2. Exploitation for Privilege Escalation, Technique T1068 - Enterprise | MITRE ATT&CK · accessed November 16, 2026
  3. Valid Accounts, Technique T1078 - Enterprise | MITRE ATT&CK · accessed November 16, 2026

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo