Cross-source coverage

T1505.004 / ATT&CK

Server Software Component: IIS Components

16 rules across 3 sources.

From MITRE ATT&CK 19.2

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: Get{Extension/Filter}Version, Http{Extension/Filter}Proc, and (optionally) Terminate{Extension/Filter}. IIS modules may also be installed to extend IIS web servers.

Adversaries may install malicious ISAPI extensions and filters to observe and/or modify traffic, execute commands on compromised machines, or proxy command and control traffic. ISAPI extensions and filters may have access to all IIS web requests and responses. For example, an adversary may abuse these mechanisms to modify HTTP responses in order to distribute malicious commands/content to previously comprised hosts.

Adversaries may also install malicious IIS modules to observe and/or modify traffic. IIS 7.0 introduced modules that provide the same unrestricted access to HTTP requests and responses as ISAPI extensions and filters. IIS modules can be written as a DLL that exports RegisterModule, or as a.NET application that interfaces with ASP.NET APIs to access IIS HTTP requests.

Tactics
Persistence
Platforms
Windows
Telemetry
WinEventLog:SecurityWinEventLog:SysmonWinEventLog:SystemWinEventLog:Microsoft-IIS-Configuration

How MITRE says to detect it DET0068

Detection Strategy for T1505.004 - Malicious IIS Components

Windows Analytic 0184

Adversary installs or modifies IIS components (ISAPI filters, extensions, or modules) using DLL files registered via configuration changes or administrative tools like AppCmd.exe. These components intercept or manipulate HTTP requests/responses for persistence or C2.

  • WinEventLog:Security EventCode=4663, 4670, 4656
  • WinEventLog:Sysmon EventCode=11
  • WinEventLog:Sysmon EventCode=7
  • WinEventLog:Sysmon EventCode=1
  • WinEventLog:System Changes to applicationhost.config or DLLs loaded by w3wp.exe
  • WinEventLog:Microsoft-IIS-Configuration Module or ISAPI filter registration events

splunk/security_content

10 rules
Detection Severity Format
Windows Disable Windows Event Logging Disable HTTP Logging Undefined SPL
Windows IIS Components Add New Module Undefined SPL
Windows IIS Components Get-WebGlobalModule Module Query Undefined SPL
Windows IIS Components Module Failed to Load Undefined SPL
Windows IIS Components New Module Added Undefined SPL
Windows PowerShell Add Module to Global Assembly Cache Undefined SPL
Windows PowerShell Disable HTTP Logging Undefined SPL
Windows PowerShell IIS Components WebGlobalModule Usage Undefined SPL
Windows Server Software Component GACUtil Install to GAC Undefined SPL
Windows Shell or Script Execution From IIS Directory Undefined SPL

SigmaHQ/sigma

5 rules
Detection Severity Format
HTTP Logging Disabled On IIS Server High Sigma
Suspicious IIS Module Registration High Sigma
ETW Logging/Processing Option Disabled On IIS Server Medium Sigma
New Module Module Added To IIS Server Medium Sigma
Previously Installed IIS Module Was Removed Low Sigma

socfortress/Wazuh-Rules

1 rule
Detection Severity Format
Sysmon - Event 7: Image loaded by · DLL Load in IIS (T1505.004) High Wazuh XML

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.