Exploitation for Privilege Escalation T1068

Tactic: Privilege Escalation

Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.

Events covered

27 catalog events are tagged with this technique by at least one rule.

Authoring guide

Patterns shared across the 145 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (151 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
EventType33eq 23, in 10, contains 1, wildcard 1exec, ProcessRollup2, exec_event, uid_change, creation
event.type33eq 29, ne 3, in 1start, change, deletion, creation, process_started
host.os.type28eq 28
process_name26eq 19, in 8, is_not_null 4, starts_with 2, ne 1bash, dash, sudo, busybox, csh
CommandLine20contains 16, regex_match 3, ends_with 1, in 1, is_not_null 1, wildcard 1 --chroot , -u#, /account, /impersonate, /name
Image20ends_with 13, starts_with 4, in 3, eq 2, contains 1, is_null 1, regex_match 1*\\\\*, *\\programdata\\*, *\\temp\\*, \bitsadmin.exe, \cmd.exe
EventID18eq 184688, 1, 6, 7045, 10
process.args16eq 7, in 6, wildcard 5, starts_with 2, contains 1, ends_with 1-*f*, -R, -*U*, -*r*, --checkpoint-action=
TargetFilename13ends_with 5, wildcard 5, contains 3, eq 2, starts_with 2, in 1.sys, /etc/passwd, .rbs, /*/etc/nsswitch.conf, /*gconv_path*
user.id13ne 11, eq 8, is_not_null 1, starts_with 10, S-1-12-1-, S-1-5-21-
parent_process_name10eq 7, in 2, regex_match 2(?i):\x5cWindows\x5csystem32\x5cconsent\.exe, spoolsv.exe, bash, brave.exe, browser.exe
ParentImage9ends_with 5, in 2, eq 1, regex_match 1*\\\\*, *\\programdata\\*, *\\temp\\*, \\sharpsuccessor\.exe, \consent.exe
IntegrityLevel7eq 7, in 2System, High, Low, Medium
event.category7eq 7process, driver, file, library, network
user7eq 5, contains 1, ne 1root, 0, 501-65535, authori, autori

Top indicator values (6433 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.

FieldKindValueRules (here)Corpus reach
event.typeeq
start
26606
event.typeeq
change
777
event.typeeq
creation
345
EventTypeeq
exec
13171
EventTypeeq
uid_change
35
user.idne
0
1116
user.ideq
0
812
EventTypein
exec
7171
EventTypein
ProcessRollup2
6117
EventTypein
exec_event
6139
EventTypein
executed
688
EventTypein
start
6134
EventTypein
process_started
574
IntegrityLeveleq
System
729
event.categoryeq
process
5128
EventIDeq
4688
4313
EventIDeq
1
3237
process_namein
bash
488
process_namein
dash
478
process_namein
fish
472
process_namein
ksh
473
process_namein
zsh
482
process_namein
busybox
336
process_namein
csh
371
process_namein
sh
383
Imageends_with
\cmd.exe
3130
Imageends_with
\powershell.exe
3182
Imageends_with
\pwsh.exe
3168
event.typene
deletion
328
file.extensioneq
dll
310

Exclusions (310 distinct)

Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.

FieldKindValueRules excluding
Imagestarts_with
/tmp/newroot/
3
Imagestarts_with
c:\windows\system32\
2
Imagestarts_with
c:\windows\syswow64\
2
process_nameeq
msiexec.exe
3
process_nameeq
spoolsv.exe
3
process_nameeq
splwow64.exe
2
CommandLinecontains
.spl
2
CommandLinecontains
add portopening
2
CommandLinecontains
route add
2
CommandLinecontains
rule name
2
CommandLinecontains
start
2
NewTargetUserNameends_with
$
2
ParentImagestarts_with
/tmp/newroot/
2
SubjectUserSideq
S-1-5-18
2
process_namein
sudo
2

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Platform (all)
Domain (all)

Sigma 35 rules

Elastic 59 rules

Splunk 32 rules

Kusto 16 rules

YARA-L 1 rule

Panther 2 rules