Modify Authentication Process: Pluggable Authentication Modules T1556.003

Tactics: Defense Impairment, Persistence, Credential Access

Adversaries may modify pluggable authentication modules (PAM) to access user credentials or enable otherwise unwarranted access to accounts. PAM is a modular system of configuration files, libraries, and executable files which guide authentication for many services. The most common authentication module is pam_unix.so, which retrieves, sets, and verifies account authentication information in /etc/passwd and /etc/shadow.

Authoring guide

Patterns shared across the 5 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 (14 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
host.os.type5eq 5
EventType4eq 3, in 1exec, ProcessRollup2, authenticated, creation, exec_event
event.type3eq 3start, change, creation
Image2is_not_null 1, starts_with 1./, /bin/, /boot/
process.args2wildcard 2/bin/bash, /bin/dash, /bin/lua*, https://github.com/linux-pam/linux-pam/releases/download/...
process_name2in 2, starts_with 1., curl, ssh, sshd, wget
TargetFilename1eq 1, starts_with 1/etc/pam.conf, /etc/pam.d/, /etc/security/pam_
auditd.data.grantors1is_not_null 1
event.category1eq 1authentication
event.outcome1eq 1success
file.extension1eq 1, is_null 1so
file.name1wildcard 1pam_*.so
parent_process_name1in 1ssh, sshd
process.args_count1eq 12

Top indicator values (92 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
2606
EventTypeeq
authenticated
1
EventTypeeq
creation
125
EventTypeeq
exec
1171
EventTypeeq
session_id_change
12
EventTypein
ProcessRollup2
1117
EventTypein
exec
1171
EventTypein
exec_event
1139
Imagestarts_with
./
110
Imagestarts_with
/bin/
12
Imagestarts_with
/boot/
110
Imagestarts_with
/dev/shm/
123
Imagestarts_with
/lib/
1
Imagestarts_with
/lib64/
1
Imagestarts_with
/lost+found/
13
Imagestarts_with
/media/
14
Imagestarts_with
/opt/
1
Imagestarts_with
/proc/
15
Imagestarts_with
/run/
18
Imagestarts_with
/sbin/
12
Imagestarts_with
/sys/
15
Imagestarts_with
/tmp/
125
Imagestarts_with
/usr/bin/
12
Imagestarts_with
/usr/lib/
1
Imagestarts_with
/usr/lib64/
1
Imagestarts_with
/usr/sbin/
12
Imagestarts_with
/var/backups/
13
Imagestarts_with
/var/lib/
12
Imagestarts_with
/var/log/
15
Imagestarts_with
/var/mail/
15

Exclusions (132 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.

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)

Elastic 5 rules