ATT&CK coverage › Technique

Server Software Component: IIS Components T1505.004

Adversaries may install malicious components that run on Internet Information Services (IIS) web servers to establish persistence. IIS provides several mechanisms to extend the functionality of the web servers. For example, Internet Server Application Programming Interface (ISAPI) extensions and filters can be installed to examine and/or modify incoming and outgoing IIS web requests. Extensions and filters are deployed as DLL files that export three functions: <code>Get{Extension/Filter}Version</code>, <code>Http{Extension/Filter}Proc</code>, and (optionally) <code>Terminate{Extension/Filter}</code>. IIS modules may also be installed to extend IIS web servers.

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Security-Auditing4688A new process has been created.
IIS-Configuration29Changes to 'Configuration' at 'ConfigPath' have successfully been committed.
IIS-W3SVC-WP2282
PowerShell4104Creating Scriptblock text (MessageNumber of MessageTotal).

Authoring guide

Patterns shared across the 9 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 (8 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
Configuration4match 2, ends_with 1, eq 1@logTargetW3C, /system.webServer/httpLogging/@dontLog, /system.webServer/modules/add, /system.webServer/modules/remove
EventID4eq 44104, 2282
Details3eq 2, match 1ETW, true, TokenCacheModule, AnonymousAuthenticationModule, DirectoryListingModule
ScriptBlockText3in 2, eq 1"*system.enterpriseservices.internal.publish*", "*httpLogging*", "*get-WebConfigurationProperty*", "*false*", "*Enable-WebGlobalModule*"
OldValue1match 1ETW
Image1ends_with 1\powershell.exe
CommandLine1match 1appcmd.exe add module, system.enterpriseservices.internal.publish, /I
ParentImage1ends_with 1\w3wp.exe

Top indicator values (38 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
EventIDeq41043108
Configurationends_with@logTargetW3C1
OldValuematchETW1
DetailsmatchETW1
Detailseqtrue1
Configurationeq/system.webServer/httpLogging/@dontLog1
Configurationmatch/system.webServer/modules/add1
DetailseqStaticFileModule1
DetailseqHttpLoggingModule1
DetailseqProtocolSupportModule1
DetailseqStaticCompressionModule1
DetailseqRequestFilteringModule1
DetailseqAnonymousAuthenticationModule1
DetailseqHttpCacheModule1
DetailseqDefaultDocumentModule1
DetailseqCustomErrorModule1
DetailseqTokenCacheModule1
DetailseqUriCacheModule1
DetailseqFileCacheModule1
DetailseqDirectoryListingModule1

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 5 rules

Splunk 4 rules