ATT&CK coverage › Technique

Permission Groups Discovery T1069

Adversaries may attempt to discover group and permission settings. This information can help adversaries determine which user accounts and groups are available, the membership of users in particular groups, and which users and groups have elevated permissions.

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Security-Auditing4662An operation was performed on an object.
Security-Auditing4688A new process has been created.
PowerShell4103Payload Context: ContextInfo User Data: UserData.
PowerShell4104Creating Scriptblock text (MessageNumber of MessageTotal).

Authoring guide

Patterns shared across the 5 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized 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 (5 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
ScriptBlockText2match 1, eq 1Invoke-SauronEye, Get-FoxDump, Invoke-KrbRelay, *Get-DomainObjectAcl*, *get-objectacl*
AccessMaskDescription1eq 1Read Property
Payload1match 1Get-MachineAccountCreator, Invoke-SauronEye, Get-FoxDump
CommandLine1match 1Get-MachineAccountCreator, Invoke-SauronEye, Get-FoxDump
EventID1eq 14104

Top indicator values (574 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.

FieldKindValueRules (here)Corpus reach
AccessMaskDescriptioneqRead Property1
PayloadmatchInvoke-Tater1
PayloadmatchInvoke-ShadowSpray1
PayloadmatchInvoke-ADRecon1
PayloadmatchPort-Scan1
PayloadmatchGet-MachineAccountCreator1
PayloadmatchInvoke-Tokenvator1
PayloadmatchInvoke-Get-RBCD-Threaded1
PayloadmatchInvoke-MITM61
PayloadmatchInvoke-OfficeScrape1
PayloadmatchNew-HoneyHash1
PayloadmatchInvoke-ADSBackdoor1
PayloadmatchInvoke-Seatbelt1
PayloadmatchInvoke-AgentSmith1
PayloadmatchInvoke-BackdoorLNK1
PayloadmatchInvoke-WireTap1
PayloadmatchExport-ADRHTML1
PayloadmatchInvoke-Snaffler1
PayloadmatchShow-TargetScreen1
PayloadmatchInvoke-ARPScan1

Common exclusions (1 distinct)

Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). 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.

FieldKindValueRules excluding
SubjectUserSideqS-1-5-181

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.

Sigma 3 rules

Elastic 1 rule

Splunk 1 rule