The following analytic utilizes EventCode 2282 which generates when a Module DLL could not be loaded due to a configuration problem. This typically occurs when a IIS module is installed but is failing to load. This typically results in thousands of events until the issue is resolved. Review the module that is failing and determine if it is legitimate or not.
- Type: Anomaly
Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2022-12-20
- Author: Michael Haag, Splunk
- ID: 40c2ba5b-dd6a-496b-9e6e-c9524d0be167
Kill Chain Phase
- CIS 10
1 2 3 4 5 `wineventlog_application` EventCode=2282 | stats count min(_time) as firstTime max(_time) as lastTime by EventCode dest Name ModuleDll | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_iis_components_module_failed_to_load_filter`
The SPL above uses the following Macros:
windows_iis_components_module_failed_to_load_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
List of fields required to use this analytic.
How To Implement
IIS must be installed and Application event logs must be collected in order to utilize this analytic.
Known False Positives
False positives will be present until all module failures are resolved or reviewed.
Associated Analytic Story
|25.0||50||50||A new IIS Module has been loaded and should be reviewed on $dest$.|
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.
source | version: 1