Forge Web Credentials T1606

Tactic: Credential Access

Adversaries may forge credential materials that can be used to gain access to web applications or Internet services. Web applications and services (hosted in cloud SaaS environments or on-premise servers) often use session cookies, tokens, or other materials to authenticate and authorize user access.

Events covered

1 catalog event is tagged with this technique by at least one rule.

Authoring guide

Patterns shared across the 16 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 (47 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
EventType6starts_with 5, eq 3AppControl, ConnectionSuccess, login
file_name5eq 5ncrypt.dll, microsoftaccounttokenprovider.dll
parent_process_name4contains 2, ne 2microsoft.tri.sensor.exe, powershell, python
DestinationHostname3eq 3login.microsoftonline.com
GlobalPrevalence3lt 3250
IncomingTokenType3eq 3, ne 2none, primaryRefreshToken
type3eq 3DeviceInventoryId, IdentityProvider
AppDisplayName2eq 1, ne 1Azure Portal, SecondAppDisplayName
AppId2eq 2FociClientApplications
DestinationPort2eq 23389
HomeTenantId2eq 2ResourceTenantId
NodeLabel2eq 2device
OnboardingStatus2ne 2Onboarded
SecondAppDisplayName2in 2Microsoft Azure CLI, Microsoft Azure PowerShell, Copilot App, Office 365 Management
TimeDiff2ge 2, le 10, 1, 90

Top indicator values (94 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
EventTypestarts_with
AppControl
55
file_nameeq
ncrypt.dll
44
DestinationHostnameeq
login.microsoftonline.com
33
GlobalPrevalencelt
250
34
AppIdeq
FociClientApplications
22
DestinationPorteq
3389
211
EventTypeeq
ConnectionSuccess
29
HomeTenantIdeq
ResourceTenantId
22
IncomingTokenTypeeq
none
22
IncomingTokenTypene
none
22
NodeLabeleq
device
23
OnboardingStatusne
Onboarded
25
SecondAppDisplayNamein
Microsoft Azure CLI
22
SecondAppDisplayNamein
Microsoft Azure PowerShell
22
TpmActivatedne
true
24
TpmEnabledne
true
24
TpmSupportedne
true
24
event.categoryeq
authentication
231
parent_process_namecontains
powershell
22
parent_process_namecontains
python
22
parent_process_namene
microsoft.tri.sensor.exe
23
typeeq
DeviceInventoryId
25
ActivityTypecontains
credentialaccess:rds/anomalousbehavior.successfulbruteforce
12
ActivityTypecontains
credentialaccess:rds/anomalousbehavior.successfullogin
1
ActivityTypecontains
credentialaccess:rds/maliciousipcaller.failedlogin
1
ActivityTypecontains
credentialaccess:rds/maliciousipcaller.successfullogin
1
ActivityTypecontains
credentialaccess:rds/toripcaller.failedlogin
12
ActivityTypecontains
credentialaccess:rds/toripcaller.successfullogin
12
AppDisplayNameeq
Azure Portal
12
AppDisplayNamene
SecondAppDisplayName
1

Exclusions (2 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)

Sigma 1 rule

Elastic 2 rules

Kusto 13 rules